The On-Call Rota People Accept: Frequency, Swaps and Fair Weeks

Friday, 17:10, at Stonebridge Insurance. Omar runs a desk of five and has just e-mailed the on-call rota for the next twelve weeks. He built it in twenty minutes in a spreadsheet. The names are in alphabetical order, and the rota starts Monday. By 17:25 he has three replies. Rita is on call the week of her sister's wedding, which has been in the shared calendar since spring. Kwame has the two public-holiday weeks, which he also had last year, and the year before. That is because K comes after J and the holidays fall where they fall. Jess, who started three weeks ago and has not yet been given access to the claims system, is primary in week four. Nobody is angry yet. Everybody is doing the arithmetic, and the arithmetic is the problem.

An on-call rota is the list that says whose week it is: which named person holds the phone, from when to when, with whom behind them. A rota people accept is one they can plan a life around, swap without a fight, and look at in December without finding their name on every hard week. Acceptance is not a soft extra. It is the thing that keeps the rota staffed, because a rota nobody accepts is left by the people who can leave. Those are the senior ones. This article is part of our After-Hours & On-Call Support series. It assumes the shape of the cover has been chosen from the coverage models for a small team. The model decides the shape of a week. The rota decides whether people will live in it.

It covers why acceptance is the only measure of a rota, then frequency and the arithmetic after leave. Swaps that are easy, the holiday rule, and the week after a bad week follow. Next come the new starter's first rota, in which they are never alone, and the manager who is in it. Publishing it far ahead and handing the phone over come next. A short war story and the rota rules to copy come last, in that order.

Why Acceptance Is the Only Measure of a Rota

A rota is accepted when the people on it stop checking whether it is fair. That sounds like a low bar and it is the whole bar, because the checking is what the rota costs. A technician who opens the spreadsheet every month to count whose name is on the bank holiday is spending attention on the rota that should be going on the work. They are building a case, quietly, that will be presented at an exit interview. The rota that is accepted is the one nobody counts, because it was built so that the count comes out even whenever anyone does.

The signs of a rota that is not accepted are easy to read once you know them. Swap requests rise, and they stop being "can you take Tuesday" and become "can you take the whole week". Sickness lands on on-call weeks more than on other weeks. One person has the holiday week three years running and has stopped mentioning it, which is worse than mentioning it. And somebody senior, one day, asks whether the organisation has considered a managed service for nights, in a tone that says they already have. Nobody has ever been talked out of resigning by a spreadsheet. They have, often, been talked into it by one.

Fairness in a rota is not sameness. It is that the load is visible, the rules are written, and the exceptions are decided by a rule rather than by whoever asked first. A rota with written rules that give the new starter a lighter first cycle is fair, because everyone had a first cycle. A rota where Kwame gets the holidays because of his surname is not, however even the week count looks. The rules below are the ones that make the load visible. They are not many. Most desks that have a rota people accept are running a version of all of them, usually unwritten. That is the problem the template at the end solves.

Frequency: How Often a Turn Comes Round

Frequency is how often one person's turn comes round, and it is the first number a technician calculates when the rota arrives. For the simple rota it is one week in N, where N is the number of people on the rota. For the primary and secondary pair it is primary one week in N and secondary one week in N, so on the rota two weeks in N. The honest N is not the headcount. It is the headcount after you remove the new starter who cannot yet carry the phone and the person on extended leave. You also remove the part-timer whose contract does not include nights. Then you spread everyone's annual leave across the year. The table works the arithmetic for a few desk sizes.

Read the "when one person is on leave" column aloud before you announce a frequency, because that is the frequency people will remember. Three people with five weeks' leave each means one of them is away for fifteen weeks of the year. In those weeks the other two are one week in two. Omar's five-person desk was really a four-person rota for most of the year, with Jess not yet able to carry the phone. It was a three-person rota in August. The published frequency was one in five. The lived one was closer to one in three and a half. Alphabetical order is a sorting method. It is not a fairness policy.

Below four people on the rota, think again before you build one, and the coverage models article says what to think about. If the count still says a rota is needed at three, the rules in this article are not optional refinements. At that size, they are the difference between a rota that lasts a year and one that lasts until the first person finds another job. A week in three with no recovery rule and no swap rule is a resignation with a start date.

Swaps That Are Easy

