ServiceNow Change Management

Change Management controls how modifications to IT systems get planned, approved, and implemented. Without a structured process, a well-intentioned update can accidentally cause a major outage. ServiceNow's Change Management module enforces a controlled workflow that reduces risk while still allowing IT teams to move quickly.

What Is a Change?

A change is any addition, modification, or removal of anything that could affect IT services. Changes include:

• Upgrading a server's operating system
• Installing a new software application
• Modifying a firewall rule
• Adding a new server to the network
• Changing a database configuration

The Three Types of Change

Standard Change

A standard change is a pre-approved, low-risk change that follows a tested and documented procedure. Because it has been approved in advance, individual standard changes do not need a new approval each time. Restarting a routine service during a maintenance window is a standard change.

Normal Change

A normal change requires full review and approval before implementation. It goes through the Change Advisory Board (CAB) — a group of stakeholders who evaluate its risk, test plan, and implementation schedule. Most medium-to-high risk changes are normal changes.

Emergency Change

An emergency change implements a fix as fast as possible to restore a broken service. Emergency changes happen outside the normal schedule. They still require approval — but from a smaller Emergency Change Advisory Board (ECAB) that can convene quickly. Full documentation happens after the fact.

Change Type Comparison:
──────────────────────────────────────────────────────────
Type       │ Risk    │ Approval    │ Pre-Approved │ Speed
──────────────────────────────────────────────────────────
Standard   │ Low     │ Pre-defined │ Yes          │ Fast
Normal     │ Med/High│ CAB         │ No           │ Planned
Emergency  │ Any     │ ECAB        │ No           │ Immediate
──────────────────────────────────────────────────────────

The Normal Change Lifecycle

Change Request submitted (CHG number assigned)
       │
       ▼
Assess → Risk, impact, implementation plan documented
       │
       ▼
Authorize → Manager or CAB reviews and approves/rejects
       │
       ▼
Scheduled → Implementation window set in the change calendar
       │
       ▼
Implement → Team makes the change during the scheduled window
       │
       ▼
Review → Did the change succeed? Any issues?
       │
       ▼
Closed → Change record completed and archived

The Change Advisory Board (CAB)

The CAB is a committee of IT leaders, architects, and business representatives who review and approve high-risk changes. In ServiceNow, the CAB meeting is managed digitally. Change managers can schedule CAB discussions, assign reviewers, collect votes, and record decisions — all within the platform.

CAB Workbench

ServiceNow's CAB Workbench is a dedicated interface for CAB managers. It shows all changes scheduled for the upcoming CAB meeting, their risk scores, implementation plans, and reviewer comments. CAB members vote to approve or reject each change from within the workbench.

Risk and Conflict Scoring

ServiceNow calculates a risk score for each change based on answers to a risk assessment questionnaire. The higher the risk score, the more scrutiny the change receives. ServiceNow also checks for change conflicts — situations where two changes affect the same CI (configuration item) during the same time window. A conflict alert warns the change manager before implementation begins.

Change Conflict Example:
─────────────────────────────────────────────────────────
CHG000100: Patch Database Server A  → Saturday 02:00 - 04:00
CHG000101: Restart Database Server A → Saturday 03:00 - 03:30

⚠ CONFLICT: Both changes affect the same CI (Database Server A)
             and overlap in time. Review before proceeding.
─────────────────────────────────────────────────────────

The Implementation Plan

Every change must include an implementation plan that answers:

• What will be done? Step-by-step instructions for the implementer.
• Who will do it? The assigned team and contact person.
• When will it happen? The scheduled start and end time.
• What is the test plan? How will the team confirm the change worked?
• What is the rollback plan? Exact steps to undo the change if something goes wrong.

The Rollback Plan

The rollback plan is critical. If a change causes an unexpected problem, the team must be able to reverse it quickly — ideally within minutes. ServiceNow requires a documented rollback plan before a change can be approved. This discipline saves organizations from prolonged outages caused by failed changes.

Change vs. Release Management

Individual changes fix one thing at a time. Release Management bundles multiple related changes into a single coordinated release. For example, deploying a new version of a business application might involve 15 individual changes — database updates, code deployments, server configuration changes. Release Management ensures all 15 changes deploy in the right order, at the right time, with one overarching approval.