Change Management
About 25% of the CIS-ITSM exam — see all 6 domains.
Purpose and the three change types
Change Management controls the lifecycle of changes to the IT environment to deliver them with the least risk and disruption. Change records live on the change_request table (extends task). The exam leans heavily on distinguishing the three baseline change types:
- Standard change: pre-authorized, low-risk, repeatable, with a proven implementation procedure. It is requested from the Standard Change Catalog as a pre-approved template, so it skips CAB and per-instance approval. Promoting recurring, low-risk normal changes into standard change templates is the recommended efficiency play.
- Normal change: anything not standard or emergency. It requires risk assessment, planning, approvals, and (when applicable) CAB review before implementation. This is the full workflow path.
- Emergency change: must be implemented fast to resolve a major incident, restore service, or close a critical security gap. Approval is expedited (an emergency CAB / e-CAB), and review may happen after the fact.
Change models and state flow
Baseline change uses change models (state-machine driven flows) rather than legacy workflows. The normal change moves through stages such as New / Assess → Authorize → Scheduled → Implement → Review → Closed, with Canceled available. Approvals are gated by state: a change typically cannot move to Implement until it has been authorized and scheduled.
Risk and the Change Risk assessment
Risk is central. ServiceNow offers two complementary mechanisms:
- Change Risk Calculator / risk conditions: enabled by default; uses predefined conditions and properties to compute risk automatically.
- Change Management - Risk Assessment plugin: lets you build a risk assessment questionnaire; the user's answers feed a scoring formula that sets the change's overall Risk (and often Impact). Newer releases also expose Change Risk via Predictive Intelligence.
Risk and impact together inform which approval path and CAB scrutiny a change needs.
CAB
The Change Advisory Board (CAB) is the group of IT decision-makers and technical experts who review and authorize changes (typically normal changes above a risk threshold). ServiceNow provides the CAB Workbench to schedule CAB meetings, build agendas from changes in scope, run the meeting, and record decisions. Standard changes do not go to CAB (already pre-approved); emergency changes use an expedited/emergency CAB.
Schedules, conflicts, and blackouts
Change scheduling uses maintenance windows, blackout windows, and change conflict detection, which flags a change scheduled at the same time as another change on the same CI, during a blackout window, or outside the CI's maintenance window (maintenance windows are when changes should happen). In the default Basic mode it checks the change's Configuration item field; Advanced mode also checks Affected CIs. Conflict detection warns and records conflicts; it does not block implementation. CIs are attached so impact and conflicts can be assessed against the CMDB.
Exam focus
- Standard (pre-approved, from catalog, no CAB) vs. Normal (full risk + approval + CAB) vs. Emergency (expedited).
change_requestextendstask; change models drive state.- Two risk paths: default Change Risk Calculator vs. Risk Assessment plugin questionnaire.
- CAB Workbench schedules and runs CAB; standard changes bypass it.
- Conflict detection and blackout/maintenance windows.
Sample questions from this domain
Three of the 75 in this domain, with the reasoning. The full set is in the question bank.
What is the primary purpose of Change Management in ServiceNow ITSM?
- A. To maintain an accurate record of configuration items and the relationships between them
- B. To control the lifecycle of changes to IT services and infrastructure, minimizing risk and disruption ✓
- C. To restore normal service operation as quickly as possible after an unplanned interruption
- D. To identify and permanently remove the underlying root causes of recurring incidents across IT services
Why: Change Management controls the lifecycle of changes to IT services and infrastructure so beneficial changes are made with minimal risk and disruption. Keeping an accurate record of CIs and their relationships is the job of the CMDB, restoring service after an unplanned interruption is Incident Management, and removing the root causes of recurring incidents is Problem Management.
Which baseline change type is pre-authorized, low-risk, and follows a documented, repeatable procedure?
- A. Emergency
- B. Major
- C. Normal
- D. Standard ✓
Why: Standard changes are pre-authorized, low-risk, repeatable changes that follow a documented procedure and are requested from an approved standard change template. Emergency changes address urgent issues through an expedited approval path, Normal changes require full assessment and authorization, and Major is not a baseline change type.
Which baseline change type is used to address urgent situations, such as resolving a major incident, and typically uses an expedited approval path?
- A. Emergency ✓
- B. Standard
- C. Normal
- D. Expedited
Why: Emergency changes handle urgent situations such as resolving a major incident and use an expedited approval path, often an emergency CAB (eCAB). Standard changes are pre-authorized routine changes, Normal changes follow the full Assess and Authorize flow, and Expedited describes the approval path but is not a baseline change type.