How to build a weekly shift schedule, step by step
Published · 6 min read
A good schedule covers every shift, gives people their hours fairly and reaches employees early enough to plan their week. Here is a method that works for teams of 5 to 50, whether you use a spreadsheet or scheduling software.
1. Start from demand, not from people
List the shifts the business needs before you think about who will work them. For each day, write down the opening and closing times, the busy hours, and how many people each shift needs. A café might need two people at 7:00, four over lunch and two to close.
Writing demand first stops the most common mistake: building the week around who asked for which days, then discovering a Friday evening with nobody on it.
2. Collect availability and time off early
Set a fixed deadline, for example Wednesday at noon for the following week, for availability and leave requests. Requests that arrive after the deadline go into the next week. A fixed rule is fairer than first come, first served and saves you from rebuilding the schedule twice.
- Approved vacation and sick leave
- Fixed constraints such as studies or a second job
- Preferences, which you try to meet but do not promise
3. Create a repeating base pattern
Most weeks look alike. Build a base pattern of shifts that repeats every week and change only the exceptions. In scheduling software you can create the whole week's shifts at once and copy the pattern forward, which turns hours of work into minutes.
4. Fill the hardest shifts first
Assign the shifts with the fewest available people first: weekends, closing shifts, holidays. Then fill the rest. If you start with the easy shifts, the hard ones end up going to whoever is left, which is how the same people always get the worst shifts.
5. Check hours, rest and fairness
Before publishing, look at each person's total for the week. Watch for people above their contracted hours, which creates overtime cost, people well below what they need, and too little rest between a closing shift and an opening shift the next morning.
Rotate weekend and closing shifts over a few weeks so the load is shared. A short note of who worked the last few weekends makes this easy to check.
6. Publish on the same day every week
Publish the schedule at a fixed time, ideally several days before the week starts, in one place everyone can reach from their phone. When the schedule lives in one system instead of screenshots in a group chat, nobody works from an old version.
7. Handle changes in the system, not in private messages
Swaps and changes will happen. Make them in the same place the schedule lives, so the published version stays correct and hours for payroll match what actually happened. Compare scheduled shifts with clock-in times at the end of the week to catch gaps early.
A quick checklist
- Every shift has the number of people it needs
- Approved time off is respected
- No one is far above or below their hours
- Enough rest between late and early shifts
- Weekend and closing shifts are rotated
- Published at the usual time, in one place
Frequently asked questions
How far in advance should a shift schedule be published?
Publish at a fixed time every week, several days before the week starts. A predictable day helps employees plan and cuts down last-minute swaps.
Is a spreadsheet enough for scheduling?
For a handful of people it can work. As the team grows, keeping availability, time off, versions and hours in sync by hand becomes the slow part, which is where scheduling software saves time.