A regional disruption may simultaneously affect a manufacturing plant, a remote service team, shared IT and the customer contact center. Local responders know the immediate hazards, but enterprise executives control scarce resources and company-wide commitments. Without an agreed coordination model, sites can issue conflicting updates, exhaust the same specialist team or wait for permission while an incident escalates. Effective continuity governance defines who commands what, how facts travel, which decisions require escalation and how independent functions cooperate without losing accountability.

Q1Distinguish local incident control from enterprise direction
Local leaders should normally have authority to protect people, secure equipment and activate site-specific immediate actions within approved boundaries. Enterprise crisis or continuity teams coordinate cross-site priorities, scarce resources, strategic decisions and external implications. Define the interface rather than creating two competing command structures. The local manager must not wait for an executive call before taking required emergency action.
ISO 22320:2018 offers incident-management guidance on roles, information and cooperation. Its principles can inform the interface, but organizations must tailor command rights to their operations, legal duties and emergency authorities. Record where public emergency services have authority and ensure internal arrangements support rather than obstruct them.
At a local facility, emergency responders may be required to isolate equipment immediately. A central crisis group should not introduce a second authorization barrier for that protective action. Instead, establish a concise reporting route into the enterprise picture. Define what the site retains authority to decide and which cross-site consequences require central direction. This reduces delay while keeping executives informed.
Technical context: ISO 22320:2018 — Guidelines for incident management is one verified source for the concepts discussed here.
Q2Assign roles by decision, not by job title alone
Define an incident coordinator, safety lead, operations recovery lead, ICT lead, communications coordinator, external liaison and record keeper as needed. For each role specify what it may authorize, what information it owns and what triggers escalation. Avoid generic RACI charts that mark several people as accountable for a single urgent decision. A named deputy should be available when an event occurs outside office hours.
Role descriptions should distinguish incident response from sustained business continuity and strategic crisis management. A technician may direct recovery work without deciding whether the company will close a site or amend customer commitments. The executive sponsor needs reliable technical input; the technician needs a clear work authorization route.
Role documents should be tested through actual conflicting decisions. A local manager might approve a temporary work location, but only security can authorize certain emergency data access; a company spokesperson may make public statements, while the regulator requires a specific licensed officer. Show these interfaces explicitly. A long contact list is not a substitute for decision rights.
Q3Build one operating picture with known uncertainty
Agree a minimum incident status record covering confirmed facts, unknowns, affected services, safety condition, restoration constraints, decisions, owners and next update. Data should have an observation time and source. If one site reports power restored while its network remains unavailable, the distinction matters to recovery choices. Do not convert an unverified estimate into an official fact merely because it appears on a dashboard.
Use a short briefing cadence proportionate to the event, with immediate escalation for material changes. The record keeper should protect decision history while avoiding duplicate reporting demands on responders. The objective is shared understanding, not an elaborate presentation that takes specialists away from their work.
A status report should distinguish verified observations, estimates and questions requiring answers. For example, “site accessible” is not equivalent to “safe production capacity restored.” Record the source of each material assertion and the next validation event. An uncertain report delivered on time is often more useful than a polished but misleading dashboard created after the decision window closes.
Q4Control cross-site dependencies and resource conflicts
Identify personnel, backup power, communications, spare equipment and contracted support shared by several locations. When two sites request the same specialist, a designated enterprise authority must decide the sequence based on consequences and feasible alternatives. The rationale and new expected outcomes should be communicated to all affected teams. Otherwise each location may believe it has an exclusive recovery commitment.
Include supply-chain and outsourced service dependencies. Local recovery may require a corporate purchase approval, a central IT administrator or an external contractor that is also affected. Test whether the coordination structure can release resources rapidly and legally, including emergency procurement and appropriate financial controls.
Multi-site competition needs a transparent method. If a specialist can restore only one site at a time, use priority-service impact, safety, prerequisites and available temporary alternatives to allocate the resource. Explain the sequence to the site that must wait. Without this feedback, the second site may pursue an incompatible workaround or send duplicated requests to the same supplier.

