CodeCrafting All articles
Engineering Culture

Whose Turn Is It, Really? On-Call Without the Martyrdom

CodeCrafting
Whose Turn Is It, Really? On-Call Without the Martyrdom

Photo: on-call rota whiteboard small engineering team office, via images.ctfassets.net

The tea round is one of the better inventions of British office life. Someone asks, everyone answers, and the burden is shared without a meeting. On-call should feel a bit like that. Not because incidents are as harmless as a biscuit run, but because the principle is the same: everyone knows whose turn it is, nobody has to volunteer every time, and the person carrying the tray is not left to do it alone for six months.

Small engineering teams often get this wrong in a well-meaning way. There is one person who knows the payment provider best. There is another who is always online at 10pm. There is a manager who quietly covers every weekend because it is easier than sorting out a rota. It works, until it does not. Then you have an outage and a burnt-out engineer at the same time.

The rota is a kindness

A rota is not bureaucracy. It is a way of making the invisible visible. If the same person is always on call, the team has not avoided a rota. It has created a rota with one name on it. Write the rota down. Put it in the calendar. Include Bank Holidays, the Christmas break and the odd Friday when half the team is at a wedding.

For a team of five to nine, a weekly rotation is usually easier to sustain than a daily one. It gives people time to context-switch into the on-call mindset and time to recover afterwards. Pair a primary with a secondary. The secondary is not there to be ignored. They are there to be the second pair of eyes, the person who can take over if the primary is on a train or has already been woken twice.

Define the interruption

Nothing corrodes on-call faster than vague expectations. What counts as a page? What can wait until morning? If the answer is everything is urgent, then nothing is. Write a short list of page-worthy events: checkout failing, login unavailable, data loss risk, a security alarm, a customer-facing outage. Everything else can go to a queue or a ticket.

This is also a kindness to the person on call. They need permission to ignore a noisy alert. They need to know that a slow report or a cosmetic bug is not a reason to lose sleep. Review alerts regularly. If an alert fires every night and nobody acts on it, it is not an alert. It is a bad habit with a pager attached.

Escalation that respects sleep

An escalation policy should be boring enough to follow at 3am. Primary gets the page. If no acknowledgement after fifteen minutes, secondary gets it. If neither responds, the incident lead or engineering manager gets it. Keep the timings realistic for your team. A fifteen-minute window is common. A two-minute window is how you teach people to sleep with one eye open.

Make sure the runbook is one click away from the alert. It should say what the service does, what the common failure modes are, how to check the dashboards and when to escalate. It does not need to be beautiful. It needs to be there. A runbook that lives in a folder called docs-old is not a runbook. It is archaeology.

And make it safe to escalate. If someone wakes the secondary and it turns out to be a false alarm, that is fine. The cost of a false alarm is much lower than the cost of an engineer sitting alone at 2am trying not to bother anyone.

Handover: the two-minute kettle note

Handover is where small teams either build trust or lose it. Keep it short and specific. Before you finish your shift, write a note with three things: any open incidents, any alerts that are noisy but not actionable, and any changes going out in the next twenty-four hours. Add the current state of any workaround. A two-minute note at the kettle beats a forty-minute meeting on Monday.

The handover should also include the human bit. If you were woken twice, say so. If you are running on three hours of sleep, say so. The next person can adjust. Pretending everything is fine is how a rota becomes a endurance test.

Pay, time off and the quiet ledger

Compensation is not a perk. It is part of the deal. Some teams pay an on-call allowance. Some offer time off in lieu. Some do both. Whatever you choose, write it down and apply it consistently. If a Bank Holiday shift is worth the same as a quiet Tuesday, say that clearly. If it is not, say that too.

There is also a quiet ledger in every team. People remember who covered the weekend before a release, who swapped shifts when a child was ill, and who always seemed to be unavailable when the pager went off. A fair rota keeps that ledger balanced. Managers should take their turn. Senior engineers should take their turn. If the most experienced person never carries the pager, the team learns that on-call is junior work.

Signals that it is working

You will know the rota is healthy when people swap shifts without drama, when the primary can say I need the secondary without apology and when post-incident reviews focus on the system rather than the person who happened to be awake. You will know it is unhealthy when one name appears on every holiday, when alerts are ignored, or when the same person always seems to be the one who knows what to do.

On-call is not a test of loyalty. It is a shared responsibility with a clear edge. Design it like a tea round: visible, fair and easy to hand over. Then nobody has to be a martyr to keep the lights on.

All Articles

Related Articles

Listed Buildings, Listed Decisions: A Register for Your Codebase

Listed Buildings, Listed Decisions: A Register for Your Codebase

When Clever Code Costs a Sprint: A Quarterly Boring-Code Audit

When Clever Code Costs a Sprint: A Quarterly Boring-Code Audit

The House With No Number: Designing UK Address Forms for Real Places

The House With No Number: Designing UK Address Forms for Real Places