ISE548 Chap.12 Crisis Response and Business Continuity
Crisis Response and Business Continuity
Protect the service through disruption
The official syllabus links crisis response, escalation, prevention, business continuity, disaster recovery and information-security practice. This chapter begins with a critical customer outcome and maps the people, process, information, facility, supplier and technology dependencies required to sustain it.
It separates immediate response from recovery, defines observable escalation thresholds and uses exercises and audit to turn lessons into changed controls.
Minimum acceptable service is defined through capacity, accuracy, safety and maximum delay before technology is selected. Workarounds receive privacy, traceability and reconciliation controls, while recovery ends only when the service meets its stated condition.
Exercises test decisions and handovers as well as assets, and every finding is assigned and retested.
What this chapter covers
- 01
Critical services and interruption
- 02
Dependencies and single points
- 03
Response versus recovery
- 04
Escalation triggers and authority
- 05
Workarounds and reconciliation
- 06
Exercises, audit and learning
Worked example · free
Recover diagnostic scheduling
- 3Define critical service and dependencies.
- 3Design response and escalation.
- 4Set a recovery test.
Key terms
- Critical Service
- An outcome the organisation must sustain or restore within its defined interruption tolerance.
- Escalation Trigger
- An observable threshold that transfers attention or authority to a higher response level.
- Workaround
- A temporary alternative process used to sustain part of a service during disruption.
- Disaster Recovery
- The restoration of technology and information capabilities required by the continuity strategy.
Crisis Response and Business Continuity FAQ
How is response different from recovery?
Response stabilises people, operations and communication during the event. Recovery restores the required service level and reconciles temporary work. A workaround may be an excellent response and still be unsuitable as a prolonged recovery state.
Why should escalation use thresholds?
Observable conditions such as outage duration, affected customers, safety impact or backlog allow staff to act consistently under pressure. Serious or prolonged is not operational until the plan defines what it means and which authority changes.
Does restoring a server prove continuity success?
Only if the critical service is reliable again. Temporary transactions, customer communications, access rights and reconciled records may still block recovery. Test the customer outcome and the transition from workaround to normal operation.
What makes an escalation rule operational?
Write an observable condition, the role notified, the authority transferred and the communication duty. An outage exceeding the controlled queue capacity is stronger than serious disruption because staff can recognise it during pressure. Link the threshold to a decision the new authority can make, then exercise the timing and record whether the handover actually occurred.
How should a temporary workaround be controlled?
Define its maximum duration, capacity, identifiers, approvals, privacy safeguards and reconciliation process. Name the condition that stops the workaround or escalates to an alternative site. Test error detection and handover, not only whether staff can begin the process. Temporary methods often weaken traceability, so recovery includes merging and verifying their records before normal operation resumes.
Which exercise type should be used?
Choose the format that reaches the claimed capability. A tabletop explores decisions and communication; a technical test proves restoration components; a simulation examines coordination and workarounds. Set measurable objectives such as message time, activation time, backlog limit and reconciliation accuracy. A completed scenario is not automatically a successful test when the critical outcome was never measured.
How do lessons become changed controls?
Classify the finding by detection, decision, communication, workaround or recovery capability. Assign an owner, due condition and retest rather than closing it when a document is edited. Update the dependency map and risk assessment when a shared resource or failed assumption is discovered. Preserve timestamps and evidence so the next audit can compare claimed improvement with observed performance.
Who should authorise the return to normal service?
Name a role with authority to compare recovery evidence against the minimum service condition. The decision should review reconciliation, backlog, data integrity, safety, customer communication and any residual workaround rather than rely on one restored asset. Record the approval and exceptions.
A premature return can hide unfinished temporary transactions and create a second disruption after the technical system appears available.
Exam move
Choose one service and map its dependencies across people, process, information, facility, supplier and technology. Remove one dependency, then write the response trigger, temporary workaround, escalation authority and recovery proof. Add the record that will feed the lesson into the next risk assessment and exercise.
Working through Crisis Response and Business Continuity in ISE548? Sia is AskSia’s AI Management tutor — ask any ISE548 Crisis Response and Business Continuity question and get a clear, step-by-step explanation grounded in how ISE548 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.