Somebody has to answer the 2 AM broken-spring call, and if that somebody is always you, you'll burn out before the year is over. A clear on-call schedule template spreads the load fairly, tells every tech exactly when they're up, and — just as important — protects them from getting woken for jobs that could have waited for coffee. Below is the grid, the rules, and the guardrails.
Fill it in for the week, post it where the crew can see it, and stop running emergency coverage out of your own phone by default.
Keep it visual. One tech owns each night; a backup covers if the primary can't answer. Rotate weekly so nobody eats every weekend.
| Day | Primary on-call | Backup | Coverage hours |
|---|---|---|---|
| Mon | [Tech A] | [Tech B] | 5 PM – 7 AM |
| Tue | [Tech A] | [Tech B] | 5 PM – 7 AM |
| Wed | [Tech A] | [Tech B] | 5 PM – 7 AM |
| Thu | [Tech A] | [Tech B] | 5 PM – 7 AM |
| Fri | [Tech B] | [Tech C] | 5 PM – 7 AM |
| Sat | [Tech B] | [Tech C] | 24 hours |
| Sun | [Tech B] | [Tech C] | 24 hours |
Rotate the assignments each week so the Friday-to-Sunday block — the heaviest — moves through the whole crew. For a two-truck shop, the "rotation" may be just you and one tech; the grid still matters, because it makes the schedule a shared agreement instead of a resented assumption.
On-call swaps are fine. Silent swaps are how a call goes unanswered at midnight. Three rules keep it clean:
Every on-call tech needs to know who to call when a job is over their head or the phone won't stop. Post this ladder next to the rotation grid:
Define what an emergency actually is, in writing, so techs aren't guessing at midnight. A car trapped in the garage, a door off-track blocking the only exit, a broken spring on the customer's only vehicle — those roll tonight. A cosmetic dent or a slow opener waits for the morning schedule. When the overnight jobs stack up, work them in order with the callback queue management guide so nothing urgent gets buried.
A rotation that grinds your best techs down costs you more than any missed call. Build in guardrails and keep them:
That last point is the one that quietly saves your rotation. Triage before dispatch is the difference between a tech woken five times a week and a tech woken only when a customer truly needs them tonight — which is the core of a working emergency dispatch workflow.
An on-call grid answers one question — which tech handles tonight's emergency. It doesn't answer the phone. Someone still has to pick up, calm the caller, capture the details, and decide whether to wake anyone at all. On a busy storm night, that "someone" is often the owner, doing triage in a bathrobe.
That's the gap Ava fills. She answers every after-hours call, runs the emergency triage (car trapped, broken spring, door off-track), captures name, phone, address, and issue, and only routes a true emergency to the on-call tech — with a full summary by SMS and email. The rotation still decides who goes; Ava decides whether tonight's call is worth waking them. Your schedule covers holidays and vacations too — pair this grid with the holiday and vacation call-coverage planner so the year has no blind spots.
Build the rotation. Post it. Then let something else take the first ring, so your techs only lose sleep for the calls that actually earn it.
Call the live demo and have Ava call you now — hear exactly what your customers will hear when they call your shop.