Q5Coordinate external communication through factual ownership
Customers, regulators, employees, suppliers, insurers and nearby communities may require different notifications. Communications should obtain confirmed operational facts from the responsible site and legal or technical interpretation from competent specialists. Establish who approves each audience-specific message. Do not allow a reassuring enterprise statement to contradict the local safety response.
Define a method to update messages when the situation changes. Where regulatory notices are legally prescribed, follow the applicable authority’s channel and deadline. A general crisis media release is not a substitute for those communications. Preserve the approved message, distribution list and issue time to support later review.
Communications teams should obtain operational facts from site owners while checking whether legal or contractual notice conditions are triggered. A single press statement cannot cover employee welfare instructions, customer service limits and regulator submissions. Maintain approved versions but allow frontline safety alerts to move rapidly through a delegated route. Later corrections should be traceable.
Q6Exercise escalation and shift handover
Use a multi-site scenario that includes contradictory reports and two requests for the same recovery resource. Have local teams make immediate protective decisions, then escalate a strategic choice with a short situation report. Test an out-of-hours deputy and a shift handover. Observe whether decision rights remain understandable when the original incident coordinator becomes unavailable.
ISO 22361:2022 provides guidance on strategic crisis management, while ISO 22320 addresses operational incident management. The division is useful: a crisis team should govern organization-wide consequence without taking over every local technical decision. Record gaps in shared situational awareness and clarify them in the next exercise.
Include deliberately conflicting reports in the exercise: one site claims restoration while a second reports a shared service still down. Force participants to identify the source of the contradiction and decide what can be communicated. Change incident leadership between shifts. The purpose is to expose decision-handovers and shared information weaknesses without inventing a perfect crisis story.
| Decision domain | Owner or objective | Observable evidence |
|---|---|---|
| Local action | Site incident lead | Protect people and secure operations |
| Cross-site choice | Enterprise coordinator | Shared resource allocation log |
| Public/regulator notice | Authorized liaison | Approved accurate transmission |
| Handover | Process and recovery owners | Accepted normal service and open actions |
Q7Return from coordinated response without losing lessons
Set criteria for scaling down the central coordination team and handing ownership back to normal process managers. Do not dissolve incident governance while customer notices, personnel welfare, backlog corrections or evidence preservation remain unfinished. Assign action owners, retain the decision log and verify the operational acceptance of recovered services.
Compare actual roles with the approved structure. Repeated escalation delays, conflicting messages or unowned dependencies indicate a design problem rather than merely poor individual performance. Feed the lessons into site plans, enterprise recovery priorities, training and supplier arrangements.
Stand-down requires an accountable transfer of unresolved work. Customer compensation, regulatory questions, equipment checks and staff welfare may continue after the emergency team closes. Use a handover record with each open issue, accepted owner and next due action. Reviewing these records often reveals problems that ordinary technical recovery metrics would never show.
Practical Review Questions
- Who may make immediate site safety decisions?
- Which decisions require enterprise escalation?
- How are uncertain facts identified in briefings?
- Can deputies coordinate a multi-site night-shift event?
Run a two-site coordination exercise
Give one site a physical safety incident and another a critical IT interruption. Require local leaders to take immediate protective actions, then ask an enterprise coordinator to reconcile resource requests. Introduce a conflicting status report and an unavailable central decision maker. Observe whether deputies know their authority and whether the common operating picture distinguishes facts from estimates. Keep the exercise technically safe and the decision log concise.
After the exercise, compare the central briefing, local actions and customer communications. Record gaps such as conflicting ownership, delayed approvals and inconsistent restoration claims. Assign handovers for outstanding welfare, regulatory and service issues before standing down the central team. The next test should prove these interfaces rather than merely repeat the same incident briefing format.
Closing Perspective
Good coordination gives local responders speed and enterprise management coherence. Decision rights, shared facts, cross-site resource allocation and honest communications must function together rather than as separate organizational charts.
References & Further Reading
Official ISO publications informing the continuity method discussed above. Guidance publications provide recommendations; ISO 22301 contains BCMS requirements. The organization must validate any sector-specific legal duties separately.