Fair Rota System: How to Build a Rota You Can Prove Is Fair
A fair rota system is one where the shifts nobody wants (weekends, late closes, nights, bank holidays and last-minute cover) are shared out in proportion to people's hours, and where you can show that they are. Almost every manager believes their rota is fair. Very few could prove it if a team member asked, and the person asking usually has a point.
The tips you will find elsewhere are sound: share rotas early, rotate the bad shifts, listen to preferences. This guide adds the part that makes them stick: a simple tally that turns "it feels unfair" into numbers, a worked example, and the rules that keep it fair after the next sick day.
The short answer
Fair does not mean identical. It means everyone carries their share of the unpopular shifts, relative to their contracted hours. Count those shifts per person over a rolling 12 weeks, rebalance anyone more than about 20% over their share, rotate bank holidays year to year, and publish the rota at least two weeks ahead.
What Makes a Rota Fair (and What Does Not)
Three things people mean when they say a rota is fair:
- Share. Weekends, closes, nights and bank holidays are spread across the team, not concentrated on whoever is newest, most junior or least likely to complain.
- Predictability. The rota is out early enough that people can plan their lives, and it does not keep changing.
- Consistency. The same rules apply to everyone. If one person's preference is honoured, everyone else's gets the same consideration.
What fair does not mean is everyone working the same hours. A part-timer on 16 hours should not do as many Saturdays as a full-timer on 40. The fair share is proportional to contracted hours, which is why you need to count rather than eyeball it.
The 12-Week Fairness Tally
Pick the shift types your team cares about. For most hospitality and retail teams that is weekends, closes and bank holidays. For care and security it is nights. Then add one column most people forget: short-notice changes, meaning shifts moved or added with less than a week's warning. Whoever absorbs those is carrying a cost the rota does not show.
Count each one per person over a rolling 12 weeks. Twelve weeks is long enough to smooth out holidays and sickness, and short enough that a problem gets fixed this quarter rather than next year.
Worked example: a five-person café team
Five full-time staff on the same contracted hours. Over 12 weeks the café needed three people on each weekend day (72 weekend shifts), one close every day (84 closes), two people on each of two bank holidays (4 shifts), and made 7 short-notice changes.
| Person | Weekend shifts | Closes | Bank holidays | Short-notice changes |
|---|---|---|---|---|
| Amy | 19 | 12 | 1 | 1 |
| Ben | 15 | 17 | 0 | 0 |
| Chloe | 14 | 16 | 1 | 5 |
| Dev | 12 | 24 | 2 | 1 |
| Ella | 12 | 15 | 0 | 0 |
| Fair share each | 72 ÷ 5 = 14.4 | 84 ÷ 5 = 16.8 | 4 ÷ 5 = 0.8 | 7 ÷ 5 = 1.4 |
Divide each person's count by the fair share and anything above about 1.2 (20% over) is worth acting on:
- Amy did 19 weekend shifts against a share of 14.4: 1.32, so 32% over. Next quarter she gets fewer weekends.
- Dev did 24 closes against 16.8: 1.43, the biggest gap in the table, and he worked both bank holidays. He has become "the closer" without anyone deciding it.
- Chloe took 5 of the 7 short-notice changes. She is the one who always says yes. That is generosity until it becomes resentment, and it is invisible on a normal rota.
- Ben and Ella are at or under their shares everywhere and worked no bank holidays, so the next two should go to them.
None of this needs special software. A spreadsheet with one row per person and one column per shift type, filled in from your published rotas, takes ten minutes a month.
Part-time staff
When contracts differ, work out each person's fair share from their hours, not a straight split:
Fair share = total shifts of that type × (their contracted hours ÷ the team's total contracted hours)
So if a 16-hour part-timer works in a team with 176 contracted hours in total, their fair share of 72 weekend shifts is 72 × 16 ÷ 176 = 6.5, not 14.4.
Rules for Allocating the Shifts Nobody Wants
- Volunteers first, then rotation. Some people genuinely prefer weekends or nights. Let them take them, then rotate the rest in a fixed order so nobody is picked by mood.
- Rotate bank holidays year on year. Whoever works Christmas Day this year is off it next year. Write it down; nobody remembers who did what two Decembers ago.
- Keep a cover order for last-minute gaps. Ask people in turn rather than calling whoever usually answers. That is how you stop a Chloe column building up.
- Record preferences in the same place for everyone. If one person's childcare constraint is honoured, everyone's fixed commitments get the same hearing.
- Pay a premium if you can. A small uplift for nights or Sundays turns an unpopular shift into one some people choose, which makes the rest of the rota easier to balance.
- Check swaps against the tally. A shift swap policy keeps flexibility from quietly moving all the bad shifts onto the same few people.
Signs Your Rota Has Drifted
Rotas rarely become unfair in one go. They drift, one favour and one sick day at a time. These are the early signs, usually visible months before anyone complains:
- Swap requests keep coming from the same shift. If Sunday closes generate most of your swap requests, the people rostered on them are telling you something.
- The same person always covers. Look back at the last ten gaps you filled at short notice. If one name appears five times, that is your Chloe.
- Nobody new ever gets a Saturday off. Long-serving staff accumulating the good shifts is common and rarely discussed, until a new starter leaves.
- The rota goes out later each month. Late rotas usually mean the manager is negotiating it person by person, which is where inconsistency comes from.
- You cannot answer "why me?" If someone asks why they are on another weekend and the honest answer is "you were free", the system has stopped being a system.
Any one of these is a prompt to fill in the tally for the last 12 weeks. It usually confirms the hunch within a few minutes, and gives you numbers to explain the fix.
How Far in Advance Should You Publish a Rota?
At present, UK law does not set a general notice period for rotas; a contract can, and many do. That is changing for some workers. The Employment Rights Act 2025 introduces a right to reasonable notice of shifts and payment when shifts are cancelled, moved or cut short at short notice, aimed at zero hours and similar contracts. GOV.UK's guidance for employers says these zero hours measures are not yet in force, and the government's timeline lists them for 2027, with the exact timings to be confirmed after consultation.
Do not wait for the law. Two weeks ahead is a sensible minimum for most small teams, and four is better if you can forecast demand. Every change after publication goes in the short-notice column of your tally, which is a useful discipline in itself.
What the Law Does Require of a Rota
There is no prescribed rota format. What the Working Time Regulations set are the limits any rota has to respect:
- 11 hours' rest between working days (12 for under-18s). A close followed by an open is the usual breach.
- Weekly rest of 24 hours in each 7 days, or 48 hours in each 14 (48 hours a week for under-18s).
- A 20-minute break for shifts over 6 hours (30 minutes over 4.5 hours for under-18s).
- 48 hours a week on average, normally averaged over 17 weeks, unless the worker has opted out.
- The minimum wage for every hour worked, including extra hours picked up through cover and swaps.
Our Working Time Regulations guide covers each of these in detail, and the step-by-step guide to creating a staff rota walks through building one from scratch.
Running a Fair Rota in TimeTally
To be clear about what software does and does not do here: TimeTally does not count weekends or closes per person for you, so the fairness tally above stays a ten-minute monthly job. What the TimeTally rota planner does is take away the things that make rotas unfair by accident:
- Leave on the rota. Approved holiday shows on the same grid you build shifts on, so you do not roster someone who is off and then hand the gap to whoever answers the phone.
- Publish early, and tell people. Publish the week (or several weeks) and send each person an email listing their shifts. Staff see their rota in the staff rota app.
- Copy a fair week forward. Once a week is balanced, copy it onto the following weeks. Days that already have a shift are skipped, never overwritten.
- Alerts you set. Flag anyone rostered over a number of hours in a week (useful for the 48-hour average), anyone under a number of hours you choose, or any day with fewer staff than you need.
- Hours and wage cost per day on the grid (cost is shown to admins who can see pay, when Pay is switched on), so balancing the rota does not quietly blow the wage budget.
- Shift swaps with approval. Staff ask a colleague, the colleague accepts, you approve, so you can check every swap against the tally.
If you want to start on paper first, our free staff rota template has the same grid layout.
“The app is simple to use, reliable, and makes managing holidays, absences, and staff records straightforward. The system has saved us a significant amount of administration time.”
Jordan Ingoe, CLI Manchester
TimeTallyA Rota Your Team Can See, Weeks Ahead
Build the week with leave in view, publish it to your team's phones, and set alerts for the hours and cover you care about. £3 per employee per month.
Free for 14 days • No credit card required
Key Takeaways
- A fair rota system shares unpopular shifts in proportion to contracted hours; it does not give everyone identical hours
- Count weekends, closes, nights, bank holidays and short-notice changes per person over a rolling 12 weeks
- Act on anyone more than about 20% over their fair share
- Rotate bank holidays year on year and keep a fixed order for last-minute cover
- There is no general legal notice period for rotas yet; reasonable notice of shifts is coming under the Employment Rights Act 2025
- Whatever the format, a rota must respect rest breaks, weekly rest, the 48-hour average and the minimum wage
Frequently Asked Questions
What is the legal requirement for rotas in the UK?
There is no law that says how a rota must be written. What the law sets is what a rota must not do: workers are entitled to 11 hours' rest between working days, a 20-minute break if they work more than 6 hours, weekly rest, and no more than 48 hours a week on average unless they opt out. Under-18s have stricter limits, and everyone must be paid at least the minimum wage for the hours they work.
How far in advance should you have a rota?
There is currently no general legal notice period for rotas, though a contract can set one. The Employment Rights Act 2025 introduces a right to reasonable notice of shifts, and the government's timeline lists it for 2027, with timings to be confirmed after consultation. In practice, two weeks is a sensible minimum for most teams.
What are some examples of unfair rota arrangements at work?
The same people always working Sundays or closing, favourites getting the Saturdays off, last-minute changes always landing on whoever says yes, bank holidays going to the newest staff every year, and rotas published so late that nobody can plan around them. Most unfair rotas are not deliberate; they are what happens when nobody counts.
What is the best rota software in the UK?
It depends on what else you need it to do. Some tools are built purely for rotas; others, like TimeTally, put the rota, timesheets and leave in one app, so you can see who is on holiday while you build the week. Try two or three on a free trial with your real team before deciding.
Sources
- Rest breaks at work — GOV.UK (breaks, daily and weekly rest, young workers)
- Maximum weekly working hours — GOV.UK
- Zero hours contracts: guidance for employers — GOV.UK
- Plan to Make Work Pay and Employment Rights Act: timeline update — GOV.UK
- Employment Rights Act 2025, section 2 (notice of shifts) — legislation.gov.uk
