Five years ago, most buildings had a simple rhythm. Staff arrived, the building was open, staff left, the building was closed. Communication planning followed the same logic, someone was always there to pick up a microphone, walk a message to the right person, or simply notice something was wrong.
That rhythm doesn’t hold as consistently anymore. More gyms are moving to round-the-clock access. More retail extends into early mornings and late nights. Healthcare and transport have long included hours with reduced staffing. Reception desks are increasingly unmanned for stretches of the day. Across many sectors, buildings are operating for more hours than they have people to staff them at any given moment, and communication planning doesn’t always keep pace.
The gap that opens at the edges of the day
Most communication systems were designed around the assumption that someone would be operating them – physically present, ready to make an announcement or respond to a call point. That assumption works fine during core hours. It starts to break down at 6am, at 11pm, on a quiet Sunday, or during any stretch where the building is open, but the desk isn’t staffed.
During those hours, a message still might need to go out. Someone still might need help. But if the system relies on a person being there to send it, the system effectively isn’t there either.
It’s not just about emergencies
It’s tempting to frame this purely around worst-case scenarios- what happens if something goes wrong at 3am. That’s a real consideration, but it’s not the whole picture. Unstaffed hours still need ordinary, everyday communications: scheduled announcements, reminders, routine updates. A system built only for the rare emergency, with nothing running the rest of the time, is also the system nobody’s used to hearing from – which makes it less likely to be understood or acted on when it does matter.
What coverage during unstaffed hours actually looks like
Covering unstaffed hours properly tends to come down to a few things working together, rather than any single fix:
- Messages that don’t need a person to trigger them: Scheduled or pre-set announcements that go out reliably on their own – Routine updates, reminders, background information, whether or not anyone’s behind a desk to send them.
- A way to escalate, not just broadcast: If something happens during an unstaffed period, the response can’t depend on someone physically being there to notice. Call points, monitoring integrations, or automatic alerts to whoever is on call matter more during these hours than at any other time.
- A route to whoever’s actually responsible, wherever they are: Fewer people on-site during unstaffed hours rarely means fewer people responsible. Whoever’s on call may be off-site entirely which makes reaching a device already in their pocket far more useful than relying on a fixed system nobody’s near.
- Visibility after the fact, not just in the moment: A record of what was sent, when, and what was actioned matters as much for unstaffed hours as staffed ones – arguably more, since there’s no one on the floor to fill in the gaps from memory afterwards.
Put together, this is less about adding more equipment and more about making sure the system doesn’t quietly rely on a person being present to function at all.
The standard worth setting
A building shouldn’t need someone behind a desk for its communication to work. If a message only reaches people when a member of staff is there to send it and only reaches the right person if they happen to notice something’s wrong, that’s not really coverage – it’s coverage with a condition attached.
As extended and unstaffed hours become more common, the organisations getting this right aren’t the ones with the most equipment. They’re the ones who’ve stopped treating ‘someone’s on shift’ as part of the plan.
