Standard Change Request process diagram
This is a worked example. Wavelength built the diagram below from the description on this page. Nobody drew it by hand.
What was said
An engineer files a change request in ServiceNow. The system runs a risk check. If the risk is high, the change advisory board reviews and approves it. If the risk is low, it is auto-approved. The change is scheduled for a maintenance window. The engineer deploys the change. After deployment, the engineer verifies the change. The change is closed in ServiceNow.
The diagram
What is in this flow
- Systems: Risk Check.
- People and teams: Engineer, CAB.
- Decisions: High Risk?.
- Size: 11 steps and 11 connections.
Steps
- Engineer
- File Change in ServiceNow (Engineer)
- Risk Check
- High Risk?
- CAB
- CAB Review (CAB)
- Schedule Maintenance Window (Engineer)
- Deploy Change (Engineer)
- Verify Change (Engineer)
- Close in ServiceNow (Engineer)
- Change Complete
Mermaid code
Copy this into any Markdown file, GitHub README, or Mermaid Live to render the same flow.
flowchart TD
n1(Engineer)
n2([File Change in ServiceNow])
n3{{Risk Check}}
n4{High Risk?}
n5(CAB)
n6[CAB Review]
n7[Schedule Maintenance Window]
n8[Deploy Change]
n9[Verify Change]
n10[Close in ServiceNow]
n11([Change Complete])
n1 -->|files| n2
n2 -->|runs| n3
n3 -->|checks| n4
n4 -->|Yes| n5
n4 -->|No| n7
n5 -->|reviews| n6
n6 -->|approved| n7
n7 -->|scheduled| n8
n8 -->|deploys| n9
n9 -->|verifies| n10
n10 -->|closes| n11
Map your own process
Describe your version out loud, or paste the transcript of a call. Wavelength draws the flow as you talk, and you can edit it by voice, by prompt, or by hand.
Every new account starts with 7 days of Pro. No card needed.
This example is part of our guide for IT runbooks.