The emergency plan explained: definition, contents & requirements
What belongs in an emergency plan that actually works when it counts? Definition per BSI 200-4 and ISO 22301, the essential building blocks, typical mistakes — and why printed binders rarely help at 3 a.m.
Cyberattack, power outage, fire: whether an organisation survives an emergency is not decided in the moment of the event — but long before, in the preparation. The central tool for that is the emergency plan. We explain what an emergency plan is, what belongs in it and which requirements standards like BSI 200-4 and ISO 22301 set.
What is an emergency plan?
An emergency plan is the documented guide for how your organisation responds to a time-critical damaging event: who alerts whom? Which immediate measures apply? How do business processes continue, and how does recovery succeed? BSI standard 200-4 anchors it as the core of emergency response, ISO 22301 as part of business continuity management — and NIS2 also presupposes robust emergency preparedness.
Distinguishing the situations matters — disruption, emergency and crisis demand different responses. We covered the details in “Emergency or crisis?”.
| Situation | Characteristic | Response |
|---|---|---|
| Disruption | Minor damage, regular operations | Normal organisation resolves it |
| Emergency | Substantial damage, time-critical | Emergency organisation + emergency plan |
| Crisis | Existential threat, unclear situation | Crisis team, leadership under uncertainty |
| Disaster | Large-scale, supra-regional | Cooperation with authorities |
What goals does an emergency plan serve?
- Minimise downtime: restart critical processes quickly and in an orderly way.
- Protect people and assets: clear responsibilities instead of improvisation.
- Meet requirements: evidence for customers, insurers and authorities (BSI 200-4, ISO 22301, NIS2).
- Protect reputation: those who respond in an orderly way keep the trust of customers and partners.
What belongs in a good emergency plan?
An effective emergency plan is more than a phone list. These building blocks have proven to be the core:
| Building block | Content |
|---|---|
| Alerting & reporting paths | Who is informed when, how and in what order — including deputies. |
| Immediate measures | The first steps per scenario: shut down, isolate, secure, document. |
| Emergency organisation | Roles, responsibilities and decision-making authority in an emergency. |
| Critical processes & resources | What must run again first — with recovery times and dependencies. |
| Recovery plans | Concrete instructions for bringing systems and processes back into operation. |
| Communication | Internal information, external bodies, reporting obligations if applicable (e.g. NIS2, GDPR). |
| Contacts & resources | Availability, service providers, contracts, plans — available offline too. |
An emergency plan nobody knows or can find is not a plan — it's decoration.
From paper into practice
The best documentation is useless if it gathers dust in a binder: employees must know the procedures, exercises must expose weaknesses, and alerting must work at 3 a.m. too — that's what an alerting app is for, which can reach responsible people even in Do-Not-Disturb mode, provided critical alerts are enabled on the device. And so the human factor doesn't become the weak point, regular awareness belongs in the mix — for instance via awareness training.
Typical mistakes
- Outdated content: contacts and systems change — the plan doesn't.
- Unfindable in an emergency: the plan sits exactly on the server that just failed.
- Too complex: 80 pages of prose help no one under stress — checklists do.
- Never rehearsed: without exercises every plan remains theory.
- No responsibilities: if “someone” is responsible, no one is.
For a deeper analysis of these pitfalls — with practical examples and remedies — see “5 common mistakes in emergency planning”.
Review and evolve regularly
An emergency plan is not a one-off project but a living document: after every exercise, every incident and every major change it belongs under review. Those who want to run this systematically grow from a single emergency plan to complete business continuity management — with business impact analysis, an exercise programme and audit-ready, exportable evidence.
For the concrete how-to, see our step-by-step guide. Want to build or modernise your emergency plan? Get in touch — we'll guide you from the first assessment to the rehearsed emergency.
Related from our offering
Keep reading
Emergency or crisis? Why the distinction decides your response
Server-room fire at 3 a.m.: emergency or crisis? Separating the two terms cleanly means alerting the right people, escalating in time — and preventing a manageable incident from becoming an existential threat.
5 common mistakes in emergency planning — and how to avoid them
Perfect on paper, useless when it counts: why emergency plans fail on vague instructions, missing upkeep, IT tunnel vision, untrained roles and slow alerting — with practical examples and concrete remedies.