Before the Office Wakes: Routing Building Failures in the Early Hours
At 6.55am on a Tuesday, water is coming through the ceiling of a ground-floor meeting room. The building is otherwise empty. The cleaner has a key but no authority. The facilities manager is on a train. The landlord's switchboard opens at 8.30. The lift maintenance contract sits in a shared drive that nobody can open on a phone. This is not a contact-list problem. It is a routing problem.
Most organisations hold plenty of names and numbers. What they lack is a short, agreed sequence that tells a person under pressure what to do first, who to call next and when to stop waiting. A facilities escalation map is that sequence. It should fit on one side of A4, be understood by someone who has never managed a building, and be tested before it is needed.
Map decisions, not just contacts
A useful escalation map begins with triggers. These are the events that tell a duty person that this is not a routine maintenance request. Examples include water entering a space with electrical equipment, a total power failure affecting access or security, a lift entrapment, a break-in, a fire alarm activation with no sign of fire, or a smell of gas. The map should name the trigger in plain language, then set out the first three actions.
Each route needs an owner and a time limit. The owner is the role responsible for the next action, not a department. The time limit is the point at which the owner stops waiting and escalates. For a leak near electrical equipment, the route might read: isolate the supply if safe to do so, call the duty electrician, notify the facilities lead, and if no answer within ten minutes, call the secondary contractor. That is more useful than a page of numbers with no instructions.
Keep the map to no more than a dozen routes. If a building has many systems, group them by consequence rather than by trade: life safety, security, water, power, access and lifts. A long list will not be read at 7am.
Build in the first ten minutes
The early hours are different from normal working time. Suppliers may be closed, landlords may have an out-of-hours line that routes to a call centre, and senior staff may be unavailable. The map should reflect that reality rather than the daytime org chart.
For each route, record the out-of-hours number, the account or contract reference, and any access instructions. Do not copy entire contracts into the map. A reference and a named contract owner are enough; the detail can live elsewhere. If a contractor requires a purchase order before attending, say so on the map and name the person authorised to raise one. If the landlord is responsible for a system, state the boundary clearly so that nobody spends twenty minutes arguing about whose problem it is.
Include a single line for life safety: call 999. That line should sit above everything else and should not be buried under building-specific detail.
Test it with a fifteen-minute tabletop scenario
A map that has never been walked through is a hope, not a control. A tabletop test takes fifteen minutes and needs no specialist equipment. Choose one realistic scenario, such as a burst pipe above a comms room or a power failure that leaves the front door secure but the alarms offline. Read the scenario aloud to the duty person and ask four questions: who notices, who is authorised to act, who is called next, and what happens if there is no answer?
Time each answer. If the map sends the reader to a contract or a shared drive, mark that as a dead end. If two people disagree about who owns the first action, that is the finding. Record one change, not a full rewrite. Repeat the exercise each quarter with a different scenario. The aim is not to prove the map is perfect; it is to find the point where it fails before a real incident does.
Keep the details current without creating another unused document
The common failure mode is a beautifully produced escalation map that is saved once and never opened. Avoid it by keeping the document deliberately small and tying its review to events that already happen. Review it when a contract renews, when a duty rota changes, when a new landlord or managing agent takes over, and after any real incident. Give one person responsibility for the map and put a review date on the front.
Verify numbers rather than trusting them. Call the out-of-hours line during business hours and ask what happens when it is answered. Confirm that the account reference is still valid. Where possible, use role-based numbers and shared inboxes rather than personal mobiles, and always provide a secondary contact for each route.
Finally, connect the map to existing routines. Include it in induction for anyone who might hold a duty phone. Refer to it in shift handovers and in the incident log. If a real event exposes a gap, update the map and note the change in the same place you record the incident. That way the document earns its place.
The measure of an escalation map is not how comprehensive it looks. It is whether, at 7am, the first person on the scene knows who to call, what to say and when to stop waiting.