A swap is two people trading on-call weeks, or parts of weeks, between themselves. The rule that makes a rota liveable is that like-for-like swaps need nobody's permission. Rita wants her sister's wedding week; she asks Dev, Dev agrees, the calendar is changed, and Omar is told, not asked. The lead's involvement is to know, so that the calendar is right and the phone goes to the right person. It is not to approve. A rota where every swap goes through the lead has made the lead the bottleneck for everyone's life. The lead will be asked, by every swap, to judge whether a wedding outranks a football match. No lead wants that job and no lead should have it.

Three rules keep swaps from becoming a second rota. First, the swap is written in the one calendar before it takes effect, by the people swapping. That way, the calendar is always the truth and nobody holds the phone on a verbal agreement. Second, a swap is a trade, not a gift. Dev takes Rita's week and Rita takes one of Dev's, agreed at the time. That way, the count stays even without anyone keeping score. Third, a swap into a hard week, a public holiday or a week known to be loud, is a favour and is named as one. The rota keeps the hard-week rotation going as if the swap had not happened. That way, the favour does not quietly move the holiday to the generous person's name for good.

Do not keep a swap ledger. The temptation is real, especially for a lead who likes a tidy sheet. It produces a document in which every favour is a debt and every debt has a date. A swap ledger is a grudge with columns. Record the swaps in the calendar, because the calendar needs to be right, and let the trade rule keep the count even. If one person is being asked to swap far more than anyone else, that is a sign about the rota, usually that their weeks keep landing on things. In that case, the fix is to re-cut the rota rather than to tally the favours.

The Holiday Rule

The holiday rule has two halves. First, nobody is on call during their own leave or on the night before it starts. Second, the weeks that contain public holidays rotate on their own cycle so the same person does not get them twice. The first half sounds too obvious to write down. It is written down because the alphabetical spreadsheet broke it for Rita within fifteen minutes of being published. The night before leave is on the list because a call at two in the morning on the day of a flight is a call the person will remember longer than the flight.

The second half needs a separate little rota of its own. This is a list of the public-holiday weeks for the year, with a name beside each. The names are assigned so that each person takes roughly the same number across the year and so that whoever had the big one last year does not have it this year. Keep this list in the same calendar as the main rota, and build the main rota around it rather than the other way about. Kwame had the two holiday weeks for three years because the main rota was built first and the holidays fell where they fell. Build the holiday list first and the main rota fills in around it, and nobody's surname decides their December.

Leave and the rota have an order, and the order is that the rota is published first and leave is booked against it. This only works if the rota is published far enough ahead, which is the subject of a section below, and it is the reason that section matters. Where leave has already been booked before a rota exists, as it was at Stonebridge, the first rota is built around the leave already in the calendar. In that case, the rule starts from the second one. Nobody is asked to cancel a wedding to satisfy a spreadsheet, and nobody should have to ask.

The Week After a Bad Week

A bad week is one the rota rules define in advance. That could mean three or more calls, or any single night call longer than two hours. The rule is that the person who has had one goes to the lightest available slot next. That means secondary rather than primary, or skipped for a cycle, with the weeks reshuffled to cover it. The definition is written down so that nobody has to plead. A technician who has been up three nights should not have to make a case to the lead for a lighter fortnight. The rota should already say so, and the lead should already be reshuffling. The recovery after a bad stretch is a bigger subject than the rota. The desk-wide version of it is in Recovery After a Bad Stretch. The rota's part is small and mechanical: the next week is lighter, by rule.

The lead decides it, and announces it, rather than waiting to be asked. The person who has had the bad week is the person least likely to ask. That is because asking feels like weakness and the weakness feels like it would be noticed. The lead reads the on-call log on Monday morning, sees three calls, and says "you are secondary next cycle, I have moved Dev to primary". That sentence costs the lead a minute and buys a rota people trust. The morning after each night call is protected on the same principle. That rule, with the time back it goes with, is in Compensation and Recovery Time.

The bad week also goes in the monthly review as a fact about the rota, not about the person. Three calls in a week is three things that broke at night. The question is why, which belongs to the measuring article later in this series. The person who answered them did their job. The rota's job is to make sure they are not asked to do it again the following week. The desk's job is to make sure the three things stop breaking.

The New Starter's First Rota: Never Alone

A new technician is never on call alone, and the rule has a schedule rather than a feeling behind it. For their first two cycles they are secondary to an experienced primary, which lets them see the calls without owning them. For the next cycle they are primary with the experienced person as secondary. That way, the first calls they take have a named colleague ten minutes behind them. Only after that are they a full member of the rota, and even then their first solo week should not be a public-holiday week. Jess in week four as primary, three weeks into the job and without claims-system access, was the alphabetical spreadsheet's worst idea, and it had several.

Before the first primary week there is a checklist, and it is about access and knowledge rather than confidence. The new starter has every account and permission the night needs, tested, including the ones only used at night. They have the on-call runbook, the one-page set of steps for each thing the phone usually rings about, and have walked through it with someone. They know the single route in and what counts as a call. They know who the secondary is and how long to try before escalating. The runbook lives where the night can reach it. In most desks, that is the knowledge base in a section visible to agents only. If you run QuerySolv, that is an article the requesters cannot see and the person on the phone can. That is exactly the split a runbook needs. How to write one is in Writing the Runbook. How a shadowing cycle teaches rather than merely accompanies is in Shadowing That Actually Teaches.

The first night call a new starter takes should be a success. The rota can arrange that by making sure a success is possible. That takes access that works, a runbook that is right, and a secondary who answers. A first call that fails because the new starter lacked a permission teaches them that the night is a trap. That lesson is very hard to unteach. Set the first one up to go well. It is the cheapest training the desk will ever buy.

The Manager Who Is in It

The lead takes a full turn on the rota, in the same role rotation as everyone else, and the lead's week is not lighter. This is the rule that makes the others believable. A lead who writes the swap rule, the holiday rule and the bad-week rule and then lives inside them is a lead whose rules are trusted. A lead who writes them for other people is a lead whose rules are a policy, and policies get the compliance they deserve. Omar had left himself off the Stonebridge rota, not out of malice but because he was "always reachable anyway", which is the sentence that precedes every permanent secondary.

There is one exception, and it is a trap. A lead who, instead of taking a full turn, offers to be the secondary every week has put themselves on the rota for fifty-two weeks a year in a light role. That sounds generous and is a slow way to burn out while the team feels guilty about it. The lead takes primary weeks and secondary weeks like everyone else. If the lead genuinely cannot carry the phone at all, for a reason that would apply to anyone in that role, the honest thing is to say so. In that case, remove the lead from the rota, and count the headcount without them. A lead who is sometimes on the rota and sometimes not, depending on the month, is on nobody's calendar and in everybody's resentment.

Publishing It Far Ahead

The rota is published at least a quarter ahead, and two quarters is better. It is published in one calendar that is the only truth, with the holiday weeks assigned first. A rota published on Friday for Monday, as Omar's was, cannot be accepted by anyone, because nobody can plan anything against it. It can only be reacted to, and reaction is what the three replies were. A rota published in March for July to September lets people book leave against it, trade weeks early, and see that the count is even before anyone has to argue that it is not. The coverage calendar that holds it, and the rule that it is the only place a coverage question is answered, is in The Coverage Calendar and the Single Point of Failure.

Far ahead needs one more rule, which is that the published rota is not edited by the lead inside a fortnight of a week starting. Changes inside that window happen by swap, between the people involved, written in the calendar by them. The lead edits the rota at the quarterly rebuild and when someone joins or leaves. This rule protects the rota from the thing that kills most of them. That is a lead who keeps "just tweaking" it in response to whoever spoke last. Eventually, nobody believes the calendar and everyone checks the phone on Monday to see whether it is theirs.

Handing the Phone Over

The week ends with a handover, on Monday morning at a fixed time. The outgoing holder tells the incoming one three things: what is still open from the week, what broke and how it was fixed, and anything that looks like it might break again. The handover takes ten minutes. It is done in person or by voice when it can be, and it is written in the on-call log either way. A phone that changes hands silently carries the week's history away with it. The incoming holder discovers at two in the morning that the same render queue failed last Thursday and nobody mentioned it. The shift handover is a discipline the desk already has for daytime, in The Shift Handover. The on-call handover is the same discipline on a Monday.

Every call the holder took during the week is a ticket, raised at the time or first thing after, and the holder's name is on it. Where the desk's tool has claim-based ownership, as QuerySolv does, the night's tickets show on Monday morning who held each one. In that setup, the handover starts from the queue rather than from memory. The week's load is visible to the lead without anyone being asked how their week was. The ticket itself, and the rule that it is raised before anything else is done, belong to the article on what counts as a call. For the rota, it is enough that the handover is a fixed moment, in the calendar, and that the phone is physically or logically passed at it rather than drifting.

A Short War Story: Six Weeks In at Northgate Retail

Northgate Retail's desk of four put Jonah, who had been there six weeks, on primary for the spring public-holiday weekend. That was because, as the lead said at the time, everyone else had plans and Jonah had said he did not mind. Nobody had checked that Jonah's account could reach the till management system, because nobody had thought of the till system as a night thing. Nobody was named as his secondary, because the rota's secondary column had never been filled in. On the Saturday morning the tills at the flagship store stopped taking card payments at 09:40. The store manager rang the number. Jonah spent fifty minutes discovering that the fix needed a permission he did not have. He then spent forty more ringing colleagues who had, reasonably, gone away for the weekend. Farah, the most senior technician, answered from a motorway services at 11:15 and fixed it remotely in six minutes. The store's own estimate was ninety minutes of cash-only trading on its busiest morning of the quarter. Jonah handed in his notice in the summer. He said in his exit conversation that he had decided the job was not for him on that Saturday. The lead's note in the review said the rota had cost a new technician and a store's morning to save four people a conversation about their plans.

The Rota Rules

The sheet below is the one Omar wrote the following week, with the five of them in the room. It has governed the Stonebridge rota since. It is one page on purpose: the rules a rota needs are few, and a rota with many rules is a rota nobody has read. Fill in the blanks, and agree it with the people on the rota rather than announcing it to them. Put the date on it, and keep it beside the calendar. Change it at the quarterly rebuild and only then.

ON-CALL ROTA RULES — ONE PAGE
Desk: ______________________   Agreed by the rota members on: ____________   Model: ______________

1. FREQUENCY
   People on the rota: ____   Turn: one week in ____ (primary), one week in ____ (secondary)
   Headcount used is after leave and excludes anyone not yet cleared for the phone.
   If the lived frequency falls below one week in ____, the model is reviewed.

2. SWAPS
   Like-for-like swaps need no approval. The two people agree, change the calendar, and tell the lead.
   A swap is a trade: the week taken is repaid with a week given, agreed at the time.
   A swap into a public-holiday week is a favour; the holiday rotation continues as if it had not happened.
   No swap ledger is kept. The calendar is the only record.

3. HOLIDAYS AND LEAVE
   Nobody is on call during their own leave or on the night before it starts.
   Public-holiday weeks are assigned first, on their own rotation: ______________________
   The rota is published before leave is booked; leave is booked against the rota.

4. THE WEEK AFTER A BAD WEEK
   A bad week is: ____ or more calls, or any single call longer than ____ hours.
   After a bad week the person takes the lightest slot next cycle; the lead reshuffles and announces it.
   The morning after a night call is protected (see the on-call agreement).

5. NEW STARTERS
   Cycles 1 and 2: secondary to an experienced primary.   Cycle 3: primary with an experienced secondary.
   Before the first primary week: all night-time access tested; runbook walked through; route and
   definition known; secondary named. The first solo week is never a public-holiday week.

6. THE LEAD
   The lead takes primary and secondary weeks in the same rotation as everyone else.
   The lead is never the standing secondary.

7. PUBLISHING
   Published ____ quarters ahead, in the coverage calendar, which is the only source of truth.
   The lead edits the rota only at the quarterly rebuild or when someone joins or leaves.
   Inside two weeks of a week starting, changes happen by swap only.

8. HANDOVER
   Monday at ______: open items, what broke and how it was fixed, what might break again.
   Written in the on-call log. Every call of the week is a ticket with the holder's name on it.

Omar rebuilt the rota on the Tuesday with the holiday weeks assigned first and Jess as secondary for two cycles. Rita's wedding week moved by a trade with Dev before the rota was even published. Omar put his own name in the rotation in full. The rota went out for the quarter after next, which gave everyone eleven weeks to book leave against it. Kwame, who had the holiday weeks for three years, got neither of them. He did not say anything about it, which was the first time in three years he had not needed to.

Frequently Asked Questions