A storm front crosses a regional distribution network at 05:20 on a Tuesday. Inside forty minutes three substations are off supply, a flooded access road has cut one of them off, and a contractor crew is parked at a fourth site waiting on a decision nobody has made. Each affected site has a competent engineer running its own response. None of the three can see the other two.
Multi-site incident command works when every affected site keeps its own commander and one named person above them holds the priorities, the scarce resources and the single version of what is happening across the network.
Multi-site incident command means each affected location runs its own response under a named commander, while one person above them sets priorities between sites, allocates scarce crews, and owns the single operational picture. Without that upper layer, sites compete for the same resources and leadership hears three different stories.
What Is Multi-Site Incident Command?
Multi-site incident command is the arrangement that decides who directs the response at each affected location, and who directs the response across all of them at once. One commander per site handles what happens on the ground there. A layer above that sets priorities between sites, moves crews and plant, and owns the single account of the incident.
The shape isn’t new, or unique to energy. FEMA’s National Incident Management System doctrine puts it in one line: an Area Command oversees management of multiple incidents, while emergency operations centres coordinate support. Utilities rarely use that vocabulary. They say duty manager, gold and silver, or the storm desk. The structure underneath is the same: site command for tactics, a level above for priorities.
The distinction that does the work: tactical decisions belong at the site, and allocation decisions can’t, because no site can see the others.
Why Does Multi-Site Incident Command Break Down In Energy Networks?
Multi-site incident command breaks down because each site is individually well run. Competent engineers make sound local decisions, and nothing in any one of them is wrong. The failure shows up between sites. Two locations request the same crew, the restoration order gets set twice by different people, and leadership receives three accounts that don’t reconcile.
Energy networks make this harder than most. Incidents spread across power stations, substations, pipelines and operational facilities at once, and the teams involved sit in different reporting lines: operations, engineering, health and safety, environmental, security and leadership. An engineer at a flooded substation has no reason to know the crew they asked for went somewhere with more vulnerable customers on supply.
Who Holds Command At Each Level Of A Multi-Site Incident?
Four roles hold command during a multi-site energy incident, each with a boundary it shouldn’t cross. Site command owns safety and tactics at a location. Network command owns priorities between locations. The control room owns the network’s electrical state. Strategic liaison owns the outside world. Written down in advance they fit together. Left undefined, they overlap at 05:20.
The fourth role exists because the network has duties outside the company. Part 3 of Schedule 1 to the UK’s Civil Contingencies Act 2004 lists holders of electricity transmission, distribution, system operator and interconnector licences as Category 2 responders, alongside gas licence holders under sections 7, 7ZA and 7AA of the Gas Act 1986. Section 2(5) allows regulations to require those bodies to co-operate with, and provide information to, the Category 1 responders running the wider emergency. That’s a conversation the network has to have with one voice. This is orientation, not legal advice, and operators outside the UK should check what their own regulator expects.
The table sets out what each level owns during a multi-site energy incident, and the decision each level should hand upwards or downwards instead of taking itself.
| Level | Who Typically Holds It | What It Owns | What It Should Not Do |
|---|---|---|---|
| Site incident command | The senior competent person at that location | Safety of everyone on site, tactical work, local isolation and make-safe | Set priorities against other sites, or speak to the regulator |
| Network or area command | The duty network operations manager | Priorities across sites, allocation of crews and plant, the single operational picture | Direct tactics at an individual site |
| Control room | The duty control engineer | Switching, telemetry, network state and the restoration sequence | Own welfare, rostering or communications for field staff |
| Strategic and external liaison | The on-call director | Regulatory notification, mutual aid requests, customer and media messaging | Change the restoration order without network command |
The fourth column is the one that gets skipped. And a site commander who takes an allocation decision isn’t overreaching on purpose. They’re filling a gap nobody filled in advance.
How Do You Decide Which Site Gets The Crew First?
Network command decides which site gets the crew first, against criteria agreed before the incident instead of argued during it. Every site will make an honest case for being the priority, and every case will be true from where it’s standing. Written criteria turn that into a decision one person can take quickly and defend afterwards.
Most energy operators weigh some version of the following, roughly in this order:
- Risk to life, on site or in the community, including any hazard that’s still live
- Customers on the priority services or vulnerable customer register who depend on supply
- Environmental containment, where a leak or spill is spreading
- Customers restored per crew-hour, which usually favours the largest fault with the clearest fix
- Work with a closing window, such as tide, daylight, road access or an approaching weather front
- Regulatory and contractual deadlines that attach to specific sites
The order is the operator’s own call. What matters is that it exists on paper, that network command applies it, and that the reason a site was ranked third is recorded at the time.
How Does Crises Control Support Multi-Site Incident Command?
Crises Control supports multi-site incident command through Incident Manager, its Incident Management Software, which gives every level the same live view of one incident. Authorised users activate the incident and launch a predefined response plan. From then on the site teams, network command and the control room are reading one timeline instead of three.
Response plans are configured per incident type, so the right teams and procedures are engaged automatically. Incident Manager launches message templates and notifies predefined recipient groups, monitors incident status, response activities and operational progress in real time, and maintains a complete incident timeline from activation through resolution. As Energy Incident Management Software it reaches people across SMS, voice calls, email, push notifications and Microsoft Teams, and two-way acknowledgement confirms who is safe and who needs help.
Allocation decisions still have to be carried out and evidenced. Incident Task Management Software assigns the work that follows a priority call, tracks completion and escalates critical response tasks, so network command can see which site has actually started, not just which site has been told. Every alert, acknowledgement, task and decision is recorded automatically. That’s what makes the restoration order defensible months later.
Several things stay with the operator. Who holds network command, the threshold at which it stands up, and the criteria that rank one substation above another are decisions the business makes in advance and writes down. The software activates the plan the operator wrote. It doesn’t write it. Contact and rota data has to be current, or the alerts reach last month’s shift. And a site commander still decides what’s safe to do on their site.
Reaching the field at all comes first. Monday’s post on alerting field engineers during a control room outage covers the channel side, and our guide to the coordination gaps in utility incidents covers what breaks once the message has landed.
Multi-Site Incident Command Checklist
This checklist turns the structure above into eight things a head of network operations can confirm before the next storm season.
- A written trigger says when network command stands up, expressed in facts the duty manager has at the time, such as a number of sites affected or a declared weather warning
- A named role, not a named person, holds network command on every shift, with a deputy
- Each site knows who its own commander is before an incident, and how to reach network command directly
- The criteria for ranking sites are written down and approved, and network command applies them
- One operational picture exists that site teams, the control room and leadership all read from
- One person is named to speak to Category 1 responders and the regulator for the whole network
- Every allocation decision is recorded with its time and its reason, as it’s made
- The structure has been exercised with at least three sites live at once, not one
Decide The Shape Before The Weather Does
Three substations off supply isn’t three incidents. It’s one incident with three faces, and what decides how well it goes is a structure somebody agreed on a quiet afternoon months earlier.
Every piece of that structure is cheap to set up and expensive to improvise. A trigger for standing up network command. A named role on every shift. Criteria that rank one site above another. One picture everybody reads. One voice to the outside. None of it needs a budget line, and all of it is close to impossible to invent at 05:20 with a flooded access road and a crew waiting.
A head of network operations can test it this quarter. Run a tabletop with three sites live at the same time, each with its own commander, and watch what happens when two of them ask for the same crew. If one person takes that decision inside a few minutes, against criteria everybody has already seen, the structure holds. If the question travels upwards and stalls, the checklist above shows which piece is missing. To see how one shared incident timeline works in practice, request a demo.
Frequently Asked Questions
What is multi-site incident command?
Multi-site incident command is the arrangement that decides who directs the response at each affected location and who directs it across all of them. Each site keeps its own commander for tactical and safety decisions, while a level above holds priorities, resource allocation and the single operational picture. It’s the structure that stops sites competing for the same crews.
What is the difference between site command and area command?
Site command and area command differ by the kind of decision they take. Site command is tactical. It runs the work at one location and owns the safety of the people there. Area command is about allocation, setting priorities between locations and moving resources, and it does not direct tactics at any individual site. FEMA’s National Incident Management System doctrine describes an Area Command as overseeing the management of multiple incidents.
Who should hold network-level command in a utility?
Network-level command should sit with a named operational role, not a named individual, most often a duty network operations manager with a nominated deputy on every shift. The role needs the authority to move crews and plant between sites without asking permission, which is what makes it a command role rather than a coordination one. The duty control engineer is usually separate, because switching and the network’s electrical state are a full job on their own.
When should a utility stand up network-level command?
A utility should stand up network-level command at a written trigger, not at the point someone feels it’s needed. Useful triggers are factual and available early, such as a second or third site being affected at the same time, a declared severe weather warning, or any incident where two sites request the same scarce resource. Standing it up early and standing it down quickly costs very little. Standing it up late means the first allocation decisions were taken by people who couldn’t see the whole network.
How does Crises Control support multi-site incident command?
Crises Control supports command across several sites through Incident Manager, which activates one incident that site teams, network command and the control room all work from. It launches predefined response plans, notifies predefined recipient groups across SMS, voice calls, email, push notifications and Microsoft Teams, and maintains a complete incident timeline from activation through resolution. The energy and natural resources page shows how the platform is used across multiple facilities.
This article was drafted with AI assistance and reviewed by the Crises Control team. Featured image: AI-generated.
