Guide · Night coverage
Night Crew Communication Protocols for Commercial Cleaning
Clear communication protocols for night cleaning crews reduce wake-up calls by 85%. Here's how to build a system that answers routine questions and escalates only real emergencies.
Run the night auditWhy most night communication fails
Most cleaning operations have no protocol. Crews text the owner's personal phone. The owner wakes up for fob questions, supply requests, and schedule notes — 85% of which have fixed answers.
The problem isn't the calls. It's that the answers live in one person's head. Move the answers out of the owner's head into a system that answers for them, and the night goes quiet.
The four pillars of a night communication protocol
- 1
One answered number for all night traffic
One number — WhatsApp, SMS, or email — that always answers. Crews stop guessing who's awake. Messages stop scattering. Every event lands in one place.
- 2
Documented answers for every routine question
Fob locations, supply rooms, backup codes, schedule notes, client contacts, vendor info. Documented in a shared layer crews can reach without a person.
- 3
Clear escalation triggers
Define what counts as an emergency: floods, alarms, lockouts, client emergencies. Only these bypass the filter. Everything else resolves silently.
- 4
One morning summary
Every event — handled or escalated — appears in a single 7:00 AM summary. Nothing falls through. No voicemail to check. No threads to piece together.
Building your shared answer layer
The answers that wake you up are the same five every night. Document them once.
Access
- • Fob locations per site
- • Alarm codes per building
- • Backup key locations
- • Vendor access codes
Supplies
- • Supply room locations
- • Liner/refill locations
- • Equipment storage
- • PPE locations
Schedules
- • Daily schedule per site
- • Special service dates
- • Holiday schedules
- • Crew contact list
Contacts
- • Client emergency contacts
- • Vendor contacts
- • On-duty supervisor rotation
- • Property manager contacts
Questions about night crew protocols
What should a night crew communication protocol include?
A night crew protocol defines: one answered number for all questions, documented answers for fobs/supplies/schedules, clear escalation triggers (floods, alarms, lockouts), and a morning summary format. Crews text one number, get instant answers for routine, live call for emergencies.
How do you document answers so crews don't call the owner?
Create a shared document or answering layer with: fob locations per site, supply room access, backup alarm codes, schedule changes, client contact notes, vendor contacts. Crews check there first. If the answer isn't there, they text the answered number.
What's the difference between a protocol and a phone tree?
A phone tree routes calls to people. A protocol routes answers to crews. A phone tree still wakes someone up. A protocol answers the question without waking anyone — only emergencies reach a person.
How do you train crews to use the new protocol?
Keep it simple: one number, text first. Show them the shared doc. Run one night with the owner on standby. Most crews adapt in one shift because texting is already how they communicate. The owner's phone stays dark.
What happens when a crew member doesn't follow the protocol?
The protocol still works. If they call the owner directly, the owner texts the answered number: 'Text this number instead.' The answering layer replies. The crew learns. The owner goes back to sleep.
How do you handle multiple sites with different protocols?
One answered number, site-specific docs. Crew texts: 'Site A fob location.' System replies with Site A fob location. Same number, site-specific answers. No confusion, no wake-ups.
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