Summary

  • The coordination room has a current spreadsheet. It names control rooms, duty officers, radio leads and telecommunications providers. When a fixed connection fails and mobile service becomes congested, however, the list does not show which agencies can still exchange operational information, who owns each fallback, or how a provider escalation is meant to begin.

  • A resilient communications plan is complete only when responder organisations can explain and exercise how information crosses agency boundaries and how provider liaison begins during disruption. Until then, the directory is useful context—but it is not proof of interoperability.

The coordination room has a current spreadsheet. It names control rooms, duty officers, radio leads and telecommunications providers. When a fixed connection fails and mobile service becomes congested, however, the list does not show which agencies can still exchange operational information, who owns each fallback, or how a provider escalation is meant to begin.

That gap matters because a directory and a communications arrangement are different evidence objects. Cabinet Office guidance for Local Resilience Forum telecommunications planning says the plan should go beyond a communications directory. It should let responder organisations understand interoperability arrangements and should include contacts for key local telecommunications service providers so liaison with industry is possible.

The distinction is operational rather than cosmetic. A telephone number can be correct while the person answering it lacks the incident role, while two organisations use incompatible channels, or while a fallback depends on the same failed access network. The directory records an address for communication. It does not demonstrate that information can move between responders under the conditions described in the emergency plan.

Local telecommunications sub-groups are intended to join contingency-planning and technical expertise. That creates a practical place to maintain more than names: the purpose and owner of each route, participating organisations, interoperability constraints, provider-escalation triggers, out-of-hours handling, known shared dependencies and the fallback if the primary arrangement is unavailable.

National coordination does not remove the local control. The Electronic Communications Resilience & Response Group supports sector resilience and emergency response, while NEAT can coordinate industry action during serious disruption. Those mechanisms matter when an incident exceeds normal commercial resolution, but a local team still needs evidence showing who recognises that threshold, who makes the request and what communications remain available while escalation is under way.

The useful test is a bounded exercise. Select a plausible loss of a fixed, mobile or data route; require participating organisations to exchange a short operational message; invoke the documented fallback; reach the recorded provider liaison point; and capture the time, owner, failure and corrective action. One exercise cannot prove every future incident, but it can distinguish a working arrangement from an untested contact list.

Sources