Handling leave and swaps without rebuilding the whole schedule

Every chief resident and head nurse knows the pattern. You spend an evening building a balanced month, publish it, and within two days you have a sick child, a conference, a wedding and two people who want to trade weekends. The temptation is either to say no to everything or to tear the schedule up and start again. Both are expensive. This guide describes a middle path: a few habits before publishing, and a disciplined way to make small repairs afterwards.

Collect leave early, with a deadline

Most of the pain of a mid-month change comes from leave that was known weeks in advance but never written down. A clear intake process removes a large share of it.

• Set a request deadline well before you start drafting, for example the 10th of the month before. Announce it in the same place every time.
• Use one channel. A shared form or sheet beats messages scattered across chat groups and hallway conversations. If it is not in the list by the deadline, it is a swap, not a leave request.
• Separate hard and soft requests. Approved annual leave, exams and courses are hard blocks. "I would prefer not to work the 14th" is a preference. Treat them differently when drafting.
• Ask for the days after, too. Someone returning from a night flight on Sunday should not be on call that Sunday night. Capture that as part of the leave.
• Publish the leave list with the rota so everyone can see why the pattern looks the way it does.

When leave is known up front, the draft can spread the remaining calls fairly from the start. Our guide to making a fair on-call schedule for residents covers how to balance totals and weekends once the blocks are in.

Lock what is published

Once a rota is published, people book childcare, travel and second jobs around it. A change that looks small to you can be large for them. Make the published version the reference point:

• Mark it clearly as the published version with a date, for example "v1, published 20 September".
• Do not regenerate or re-balance the whole month after publishing. Any change should touch as few people and days as possible.
• Allow changes through swaps or coordinator-led cover only, never by quietly editing a cell.
• Freeze the past. Days that have already been worked are a record, not a plan, and should not be edited except to correct what really happened.

Local repair instead of a rebuild

When a gap appears, the aim is to close it by moving the smallest number of shifts. Work through these options in order:

1. Direct swap pair. Two people exchange one shift each. Only two cells change, and each person's total stays the same.
2. Like-for-like swap. Prefer trading a weekday call for a weekday call, a weekend for a weekend, a night for a night. A Saturday traded for a Tuesday silently shifts weekend load from one person to another.
3. Swap within the same week or fortnight where possible, so the change does not ripple into the next month's balance.
4. Cover with payback. If no swap exists, someone covers and is owed a shift later. Record the debt so it is actually repaid.
5. Three-way swap. A gives to B, B gives to C, C gives to A. Useful when no direct pair works, but check each of the three people separately.

Only if several people are out at once, for example during an outbreak, is it worth re-drafting the remaining weeks. Even then, keep the days already worked and the next few days fixed, and redraft from there.

A swap request checklist

A swap that looks fine on the face of it can break a rest rule or a skill mix two days later. Before approving, check:

• Both people agree, in writing, in the agreed channel.
• Qualification and grade match. A junior cannot take a slot that needs a senior, or a nurse without the required competency cannot cover a specialist unit.
• Rest after call or nights is still respected for both people, looking at the day before and the day after each new shift. See rest after night shift and call for how to think about this; check your own local rules for the exact limits.
• No back-to-back calls or too many in a row are created for either person.
• Weekend balance. If a weekend shift moves to someone else, their weekend count goes up. Is that still within your agreed range?
• Leave and blocked days of the person taking the shift are not overlapped.
• Team cover on the day is still sufficient, including the minimum number of experienced staff.
• The change is recorded in the rota and in the change log, and the updated version is shared.

Worked example: one Saturday, one swap

A team of 10 residents covers a 30-day month with one call per day, so 30 calls in total, or 3 per person. The month starts on a Sunday, so it has 9 weekend days and 9 weekend calls: nine residents get one weekend call and one resident gets none. The coordinator tracks weekend calls across months to even this out.

After publishing, Dr. Aksoy asks for Saturday the 14th off for a family event. Dr. Demir offers to take it in exchange for Aksoy's Tuesday the 17th call. Here are the relevant days before the swap:

Demir takes Saturday the 14th and Aksoy takes Demir's Tuesday the 17th. That is a direct swap pair: two cells change, nobody else is touched. Before the swap, each of them has one weekend call this month (Demir's is on Sunday the 29th). Now run the checklist:

• Rest: Demir has nothing on Friday 13th or Sunday 15th, so Saturday is clear. Aksoy has nothing on Monday 16th or Wednesday 18th, so Tuesday is clear.
• Totals: each still has 3 calls for the month. Unchanged.
• Weekend balance: this is not like-for-like. Aksoy goes from 1 weekend call to 0 this month; Demir goes from 1 to 2.

The swap is safe, but it moves weekend load. The coordinator approves it and records it. If both would normally get one weekend call next month, the coordinator gives Aksoy two and Demir none. Over the two months both end up with the same number: Aksoy 0 + 2 = 2 and Demir 2 + 0 = 2. That is the whole point of tracking. Without the record, the imbalance would simply disappear from memory.

Keep an audit trail

A change log protects everyone: the coordinator when questions come up, and staff when there is a dispute about who was on. It does not need to be elaborate. For each change, record:

• Date of the change and who approved it.
• The shift or shifts affected (date, shift type, unit).
• Who was originally assigned and who is now assigned.
• The reason category: leave, sickness, swap, cover with payback, correction.
• Any debt created: "Demir owed one weekday by Aksoy" or "Kaya owed one weekend".

Number your published versions (v1, v2, v3) and share the latest one in a single place. When a question comes in, the log tells you which version someone was looking at.

Keep fairness counts honest

The most common way a fair schedule turns unfair is that the counts are kept on the plan rather than on what happened. If the spreadsheet still credits Aksoy with the Saturday she swapped away, she looks overloaded on weekends and Demir looks underloaded, and next month's draft will push weekends in exactly the wrong direction.

• Count the shift the person actually worked, not the one they were originally assigned.
• Keep separate counts for totals, weekends, nights and holidays. A swap can be neutral on one and not on another, as the example showed.
• Carry counts across months. Fairness over a single month is often impossible with small teams; fairness over a quarter is realistic.
• Count sick cover as worked for the person who covered it. Whether the absent person "owes" anything is a local policy decision; write it down and apply it consistently.
• Review the counts monthly and share them. Transparency settles most arguments before they start.

If you are building your nursing rota on a template, the same idea applies to night and weekend tallies; see the nurse shift schedule template guide. And if you want a quick, balanced starting point for a small team, the free call schedule generator runs entirely in your browser, with nothing sent to a server.