Sign up free

Solution · Change enablement

Make changes safely, without turning every change into a meeting.

Most outages are caused by changes, not by accidents: a patch applied at noon, a setting changed by hand, a server rebooted without telling anyone. A good change process does not slow work down — it stops the avoidable outage.

By itserva Editorial Team Updated November 20, 2026 Reviewed by [REVIEWER NAME, CREDENTIAL]

Every change proposed in writing, with its risk and rollback plan.

Approvals from the right people, in proportion to the risk.

A record that shows exactly what changed, when, and why.

The problem

Why changes cause outages

Change goes wrong in predictable ways, and almost all of them are human: the change nobody recorded, the risk nobody assessed, the rollback nobody planned.

Changes made by hand, unrecorded

Someone fixes a setting directly on the server and tells nobody. Weeks later the setting causes an outage, and nobody can say who changed it, when, or why — because there is no record at all.

Risk assessed by gut feel

Every change is called low risk until it is not. Without a written assessment of impact and likelihood, the team approves what feels safe and learns the real risk from the outage.

The wrong approver

A change to the customer portal is approved by someone who has never used it. Approval only works when the people who understand the impact are the ones who say yes.

No way back

The change fails and there is no rollback plan, no backup taken, and no one who remembers the old setting. The team improvises a fix under pressure, which is how a small change becomes a long outage.

The process

Five steps, and the itserva page for each

Five steps, sized to the risk of the change.

  1. 01

    Propose the change

    Write down what will change, why, and when. A written proposal forces the first useful question — is this change needed at all — before any work starts.

    Change Request Template →

  2. 02

    Assess risk and impact

    Ask what depends on the thing being changed, and what breaks if the change goes wrong. The dependency map is the assessment; guessing is not.

    What is a CMDB? guide →

  3. 03

    Approve with the right people

    Match the approval to the risk: a small, reversible change needs one informed approver; a change to a critical service needs the people who own it. Record who is responsible, accountable, consulted and informed.

    RACI Matrix Template →

  4. 04

    Plan the rollback

    Before the change goes in, write down how to undo it: the old setting, the backup, and who can reverse it. A change without a way back is a gamble, and the rollback plan is what turns it back into a change.

    ITIL 4 Explained guide →

  5. 05

    Review after the change

    Once it is done, check that it worked, record what actually happened, and note anything unexpected. The review is where the next change gets safer — or where a quiet failure is caught early.

    Post-Incident Review Template →

What’s included

Tools, templates and guides for change enablement

Template

Change Request Template

Propose, assess and approve a change with its risk and rollback plan.

Template

RACI Matrix Template

Make it clear who is responsible, accountable, consulted and informed.

Guide

What is a CMDB?

What a configuration database stores, and how it shows what a change affects.

Guide

ITIL 4 Explained

The service value system, the four dimensions and the practices that matter most.

Product

Docs & Templates

Fill-in incident, change and SLA templates — download as Word or PDF, or save a draft.

Template

Root Cause Analysis Template

Work through the five whys when a change causes an incident.

Measure it

The four numbers worth tracking

Four numbers show whether changes are getting safer. A change process that nobody measures is a change process nobody can improve.

Changes per month

How many changes the team makes, split by service. A sudden rise is worth a look: it may be healthy progress, or it may be churn that the process is not catching.

Read ITIL 4 explained →

Failed changes

Changes that had to be rolled back or caused an incident. Each one deserves a review — not blame, but a look at what the assessment missed.

Use the root cause template →

Emergency changes

The share of changes made as emergencies, outside the normal process. A high share usually means the normal process is too slow, not that the team is reckless.

Use the change request template →

Change-related incidents

Incidents traced back to a change. When this number falls, the assessment step is working; when it rises, the assessment is where to look first.

Calculate your MTTR →

Frequently asked questions

Is change enablement the same as change management?

Nearly. ITIL 4 renamed change management to change enablement to stress that the practice should enable safe change, not block it. The work — propose, assess, approve, record — is the same.

Do small changes need approval?

They need a record and a rollback plan; the approval can be light. A change that is small, reversible and well understood does not need a committee — it needs one informed person to say yes.

What is an emergency change?

A change made outside the normal process because waiting would cause more harm — for example, fixing a security flaw or restoring a failed service. It still gets recorded and reviewed afterwards.

How do we assess the risk of a change?

Ask two questions: what breaks if this goes wrong, and how likely is that? The first comes from the dependency map; the second from how similar changes went before. Write both answers down.

Write the next change down before you make it.

Fill in the change request template for the next change on your list — risk, rollback and approver included. A free workspace saves it, so the record survives long after the change itself.

Create a free workspace