Free Weekly Shift Schedule Template (Excel Rota)
A weekly rota with per-person shift counts and daily coverage totals, so you can see understaffed days before they happen. Free Excel download.
Most rota templates tell you who is working. Very few tell you whether that is enough.
The failure looks the same everywhere: the grid is full, every name has shifts, and then Thursday arrives with two people covering a job that needs four. Nobody spotted it because nothing in the sheet was counting.
This template adds a coverage row — the number of people on duty each day — directly under the rota.
Weekly Shift Schedule Template
A seven-day rota with per-person shift counts and a coverage total for every day, so thin days show up while you can still fix them.
- Seven-day grid, one row per person
- Shifts per person calculated automatically, ignoring Off
- Coverage total for each day, highlighted
- An Employees tab so names stay consistent
Prefer Google Sheets? Download the file, then in Sheets choose File → Import → Upload. Formulas and dropdowns carry over.
When the spreadsheet stops keeping up — usually somewhere past ten people — you can upload this exact file to SimplyPTO and it becomes a working team, with departments, allowances, and carryover already set. See how importing works.
How to use it
- Fill in the Employees tab first. Names typed directly into the rota drift — "Sam", "Sam O", "S. Okafor" — and any counting you do later breaks silently.
- Write shifts into the grid as free text:
09:00-17:00,Early,Late,Off. - Read the Shifts column for per-person totals and the On duty each day row for coverage.
The counting formula ignores blanks and the word Off, so marking a rest day explicitly does not inflate anyone's total:
=COUNTA(B4:H4)-COUNTIF(B4:H4,"Off")
Why the shift cells are free text
Dropdowns feel like the obvious answer and they are usually the wrong one for a rota.
Shift labels vary enormously between teams — start times, named shifts, split shifts, on-call, training, cover. A validation list broad enough to be useful is too long to pick from, and a list that is too narrow means people start typing around it. Within a fortnight you have Early, early, E, and 9-5 in the same column, and any counting is meaningless.
The template validates nothing in the shift cells and counts only what it can count reliably: whether a cell has something in it, and whether that something is Off. That is a deliberately low bar, and it is the reason the coverage row stays accurate.
The attendance tracker takes the opposite approach with a short coded list, because there the codes are the data.
Coverage is the number that matters
Fill a rota by asking "who is free?" and you get a schedule that looks complete and fails on the busy days. Fill it by asking "how many do I need on Thursday?" and the same information arrives in a useful order.
Work out your floor first:
| Team size | Minimum on duty | Can be away at once |
|---|---|---|
| 5 | 3 | 2 |
| 8 | 5 | 3 |
| 12 | 8 | 4 |
Then the question for any leave request stops being whether someone deserves the time and becomes whether the day still clears the floor. That is a far easier conversation, and a far more defensible one.
The team coverage calculator will work out your maximum-away figure, and — more usefully — whether your team's annual leave entitlement even fits inside your annual coverage capacity. For a lot of small teams it does not, which is worth knowing in January rather than discovering in December.
Predictive scheduling: publish early, change rarely
If you schedule hourly staff in retail, hospitality or food service, advance notice may not be optional.
Predictive scheduling laws — sometimes called fair workweek laws — exist in Oregon statewide and in cities including Seattle, New York, Chicago, Philadelphia, San Francisco and Los Angeles. The details vary, but the shape is consistent:
- Advance notice of the schedule, commonly 14 days
- Predictability pay owed when you change a published shift late
- Rest between shifts, with a premium owed for "clopening" patterns
- Good-faith estimate of hours given at hire
- Right to decline shifts added after publication
Two weeks of notice is a reasonable default even where nothing requires it. It is also the point at which a weekly spreadsheet starts to strain, because you are now maintaining a published version and a working version at the same time.
Where a rota spreadsheet stops working
A weekly grid is genuinely fine for a small, stable team. It stops being fine at recognisable moments:
- Leave lives somewhere else. The rota does not know who booked Thursday off, so you schedule them anyway and find out when they do not arrive.
- You are maintaining two versions. The published one and the one with this week's changes.
- Changes are invisible. Somebody edited Friday and there is no record of who, or what it said before.
- People check a file rather than being told. Anyone who does not open the sheet does not know their shift changed.
That first one is the real problem, and it is not solvable inside a rota. A schedule and a leave calendar are two views of the same week; keeping them in separate documents guarantees they disagree eventually, and the disagreement always surfaces on the day.
Related templates
- Weekly timesheet template for hours actually worked, once the shifts have happened
- Employee attendance tracker for who was actually in
- PTO tracking spreadsheet for the leave that should be shaping the rota in the first place
If you are already running two or three of these side by side, bringing your existing sheet across puts the team, the leave and the calendar in one place — the rota stops being the last to know when someone is away.
Frequently asked questions
What should a shift schedule include?
At minimum: who is working, which days, and what hours. The part most rotas leave out is a coverage total per day — the number that tells you whether Thursday is actually staffed before Thursday arrives.
How far in advance should shifts be published?
Two weeks is the common standard, and in several cities it is the legal one. Predictive scheduling laws in Oregon, Seattle, New York City, Chicago, Philadelphia and elsewhere require advance notice and pay a penalty for late changes.
How do I stop everyone booking the same week off?
Decide your minimum coverage first, then approve against it rather than first-come-first-served. Once you know how many people can be away at once, most requests answer themselves and the awkward ones are visible early.
Should the rota use dropdowns for shifts?
Usually not. Shift labels vary too much between teams for a fixed list to survive, and a validation list people have to fight is worse than free text. Keep the shift free-form and validate the things you actually count.