How to Make a Shift Schedule (Step-by-Step)
Updated 2026-02-01
Making a shift schedule comes down to five decisions: who works, when they work, how shifts rotate, who is off, and how people get the final roster. Here is a repeatable way to do it in about ten minutes.
1. List your staff and their constraints
Write down everyone who needs a shift, plus anything that limits when they can work — a student who can’t open, someone who can’t close two nights in a row, a key-holder who has to be present at open and close. Keeping constraints visible up front saves you from re-doing the grid later.
2. Define your shifts
Most workplaces run on two to four shift blocks. A common set:
| Shift | Typical hours |
|---|---|
| Morning / Open | 7:00a – 3:00p |
| Day | 9:00a – 5:00p |
| Evening / Close | 3:00p – 11:00p |
| Night | 11:00p – 7:00a |
Name shifts by what staff call them, not by internal codes. “Close” is clearer than “Shift C”.
3. Cover the busy times first
Fill your highest-demand slots before anything else — the Friday dinner rush, the Monday morning open. Coverage gaps at peak times cause more pain than a slightly uneven Tuesday.
4. Rotate fairly
If nobody wants every Saturday night, rotate it. A simple rule like “no one closes more than twice in a row” and “weekend nights rotate weekly” keeps things fair without a complicated algorithm. Our shift schedule maker has an auto-fill rotation that spreads shifts across your team as a starting point you can adjust.
5. Publish something people can read
A schedule only works if staff can see it. Print it for the break room, export a CSV to share, or save a PDF to post in your group chat. Give people enough notice — a week ahead is a reasonable floor.
Make it in the browser
You don’t need Excel for any of this. Open the free shift schedule maker, add your staff, click cells to assign shifts, and print. If you want a starting point, use the weekly shift schedule template.
Check coverage before you publish
A schedule can look tidy and still leave the operation short. Do one final coverage pass by reading each shift as the customer or supervisor will experience it. Ask whether the right people are present, not merely whether someone is assigned. A restaurant may need a key-holder, a cook, and a server; a warehouse may need a trained forklift operator and a floor lead; a clinic may need the role mix required by its own policies. List those roles beside the schedule while you plan instead of relying on memory.
It also helps to mark known exceptions before filling normal shifts: approved leave, training, public holidays, recurring deliveries, and the busiest time of day. When a constraint changes, update the source schedule rather than sending a separate chat message. One visible version is easier for everyone to trust.
Use a fairness check
Fairness is not an identical number of shifts for every person. It means the inconvenient parts of the work are shared according to a rule the team understands. Compare each person’s total hours, closes, nights, weekends, and short turnaround periods. If someone has taken extra desirable shifts because they asked for them, note that choice so it does not look like an accidental imbalance.
For a rotating team, review the entire cycle instead of only the coming week. A 2-2-3 or 4-on-4-off calendar can look uneven in one week yet balance correctly over two or four weeks. The four-team rotation guide explains how to check a complete cycle.
Give people a clear change process
Add a publication date to every schedule and state who can approve swaps. Staff should know whether they may trade directly, need manager approval, or must record the change somewhere else. That simple rule prevents two people from assuming the same shift is covered. When a swap is approved, edit the main schedule and re-share it; do not leave the old version on a wall or in a shared folder.
A reusable final checklist
- Every required shift and role is covered.
- Leave, training, and known events have been accounted for.
- Hours, nights, closes, and weekends have been reviewed for fairness.
- The start date, time zone where relevant, and version date are visible.
- Staff know where to find the current copy and how to request a change.
Once those checks are complete, publish a printable view and keep a working copy for the next period. The goal is a schedule people can act on without having to ask what a colour, code, or last-minute message means. Review the process after each period and keep the instructions visible for the next scheduler.