Emergency Drill & Exercise Logger: Turn Every Drill Into Evidence and Action
Schedule fire drills, tabletops, and failover tests, capture participation and timing as you run them, and have your coordinator approve the after-action findings — so every exercise becomes tracked improvement actions and audit-ready evidence.
A web tool where you schedule emergency drills and continuity exercises, get Resend reminders, capture participation and time-to-complete as you run each one, log after-action findings, have the drill coordinator approve those findings and the improvement actions before the record is finalized as evidence, track actions to closure across drills, and export a clean drill-log CSV plus an open-actions list.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- Your drill schedule (type, scope, frequency)
- A way to capture results during/after each drill (CSV, Sheet, or the built-in form)
- Claude Code or any AI coding agent
The problem this kills
You're required to run drills — fire evacuations, tabletop scenarios, IT failover tests — and, more importantly, to prove you ran them and that you learned something. So the evidence ends up scattered: a sign-in sheet photographed on someone's phone, a stopwatch reading scribbled on a clipboard, an after-action email that never turned into actual fixes, and a calendar reminder that everyone snoozed until the drill was three months overdue.
Then the auditor (or the regulator, or the insurer, or the parent company) asks for a year of drill records with participation, timings, findings, and proof that the findings were closed out. Now you're reconstructing history from inboxes and a binder. The findings that mattered — the fire door that stuck, the failover that took four times too long — quietly evaporated because nobody owned them. You don't need to live like this, and you don't need to be a developer to fix it.
What you'll build
A simple internal web tool. You set up your drill schedule (each exercise type, its scope, and how often it must happen) and the tool puts every upcoming and overdue drill in one place. As a drill approaches, it sends Resend reminders to the right people. When you run the drill, you capture results right there: who participated (attendance), the time-to-complete (evacuation time, recovery time), how it went, and your after-action findings. The tool turns each finding into an owned improvement action with a due date. Then the drill coordinator reviews and approves the findings and actions — and only then is the drill record finalized as evidence. Open actions are tracked to closure across drills, so a fix raised after March's fire drill is still visibly open in June. At any point you can export the full drill log as a CSV and a list of open actions.
What's inside the Implementation Plan
The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — which drill and exercise types you're required to run, how you define "passed," how you measure timing today, where your attendance and findings live now (a spreadsheet, a form, an EHS or GRC system), your typical and peak drill volumes, who has to sign off, and your messy edge cases — and then it tailors the data model, the schedule rules, and every later step to your answers. This is not a generic template; the agent reflects a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through the schedule and reminders, the run-and-capture screen, the findings-to-actions logic, the coordinator approval gate, the cross-drill action tracker, and the CSV exports — each step with a ready-to-copy prompt. There's also a fallback so you can build the whole thing today even with no API to your EHS or continuity system.
The governance it includes (this is the point)
This is real compliance evidence, so it ships with the controls an EHS or continuity team needs: login so only your team can use it, row-level security so you only ever see your own organization's drills and actions, a complete audit trail of who recorded, edited, and approved each drill and when, a hard human-approval gate so a drill record isn't finalized as evidence until the coordinator signs off on the findings and actions, and duplicate guards keyed on a drill id so the same exercise can't be logged twice. Findings that aren't acted on can't quietly disappear — they live as open actions until someone closes them.
Who it's for
EHS leads, business-continuity and emergency-preparedness coordinators, facility safety officers, and quality/risk managers who are required to conduct drills and exercises and to evidence them — and who are tired of rebuilding the record from photos and emails every time someone asks. If you can describe how your drills work and how you decide one "passed," you can build this.
You've got this — start with the plan, paste the first prompt, answer the interview, and you'll see your first scheduled drills and reminders take shape the same afternoon.