During financial year closing, a processing error in a critical financial system occurs. Senior management demands a change to be implemented in order to not further delay the business processes. Which sort of change is applied?

The situation describes a high-impact incident (a processing error in a critical financial system) occurring during a time-sensitive business period (financial year closing). The demand from senior management to implement a fix immediately to prevent further business disruption necessitates an emergency change. According to IT Service Management principles, emergency changes are those that must be implemented as soon as possible to resolve a high-impact incident. The assessment and authorization process for these changes is expedited to ensure a swift resolution, with full documentation and review often occurring after the change has been implemented.

A. Normal: Normal changes are subject to a full authorization and scheduling process, which is too slow for this urgent scenario.
B. Standard: Standard changes are pre-authorized, low-risk, and routine. This scenario involves an unexpected error, not a routine activity.
C. Exceptional: While the situation is exceptional, "Emergency Change" is the specific, formal term used in IT service management frameworks for this type of urgent change.

1. AXELOS. (2019). ITIL® Foundation, ITIL 4 Edition. TSO (The Stationery Office). In Section 5.2.4, "Change enablement," an emergency change is defined as a "change that must be implemented as soon as possible; for example, to resolve an incident or implement a security patch." This directly aligns with the scenario of fixing a critical error to prevent further business process delays. The description of normal and standard changes in the same section confirms they are inappropriate for this situation.