Change models
Quick answer
Normal, standard and emergency change, change models, risk assessment and the standard change template process.
Key takeaways
- Change models make change types configurable, not coded
- Standard changes are approved once as templates
- Emergency change needs retrospective review to stay honest
- A healthy standard change ratio shortens CAB
Change types
Normal change follows full assessment and CAB. Standard change is pre approved, low risk and repeatable. Emergency change is for restoring service and gets retrospective review. Getting the mix right is what makes CAB shorter.
Change models
A change model defines the states, transitions and approvals for a type of change. Models replaced hard coded workflow logic, so a new model is configuration rather than a workflow rewrite.
Standard change catalog
Standard changes come from templates that go through a proposal and approval cycle once.
- Propose the template, review it, publish it, then anyone can raise that change without CAB
- Review published templates periodically, retire the ones nobody uses
- Measure the ratio of standard to normal change, rising standard change usually means the process is maturing
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What defines the states and approvals for a change type?
- A. A workflow only
- B. A change model
- C. A UI policy
- D. An SLA
Show answer
B. A change model
Change models hold the state flow and approval policy.
A standard change template is approved
- A. Every time it is used
- B. Once, at publication
- C. By the CAB weekly
- D. Never
Show answer
B. Once, at publication
Pre approval at publication is what removes CAB from routine work.