On this page
- Decide what counts before you count
- Weekend arithmetic: what is possible
- Even it out over a quarter, not a month
- Holidays: sort them into tiers
- Rotating holiday groups
- Weighted points: when simple counts are not enough
- Part-time staff: pro rata, stated in advance
- Keep a yearly ledger and publish it
- Checklist
- Sources
Decide what counts before you count
Most weekend disputes start with a definition nobody wrote down. Is a Friday night a weekend shift? Does a Sunday night that ends on Monday morning count? Is a lone Saturday "a weekend" or "half a weekend"? Settle these before you build anything, and write the answers at the top of the rota.
- Weekend window. A simple, common definition: any work between 00:01 on Saturday and 23:59 on Sunday. That is the definition the 2016 contract for resident doctors in England uses for its weekend limits.
- Unit of counting. Count weekends touched, not shifts. One Saturday shift costs a person almost as much of their weekend as two shifts do.
- Friday nights. If a Friday night is as disruptive as a Saturday in your unit, count it as weekend work, or give it its own counter.
- Holiday window. Decide whether "Christmas" means 25 December only, or also the night before. Most teams treat Christmas Eve night and New Year's Eve night as holiday shifts.
Weekend arithmetic: what is possible
Weekend frequency is decided by headcount, not by cleverness. Work out the number before promising anyone "one in three".
Example: 12 nurses, and each weekend needs 4 people (two on days, two on nights), each working the whole weekend. A year has 52 weekends, so that is 52 × 4 = 208 weekend slots. Divided by 12 people, that is about 17.3 weekends each, or roughly 1 in 3.
| Team size | Weekends each per year | Frequency |
|---|---|---|
| 8 | 26 | 1 in 2 |
| 12 | about 17.3 | about 1 in 3 |
| 16 | 13 | 1 in 4 |
If the team splits weekends (Saturday for one person, Sunday for another), you fill the same slots with twice as many people touching a weekend, and everyone loses more weekends. That is why keeping weekends whole is the single most effective fairness rule. Your contract may also cap frequency: in England, the 2016 resident doctor contract asks employers to take all reasonable steps to avoid more than 1 weekend in 3, with an absolute limit of 1 in 2.
Even it out over a quarter, not a month
One month rarely divides evenly. With 12 people and 4 slots per weekend, a 13-week quarter has 52 slots: 4 people work 5 weekends and 8 people work 4. Next quarter, the four who did 5 move to the back of the queue. Over a year, everyone ends within one weekend of each other.
The same idea works for any team: calculate the fair share (slots ÷ people), let the remainder fall on different people each period, and record who carried the extra. Without that record, the extras quietly land on the same reliable people every time.
Holidays: sort them into tiers
Holidays are not equal. Working Christmas Day is not the same as working a spring bank holiday. Sort your local holiday list into tiers and balance each tier separately over the year:
| Tier | Examples | How to balance |
|---|---|---|
| Major | Christmas Day, Christmas Eve night, New Year's Eve night, New Year's Day; national or religious holidays your team cares most about | Rotate yearly by group; nobody works the same major holiday two years running if avoidable |
| Standard | Other public holidays | Count per person over the year; aim for equal counts |
| Peak leave | School holiday weeks, the week between Christmas and New Year | Rotate leave approval priority, not just shifts |
For multicultural teams, ask people which holidays matter to them. Someone who does not celebrate Christmas may happily work it in exchange for their own festival off. That kind of swap is fair as long as it is voluntary and recorded.
Rotating holiday groups
The simplest system for major holidays: split the team into two groups.
- Year 1: Group A works Christmas, Group B works New Year.
- Year 2: they swap.
For larger teams, use three groups across Christmas, New Year and one more major holiday, so each person works one of the three each year. Publish the groups at the start of the year so people can plan travel, and handle starters and leavers by placing them in the group with the fewest people.
If your contract gives a day off in lieu for holiday work, put that day on the rota at the same time. For example, the 2016 contract in England gives resident doctors a standard working day off in lieu when they work, or are on call, on a public holiday.
Weighted points: when simple counts are not enough
When shifts differ a lot in how much people dislike them, give each type a weight and balance the total. A starting point you can adapt:
| Shift type | Points |
|---|---|
| Weekday day | 1 |
| Weekday night | 1.5 |
| Friday night | 2 |
| Saturday or Sunday shift | 2 |
| Standard public holiday | 3 |
| Major holiday | 4 |
Two warnings. First, keep the table short. Five or six categories is plenty; more and nobody can check the totals. Second, points should support the separate counts, not replace them. Someone with the same points total but three major holidays in a row will still feel hard done by, so publish both the points and the plain counts.
Part-time staff: pro rata, stated in advance
Part-time staff should normally carry weekends and holidays in proportion to their hours. A nurse on 0.6 of full time would do about 60% of a full-timer's weekends: in the 12-person example, about 10 instead of 17. Write the rule down. Without it, part-timers either end up on almost every weekend (because they are "around") or almost none (because they "only work weekdays"), and both cause resentment.
Keep a yearly ledger and publish it
The ledger is what makes fairness checkable. One row per person, with these columns, updated each time a rota is published or a swap is made:
- Weekends worked this year, and the extra weekends carried
- Major holidays worked (with dates), and standard holidays
- Nights, if you balance them too
- Points total, if you use weights
- FTE, so pro rata targets are visible
Share it with the whole team. Once people can see the numbers, most "why me again?" questions answer themselves, and the person who builds the rota stops being the one who has to defend it. Swaps should update the ledger too, so a traded weekend counts for the person who actually worked it. Our guide to leave and swaps covers how to keep counts honest after publishing.
Checklist
- The weekend and holiday definitions are written at the top of the rota.
- The weekend frequency your headcount allows has been calculated and shared.
- Weekends are kept whole wherever possible.
- Major holidays rotate by group, and the groups are published for the year.
- Part-time targets are pro rata and written down.
- The ledger is up to date after every rota and every swap.
For on-call rotas, the same method is applied to residents in how to make a fair on-call schedule and to 24-hour call in how to make a fair 24-hour call schedule. For nursing patterns that fix weekends in advance, see 12-hour nursing shift patterns explained. To draft a balanced call list in seconds, try the free call schedule generator; it runs in your browser and your data stays on your device.
Sources
- BMA, Resident doctors' handbook on the 2016 contract: weekend definition (00:01 Saturday to 23:59 Sunday), the 1 in 3 and 1 in 2 weekend limits, and the day off in lieu for public holiday work.
Keep the ledger without the spreadsheet
FasterShift is an AI-powered scheduler for healthcare teams. Tell it "share weekends evenly" or "whoever worked Christmas is off New Year", and it builds the rota with weekend and holiday counts per person, carried across months. Try FasterShift free for 14 days — no card needed. After the trial, plans start from US$12 per team per month.
Get new guides by email
Practical rota and shift scheduling tips plus product news; no spam.