Describe your building, occupants, alarm process, evacuation routes, assembly areas, and drill goals. Makeform turns the brief into an editable checklist form that safety officers and building managers can use to record pre-drill checks, observer notes, headcounts, exceptions, and corrective actions in one submission.
Route drill records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a complete scenario, adapt the details, or send the prompt to the Makeform builder. Each example shows a practical starting structure, not a completed safety assessment.
Prompt ready4 formats
Audience
Floor wardens and facilities teams reviewing an office evacuation
Format
Mobile checklist with floor-by-floor observations and reconciled headcounts
Prompt size
485 chars
Brief qualitySends to builder
Example checklist structure
Mobile checklist with floor-by-floor observations and reconciled headcounts
Prompt exampleEditable in builder
Drill date, coordinator, and alarm time
Date & timeFirst ask
2
Were alarms audible and routes usable on each floor?
Multiple choice grid
3
Expected, confirmed, absent, and unresolved counts
Number
4
Which route or behavior issues were observed?
Checkboxes
5
Corrective action owner and due date
Short answer
Suggested routing tags
Suggested
Drill complete
Headcount exception
Corrective action
Separate expected occupants, people confirmed at the assembly area, known absences, and unresolved names. One total cannot show why a headcount does not reconcile.
Step 1
Prepare
routes, roles, rosters, and assembly areas checked
Step 2
Observe
alarm, sweeps, movement, and communication recorded
Step 3
Reconcile
people, absences, visitors, and exceptions matched
Step 4
Improve
issues assigned to an owner with a review date
A usable drill record
Turn an evacuation exercise into evidence for the next review.
A checklist should do more than mark a drill complete. It should preserve what was checked, what observers saw, how the headcount reconciled, and which changes still need attention.
Checks follow the actual sequence
Group preparation, alarm activation, sweeps, route movement, assembly, reconciliation, all-clear, and debrief fields in order. Wardens can work through the form without jumping between unrelated questions.
Headcounts explain discrepancies
Capture expected people, confirmed arrivals, known absences, visitors, relocated occupants, and unresolved names separately. Conditional details appear when the numbers do not reconcile.
Findings become assigned work
Turn a blocked exit, inaudible alarm, roster gap, or delayed sweep into an action with a location, priority, owner, due date, and verification note.
Adapt it to the site
One framework, different evacuation realities.
Keep a common review structure while changing zones, roles, occupant groups, and exception fields for the building being assessed.
Offices and mixed-use buildings
Organize observations by floor, stairwell, tenant, warden zone, and assembly area. Record visitors and hybrid-work attendance without assuming the roster equals occupancy.
Schools and community sites
Use class, program, or room rosters; record transfers between groups; and give assembly coordinators a consistent exception handoff.
Warehouses and operational sites
Include shift, work zone, equipment shutdown, yard movement, contractors, drivers, and routes affected by stored materials or vehicle traffic.
Hotels and public venues
Track occupied areas, guest assistance, vendors, event attendees, announcements, alternate assembly points, and communication between duty teams.
Checklist workflow
Build a checklist around your plan, then use each drill to refine it.
Makeform provides the editable form structure. Your site's emergency plan, responsible personnel, current floor layouts, occupant needs, and local requirements should determine the final questions and response process.
Name the building type, floors or zones, occupant groups, evacuation roles, primary and alternate routes, assembly areas, and the kind of drill or review. Mention special processes such as equipment shutdowns, visitor logs, or assisted evacuation.
02
Match fields to the current site plan
Replace sample labels with real zone names, roster sources, warden roles, communication channels, and action owners. Remove questions that do not apply and add location-specific checks identified by the people who manage the site.
03
Use conditional paths for exceptions
Show detail, photo, immediate-action, and escalation fields only when an observer reports a blocked route, alarm problem, delayed sweep, assistance issue, or headcount mismatch. Keep routine submissions fast without hiding the information a problem requires.
04
Review records and close actions
Filter submissions by drill date, building, zone, issue type, or action status. Revisit overdue work before the next exercise and use recurring findings to decide which route, roster, equipment, or communication step needs another look.
Paper, document, or live form
Choose a format that keeps observations connected to follow-up.
A printable sheet can support a small walk-through, while a shared document can hold planning notes. An online checklist is most useful when several observers submit structured records and findings need owners.
Approach
What it captures well
Where it needs help
ApproachPaper checklist
What it captures wellA simple sequence of checks carried by one observer during a walk-through or small drill.
Where it needs helpMultiple copies must be combined manually, handwriting can obscure details, and action status lives elsewhere.
ApproachShared document or spreadsheet
What it captures wellPlanning notes, route inventories, role assignments, and a consolidated table maintained by a coordinator.
Where it needs helpSimultaneous mobile entry, required exception details, photo collection, and conditional questions can become awkward.
Approach
Generated online checklist
What it captures wellConsistent observer submissions, structured counts, conditional exception details, uploads, timestamps, and assigned actions.
Where it needs helpIt still needs to be reviewed against the site's current emergency plan and tested by the responsible team.
Field guide
What an emergency evacuation checklist should record.
Use these six sections as a practical starting point. The correct checks, roles, terminology, and escalation steps depend on the building and its emergency plan, so have the responsible team review the finished form before use.
Exercise context
Identify exactly what was tested.
A record is difficult to compare later if it does not say which site, shift, floors, zones, and scenarios were included. Capture the plan version or internal procedure used, the drill objective, start conditions, observers, and any areas intentionally excluded. This context prevents a partial exercise from being mistaken for a whole-building review.
Building, address or site code, floor, zone, shift, and occupied areas.
Exercise type, objective, date, start time, coordinator, and observer names.
Plan or procedure version, participating groups, exclusions, and weather when relevant.
Readiness checks
Review routes, exits, and assigned resources first.
Pre-exercise fields should reflect what the team can actually observe: routes are identified, exits and access paths are usable, assembly areas are available, role lists are current, and headcount sources are ready. If a check fails, collect the precise location, a short description, a photo when useful, and the immediate control taken before proceeding.
Primary and alternate route, exit, stairwell, door, aisle, and external path status.
Assembly-area markers, radios, rosters, visitor logs, and role assignments available.
Location, issue detail, photo, and immediate response for any failed check.
Alarm and communication
Record whether messages reached each area.
A single alarm checkbox hides where a signal or instruction was missed. Ask observers to note activation time, audibility or visibility by zone, announcement clarity, radio or phone handoffs, and the time key updates reached wardens and assembly coordinators. Include a neutral not-observed option so missing evidence is not recorded as a pass.
Alarm activation, announcement, notification, and acknowledgment timestamps.
Audible and visible signal status by floor, room, work zone, or outdoor area.
Communication gaps, affected audience, backup method used, and supporting notes.
Movement and sweeps
Observe behavior without reducing it to one time.
Total evacuation time matters, but it does not explain a bottleneck. Record when movement began, whether assigned sweeps were completed, which route each zone used, where congestion occurred, whether doors or equipment were handled as assigned, and how assistance arrangements worked. Use zone-specific repeats so several observers can report consistently.
Movement start, zone-clear, assembly arrival, reconciliation, and all-clear times.
Sweep completion, route used, flow problems, unsafe re-entry, or other observed behavior.
Assistance requested, assigned helper or method, location, outcome, and handoff notes.
Assembly and headcount
Make every discrepancy explainable.
Do not ask only whether everyone was accounted for. Separate the expected population from confirmed arrivals, known absences, people working elsewhere, visitors, contractors, people at an alternate point, and unresolved individuals. Collect names or identifiers only to the degree appropriate for the site's process, and require a reconciliation note when totals differ.
Roster or occupancy source, time retrieved, responsible counter, and assembly zone.
Expected, confirmed, absent, relocated, visitor, contractor, extra, and unresolved totals.
Discrepancy details, last known area, communication handoff, and resolution timestamp.
Debrief and actions
Close the loop before the next exercise.
End with strengths, issues, immediate controls, and improvement work rather than a vague notes box. Each action should identify the affected location or process, an owner, target date, status, and how completion will be checked. A later reviewer can then distinguish an observation from work that was accepted, completed, and revisited.
Finding category, location, description, impact, priority, and attached photo or document.
Immediate control, longer-term action, responsible owner, target date, and current status.
Completion evidence, verification note, reviewer, review date, and next-drill consideration.
Related tools
Connect evacuation readiness to inspections, incidents, and continuity work.
Use live Makeform tools for adjacent records while keeping each form focused on one operational purpose.
Practical answers for safety officers, facilities teams, wardens, and building managers creating a repeatable evacuation review form.
What is an emergency evacuation checklist?
An emergency evacuation checklist is a structured record for reviewing readiness and documenting an exercise or event. It can cover the site and scenario, routes and exits, alarms and messages, assigned sweeps, movement to assembly areas, headcount reconciliation, exceptions, all-clear timing, observer findings, and corrective actions. It supports consistent collection, but it does not replace the building's emergency plan, trained roles, or site-specific review.
What should I include in the checklist for an evacuation drill?
Start with the drill objective, included zones, coordinator, observers, and plan version. Add readiness checks for routes, exits, assembly areas, rosters, visitor records, and assigned resources. During the drill, capture alarm and communication timestamps, zone sweeps, route use, assistance arrangements, assembly arrival, and observed bottlenecks. Finish with reconciled occupant counts, unresolved exceptions, all-clear details, lessons, and corrective actions with owners and target dates.
How should an evacuation headcount section work?
Use separate number fields for the expected population, confirmed people at each assembly point, known absences, people assigned elsewhere, visitors, contractors, relocated occupants, extra names, and unresolved people. Record the roster or occupancy source and the person performing the count. When totals differ, conditional logic should request the names or identifiers used by your process, last known location, communication handoff, and the time the discrepancy was resolved.
Can several wardens or observers use the same checklist?
Yes. Publish one form and have each observer submit a record for an assigned floor, zone, stairwell, or assembly area. Include fields for observer, assignment, location, and submission type so records can be filtered and combined later. If one coordinator needs a consolidated view, send structured responses to a shared sheet or workflow and keep a common drill identifier on every submission.
Can the form reveal extra questions only when a problem is found?
Yes. Conditional logic can reveal location, description, photo, immediate response, notification, priority, action owner, and due-date fields after a failed check or exception. It can also request reconciliation details when headcounts differ. Design those branches before the drill and test them on a phone so an observer can supply useful detail without navigating an unnecessarily long routine checklist.
Is this emergency evacuation checklist generator free?
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and reuse your checklist without an invented response cap. The paid tier removes the Makeform badge. You should still review every generated field against your current site plan and operating process before putting the form into use.
Should one checklist cover preparation, the drill, and corrective actions?
It can, especially for a small site and one coordinator. For a larger building, it may be clearer to use one readiness submission, repeated observer submissions by zone, a headcount or assembly submission, and a follow-up record linked by the same drill identifier. The important part is consistent identifiers, clear ownership, and a process for combining the records without losing exceptions between stages.
How often should I update the checklist?
Review it whenever the building layout, occupant groups, tenant mix, shift pattern, assembly areas, contact paths, warden assignments, roster source, equipment, or emergency plan changes. Also revisit it after each exercise or event: recurring bottlenecks, incomplete counts, outdated zone names, and unused fields are direct signals that the checklist or the surrounding process needs adjustment before the next use.
Make the next evacuation review easier to record and act on.
Generate an emergency evacuation checklist for your building, drill, and headcount process.
Unlimited free forms and responsesEditable route and headcount fieldsStructured issues and follow-up actions
