Service management deep-dive · Lesson

Change management

Quick answer

Change Management (Change Enablement in ITIL 4) governs modifications to production so improvements happen without causing the next outage. It balances speed against risk by matching the level of oversight to the risk of the change.

Key takeaways

Three change types
Risk, approval and the CAB
Scheduling & conflict detection
The change lifecycle
Where it links

Change Management (Change Enablement in ITIL 4) governs modifications to production so improvements happen without causing the next outage. It balances speed against risk by matching the level of oversight to the risk of the change.

Three change types

Standard

Pre-approved, low-risk, repeatable (from a change template/catalog). No CAB, minimal friction.

Normal

Full assessment and approval, usually via CAB, before scheduling.

Emergency

Expedited path for urgent fixes (e.g. resolving a P1), with retrospective review.

Risk, approval and the CAB

Change requests (extending task) carry risk and impact, often scored by a risk assessment questionnaire or a risk-calculation rule. Higher risk routes to more approvals, culminating in the Change Advisory Board (CAB) for significant normal changes. Approvals are captured on the record, not in email, via the approval engine or a flow.

Scheduling & conflict detection

The change schedule and conflict detection check that a change doesn't collide with a blackout/maintenance window, or with another change on the same CI, before work begins. This is where CMDB accuracy pays off directly.

The change lifecycle

New --> Assess --> Authorize --> Scheduled --> Implement --> Review --> Closed
        (risk + approvals)      (conflict check)        (PIR: post-implementation review)

Where it links

Changes are the delivery vehicle for problem fixes and many incident resolutions; they reference the CIs they affect so impact is visible, and they increasingly integrate with DevOps pipelines for automated change creation.

Common mistakes

Routing everything through CAB, turning it into a rubber-stamp bottleneck.
Not maintaining standard change templates, so low-risk work drags.
Skipping CI linkage, losing conflict detection and impact.
No post-implementation review, so failed changes teach nothing.

Want to learn this properly?

Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.

See the course Ask a question

Check your understanding

Which change type is pre-approved and low-risk?
- A. Emergency
- B. Standard
- C. Normal
Show answer
B. Standard
Standard changes are pre-approved and repeatable.
Who typically approves a normal change?
- A. The caller
- B. The Change Advisory Board (CAB)
- C. Nobody
Show answer
B. The Change Advisory Board (CAB)
Normal changes are assessed and approved, often by the CAB.
An emergency change exists to:
- A. Add a new employee
- B. Expedite a fix for an outage
- C. Order laptops
Show answer
B. Expedite a fix for an outage
Emergency changes get expedited approval to resolve outages.

Frequently asked questions

What does the term Change management refer to in ServiceNow?

What is another point to note about Change management?

Change requests (extending task) carry risk and impact, often scored by a risk assessment questionnaire or a risk-calculation rule.

What else is worth knowing about Change management?

Higher risk routes to more approvals, culminating in the Change Advisory Board (CAB) for significant normal changes.

What tends to go wrong with Change management?

Routing everything through CAB, turning it into a rubber-stamp bottleneck. Not maintaining standard change templates, so low-risk work drags. Skipping CI linkage, losing conflict detection and impact.