IT Change Management Process Flowchart
A change request flow with standard changes, change advisory board review, a scheduled change window, testing and rollback.
4 teams14 steps3 decisionsFree download
Free to download. Edit it in Flow Studio to change the teams and steps, ask AI for changes, or export to PowerPoint, Word or draw.io.
Step by step
The same flow as a numbered list, ready for an SOP, a BRD or a ticket.
| # | Step | Who | Next |
|---|---|---|---|
| 1 | Change neededStartRequester · step 2 | Requester | step 2 |
| 2 | Raise a change requestDocumentRequester · step 3 | Requester | step 3 |
| 3 | Standard low-risk change?DecisionChange manager · Yes: step 7, No: step 4 | Change manager | Yes: step 7, No: step 4 |
| 4 | Review risk and rollbackChange board · step 5 | Change board | step 5 |
| 5 | Approved?DecisionChange board · Yes: step 7, No: step 6 | Change board | Yes: step 7, No: step 6 |
| 6 | Rework the planRequester · Resubmit: step 2 | Requester | Resubmit: step 2 |
| 7 | Schedule a change windowChange manager · step 8 | Change manager | step 8 |
| 8 | Change windowWaitEngineer · step 9 | Engineer | step 9 |
| 9 | Make the change and testEngineer · step 10 | Engineer | step 10 |
| 10 | Tests pass?DecisionEngineer · Yes: step 11, No: step 12 | Engineer | Yes: step 11, No: step 12 |
| 11 | Close and recordDocumentChange manager · step 13 | Change manager | step 13 |
| 12 | Roll backEngineer · step 14 | Engineer | step 14 |
| 13 | Change completeEndChange manager · Done | Change manager | Done |
| 14 | Change rolled backEndEngineer · Done | Engineer | Done |
When to use it
Use it to make production changes safe without slowing down routine work, and to show auditors how changes are approved.
Who's involved
- Requester3
- Change manager4
- Change board2
- Engineer5
Yours works differently?
Describe your own process in a few sentences and Flow Studio draws it, with your teams and your rules.
Describe your processarrow_forwardHow to get it right
- 1Keep a list of standard, low-risk changes that skip the board. It's what keeps the process fast.
- 2Ask for a rollback plan on every change request, not just the risky ones.
- 3Test right after the change, inside the window, while the people who made it are still there.
- 4Close each change with a short record of what was done and whether it worked.
Questions
What is a change advisory board (CAB)?
A small group that reviews higher-risk changes, checks the risk and rollback plan and approves a time to make the change.
What is a standard change?
A routine, low-risk change that has been done safely many times, such as a certificate renewal. It's pre-approved and doesn't need the board.
More process flow templates
- Incident managementAn incident response flow from alert to postmortem: triage, severity, incident lead, mitigation, status updates and closing the loop.
- Bug triageHow a bug report is checked for duplicates, reproduced, prioritised, fixed in a hotfix or the next sprint, and closed with the reporter told.
- Access requestHow an employee gets access to a system: manager approval, data owner approval for sensitive data, least-privilege access and regular access reviews.
- Software releaseA release process from merged code to everyone: staging, regression tests, go or no-go, a staged rollout with monitoring, rollback and release notes.