The Emergency Change Route provides a controlled mechanism for implementing urgent changes where waiting for the standard delivery cycle would create unacceptable business risk.
Emergency changes are exceptions to the normal change process. They should be used sparingly, assessed quickly, and managed with discipline.
Urgency alone does not automatically qualify a request as an emergency.
Purpose
The Emergency Change Route exists to allow rapid action where immediate intervention is necessary to protect:
- Business continuity
- Critical reporting capability
- Financial or regulatory deadlines
- Data integrity
- Security or access control
- Operational decision-making capability
It is designed to restore stability, reduce impact, and protect service confidence.
What Qualifies as an Emergency Change
Examples may include:
- Critical report unavailable during key business activity
- Incorrect figures materially affecting decisions or submissions
- Failed refresh impacting period-end or board reporting
- Security or access issue requiring immediate correction
- Data source failure requiring urgent reroute
- High-impact production defect with no practical workaround
- Major scheduled event at risk without intervention
What Does Not Normally Qualify
The following would not normally be considered emergencies:
- Late requests caused by missed planning windows
- Nice-to-have enhancements
- Cosmetic improvements
- Convenience requests
- Minor defects with available workaround
- Changes requested without sufficient notice
- Requests that are urgent only to one individual without wider impact
Urgent demand and emergency risk are not the same thing.
Standard Emergency Process
Where an emergency route is required, the following minimum steps should apply.
| Step | Action |
|---|---|
| 1 | Confirm business impact and urgency |
| 2 | Identify affected service or asset |
| 3 | Assess safest available remedy |
| 4 | Obtain rapid approval from accountable owner |
| 5 | Implement controlled fix |
| 6 | Validate outcome |
| 7 | Communicate completion |
| 8 | Complete post-change review |
Minimum Information Required
Requests should include:
- What is failing or at risk
- Business impact now
- Deadline or critical timing
- Affected users or functions
- Known workaround (if any)
- Preferred contact for decisions
- Evidence such as screenshot or error message
Approval Principle
Emergency changes should be approved by an appropriate accountable owner based on impact.
Examples may include:
- Service owner
- Product owner
- Business lead
- Programme lead
- Senior technical lead (for immediate containment)
Approval should be proportionate and recorded.
Delivery Expectations
Emergency delivery aims to restore service safely, not necessarily provide the perfect long-term solution.
Temporary containment may be preferable to rushed redesign.
Examples:
- Revert to previous version
- Restore last known good dataset
- Apply temporary patch
- Redirect to alternate source
- Pause failing process pending permanent fix
Communication Expectations
Where user impact exists, communication should be prompt and factual.
Updates should cover:
- Nature of issue
- Current impact
- Expected next update
- Resolution status
- Any required user action
Post-Implementation Review
Every emergency change should be reviewed afterwards.
The review should consider:
- Root cause
- Why emergency route was required
- Whether planning could have prevented it
- Permanent corrective action needed
- Any lessons for future change management
Emergency fixes should not become permanent technical debt by default.
Governance Note
Repeated emergency changes in the same area may indicate a wider process, quality, capacity, or architecture issue requiring management attention.
Related Guidance
See also:
- Change Management
- How to Raise a Change
- Change Levels Matrix
- Recent Changes
- Breaking Changes Register
- Change & Release Calendar
Final Note
Emergency change is not the fast lane for normal work. It is the controlled route for exceptional situations where delay creates greater risk than change itself.