Emergency Tenant Communication During Building Emergencies
How property managers own emergency messaging: the first ten minutes, message templates, channel fallbacks, accessible notices, and the record after the event.
In a building emergency, residents act on whatever information reaches them first. If that is an alarm and a neighbour's guess, the stairwell fills with people who do not know whether to leave or stay put. The manager's job in that window is narrow: get one accurate message to everyone, fast, then keep updating until the event closes.
Emergency tenant communication is therefore a prepared function, not an improvised one. It needs a named message owner, pre-written templates, at least two channels that do not depend on each other, and a log — all decided before anything happens.
Key takeaways
- Send the first message within 15 minutes of confirming an event, even if it only says what is known, what to do now, and when the next update comes.
- Never guess at a cause. "We do not know yet" is a complete sentence and is safer than a theory that a resident repeats as fact.
- Give every message the same five parts: what happened, where, what to do now, what not to do, when the next update arrives.
- Use two independent channels — the announcement system plus printed notices or a calling tree — and assume mobile service will be congested.
- The manager owns messaging, roles and records. Fire alarm design, suppression systems, the fire safety plan and evacuation engineering are commissioned and approved by qualified persons.
What does emergency tenant communication need to do?
It needs to move people to a safe action, keep them clear of responders, and prevent the vacuum that fills with rumour. Every message is judged against those three jobs, not by how reassuring it sounds.
It also sets the tone: short sentences, present tense, no jargon, no speculation about fault, a stated time for the next update. Residents handle bad news delivered clearly; they handle silence badly.
What happens in the first ten minutes?
Confirm the event, notify the response lead, and prepare the first message in parallel rather than in sequence. The person dealing with the leak and the person drafting the notice should be two different people.
In the first ten minutes: confirm what is physically happening from someone on site, call 911 for anything involving fire, smoke, gas, injury, entrapment or a person in danger, notify the after-hours lead and the relevant contractor, pick the fastest channel with a fallback ready, then send once the facts are confirmed with an explicit next-update time.
Do not wait for a complete picture: the first message is a placeholder with instructions and earns the right to send the second.
Who owns what in an emergency?
Roles, not hierarchy. During an active event the fire service may take command; the building team's job is to support that and keep talking to residents.
| Role | Who holds it | What they own | Record kept |
|---|---|---|---|
| Incident lead | Building manager or after-hours duty manager | Decision to send messages, escalation calls, contact with responders | Timestamped incident log |
| Message owner | Communications lead or designated coordinator | Drafting and issuing notices, updating the template | Copy of each message with send time |
| Site verification | Concierge, operator or security | Facts from the location, photos where safe, access for responders | Site notes and photos |
| Contractor liaison | Operations coordinator | Dispatching and confirming trade attendance | Call log and arrival times |
| Resident support | Front desk or appointed staff | Directing people, answering questions, flagging anyone who needs help | Contact log, no medical detail |
| Owner liaison | Regional manager | Informing the owner, aligning on external statements | Briefing note |
Two rules keep the table useful. Every role has a named deputy, because the manager may be unreachable. And nobody issues a message outside the owner's draft; two versions of the same event destroy trust in both.
What should an emergency message contain?
Five parts, in this order, in under 120 words: what happened, where it happened, what residents must do now, what they must not do, and when the next update comes.
A worked example for a water ingress event:
Water shut-off, Tower B, floors 8 to 12. A pipe has failed on level 9 and water is affecting the corridor and two suites. If you are on floors 8 to 12, stay in your suite unless emergency services direct you otherwise. Do not use the elevators or enter the affected corridor. The water has been isolated and cleanup crews are attending. Next update by 15:30.
The same structure works for a fire alarm, a gas odour report, a power failure, a burst sprinkler, a police operation. Only the instructions change.
For smoke or fire, the message does not replace the fire safety plan or the alarm. It supports them: residents follow the plan and posted instructions, and the message adds what the alarm cannot say — which stairwell, where the assembly point is.
Which channels should you use, and how do they fail?
At least two, chosen so that the failure of one does not disable the other. The building announcement system, printed notices at exits and in elevators, a phone or SMS tree, email, and the building app or portal are the usual options.
Each fails predictably. The announcement cannot reach a suite with a fan running. Email is unread on a Saturday night. SMS depends on a network that congests when the whole block calls at once. A portal needs a login nobody remembers under stress.
Pair channels by failure mode, not preference. Voice announcement plus a printed notice at each stairwell door covers the asleep resident and the network outage. A calling tree covers residents who will not read email.
Keep a pre-printed pack of blank templates and pens in the lobby cupboard and at the after-hours post. Nobody should be inventing a notice layout on a laptop with 4 percent battery.
How do you reach residents who need extra help?
Before the event, with consent, and with the minimum information necessary. Keep a voluntary list of residents who have said they may need assistance in an evacuation: mobility limitations, hearing or vision limitations, or a preference for a phone call in a language other than the one used on the notice.
Do not collect diagnoses. "Prefers a phone call, may need help with stairs" is enough; anything more is personal health information needing a stronger justification and tighter handling. Confirm collection and retention with your privacy lead — the Office of the Privacy Commissioner publishes guidance on privacy in the landlord and tenant relationship.
Keep a one-page notice in the three or four languages most used in the building, with pictograms for the five actions that matter: evacuate, stay put, no elevators, use this stair, go here. Script the front-desk answer for a resident who cannot hear the announcement.
What is outside the manager's role?
Alarm design, suppression systems, smoke control, fire safety plan approval, evacuation modelling, structural or electrical assessment. Those are commissioned from qualified professionals and accepted by the authority having jurisdiction; the manager knows who holds them, keeps the records and communicates.
Not legal or regulatory advice. Fire codes, building codes, evacuation requirements and owner obligations differ by province and municipality and are enforced by the local fire service. Confirm requirements for your building with the authority having jurisdiction and with the qualified persons who maintain its life-safety systems. Public Safety Canada publishes national guidance through its emergency management programme.
The manager should never comment on cause or liability during an active event. "The fire department is investigating" and "the owner will issue a statement" are complete answers.
What does the record look like afterwards?
A timestamped log, the text of every message sent, the channels used, names of residents contacted directly, contractor attendance times, safe photos, and a note of what was not known at the time. Keep it with the incident report, not in an inbox.
The log does two jobs: it supports insurance and owner reporting, and it is the raw material for the debrief — what the first message said, how long it took, which channel failed, who could not be reached.
Run the debrief within five business days, with everyone who held a role. Two questions start it: what slowed the first message down, and who did not receive it.
How do you test the messaging without a real emergency?
Twice a year: one announced tabletop with the role holders, and one unannounced test of the channel chain. The tabletop takes forty-five minutes and a scenario card; the channel test takes an hour and reveals which phone numbers are dead.
Use the same structure each time — event, first message, escalation, update, all-clear — and time each step. A team that drafts a correct notice in eight minutes in a drill will do it in twelve in a real event, which is inside the window that matters.
Add the messaging check to the inspection cycle. Unlit exit signage, a notice board taken over by advertising, a propped stairwell door — these make good messaging useless. Note them, photograph them and route them to the contractor or the commission.
Frequently asked questions
How fast should the first emergency message go out?
Within 15 minutes of confirming the event, or immediately after calling 911 if life safety is involved. The first message may be incomplete; it needs to say what is known, what to do now, and when the next update comes.
Who should send it?
One named owner per building, with a deputy, drafting from an approved template the incident lead signs off. Multiple senders produce conflicting instructions, and residents believe the worst version.
Should we tell residents the cause?
Not during the event. Cause is often unknown, sometimes contested and occasionally a matter for investigators or insurers. Say what you know, say what to do, and defer cause to the authority handling it.
What about commercial tenants with staff in the building?
Notify the tenant contact and the building's safety representative at the same time as residents, and ask them to confirm their staff are accounted for. Commercial floors usually have internal wardens, so the message should reach that person, not only the lease signatory.
Do we need to message residents after the event?
Yes, within 24 hours: what happened factually, what was done, what is still being repaired, who to contact. An all-clear with no follow-up leaves residents filling the gap with the version they heard in the elevator.
Build the record that survives the event
Messaging is only half of emergency readiness; condition records are the other half. NeatScore lets property managers run area-specific inspections with APPA 1–5 scoring, critical items flagged, photos on every item, offline inspections that sync, deficiency tracking and a dated branded report — so blocked exits, unlit signage and wet floors are documented before an incident rather than after one. Try it free for 14 days, or see pricing.
For the wider programme, start with tenant relations in property management, then the planning side in emergency response planning for buildings. The notice mechanics are covered in notice templates tenants actually read and the calmer cousin of this topic in telling tenants about service changes.
