Read a sample: 1. Start With Your Workplace
An emergency plan begins with a simple question: Who and what are we responsible for when normal work is interrupted?
The answer may be less obvious than it first appears. A small office may share a building with other tenants. A shop may have customers in the sales area, contractors working in the stockroom, and employees arriving at different times. A business with a single address may still have delivery drivers, remote workers, or staff who regularly visit other locations. Each arrangement affects who needs information, who can make decisions, and where a plan must connect with someone else’s.
You do not need to solve every emergency scenario before you begin. You do need a clear picture of the workplace the plan is intended to serve. That picture becomes the foundation for identifying hazards, assigning roles, choosing evacuation and shelter procedures, and testing whether those procedures work.
This chapter helps you establish that foundation. By the end, you should have a defined planning scope, a preliminary list of decision-makers, an inventory of people and spaces, and a short record of questions that need attention. These are working notes, not a finished emergency plan. They will become more useful as employees, building representatives, and other knowledgeable people review them.
A workplace emergency plan describes how the organization intends to recognize an emergency, communicate instructions, protect people, coordinate a response, and account for those affected. Depending on the workplace, it may also describe how to interrupt operations, communicate with building management or responders, and support a safe return when the appropriate authorities or responsible parties allow it.
The plan should be specific enough that someone can use it under pressure. “Employees should go somewhere safe” is a good intention, but it leaves too many decisions for the moment of an emergency. A useful procedure identifies who gives instructions, how people receive them, what action they should take, and where they can find further direction.
At the same time, no document can anticipate every condition. An exit may be blocked, a designated coordinator may be absent, or an incident may affect only part of a building. Your plan should establish responsibilities and choices without encouraging people to follow an instruction blindly when conditions make it unsafe. It should also make room for directions from emergency responders and other authorities.
For now, distinguish the emergency plan from several related documents:
- Business continuity plans address how essential services or operations might continue or resume after disruption. They can support emergency planning, but restoring work should not take priority over protecting people.
- Building procedures may cover alarms, shared exits, assembly areas, and coordination among tenants. Your workplace plan needs to fit with these procedures rather than assume your organization controls the whole property.
- Equipment and process procedures may explain how to shut down machinery, isolate a process, or secure materials. Only people authorized and trained for those tasks should be assigned them.
- Contact lists and rosters support communication and accountability. They are useful only if someone maintains them and can access them when needed.
These boundaries help prevent an important planning mistake: treating the emergency plan as either a complete manual for every disruption or a collection of names with no practical instructions between them.
Start by stating exactly what your first plan covers. A scope statement can be short:
> This plan covers employees, contractors, and visitors at the company’s leased office and stockroom, including work performed during opening, normal business hours, and closing. It addresses emergency notification, evacuation, shelter, accountability, and coordination with building management and responders.
This example is a starting point, not a universal model. A real scope statement should reflect the organization’s locations and activities. If your business occupies two floors, uses a detached storage building, or operates a mobile crew, say whether those areas and workers are included. If they are not, identify which plan covers them or who will develop one.
Consider the following boundaries as you write:
Physical boundaries. List the addresses, buildings, floors, suites, outdoor areas, and shared spaces relevant to the plan. Include areas people use only occasionally, such as an archive room or a fenced loading area. Note which spaces are controlled by another tenant, a landlord, or a property manager.
Time boundaries. Consider normal hours as well as opening, closing, overnight work, weekends, and periods when only one or two people are present. The people available to carry out an emergency role may change substantially across those periods.
Organizational boundaries. Identify employees and others the organization directs, hosts, or otherwise needs to consider. A contractor may have a separate employer and its own procedures, but that does not remove the need to coordinate how the contractor will receive an alarm or leave your space.
Activity boundaries. Note work performed away from the main site, including deliveries, client visits, and remote work. You may decide that another procedure covers those activities. Record the connection so they do not disappear between plans.
A scope statement does not need to resolve every question immediately. If you are unsure whether the landlord’s plan includes your visitors, write that down as an open question and assign someone to find out.
Planning becomes difficult when everyone assumes someone else has authority. Before writing detailed procedures, identify the people who can approve the plan, commit resources, make operational decisions, and coordinate with outside parties.
In a small…