On-call rota: covering the out-of-hours without burning the team

An on-call rota is the arrangement that decides who picks up the phone outside working hours. Small teams usually start without one — whoever happens to see the alert responds — and that works until the person who always notices burns out or leaves. A rota is partly about coverage and mostly about making the burden visible, predictable and paid.

What an on-call rota has to settle

• Who is on, for which window, published far enough ahead that people can plan their lives around it.
• What they are expected to do: acknowledge within a stated time, or actually fix things, which are very different commitments.
• What triggers a call at all — a paging policy, since a rota without one means everything pages and nothing is urgent.
• Who the second line is when the first person does not answer, because they will not always answer.
• How swaps work, so changes happen openly rather than by private arrangement nobody else knows about.
• What happens after a bad night: time off in lieu, a later start, or nothing — and saying which in advance.

Sizing it honestly

Below about four people a rota is not sustainable, because one week in three with no holidays is a resignation in slow motion. If the team is smaller, the honest options are a narrower window of cover, an explicit best-effort arrangement rather than a guarantee, or paying somebody external. Pretending a team of two provides twenty-four hour cover produces a promise that holds until the first week somebody is ill, which is also the week it is discovered by a customer.

Check how on-call time is treated under your local employment law. In many jurisdictions time where somebody must be reachable and able to respond quickly counts at least partly as working time, which affects rest breaks, maximum hours and minimum wage calculations — and getting that wrong is an expensive discovery.

Paying for it

1. Pay a standing allowance for being available, separately from payment for work actually done.
2. Pay for callouts by the hour with a minimum, since a fifteen-minute fix at 3am costs the whole night.
3. Make the allowance the same for everybody at the same level, published rather than negotiated individually.
4. Cover the practicalities: the phone, the connection, and the expectation of being able to get online within minutes.
5. Record every callout, because the log is what justifies either more staff or fixing the thing that keeps paging.

The handover that prevents repetition

The most wasteful pattern in out-of-hours support is the same fault being diagnosed from scratch by four different people over four weekends. A short written handover at the end of each rotation — what paged, what was done, what is still outstanding — removes most of that, and a note against the recurring alert removes the rest. Teams that skip it pay for the same investigation repeatedly and never accumulate the knowledge that would end it.

Ettex Calendar is a reasonable home for the rota itself, published so that everybody can see who is on without asking, with swaps visible rather than arranged privately. What happened during a rotation belongs in the incident record, since the handover is only useful if the next person can find it.