Online Tool Store
· 5 min read
Plan a Staff Shift Rota Without a Spreadsheet
Manesh Jayawardhana
CIO & Co-founder
Six people, seven days, two shifts a day, and three of them have said they can’t do Thursdays. You’ve drawn this on paper twice, discovered a gap on Saturday afternoon both times, and you’re now considering just asking who wants what and dealing with the mess afterwards.
Scheduling a small team is a genuinely awkward problem — big enough that you can’t hold it in your head, small enough that a proper workforce management system is comical overkill.
What a rota actually has to do
Three things, in order of importance.
Cover every slot. The point of the rota is that someone is on shift for every hour the business is open. Gaps are the failure mode that costs money.
Distribute fairly. Not equally — people have different contracted hours — but transparently. Most rota disputes are about perceived unfairness in who gets weekends and evenings, and a visible grid defuses more of that than any amount of explaining.
Respect the constraints. Availability, minimum rest between shifts, maximum hours, and whatever your local employment rules require. These are hard limits, not preferences.
Everything else — preferences, pairing people who work well together, keeping the new starter with someone experienced — is optimisation on top of those three.
Why people get stuck here
- The grid is hard to hold mentally. Seven days by two shifts by six people is 84 cells, and your brain will drop one.
- Availability changes weekly. A rota built on last month’s constraints is wrong by the time it’s published.
- Fairness is invisible in a list. Written as a list of shifts per person, nobody can see the pattern. Written as a grid, everyone can.
- Swaps aren’t tracked. Two people agree a swap in a message thread and the published rota never reflects it.
- Published too late. People need notice to arrange their lives, and short notice is the main driver of last-minute call-offs.
What a good rota looks like
A grid you can scan for holes
Days across, people down, shifts in the cells. An empty cell where cover is needed should be immediately obvious — that’s the whole reason to use a grid rather than a list.
Visible totals per person
Hours per person per week, shown alongside the grid. It answers the fairness question before anyone asks it.
Published with real notice
A week ahead is the minimum most people need; two is better. Some jurisdictions have legal requirements about scheduling notice, and it’s worth knowing yours.
| Problem | Where It Shows Up | Fix |
|---|---|---|
| Uncovered slot | Empty cell in the grid | Check the grid before publishing, not after |
| Uneven weekends | Weekend column pattern | Rotate weekend duty explicitly |
| Back-to-back shifts | Late shift then early next day | Check rest gaps between consecutive days |
| Unequal hours | Per-person totals | Compare totals against contracted hours |
Common mistakes to avoid
- Building the rota before collecting availability. You’ll rebuild it. Collect first, with a deadline.
- Scheduling a close followed by an open. It’s legal in many places and it’s still how you burn people out.
- Giving the same person every weekend. Even if they volunteered, rotate it — willingness in January isn’t willingness in June.
- Publishing without a swap process. People will need to swap; decide in advance how that gets recorded and approved.
- Forgetting holidays and known absences. Check them before you start rather than rebuilding around them afterwards.
How to do it with Shift Rota Planner
Online Tool Store’s Shift Rota Planner gives you a simple shift schedule grid in your browser — staff names and hours stay on your own device, which matters for what is, after all, employee data.
- Collect availability from everyone with a stated deadline before you start building.
- Set up the grid with your days and shift slots.
- Fill the hardest-to-cover slots first — usually weekends and early mornings — while you still have options.
- Fill the easy slots afterwards, then scan the whole grid for empty cells.
- Check per-person totals against contracted hours and against last week’s pattern.
- Publish with as much notice as you can, and record any subsequent swap on the grid rather than in a message thread.
The Weekly Planner and the Timesheet Calculator cover the steps either side of the rota itself.
Frequently asked questions
How far ahead should I publish a rota?
At least a week, ideally two. Beyond the goodwill, some jurisdictions have predictive scheduling laws requiring specific notice periods and compensation for late changes — check what applies where you operate.
How do I handle shift swaps fairly?
Set one rule and apply it consistently: swaps must be between people qualified for the slot, agreed by both, and recorded on the published rota by you rather than between themselves. The recording step is the one that gets skipped and the one that causes the no-show.
Is my staff data uploaded anywhere?
No. The planner runs entirely in your browser with no uploads or accounts, so names, hours, and availability stay on the machine you’re working on.
Final thought
Fill the hard slots first and check the grid for holes before you publish. Almost every rota emergency is a gap that was visible on Tuesday and noticed on Saturday.