Who is on call this weekend?
The rota was posted in the engineers' group chat a month ago. Since then, two engineers swapped a weekend, one is off sick and another agreed to cover a Tuesday. On Saturday night a contract client's comms room overheats. The answering service calls the number on the rota, which belongs to the engineer who swapped. He is at a wedding. Eventually someone reaches the service manager, who rings round.
On Monday, the call-out pay and the client invoice depend on a text message about when the engineer arrived.
A rota that lives outside your systems
Out-of-hours cover is essential for air conditioning contractors with critical clients, and it is often run informally. The rota is a document or message. Swaps are agreed between engineers. The answering service or phone forwarding uses a list updated occasionally. Call-out time is reported by the engineer afterwards.
Out-of-hours work also involves more parties than daytime work: an answering service or call forwarding, clients' monitoring systems, the engineer on call and a manager behind them. Each holds its own copy of who to call, and the copies drift apart.
- Swaps and sickness are not reflected in who gets called.
- Nothing escalates when the on-call engineer does not answer.
- Alarms from clients' systems go to fixed numbers.
- Call-out time is reported from memory.
- Clients are billed for out-of-hours work inconsistently.
What informal cover costs
Critical calls that take too long to reach anyone, with consequences for clients and contracts. Disputes over call-out pay that affect morale. Out-of-hours work billed late, or not at all. And a service manager who is never really off, because they are the fallback for every problem.
Clients with critical cover also expect evidence. If a contract includes out-of-hours response, the client will eventually ask when calls came in and when someone attended, and a group chat is not an answer.
The on-call rota we build
- The rota is held in a simple scheduling tool: primary and backup on call for each period, set by the manager.
- Swaps are requested and accepted in the tool, and sickness or leave updates cover automatically with the manager's approval.
- Out-of-hours calls from your answering service, phone forwarding or website are routed to whoever is on call now, using Twilio or your phone system.
- Alarms from clients' monitoring route the same way. If the on-call engineer does not acknowledge within the time you set, it escalates to the backup and then the manager.
- Each call-out creates a job with timestamps for call received, acknowledged, arrived and completed.
- Call-out time feeds pay calculations under your rules and out-of-hours charges on the client invoice.
| Rota task | Group chat | On-call rota |
|---|---|---|
| Who is on call | Last posted message | Live rota with swaps |
| Routing calls | Fixed number | To whoever is on call now |
| No answer | Nothing happens | Escalates |
| Time recorded | From memory | Timestamps per stage |
| Pay and billing | Argued over | From recorded time |
Cover that works at two in the morning
Calls reach the engineer who is actually on call, with a backup if they miss it. Swaps happen without anyone forgetting to tell the answering service. Pay and billing come from recorded times. And the service manager can switch off when they are not on the rota.
Engineers also see a fairer rota. The system shows who has been on call how often, which makes swaps and cover easier to agree and reduces the sense that the same people always pick up the weekend.
Warning signs
- Your rota is a message or document.
- Out-of-hours calls have gone to someone who swapped off.
- Nothing escalates when calls are not answered.
- Call-out pay is disputed.
- Out-of-hours work is billed inconsistently.