Writing an Emergency Response Plan People Will Actually Read
Most church emergency plans are written once, printed, put in a binder, and never opened again until someone goes looking for it during an actual emergency — which is the worst possible time to read something for the first time.
Shorter than you think
If your plan is more than a few pages per scenario, nobody's reading it end to end, and nobody's retaining it. Aim for something closer to a checklist than a manual: what happened, who does what, in what order, with phone numbers and exact locations spelled out. Save the detailed reasoning and policy language for a separate reference document — the response plan itself should be scannable in under a minute by someone whose hands are shaking.
Organized by scenario, not by department
Volunteers don't think "what does the facilities section of the plan say." They think "there's a medical emergency in the lobby, what do I do." Structure your plan around the scenarios you'll actually face — medical, severe weather, disruptive individual, fire, lockdown, missing child — each with its own short, self-contained set of steps.
Named roles, not job titles
"The head usher" means something different to every new volunteer. "Jordan Avery, mobile: 555-0142" means something to everyone. Where possible, name actual people for actual roles, and keep that list current — this is the single biggest reason plans go stale, and it's the easiest to fix with a quarterly check.
Written for the newest person on your team
If a volunteer who joined last month can't follow it under stress, it's not specific enough. Avoid internal jargon, assume no prior knowledge, and spell out exact locations ("AED is on the wall behind the welcome desk, left of the coffee station") rather than vague references ("AED is in the lobby").
A living document, not a one-time project
Plans go stale the moment your building, staff, or team changes — which is constantly. Build in a recurring review (quarterly works well for most churches), and treat every real incident, drill, or near-miss as an input that should change the document, not just a story you tell afterward.
The goal isn't a plan that looks thorough to an outside auditor. It's a plan that a volunteer with shaking hands can actually follow at 10:47 on a Sunday morning. Write for that moment, not for the binder shelf.