Skip to content
ICM Holdings International
Search⌘ K
Index
Risk as a decision system

16 · Governance and application

Crisis response is part of ordinary governance

Prepare decision authority, communication, recovery and learning before an event

152 pages · Edition 2026-10-10

Governance and application

A response readiness framework

Crisis response is part of ordinary governance

Crisis response should be considered while the institution can still examine authority, resources and dependencies calmly. A risk system that records only prevention and residual likelihood can leave the event response undefined. The response need not be a large generic manual. It should identify the objective to preserve, the adverse state that activates the plan, the available capabilities and the person authorised to act. The institution should distinguish a designed response from a tested response and from one that can actually be executed at the required boundary.

The recurring shared-support mechanism makes this distinction important. The same failure that removes prevention and mitigation may also impair communications, decision access or a contingency route. A response that depends on the unavailable support can be least usable in the state where it is needed most. The model's unavailable-state consequence retains the gross loss because its supplied protective functions are absent. The engine does not calculate a separate crisis response. The plan should therefore identify whether it introduces a genuinely different capability or merely restates the same unsupported protection.

Response timing is an operational variable, not an implication of an annual mean. Detection, verification, authority, mobilisation, access and restoration can each consume time. Their sequence may be constrained by safety, staff or resource availability. A plan that lists tasks without dependencies can omit the true response bottleneck. The annual demonstrator does not calculate that sequence or the contribution loss accumulated during it. If duration determines the acceptance question, the institution should construct an appropriate timed response representation rather than infer recovery from the conditional severity scalar.

Evidence and scope

GAO schedule guidance addresses sequencing, schedule risk and the reliability of programme timing.

Evidence: Schedule Assessment Guide: Best Practices for Project Schedules

Evidence and scope

NASA systems-engineering guidance includes decision analysis within technical management.

Evidence: NASA Systems Engineering Handbook

The response should identify the minimum viable objective. Full restoration may be unnecessary for a temporary service obligation, while a partial capability may be inadequate for a safety or critical-customer condition. The plan should state which output must continue and which activities may be deferred. This avoids treating every contingency as a complete duplicate of normal operations. It also prevents a low-cost workaround from being credited with a service quality it cannot provide. A response objective should be specific enough that a test can reveal whether it is achieved.

Authority during the event needs a separate basis from authority for research. The fictional Chair's information mandate does not authorise an operator to shut down equipment, procure emergency services or execute an indemnity. A real institution may have predelegated operational powers, but this paper does not assume them. The response record should identify the actual delegation, its exposure limits and the escalation route if the authorised person is unavailable. A plan that depends on obtaining new committee approval after communications fail may be impractical even when its ordinary governance is sound.

Completed fictional response-capability inquiry

This is a designed inquiry, not a tested emergency plan or actual delegation.

Scroll for all columns. With the table focused, use the left and right arrow keys.

Completed fictional response-capability inquiry
Response propositionRequired objectCurrent statusAdverse route
Critical dispatch capabilityDefined temporary service objectiveObjective identified; capability unresolvedConsequence acceptance HOLD
Independent operating supportDependency map of alternative routeNot suppliedDo not credit nominal redundancy
Mobilisation and accessActual resources, permissions and sequenceNot suppliedNo restoration-time conclusion
Event authorityVerified operational delegation and backupNot representedInformation Chair has no invented emergency power
Relevant exerciseTest design with a failure consequenceNot executedNo claim of tested readiness
Return to normalRestoration and temporary-exposure ending ruleTo be establishedNo indefinite workaround acceptance
Illustrative calculation. Assumptions and sensitivity are published with the model.

The unavailable-support boundary yields residual annual expectation of USD 200.00 thousand under its supplied event and severity. This does not estimate the duration of an actual crisis. Its value for response design is to make the absent protective state explicit. The response inquiry must show what different capability would change that state or its consequence. Merely relabelling the unavailable safeguard as a contingency would not provide a distinct intervention.

