PeopleMuster

Shift schedule template

Shift schedules fail on cover, rarely on names. So this rota is laid out by shift instead of by person: every day shows who works the morning, the mid and the evening, and a last column asks whether the minimum was met. Short shifts jump out before anyone has to call round for help.

Pick this layout when a site must never drop below a set number of people on each shift: a front desk, a support line, a warehouse floor. If your question is what one person works this week, the weekly work schedule reads better, because it runs one row per person.

SHIFT SCHEDULE (ROTA)
Location: [LOCATION]
Period: [FIRST DATE] to [LAST DATE]
Minimum people per shift: [MINIMUM COVER]
Rota owner: [ROTA OWNER]

PART 1 - THE SHIFTS
Shift | Starts | Ends | Unpaid break (min) | Shift lead
Morning | [MORNING START] | [MORNING END] | [BREAK MINUTES] | [SHIFT LEAD]
Mid | [MID START] | [MID END] | [BREAK MINUTES] | [SHIFT LEAD]
Evening | [EVENING START] | [EVENING END] | [BREAK MINUTES] | [SHIFT LEAD]

PART 2 - WHO WORKS EACH SHIFT
Date | Day | Morning | Mid | Evening | Minimum met?
[DATE] | Mon | [NAMES] | [NAMES] | [NAMES] | Yes / No
[DATE] | Tue | [NAMES] | [NAMES] | [NAMES] | Yes / No
[DATE] | Wed | [NAMES] | [NAMES] | [NAMES] | Yes / No
[DATE] | Thu | [NAMES] | [NAMES] | [NAMES] | Yes / No
[DATE] | Fri | [NAMES] | [NAMES] | [NAMES] | Yes / No
[DATE] | Sat | [NAMES] | [NAMES] | [NAMES] | Yes / No
[DATE] | Sun | [NAMES] | [NAMES] | [NAMES] | Yes / No

PART 3 - HANDOVER LOG
Date | From shift | To shift | Handed over by | Received by | What was passed on
[DATE] | Morning | Mid | [NAME] | [NAME] | [OPEN ITEMS]
[DATE] | Mid | Evening | [NAME] | [NAME] | [OPEN ITEMS]

On-call for the period: [ON-CALL NAME AND NUMBER]

What to put in each blank

[MINIMUM COVER]
Write the smallest number of people each shift can run with. Part 2's last column checks every shift against it.
[MORNING START]
Use a 24-hour clock, like 06:00. Fill the other start and end times the same way.
[SHIFT LEAD]
Name one person who owns each shift. When two people think they're in charge, neither is.
[NAMES]
List first names separated by commas. Count them against the minimum before you mark Yes.
[OPEN ITEMS]
Note what the next shift must finish or watch: a late delivery, a customer waiting on a callback.
[ON-CALL NAME AND NUMBER]
Give the person to ring when a shift falls short, with a direct number.

Before you send it

  • Fill Part 2 shift by shift, not person by person. You'll see the weak shift while there's still time to move someone into it.
  • Mark No in the last column honestly, then fix it. A rota that shows Yes everywhere by default hides the one day that matters.
  • Keep the handover log even on quiet days. Two weeks of short entries is how you learn which handover drops things.
  • Rotate evening and weekend shifts in a pattern people can predict, such as one weekend in three. Fairness you can see causes fewer swap requests than fairness you promise.

Every shift in PeopleMuster carries its own time window, and browser check-in opens inside it: by default from 60 minutes before the start until 120 minutes after.

Questions people ask about this letter

What is the difference between a shift schedule and a rota?

Most teams use the two words for the same document. Rota is more common in British English and shift schedule in American English. Both assign named people to named shifts over a set period, usually one or two weeks.

How many people should each shift have?

Work it back from the busiest hour of that shift, then add one for breaks and absence. A desk that needs 2 people at its peak usually rotas 3, so a break or a sick day leaves it at the minimum.

Should shifts overlap?

A 15 to 30 minute overlap between shifts makes handover real. Without it, the leaving shift walks out as the next one walks in, and open items live in nobody's head.

Other templates