Back to Glossary
ITSM
Emergency Change
Quick Definition
A change that must be implemented as soon as possible, usually to resolve an incident or to address an urgent security or business need, using an expedited authorisation path.
Detailed Explanation
Emergency changes bypass the usual scheduling because waiting would cause greater harm. They still need assessment and authorisation, usually by a smaller group with delegated authority, and a fuller review afterwards. Overuse is a warning sign that planning or testing is weak.
Example: A critical security patch is released and must be applied to production within hours. A small emergency group assesses the risk, approves the change and records it. A post-implementation review checks that it worked and whether the process can be improved.
How it differs from related terms: Standard change: pre-authorised, low-risk, repeatable. Normal change: assessed and scheduled through the normal path. Emergency change: expedited because of urgency.
Related Terms
Relevant Frameworks
ITIL