Employee Shift Schedules: 8, 10 and 12-Hour Patterns for Hourly Teams

Choose by how your demand behaves and what your people can sustain. The common patterns differ in clear ways:

• Fixed 8-hour shifts (three per day): Each person works the same shift every week, five days. It's predictable and easy to staff, but needs enough people to cover weekends and time off.
• Rotating 8-hour shifts: People move between days, evenings and nights on a cycle. It shares the unpopular shifts fairly, but rotations that move backward or change quickly are hard on sleep.
• 10-hour shifts, four days a week: Fewer handoffs and a three-day weekend, which many employees like. Coverage gets awkward at the start and end of the day, and overtime rules can be a factor in some states.
• 12-hour shifts (two per day): Half the handoffs, but long days. Common in healthcare, manufacturing and security. Common patterns rotate blocks of days and nights with several days off between, and need fatigue safeguards.
• Split or staggered shifts: Overlapping start times to match peaks, useful in retail and restaurants.

Start from demand, not preference: chart hourly workload for a typical week, then choose the pattern that puts people where the work is.

Do the math in hours, then convert to people. There are 168 hours in a week. If you need one person on duty at all times, that's 168 hours of coverage per position.

Say each employee works five 8-hour shifts, or 40 hours a week. Dividing 168 by 40 gives 4.2 people per position, and you can't hire 0.2 of a person. Then add allowance for vacation, sick days, training and turnover. In practice, you'd plan for five or six people per always-staffed position, depending on how much absence you expect.

For 12-hour shifts on a rotation, the math changes because people work fewer, longer shifts, but the same principle holds: total coverage hours divided by hours per person, plus a buffer. Build the calculation into your sheet with your own numbers: required hours per day and role, shifts per person per week, expected absence rate. Then test the schedule against a bad week, such as two people out sick during a holiday.

Most schedule complaints trace back to unclear rules. Write these down and share them:

1. Publish on a fixed day, well ahead. Two weeks' notice is a common target, and some cities require it for certain employers under predictive scheduling (fair workweek) laws.
2. Set minimum rest between shifts. Avoid closing one night and opening the next morning. Some jurisdictions require rest periods.
3. Define swap rules. Who can trade, who approves and how the manager checks that a swap doesn't cause overtime.
4. Rotate unpopular shifts evenly, and keep a visible log so people can see it's fair.
5. Collect availability regularly, and honor approved availability.
6. Cap consecutive days worked.
7. Set an on-call and call-in process for absences, with a list of who can cover.

Overtime is a related risk, since a schedule that quietly pushes people past 40 hours costs more; the FLSA overtime rules guide covers how to design around it.

Unpredictable or unfair schedules are one of the most common reasons hourly workers leave, and turnover is costly to replace. The Bureau of Labor Statistics' JOLTS data shows how much industries differ: the quits rate in leisure and hospitality is 4.0 per 100 employees, compared with 1.1 in finance and insurance¹.

You can't fix industry-wide turnover with a schedule alone, but scheduling is something you control. Track your own quit rate by shift and manager, and ask exiting employees about their schedules. If one shift has far higher turnover, look at its start times, rest gaps and predictability.

Small changes matter: consistent start times, advance notice, honoring availability and giving people a say in swaps. Employees can plan childcare, classes and second jobs around a schedule they can trust, and they're more likely to stay.

A spreadsheet works for a single location and a stable team. Use one row per person and one column per day, color-code shifts and add a totals column that sums weekly hours so overtime is visible before you publish. Add a second tab with required coverage per hour to check gaps.

Software becomes worthwhile when you have multiple locations, frequent swaps, availability requests or labor-law rules to enforce. Scheduling tools such as Deputy and When I Work handle shift publishing, swap requests, availability and time tracking, with different emphasis, so compare them in Buddy Punch vs Deputy vs When I Work. Confirm what each tool does about overtime alerts and local scheduling rules in your state, and don't assume compliance is automatic.

Whichever you choose, review the schedule after each cycle: unfilled shifts, last-minute changes, overtime hours and complaints. Adjust the pattern, not just the names. The employee handbook template is the place to record the rules.