Register of Emergency Plans
The Emergency Management Department of the Velocity Interoperability Network holds a single register of emergency plans for the whole of the Velocity Interoperability Network. There are twenty-four plans: six site emergency plans, one for each principal site; fourteen hazard response plans, one for each hazard the Network is exposed to; and four Network continuity plans, which set out how the essential functions of the Network are maintained while a response is under way.
Before the Department was established, each member organisation held its own arrangements. They were not written to a common form, they used different terms for the same thing, and none of them provided for a hazard affecting more than one site at once. During the transition period from 10 August to 5 September 2026 the arrangements were transferred to the Department and rewritten. Every plan in the register was reviewed within the six weeks before establishment.
- 24
- Plans in the register at establishment, all reviewed within the preceding six weeks
- 6
- Site emergency plans, one for each principal site of the Network
- 14
- Hazard response plans covering the hazards the Network is exposed to
- 4
- Network continuity plans for the essential functions of the Network
What the register records. Every entry names the plan, its reference, the office that owns it, the sites it covers, the date on which it was last reviewed and the date by which it must next be reviewed. The plans themselves are held by their owners and by the Network Coordination Centre; the parts of a site emergency plan that concern a particular member organisation are supplied to that organisation on request.
Site emergency plans. A site emergency plan names the site emergency controller and two deputies, records the assembly points and the buildings that may be used as refuge, sets out the local warning arrangements, and lists the reserve equipment held at the site. Site emergency plans are reviewed every six months.
| Reference | Site | Owner | Last reviewed | Next review |
|---|---|---|---|---|
| EP/S/01 | Central Exchange | Network Coordination Centre | 2 September 2026 | 2 March 2027 |
| EP/S/02 | Northgate Relay | Site emergency controller, Northgate Relay | 1 September 2026 | 1 March 2027 |
| EP/S/03 | Southbank Terminal | Site emergency controller, Southbank Terminal | 28 August 2026 | 28 February 2027 |
| EP/S/04 | Eastfield Campus | Site emergency controller, Eastfield Campus | 26 August 2026 | 26 February 2027 |
| EP/S/05 | Westbrook Distribution Site | Site emergency controller, Westbrook Distribution Site | 24 August 2026 | 24 February 2027 |
| EP/S/06 | Meridian Court | Site emergency controller, Meridian Court | 3 September 2026 | 3 March 2027 |
Hazard response plans. A hazard response plan sets out how a particular hazard is recognised, at what point the alert level should be raised, which measures are taken in what order, and which of them may be omitted when time is short. Hazard plans are reviewed every twelve months and after any use.
| Reference | Hazard | Sites covered | Last reviewed | Notes |
|---|---|---|---|---|
| EP/H/01 | Flooding and surface water | All sites | 3 September 2026 | Revised after Exercise Meridian |
| EP/H/02 | Severe weather and high wind | All sites | 31 August 2026 | — |
| EP/H/03 | Fire in an occupied building | All sites | 30 August 2026 | — |
| EP/H/04 | Failure of the electrical supply | All sites | 3 September 2026 | Revised after Exercise Meridian |
| EP/H/05 | Loss of network connectivity | All sites | 2 September 2026 | Under test at Exercise Northgate II |
| EP/H/06 | Failure of the water supply | All sites | 29 August 2026 | — |
| EP/H/07 | Release of a hazardous substance | Westbrook Distribution Site, Eastfield Campus | 27 August 2026 | — |
| EP/H/08 | Structural failure or partial collapse | All sites | 25 August 2026 | — |
| EP/H/09 | Public health incident | All sites | 1 September 2026 | Held jointly with the Health Department |
| EP/H/10 | Extreme heat | All sites | 24 August 2026 | — |
| EP/H/11 | Interruption of fuel supply | Westbrook Distribution Site, Southbank Terminal | 23 August 2026 | — |
| EP/H/12 | Incident with multiple casualties | All sites | 1 September 2026 | Held jointly with the Health Department |
| EP/H/13 | Loss of access to a principal site | All sites | 2 September 2026 | — |
| EP/H/14 | Site security incident | All sites | 26 August 2026 | Held jointly with the Interior Department |
Network continuity plans. These four plans answer a question the site and hazard plans do not: what happens if the arrangements for responding are themselves disrupted. They are reviewed every twelve months.
| Reference | Plan | What it provides for | Last reviewed |
|---|---|---|---|
| EP/C/01 | Continuity of the Network Coordination Centre | Transfer of the Centre's duty to Northgate Relay within 45 minutes | 2 September 2026 |
| EP/C/02 | Continuity of alerting | Issue of alerts when the primary channel is unavailable, including by written notice and on foot | 2 September 2026 |
| EP/C/03 | Continuity of essential Network functions | The order in which functions are restored, and what may be suspended while a response is under way | 31 August 2026 |
| EP/C/04 | Mutual support between sites | Release of a site response team to another site, and the conditions under which it may be refused | 28 August 2026 |
How a plan is reviewed. A plan that is not reviewed becomes a description of a site that no longer exists. The five steps below govern every review in the register.
Step 1: The plan owner opens the review
A review is opened on the date recorded in the register, or immediately after any incident or exercise in which the plan was used. The owner is named in the register and cannot delegate the review outside their own office.
Step 2: Findings are gathered
The owner collects the findings of any incident or exercise since the last review, the changes at the site or in the hazard, and the representations of the member organisations affected. Every finding is answered in writing, including those that are not acted upon.
Step 3: The plan is amended
Amendments are made to the plan itself, not recorded in a separate list of corrections. A plan that requires a reader to hold a second document in mind has already failed.
Step 4: The amended plan is tested
Where an amendment changes what a person must do, it is tested before the plan is issued: by exercise where the change is substantial, and otherwise by walking the change through with the site response team.
Step 5: The register is re-dated
The Department records the date of review and the date of the next review in the register, and publishes the amended entry on this page. Site emergency plans are reviewed every six months and hazard and continuity plans every twelve months.
A member organisation that holds arrangements not reflected in the register, or that believes an entry has become inaccurate, should write to contact@emergencies.gov.vin. The plans are tested by the exercise programme described on the Response page, the alert levels at which they are opened are set out on the Network Alert Levels page, and the currency of the register is reported in the quarterly statistics.