The completed adverse route is a consequence-acceptance hold, not a forecast of response failure. The missing resource, access and delegation objects can be investigated within the existing information mandate. If they cannot be established by the gate, the Chair ends that mandate and preserves the hold. A later actual emergency would be governed by real operating authority, which this research record neither supplies nor restricts. The distinction prevents a committee planning example from being misread as instructions for an actual incident.

Response resources should be accessible in the adverse state. A spare part in an inaccessible facility, an alternative supplier affected by the same disruption or a team without the relevant permissions may not provide the capability described in a plan. The institution should examine mobilisation and access rather than count nominal resources. The analysis can distinguish evidence that a resource exists from evidence that it can be used at the needed time. Both are relevant, and the second may remain unresolved after the first is established.

Exercises should test decision paths as well as technical steps. A tabletop can reveal unclear authority, contradictory instructions or missing information without reproducing a physical event. A functional test can examine a particular capability. A full rehearsal can expose coordination and timing problems but can be costly or disruptive. The exercise should state which proposition it can challenge and which it cannot. Completing an exercise is not equivalent to accepting every part of the response. A failed or ambiguous result needs an owner and a consequence for the plan.

A response can introduce new risk. Rapid substitution may create quality, security or safety issues. Manual workarounds can increase error or reduce auditability. Emergency procurement can alter cost and counterparty exposure. These consequences should be considered in the response condition rather than treated as irrelevant because the original disruption is urgent. The institution may accept a temporary tradeoff within actual authority, but should preserve its boundary and restoration rule. A crisis does not erase the need to identify which objective is being protected and which exposure is being created.

Communications should support action and evidence preservation. The recipient needs to know what state has been detected, what is uncertain, what act is requested and who may decide. A general message that risk is high can cause unnecessary escalation without identifying a response. The plan should also preserve observations needed for later learning, while avoiding collection that interferes with immediate safety or service. The record can separate provisional operational judgments from later causal conclusions. This prevents an early explanation from hardening into an untested incident narrative.

The fictional major-consequence branch has no demonstrated response capability. The completed plan inquiry therefore remains held. The Operating Owner is asked to identify an alternative dispatch capability, its dependencies, access, resources and authority. The custodian records what can actually be reviewed. The Chair decides whether the bounded information mandate should continue or stop at its gate. The record does not claim that the alternative route exists or that a test has succeeded. It defines the missing proposition needed before consequence acceptance.

Return to normal operation by checking for displaced dependencies. A manual dispatch workaround may sustain the minimum service while depending on staff concentration and deferred reconciliation. Restoring the original support system does not automatically resolve those accumulated records or release the temporary staff obligation. Compare the entry condition, the service preserved, the unresolved work and the proposed exit condition. An exit test should confirm that ordinary operation can sustain the service and that the temporary route can be withdrawn safely. Otherwise the response has succeeded at immediate continuity but left another mechanism requiring treatment. Those outcomes deserve separate conclusions.

Test capability in the state that needs it

Link the response objective to its resources, access, dependency and actual authority. Keep designed, exercised and executable readiness separate.

  1. Map detection-to-restoration dependencies when timing is material.
  2. Challenge contingencies that rely on the same unavailable support.
  3. Define a return-to-normal and temporary-exposure ending condition.

Exercise the response path under the shared-support failure, rather than only during normal access. Ask whether the alternate instruction, contact route and decision authority remain reachable when the dependency is unavailable. An alternate resource that requires the failed authentication or communications path is nominal redundancy. A genuinely accessible route must also support the minimum service within the relevant response window. This test explains why the major-consequence branch needs more than a written contingency, while a modest reversible disruption may need only a simple local action. The exercise is a qualitative challenge to readiness; the annual loss engine supplies no restoration-time estimate.

Detailed plans can fail under unfamiliar events

A plan should preserve flexible authority, reliable information and adaptable capabilities rather than prescribe every possible action. The mechanism record can identify constraints and dependencies while leaving appropriately delegated judgment for unforeseen states.

No crisis duration or actual readiness is established

The app has no timed response, resource mobilisation or emergency authority model. The completed inquiry does not claim a tested plan, available alternative route or operational instruction.

Evidence at the point of use

Open a citation in the chapter to inspect its source, stated support and limits.

Find the next connection

Open the full search desk