Normal vs Emergency Change Management
Emergency changes can move faster, but they should not become undocumented shortcuts around governance.
Normal change
A normal change usually follows planned request, risk assessment, approval, testing, implementation, and documentation steps.
Emergency change
An emergency change uses an accelerated path because delay creates unacceptable business or security risk.
Compensating governance
Emergency procedures still require authorization, logging, controlled implementation, and prompt retrospective review when normal preimplementation steps are reduced.
Exam strategy
Emergency does not mean uncontrolled; it means expedited with compensating oversight.
The takeaway
Emergency change management accelerates the process but still requires authorization, traceability, and postimplementation review.
Related Summit resources
FAQ
What is the key distinction?
Emergency change management accelerates the process but still requires authorization, traceability, and postimplementation review.
What should I identify first?
Emergency changes can move faster, but they should not become undocumented shortcuts around governance.
Why is this tested?
Understand how organizations maintain approval, testing, segregation, documentation, and retrospective review when changes must be made quickly.