The prompt
Score 10 of 10, Excellent
Use it when You need written emergency procedures for your building or site, built from your own layout and contacts and ready to check against local rules.
- {{site_details}}
- {{emergency_types}}
- {{emergency_roles}}
- {{contacts}}
- {{rules}}
- {{site_name}}
- {{audience}}
- {{approver}}
Full prompt and why it works
System prompt
You help facilities and safety managers write emergency procedures for one site. You write only from the site details and rules given, in short steps people can follow under stress, and mark every gap, because a guessed exit or phone number puts people in danger.
User message
<site> {{site_details}} </site> <emergencies> {{emergency_types}} </emergencies> <roles> {{emergency_roles}} </roles> <contacts> {{contacts}} </contacts> <rules> {{rules}} </rules> Write emergency procedures for {{site_name}}, for {{audience}}, so that anyone on site, including a visitor on their first day, knows what to do in the first minutes of each emergency listed, and the people with emergency roles know their own part. Cover every type in the emergencies section and meet the rules section. Produce: 1. A posting summary that fits on one printed page, under 250 words: for each emergency, how it is signaled and the first actions for everyone, at most four each. 2. A procedure for each emergency type, under 300 words each, with these labeled parts: How it is raised; Everyone (numbered steps, each starting with a verb); Role actions (by role from the roles section); Where to go (exits, assembly point or shelter area, named exactly as in the site details); Accounting for people (how the headcount uses the sign-in or visitor records); People who need help to leave or shelter (by role or plan, never by name); All clear (who gives it and how). 3. A contacts table with the columns Role, How to reach, When to call. 4. Drills and review: how often each emergency is drilled, who runs it and what is recorded, taken from the rules, and when the procedures are next reviewed. 5. Gaps and conflicts: everything missing from the material, and anywhere the site details seem to conflict with the rules. <example> The form of an Everyone list: "1. Raise the alarm using [method from site details]. 2. Leave by the nearest exit marked [signage from site details]. 3. Go to [assembly point from site details] and report to the warden." This shows the form only; use the site's real methods and places. </example> Rules for the draft: - Do not invent exits, assembly points, alarm sounds, equipment locations, phone numbers or legal requirements. Where something is missing, write [CHECK: what is needed] in place and list it under Gaps and conflicts. - Do not give first aid or medical treatment steps beyond what the site's own procedure states; the steps are to call for help, send for a first aider and bring the equipment the site names. - Do not cite codes or regulations unless they appear in the rules section. - Write for someone who is frightened and reading fast: short sentences, one action per step, no background inside the steps. A good procedure is one a visitor could follow alone on their first day. Start the document with the line "DRAFT for {{approver}} to check against the rules and, where they require it, with the local fire service or authority, before it is posted." If the emergencies section names a type the site details say nothing about, write its procedure as headings with [CHECK] placeholders rather than filling it from general practice.
Variables
- {{site_details}}
- The building or site: floors, exits, assembly points, shelter areas, alarms, equipment such as extinguishers, first aid kits and defibrillators and where they are, opening hours and who is usually on site.
- {{emergency_types}}
- The emergencies to cover, for example fire, medical, severe weather, gas leak or lockdown, and anything the site has for each.
- {{emergency_roles}}
- Who does what in an emergency, by role: wardens, first aiders, the person in charge, reception.
- {{contacts}}
- Emergency numbers and internal contacts, by role.
- {{rules}}
- The local rules, codes, insurer or landlord conditions the procedures must meet, as you have them. Write "none given" if you have none yet.
- {{site_name}}
- The site the procedures are for, for example "the warehouse and offices at our main depot".
- {{audience}}
- Who will use them, for example "all staff, contractors and visitors".
- {{approver}}
- Who checks and signs the procedures off, for example "the facilities manager".
Why it works
- If unsure. Every missing exit or phone number becomes a [CHECK] placeholder and a listed gap, and the document opens as a draft to be checked against local rules before it goes on the wall.
- What good looks like. Steps are written for someone frightened and reading fast, one action each and starting with a verb, which is how people actually use an emergency notice.
- What to avoid. No first aid beyond the site's own procedure and no codes that are not in your rules, so the draft never gives advice nobody approved.