Capability template for health, safety and environment
Emergency drill brief
Before a fire, evacuation or other drill, the site or office manager gets one brief: the scenario the responsible person has approved, who does what, what each observer records, and the questions for the debrief. It writes no emergency plan.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
A drill is worth running only if it answers a question. The brief starts there: one question, taken from something the site wants to learn, such as whether a corrected arrangement now holds or whether everyone can be counted when one exit cannot be used.
Everything else follows from the site's own arrangements. The scenario is written up for the responsible person to approve. The run sheet puts the alarm, the routes, the assembly point and the roll call in order, with the times your site has set. Each person with a part in the drill appears with their deputy, and the page says plainly when a holder is away on the day or when one person has been given the observer's chair and a duty at once.
Observers go out with something to record, not a feeling to report: what to watch, where, and what to write down. Findings from the last drill come back as things to look at on this one. Afterwards the debrief has a question for every observation, ready to read aloud.
The AI assistant writes no emergency plan, says nothing about what any law requires, approves nothing and judges nothing. It prepares the brief; people run the drill and decide what it showed.
Who starts the work, and when
The site manager, office manager or facilities lead starts it once the date of a drill is set, usually a week or two ahead, so that the responsible person can approve the scenario and the observers can be chosen. It can run again if the date moves, a role-holder is absent or the scenario changes.
The responsible person for emergency arrangements approves the scenario and the brief, and runs or authorizes the drill.
What they supply
- The drill details. Site, type of drill, date and times, who approves, who leads, how many people are expected, who is told in advance, the targets your site has set, and when the debrief is.
- The scenario, in a few sentences, with what is pretended, what is real and when the drill stops. If you have not chosen one, the capability offers up to three options and stops until you do.
- The site's arrangements. Alarm, exits, routes, assembly point, roll call and all clear, as your emergency plan already describes them.
- The roles. Who holds each part in the plan, with a deputy, and who will observe.
- Absences around the date.
- Findings from earlier drills, with what was done about each.
What comes out
One brief in a fixed order: the header and counts, the question the drill answers, the scenario, the run sheet, the gaps in the arrangements list, the roles and observers, the observation points, the earlier findings and where each will be looked at, the debrief questions, the decisions for the responsible person, what the brief does not cover, and a closing line that it is a draft for the responsible person's approval and that nothing has been announced, sent or run.
Every line traces to something you supplied. Where something was not supplied, the brief says so and asks. A person approves it before anything is announced or run.
An invented example
Illustrative example with invented data. The company, the site, the roles, the arrangements, the findings, the dates and the times below are all invented, and the arrangements are not a model for any real site. The site is an invented packaging workshop with a first-floor office, run by an invented business called Company A. First come the inputs the site manager supplied, in full, then the brief the capability returned.
The inputs
1. Drill details
Site: Unit 4, Company A (workshop and first-floor office)
Drill type: fire evacuation
Date: Wednesday 18 November 2026
Start: 10:30
Finish by: 11:00
Today: Tuesday 10 November 2026
Approver: Site manager
Drill lead: Operations coordinator
Expected on site on the day: workshop 26; office 7; visitors 1 (arranged)
Announced in advance to: Site manager, drill lead, the two observers
Not announced to: everyone else
Targets: reach the assembly point 5 minutes after the alarm; roll call complete 8 minutes after the alarm
Debrief: Wednesday 18 November 2026, 14:00
Question we want answered: Does everyone reach the assembly point, and is everyone counted, within our targets when exit D2 cannot be used?
Scenario: A fire is reported in the glue store at the back of the workshop. Exit D2 is unusable. The office must leave by the internal stair. A visitor is signed in.
Scenario approved: yes, by the Site manager, Monday 9 November 2026
Pretended: the fire in the glue store, and exit D2 being unusable
Real: the alarm sounds, people leave and assemble; nothing is lit and nothing is moved
Pretend blockage: at 10:15 the drill lead puts a "blocked" sign across D2; the door stays closed
Alarm: sounded by the drill lead at 10:30 from the call point by the front desk
Stop the drill if: a real emergency happens, anyone is hurt, or the drill lead calls it off
Observers: Maintenance technician (workshop and assembly point); Receptionist (office)
2. The site's arrangements (from the Company A emergency plan)
ID,Arrangement,Detail,Where written
A01,Alarm,"Continuous bell, started from any call point; heard in the workshop and the office",Emergency plan section 2
A02,Exit,"Workshop front exit D1 onto the yard",Emergency plan section 3
A03,Exit,"Workshop rear exit D2 onto the loading lane",Emergency plan section 3
A04,Route,"Office to the internal stair, then out through D1",Emergency plan section 3
A05,Assembly point,"Visitor car park by the gate",Emergency plan section 4
A06,Roll call,"Each fire warden counts their own area; the receptionist takes the visitor log to the assembly point",Emergency plan section 5
A07,All clear,"Given in person by the site manager; nobody re-enters until then",Emergency plan section 6
3. The roles
ID,Plan role,Duty in the plan,Holder,Deputy
R01,Workshop fire warden,"Clears the workshop and counts people at the assembly point",Shift supervisor,Machine operator lead
R02,Office fire warden,"Clears the office and counts people at the assembly point",Accounts clerk,Receptionist
R03,Visitor log,"Takes the visitor log to the assembly point",Receptionist,Operations coordinator
R04,Site manager,"Gives the all clear",Site manager,none
4. Absences
Accounts clerk: away Monday 16 to Friday 20 November 2026
5. Findings from the last drill (Monday 2 March 2026)
Finding ID,Date,Finding,Action,Status
F01,2026-03-02,"Roll call for the office took 9 minutes because the visitor log was left at reception","Visitor log kept in a grab folder by the front desk",done
F02,2026-03-02,"Exit D2 was blocked by pallets","Floor zone marked in front of D2 and checked weekly",open
F03,2026-03-02,"Two people on the first floor did not hear the alarm","Check the bell volume in the meeting room",
The output
EMERGENCY DRILL BRIEF: fire evacuation, Unit 4, Company A (workshop and first-floor office)
Date: Wednesday 18 November 2026, 10:30 to 11:00. Prepared: Tuesday 10 November 2026, from the drill details, the arrangements list (7), the roles list (4), the previous findings (3). Approver: Site manager. Drill lead: Operations coordinator. Scenario: approved by the Site manager on Monday 9 November 2026 (as supplied). Announced in advance to: Site manager, drill lead, the two observers. Not announced to: everyone else. Expected at roll call: 34 (workshop 26, office 7, visitors 1). Counts: arrangements 7; roles 4; previous findings 3; observation points 7. Flags: 4.
The question this drill answers
Does everyone reach the assembly point, and is everyone counted, within our targets when exit D2 cannot be used? Source: supplied.
The scenario
A fire is reported in the glue store at the back of the workshop. Exit D2 is unusable. The office must leave by the internal stair. A visitor is signed in. Pretended: the fire in the glue store, and exit D2 being unusable. Real: the alarm sounds, people leave and assemble; nothing is lit and nothing is moved. Stop the drill if: a real emergency happens, anyone is hurt, or the drill lead calls it off.
Run sheet
- 10:15. Put a "blocked" sign across D2; the door stays closed. By: Drill lead. Arrangement: A03.
- 10:30. Sound the alarm from the call point by the front desk. By: Drill lead. Arrangement: A01.
- From the alarm. The workshop leaves by D1. By: Workshop fire warden (R01). Arrangement: A02.
- From the alarm. The office leaves by the internal stair, out through D1. By: Office fire warden (R02). Arrangement: A04.
- 10:35. Everyone is at the assembly point (target: 5 minutes after the alarm). By: everyone on site. Arrangement: A05.
- 10:38. Roll call complete (target: 8 minutes after the alarm). Each fire warden counts their own area; the visitor log is brought to the assembly point. By: Workshop fire warden (R01), Office fire warden (R02) and Visitor log holder (R03). Arrangement: A06.
- After the roll call. The all clear is given in person; nobody re-enters before it. By: Site manager (R04). Arrangement: A07.
Gaps in the arrangements list
- Help to leave for people who cannot use the stairs or need assistance: no arrangement in the list. FLAG, arrangement not supplied. See decision 1.
Roles for the drill
- R01 Workshop fire warden. Duty: clears the workshop and counts people at the assembly point. Holder: Shift supervisor. Deputy: Machine operator lead. On the day: neither reported away.
- R02 Office fire warden. Duty: clears the office and counts people at the assembly point. Holder: Accounts clerk. Deputy: Receptionist. On the day: holder away (Monday 16 to Friday 20 November 2026, as supplied); deputy not reported away. FLAG, holder away. See decision 2.
- R03 Visitor log. Duty: takes the visitor log to the assembly point. Holder: Receptionist. Deputy: Operations coordinator. On the day: neither reported away.
- R04 Site manager. Duty: gives the all clear. Holder: Site manager. Deputy: none. On the day: not reported away.
Observers
- Maintenance technician: workshop and assembly point. Holds no duty in the roles list.
- Receptionist: office. Holds a duty: R03 holder, and deputy for R02, which covers the Office fire warden on the day. FLAG, observer holds duties. See decision 3.
What to observe
- O01 Alarm (A01). Watch for: whether the bell is heard at the observer's position; anyone who says they did not hear it. Record: heard yes or no at the position, and the number of people who report not hearing it. Observers: Maintenance technician (workshop), Receptionist (office). Previous finding: F03.
- O02 Exit D1 (A02). Watch for: the workshop leaving by D1. Record: the time the first and the last person pass D1, and whether a queue forms. Observer: Maintenance technician.
- O03 Exit D2 (A03). Watch for: before the start, the floor zone in front of D2 (from F02); during the drill, whether anyone goes to D2. Record: the zone clear or not clear at 10:15, and the number of people who go to D2. Observer: Maintenance technician. Previous finding: F02.
- O04 Office route (A04). Watch for: the office leaving by the internal stair and out through D1. Record: the time the last person leaves the office. Observer: Receptionist.
- O05 Assembly point (A05). Watch for: people arriving at the visitor car park by the gate. Record: the time the last person arrives, against the 10:35 target. Observer: Maintenance technician.
- O06 Roll call (A06). Watch for: each fire warden counting their own area; the visitor log arriving. Record: whether the visitor log is at the assembly point when the roll call starts, the time the roll call completes against 10:38, and the total counted against 34 expected. Observer: Maintenance technician. Previous finding: F01.
- O07 All clear (A07). Watch for: the all clear given in person; anyone going back in before it. Record: the time of the all clear and the number of people who go back in before it. Observer: Maintenance technician (area taken from the run sheet).
Findings from earlier drills
- F01 (2 March 2026). Roll call for the office took 9 minutes because the visitor log was left at reception. Action: visitor log kept in a grab folder by the front desk. Status: done. To look at on this drill: O06.
- F02 (2 March 2026). Exit D2 was blocked by pallets. Action: floor zone marked in front of D2 and checked weekly. Status: open. To look at on this drill: O03.
- F03 (2 March 2026). Two people on the first floor did not hear the alarm. Action: check the bell volume in the meeting room. Status: not stated. To look at on this drill: O01. FLAG, status not stated. See decision 4.
Debrief questions (Wednesday 18 November 2026, 14:00)
- O01. Who did not hear the alarm, and where were they?
- O02. Did the workshop use D1 only? Was there a queue at D1?
- O03. Was the floor zone in front of D2 clear before the start? How many people went to D2, and what did they do next?
- O04. Did everyone in the office leave by the internal stair, and who was last out?
- O05. How long did the last person take to reach the assembly point, against the 5-minute target (10:35)?
- O06. Was the visitor log at the assembly point when the roll call started? Did the count match the 34 expected, and was the roll call complete by 10:38?
- O07. Did anyone re-enter before the all clear, and how many?
- What happened that nobody planned for?
- What did people tell you they found confusing?
- Which observations need an action, who owns each, and by when? The Site manager decides.
Decisions for the Site manager: 4
- Arrangements, help to leave not supplied. The arrangements list has no arrangement for people who cannot use the stairs or need help to leave, so the brief cannot set an observation point for it. Is there one that should be added to the list, and should it be observed?
- R02, holder away. The Accounts clerk, the Office fire warden, is away on the day (Monday 16 to Friday 20 November 2026). The deputy is the Receptionist, who is also the office observer. Who counts the office depends on it. Does the Receptionist cover R02 in this drill, or is someone else named?
- Observers, observer holds duties. The Receptionist is the observer for the office, holds R03 and is the deputy for R02. Who observes the office, if the Receptionist is carrying the visitor log and counting the office?
- F03, status not stated. The finding has an action and no status, and what O01 looks at depends on it. Has the bell volume in the meeting room been checked? If not, O01 will look at it as an open action.
Not covered
This brief does not direct a live emergency, does not demonstrate rescue capability, is not an emergency plan and does not say what any law or regulator requires. It does not check how much one observer carries, whether two observation points fall at the same moment in different places, or whether an absence is inside the expected numbers; the Site manager looks at those when approving. It records what to watch and ask; the Site manager decides what the drill showed.
Draft for the Site manager's approval. Nothing has been announced, sent or run.
Where it fits
- Health, safety and environment, which owns the emergency arrangements and the drills that test them.
- Operations and process improvement, where a drill is a planned interruption to live work and the follow-up should reach someone who owns it.
- Executive and office support, where the office manager often runs the drill for a building.
- Manufacturing, where noise, machinery and yard routes shape what a drill can show.
- Logistics and trade, where vehicles, shift patterns and visitors change who is on site.
- Hospitality, where guests and casual staff are part of every evacuation.
- Professional services, where visitors, floors of tenants and shared stairs make the roll call the hard part.
- Established businesses, where the plan was written years ago and drills have become a habit.
- Growth and scaling, where a new unit or floor has people who have never walked the routes.
What has to change for your company
Use your own emergency plan as the only authority: the capability adds no arrangements of its own. Decide who approves a scenario and who leads a drill, and whether observers may also hold a duty. Set your targets, such as time to the assembly point and time to complete the roll call, or leave them out. Decide how announced or unannounced drills are handled and who is told. Agree where observation sheets are kept and who owns each action from the debrief. It runs in ChatGPT, Claude, Copilot or Gemini, from notes you supply; it needs no connection to any building system.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was run three times on its invented example in Claude on 10 November 2026, the template being edited after the first and second runs. The record of the third run is published with it; that run was not blind (the assistant that made the edits had seen the example's output), so it shows the template can be followed to the same result, not that a model which had not seen the answer would reach it. It has not yet been tested in a client environment, and not as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on a past drill your site remembers well, plus cases written in advance with their expected behaviour: a holder away on the day, an observer who also has a duty, an arrangement missing from your list, a scenario that asks for real fire or smoke. The responsible person checks every line against the emergency plan before anyone relies on it. Site safety induction pack teaches new people the arrangements; this capability tests them. Business continuity plan is about keeping the business running afterwards, which is a different piece of work.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: