Rotas sorted in minutes, not hours
We handle the hard bit. You approve and publish. Your team gets notified instantly.
We handle the hard bit. You approve and publish. Your team gets notified instantly.
A consultant on-call rota is a different beast from a junior doctor rota. The contract is different (2003, not 2016), the unit of work is different (Programmed Activities, not shifts), and the design pressure is different — you’re not trying to stay inside rigid hour limits so much as balancing frequency, fairness, and the categorisation of what “being on-call” actually means for each consultant.
This post walks through the main on-call rota structures specialty teams use, what each one is good for, and the trade-offs worth thinking about before you pick one.
Disclaimer: This article is general guidance on common on-call rota structures, not advice on any specific consultant’s contract or pay. Job planning, on-call categorisation, and availability supplements are determined by local agreement between the consultant and the employing trust under Schedule 16 of the 2003 Terms and Conditions of Service. For decisions on a specific rota or job plan, refer to your medical staffing team, clinical director, and where needed the BMA. Rapid Rota accepts no liability for decisions made in reliance on this article.
Before the structures themselves, a quick reminder of the building blocks. Skip this section if you’re already across them.
Programmed Activities (PAs). The 2003 consultant contract divides the working week into PAs of 4 hours each. A full-time job plan is typically 10 PAs, commonly split 7.5 Direct Clinical Care (DCC) and 2.5 Supporting Professional Activities (SPA), though the mix varies by specialty.
On-call categorisation. On-call duties are categorised A or B based on the typical nature of the response:
The category is set by a prospective assessment from the employing trust, based on the typical nature of calls the consultant receives during on-call periods. It isn’t the consultant’s choice, and it isn’t set by the individual calls — it’s set by the pattern.
On-Call Availability Supplement (OCAS). Consultants on an on-call rota receive a supplement on top of basic salary, calculated by rota frequency and category:
| Frequency | Category A | Category B |
|---|---|---|
| High (1 in 1 to 1 in 4) | 8% | 3% |
| Medium (1 in 5 to 1 in 8) | 5% | 2% |
| Low (1 in 9 or less) | 3% | 1% |
The percentage is of full-time basic salary. Part-time consultants who participate on the same basis as full-time colleagues receive the full supplement; different participation gets the equivalent frequency supplement.
Work arising from on-call. Under Schedule 5 of the 2003 TCS, unpredictable emergency work that arises from on-call duties and happens outside a scheduled PA is separately recognised. Predictable work that follows from on-call (e.g. a post-take ward round) is typically built into the job plan as PAs.
“1 in N” is the industry shorthand for how often each consultant in the team takes the on-call bleep. A 1 in 8 rota means there are 8 consultants taking a share, and each one is on-call one week out of every eight.
The number that “feels right” for a specialty varies, but the rough landscape:
There’s no “correct” N. The questions to ask are: is the team big enough to sustain the frequency you want without overstretching individuals? Is the workload during on-call compatible with the recovery period before the next one? And does the resulting OCAS band reflect the actual demand?
The simplest structure. A fixed rotation where each consultant takes on-call in turn, one after the other, indefinitely. Sheet of paper with names down one side and weeks across the top.
Good for: Small, stable teams. Everyone knows where they sit, everyone’s treated identically, administrative overhead is minimal.
Trade-offs: Inflexible. Any absence (leave, sickness, study) has to be absorbed by the team, usually by a swap that then cascades through the rota. Doesn’t naturally accommodate part-time working or differential commitments.
The team runs two rotas — one for Monday–Friday on-call, one for Saturday–Sunday — and a consultant’s weekday week doesn’t necessarily correspond to their weekend commitment.
Good for: Specialties where weekend workload is qualitatively different from weekday on-call (e.g. no elective backstop, reduced junior cover). Decoupling weekends lets the team think about weekend cover as its own problem rather than a tail on the weekday rota.
Trade-offs: More complex to administer, and fairness becomes harder to evaluate because you’re balancing two dimensions. Consultants can end up feeling they got a bad deal on one rota even if the other evens out. Needs visible accounting to stay fair.
Different on-call roles rotate separately. A consultant might be on post-take ward round one week, acute intake the next, and elective emergency cover a third. Each has its own rotation.
Good for: Larger specialties with distinct workstreams that can genuinely be separated. Lets each role be filled by someone prepared for it, rather than treating all on-call as interchangeable.
Trade-offs: Requires the team to be big enough to staff each zone meaningfully. Adds handover complexity — a consultant coming off acute intake may need to hand cases to whoever is now taking them. OCAS calculations become more complex because a consultant may be on multiple rotas with different frequencies, and the supplement has to be worked out accordingly.
Rather than each absence triggering a swap, leave and cover are factored in prospectively when the rota is designed. The rota is published knowing that, for example, Consultant A is on annual leave in week 17, and cover has already been assigned.
Good for: Teams where leave is booked well in advance and the rota is built to a 6 or 12-month horizon. Reduces the “firefighting” feel of handling absences one at a time.
Trade-offs: Requires earlier commitment from consultants about leave, which doesn’t always suit everyone. And unforeseen absences (sickness, emergencies) still need reactive cover, so you still need a swap or cross-cover mechanism — prospective cover just reduces the volume of ad hoc changes.
The team splits into those who cover acute on-call and those who cover longer-term or follow-up responsibilities (e.g. ward cover for in-patients under the specialty). Some consultants sit on both rotas; others only one.
Good for: Specialties where acute on-call and inpatient continuity are genuinely different jobs requiring different skills or sub-specialisation. Often seen in larger units where sub-specialty expertise matters.
Trade-offs: Can create a two-tier feel (“acute people” vs “ward people”) if not handled carefully. Makes cross-cover harder because the skill set doesn’t always transfer. Tends to require explicit governance around who can cover what.
Fairness in on-call rotas is less about treating everyone identically and more about treating everyone defensibly. A few dimensions worth thinking about explicitly:
Frequency. Is every consultant’s expected number of on-call periods per year broadly equivalent, adjusted for their contracted PAs? A full-time consultant doing 1 in 8 should expect roughly double the on-call weeks of a part-time consultant on a 1 in 16 equivalent.
Timing. Does the same consultant end up with the “bad” weeks (Christmas, school holidays, bank holidays)? A rolling pattern usually distributes these over years, but a new rota can inadvertently stack them on one person. Worth modelling before publication.
Weekends and nights. Category A night commitment is a distinct burden. If the rota is designed so some consultants get more Category A nights than others, that should be visible and agreed rather than an emergent property of the pattern.
Cross-cover exposure. When a colleague is off, who covers? If certain consultants are always the first call for cross-cover, that’s invisible work that should be accounted for in the overall fairness picture.
Two practical workload concerns come up repeatedly.
Recovery time. After an intensive on-call period — a run of disturbed nights, a complex post-take — the consultant needs time to recover. A rota that puts them straight back into a high-commitment elective week with no buffer is a fatigue and error risk. Good rotas schedule lighter PAs in the week following on-call where the team size allows.
Predictable vs. unpredictable work. Under the contract, predictable work arising from on-call (the post-take ward round, the follow-up clinic) should be built into the job plan as PAs. Unpredictable work is recognised separately under Schedule 5. When job plans don’t keep up with how on-call actually plays out — e.g. a post-take has grown from 2 to 3 hours — consultants end up absorbing extra work that isn’t contractually compensated. Worth reviewing annually.
Start with the team, not the rota. Who is available, at what commitment, with what constraints? A rota designed for the team you wish you had rarely survives contact with reality.
Map leave before you map on-call. The lowest-friction rota is one where leave has been factored in from the start — not bolted on after.
Make the OCAS implications visible. Consultants should understand what the frequency band means for their supplement, and changes should be flagged rather than discovered in the next pay slip.
Model the worst case. What does the rota look like if two consultants are off at the same time in the same week? If the answer is “we break” or “one person covers everything,” the rota is fragile. Usually worth designing one layer of resilience in from the start.
Review annually, minimum. Job plans are reviewed yearly under the contract, and the on-call rota should be reviewed on the same cycle. What worked a year ago may not still fit, especially if the team has grown, shrunk, or restructured.
Consultant on-call rotas are where spreadsheets age fastest. The interactions — PAs, on-call frequency, category, supplement, prospective cover, swap cascades — are hard to track by hand, and a change that looks small (one extra week of cover for a colleague on leave) can quietly shift a consultant’s frequency band and change their OCAS.
Purpose-built rota software tracks all of this in the same place, flags when changes move someone across a band, and produces the documentation job planning relies on. If you’re running a consultant team on a spreadsheet and the annual job planning round feels harder every year, that’s a signal worth acting on.
For the contract itself, the 2003 Terms and Conditions of Service for Consultants (England) is the authoritative source, and Schedule 16 is the specific section on on-call availability. NHS Employers’ consultant contract FAQs cover most of the common situations that come up when designing or revising rotas. The BMA’s consultant contract pages are useful for the consultant-facing view of the same rules.
For specialty-specific conventions — what frequency bands, what categorisation, what patterns are normal — your Royal College will usually have guidance, and the medical staffing team at your trust will know what neighbouring departments do.
Rapid Rota gives you the power to plan smarter, faster, and fairer.