Guide · Night coverage

Cleaning Crew Emergency Protocols for Night Operations

Define clear emergency protocols so only real emergencies reach you. Floods, alarms, lockouts escalated in under 60 seconds. Routine handled silently.

Run the night audit

The problem: crews can't tell emergency from routine at 2 AM

Without clear definitions, crews either call about everything (waking the owner for fob questions) or nothing (missing the 3 AM water leak). Both outcomes cost money.

The fix isn't more rules — it's a shared definition of 'emergency' posted at every site and built into the answering layer. When the definition is clear, crews escalate correctly without waking the owner for non-emergencies.

The emergency checklist — post at every site

Water / Flood

  • • Active leak or standing water
  • • Ceiling stain growing
  • • Pipe burst
  • • Sewage backup

Fire / Smoke

  • • Visible flames or smoke
  • • Fire alarm activated
  • • Burning smell with visible source
  • • Sprinkler activation

Security / Access

  • • Lockout — no access to site
  • • Broken door/window
  • • Intruder or suspicious person
  • • Security alarm triggered

Life Safety

  • • Gas smell
  • • Power outage in occupied areas
  • • Medical emergency
  • • Structural damage

The escalation flow — under 60 seconds

  1. 1

    Crew detects event

    Crew assesses against emergency checklist. If it matches — text the answered number immediately.

  2. 2

    System triages instantly

    Keywords (leak, fire, alarm, lockout, gas) trigger immediate escalation path. No human delay.

  3. 3

    Live call to on-duty contact

    Automated call placed to on-duty supervisor/owner within 30 seconds. Call includes site, event type, crew name.

  4. 4

    Confirmation & action

    On-duty contact acknowledges. Crew gets immediate guidance. Event logged for 7:00 AM summary.

Questions about emergency protocols

What counts as a real emergency for a night cleaning crew?

Real emergencies are events that threaten people, property, or the contract: water leaks/floods, fire/smoke alarms, security alarms, lockouts, gas smells, power outages affecting safety, structural damage, medical emergencies. A missing fob or supply question is not an emergency.

How do you teach crews to distinguish emergencies from routine?

Give them a clear checklist: 'Does this threaten people, property, or the contract right now?' If yes — escalate immediately. If no — text the answered number. Post the checklist at every site. Run one drill. Crews learn fast when the rule is clear.

What should a crew do when they find a water leak at night?

1. Shut off water if safe and accessible. 2. Text the answered number: 'Water leak at [site/unit].' 2. The system escalates to on-duty contact in under 60 seconds. 3. Crew secures the area if safe. 4. Morning summary logs the full timeline.

What if a cleaner triggers a fire alarm by accident?

Crew texts: 'Fire alarm triggered at [site]. No visible fire. Evacuated.' System escalates to on-duty contact and fire department if needed. Owner gets live call. Morning summary has full timeline. False alarm documented, no owner wake-up for non-emergencies.

What if a cleaner is locked out of a building at night?

Crew texts: 'Locked out at [site].' System checks shared doc for backup fob/key location. If documented — replies with location. If not documented — escalates to on-duty contact for access decision. Owner wakes only if access can't be resolved from docs.

How do you prevent false emergency escalations?

Clear definitions, site-specific docs, and crew training. If crews know where the fob is, they don't escalate a lockout. If they know the alarm code, they don't escalate a false alarm. Documentation prevents false escalations better than rules.

Related guides

See what your night actually looks like

Run the night audit to map how your after-hours traffic flows right now, and where a silent answering layer would change it. No dashboard, no login, and no information to get started — just your phone number.

Run the night audit