Ever wonder who actually does the behind-the-scenes work when something goes sideways at a hospital, a school, or a big event? Not the one in the hard hat yelling orders. Not the person on the loudspeaker. The quiet role that makes the whole response not fall apart.
We're talking about the general staff member who prepares the incident plan, the binders, the drills, the after-action notes — the incident paperwork and coordination that nobody notices until it's missing. And here's the thing — most organizations couldn't tell you who that person is until they need them at 2 a.m.
The short version is: the general staff member who prepares incident-related documentation and readiness is usually the Emergency Preparedness Coordinator (or whatever that role is called in your shop). But the title lies. The work is bigger than a title No workaround needed..
What Is the Role That Prepares the Incident
Look, an incident in this context isn't a fender bender. On the flip side, it's an emergency operation — a fire, an active threat, a power failure, a cyberattack, a flood in the basement. When those happen, groups use an incident command system (ICS) to stay sane. Within that system, there's a general staff: Operations, Planning, Logistics, Finance/Admin.
But before the incident? Someone has to prepare the incident. That someone is often a non-sworn, non-uniform general staff support person — call them the preparedness coordinator, the planning section assistant, the emergency program manager, or the safety and compliance clerk. They don't run the fire. They make sure the fire has a plan.
Not the most exciting part, but easily the most useful.
The Planning Section Is the Clue
In ICS, the Planning Section collects info, maintains status, and prepares the Incident Action Plan (IAP). Outside of an active incident, the general staff member who prepares incident readiness usually sits close to that Planning function. They write the templates. They build the maps. They schedule the tabletop exercise that everyone rolls their eyes at — until it works.
It's Not Always One Person
Real talk: in a small school or a local clinic, this job is glued onto someone's else's desk. The facilities manager. Think about it: the office administrator. Because of that, the nurse. Here's the thing — the "extra duties as assigned" person. In bigger places, it's a dedicated role. But the function is the same — somebody owns the incident preparation, or it owns you.
Why It Matters / Why People Care
Why does this matter? Because most people skip it. Also, they think incident response is about heroics. It isn't. It's about the boring file that was updated last March and the phone tree that actually has correct numbers Simple, but easy to overlook..
Turns out, when an incident hits, the organizations that survive intact are the ones where a general staff member already prepared the incident framework. The ones that fall apart are where "Dave usually knows this stuff" and Dave is on vacation.
I know it sounds simple — but it's easy to miss. That said, a 2021 hospital flood I read about? The pumps worked. Because of that, the plan didn't. In real terms, nobody had printed the evacuation routes because the prep person had left and the task was never reassigned. That's a preparation gap, not a equipment gap.
And here's what most people miss: preparing the incident isn't only about the big bad disaster. It's about the small repeated ones — the chemical spill in the lab, the violent patient, the server room overheating. The general staff member who prepares incident response for those makes the bad day shorter Less friction, more output..
How It Works (or How to Do It)
So how does a general staff member actually prepare an incident? Not by writing one giant PDF and calling it done. It's a cycle. Here's the messy, real version.
Step 1: Know What Could Go Wrong
You start with a hazard vulnerability assessment (HVA). Rank it. Sit with the ops people, the facilities people, the IT person who looks tired. Now, a tornado scores high in Oklahoma; a ransomware attack scores high everywhere now. List what could happen. The prep member doesn't predict the future. They list the likely pasts repeating.
Step 2: Build the Incident Templates
Next, you draft the shells. That's why if you've never seen an IAP, it's basically: here's what we want to do, who's doing it, what the safety rules are, when we meet again. Incident Action Plan template. Incident log. Resource request form. Communications tree. These are the bones the incident commander will fill in at hour two. The general staff member prepares incident documents so the commander doesn't freehand it on a napkin Easy to understand, harder to ignore..
Step 3: Run the Drills Nobody Likes
Then you schedule exercises. Because of that, tabletop first. Full-scale if you're brave. The prep person books the room, sends the invite people ignore, prints the scenario, and facilitates. In practice, the drill is where you learn the plan was wrong. Good. That's the point. Fix it before the real one That's the part that actually makes a difference..
Step 4: Keep the Binders Honest
Plans rot. Worth adding: people change jobs. Worth adding: they act like writing the plan is the finish line. Now, radios get retired. Still, they verify the shelter locations, the utility shutoffs, the legal contacts. Honestly, this is the part most guides get wrong. So the general staff member reviews the incident materials on a calendar — quarterly, semi-annual, whatever the rule says. It's the starting line And that's really what it comes down to. That's the whole idea..
This is the bit that actually matters in practice.
Step 5: Debrief and Archive
After any real incident or drill, the prep member collects the after-action report. What worked. Here's the thing — what didn't. Because of that, what to buy. They file it where the next person can find it. Which means not in someone's inbox. In the system Surprisingly effective..
Step 6: Train the Replacements
Finally — and this is overlooked — they cross-train. Because the day the incident happens, they might be the one stuck in traffic. A good general staff member prepares incident continuity by teaching two other people to do the boring parts.
Common Mistakes / What Most People Get Wrong
Let's get specific about where this goes off the rails And that's really what it comes down to..
One: the plan is written by consultants and never opened. That's why i've seen three-ring binders from 2014 with a logo from a vendor that went out of business. That's not preparation. That's decoration.
Two: the prep person has no authority. Now, they can email reminders, but if facilities ignores them, nothing changes. The general staff member who prepares incident readiness needs a mandate from the top, or they're a polite nuisance Small thing, real impact..
Three: they focus on the document, not the habit. A plan nobody has walked through is a fairy tale. The mistake is treating the incident prep as a compliance checkbox for the accreditation visit instead of a muscle you build.
Four: they use jargon to sound official. But if the front desk can't understand the alert procedure, the plan failed. Now, Incident command system is fine. The best prep members translate.
Five: they forget the human side. Lockdown drills without trauma-informed language scare kids and staff. The prep role includes making the incident less awful to experience, not just survive.
Practical Tips / What Actually Works
Here's what actually works if you're the person stuck with this job — or you're hiring them.
- Name the role. Even if it's 10% of someone's time, write it down. "John prepares incident plans" beats "we think Sarah does that."
- Use plain language in the plan. Write it like you'd say it. "If the alarm rings twice, go to the north lot." Not "initiate phased egress per annex C."
- Do one small drill a quarter. Not a full apocalypse simulation. Just a comms test. A fire extinguisher refresher. A fake power loss at lunch.
- Keep a living doc, not a binder. A shared drive with version dates beats a printed book that's wrong by October.
- Sit with the people who do the real work. The prep member who never leaves the office writes useless plans. The one who walks the floor knows the broken door in the east hall.
- Measure boring things. How fast did the alert go out? How many numbers were wrong? That's your scoreboard.
- Hand it off before you need to. Cross-train like you're quitting next month. Because one day you will be out, and the incident won't wait.
And look — don't wait for a grant or a mandate. The general staff member prepares incident readiness with whatever they have. A spreadsheet. A clipboard. A group chat.
than perfect.
Conclusion
Incident preparation isn't about having the right answer—it's about asking the right questions before anyone asks you. That said, it's the person who checks the fire extinguisher monthly, not the one who updates the plan annually. It's about building habits that persist when stress clouds judgment, not creating documents that gather dust Simple as that..
The difference between a facility that handles an emergency well and one that doesn't often comes down to this: someone paid attention to the boring details when no one was watching. Someone who understood that preparation is less about planning and more about practice—about making the routine dependable enough that when crisis hits, the only thing left to manage is the crisis itself.
Most guides skip this. Don't.
Start small. Test regularly. Write clearly. Day to day, name your person. And remember: the goal isn't to be ready for every possible disaster—it's to be ready for the one you actually face. Everything else is just noise No workaround needed..
