UnixTime

Research Note

Emergency Change Record

  • Updated Jun 17, 2026
  • Read 01 min read
  • Status reviewed

Use this record when an urgent operational or security situation requires a change outside the normal approval cycle.

On this page

When to use this

Use this record when an urgent operational or security situation requires a change outside the normal approval cycle.

Emergency change details

Field Value
Emergency change ID TBD
Triggering incident/problem TBD
System/service TBD
Risk of delaying change TBD
Authorizing person TBD
Implementer TBD
Implementation time TBD
Testing possible before change TBD
Rollback/failback TBD
Result TBD
Post-implementation review date TBD
Retrospective approval TBD

Review checks

  • Emergency rationale was valid.
  • Activity was logged.
  • Security impact was reviewed afterward.
  • Documentation/configuration records were updated.
  • Further corrective action was recorded.
  • Template
  • Iso27001
  • Change management
  • Emergency change

Note Metadata

Aliases: Emergency Change Log

Source: 90 Templates/Emergency Change Record.md