Understanding 24 hour shift schedules
Start with the operating window, then assign crews. These example times cover a full day without gaps:
| Arrangement | Shift start and end times | Employee assignment |
|---|---|---|
| Three eight hour shifts | 00:00 to 08:00; 08:00 to 16:00; 16:00 to 24:00 | One eight hour slot |
| Two twelve hour shifts | 06:00 to 18:00; 18:00 to 06:00 next day | One twelve hour slot |
| Continuous 24 hour duty | 07:00 to 07:00 next day | One employee remains on duty throughout |
A shift slot is a period requiring coverage. A crew is the group assigned to cover it. Three daily slots do not mean three crews can cover weekends and still take days off, as the hours in the BMS shift configuration catalog demonstrate.
Fixed assignments keep employees on the same time slot. Rotating assignments move them between slots across a cycle. Either arrangement still needs enough qualified people for every staffed position.
How does a 24 hour shift work?
In a hypothetical assignment, an employee reports at 07:00 Monday and remains on duty until 07:00 Tuesday. The employer must separately establish duties, meal coverage, sleep opportunities, paid time, and who takes over afterward. A 24 hour assignment does not automatically include eight unpaid hours.
Under the applicable US federal sleep time rules, excluding up to eight scheduled sleeping hours requires an agreement, adequate sleeping facilities, and the ability to usually obtain an uninterrupted night's sleep. See the Department of Labor sleep time criteria.
Work interruptions count as hours worked. If the employee cannot obtain at least five hours of sleep during the scheduled sleeping period, the entire sleeping period counts as work under DOL guidance on interrupted sleep. This rule is not permission to use continuous 24 hour duty in every role or jurisdiction.
What's an 8 hour, 3 team, 24/7 shift pattern?
It assigns one crew to each daily eight hour slot. The problem is days off: three crews working five shifts each do not supply a full week of coverage.
For a hypothetical operation with equal sized crews:
- Required coverage: 7 days × 24 hours = 168 crew hours.
- Available coverage: 3 crews × 5 shifts × 8 hours = 120 crew hours.
- Uncovered time: 168 − 120 = 48 crew hours, before relief or leave.
Three crews can cover the base calendar only by each working seven eight hour shifts, or 56 hours per employee weekly. That matches the three crew arrangement in the BMS catalog.
At a budget of 40 hours per person, one continuously staffed position requires 168 ÷ 40 = 4.2 full time equivalents before relief. Four employees working 40 hours provide only 160 hours. A full time equivalent is a capacity measure, not a complete headcount plan.
For covered, nonexempt employees under ordinary federal rules, overtime applies after 40 hours in the established workweek. A 56 hour week therefore contains 16 overtime hours; applicable exceptions must be checked with payroll. The DOL overtime guidance also prohibits averaging hours across multiple weeks.
Products discussed
24 Hour Shift Schedules: Coverage Templates and Crew Math tools mentioned
Official marks identify the products materially discussed in this section.
What's a rotating 4 team, 24/7 shift pattern?
Four crews can rotate through three daily slots and one day off. Copy the following tables into a coverage workbook: Tab 1: 24/7, Tab 2: 24/5, and Tab 3: Relief and ownership. Together, they expose coverage and payroll requirements that a repeating calendar hides.
Tab 1: A complete 28 day coverage cycle
This hypothetical template begins Monday at 00:00. S1 means 00:00 to 08:00, S2 means 08:00 to 16:00, and S3 means 16:00 to 24:00. Record shifts on their start date.
Assume equal crew sizes, fully paid shifts, a Monday 00:00 payroll workweek, and no clock changes. Each employee follows their crew's assignments.
| Day | Weekday | Crew A | Crew B | Crew C | Crew D |
|---|---|---|---|---|---|
| 1 | Monday | S1 | S2 | S3 | Off |
| 2 | Tuesday | S2 | S3 | Off | S1 |
| 3 | Wednesday | S3 | Off | S1 | S2 |
| 4 | Thursday | Off | S1 | S2 | S3 |
| 5 | Friday | S1 | S2 | S3 | Off |
| 6 | Saturday | S2 | S3 | Off | S1 |
| 7 | Sunday | S3 | Off | S1 | S2 |
| 8 | Monday | Off | S1 | S2 | S3 |
| 9 | Tuesday | S1 | S2 | S3 | Off |
| 10 | Wednesday | S2 | S3 | Off | S1 |
| 11 | Thursday | S3 | Off | S1 | S2 |
| 12 | Friday | Off | S1 | S2 | S3 |
| 13 | Saturday | S1 | S2 | S3 | Off |
| 14 | Sunday | S2 | S3 | Off | S1 |
| 15 | Monday | S3 | Off | S1 | S2 |
| 16 | Tuesday | Off | S1 | S2 | S3 |
| 17 | Wednesday | S1 | S2 | S3 | Off |
| 18 | Thursday | S2 | S3 | Off | S1 |
| 19 | Friday | S3 | Off | S1 | S2 |
| 20 | Saturday | Off | S1 | S2 | S3 |
| 21 | Sunday | S1 | S2 | S3 | Off |
| 22 | Monday | S2 | S3 | Off | S1 |
| 23 | Tuesday | S3 | Off | S1 | S2 |
| 24 | Wednesday | Off | S1 | S2 | S3 |
| 25 | Thursday | S1 | S2 | S3 | Off |
| 26 | Friday | S2 | S3 | Off | S1 |
| 27 | Saturday | S3 | Off | S1 | S2 |
| 28 | Sunday | Off | S1 | S2 | S3 |
Repeat boundary: Day 29 is Monday and repeats Day 1. Crew D finishes Day 28's S3 at Monday 00:00; Crew A takes over on S1.
| Employee's crew | Week 1 hours | Week 2 hours | Week 3 hours | Week 4 hours |
|---|---|---|---|---|
| A | 48 | 40 | 40 | 40 |
| B | 40 | 40 | 40 | 48 |
| C | 40 | 40 | 48 | 40 |
| D | 40 | 48 | 40 | 40 |
Each employee works 21 shifts, totaling 168 hours per cycle, or 42 weekly on average. Each 48 hour week contains eight federal overtime hours under ordinary covered, nonexempt rules. The average does not replace the payroll calculation.
Warning
This is a coverage illustration, not a fatigue or compliance endorsement. It rotates shift times rapidly and contains no additional capacity for absences, handoff overlap, or separately staffed breaks.
Put the workflow into practice
See how your team could use this workflow
A 24/5 shift pattern with 12 hour shifts
Tab 2: Two weeks covering Monday morning through Saturday morning
Define operations as Monday 06:00 through Saturday 06:00. The payroll workweek runs from Monday 06:00 to the following Monday 06:00. Day shifts run 06:00 to 18:00; night shifts run 18:00 to 06:00 the next day.
This hypothetical template assumes fully paid shifts and equal sized crews. A and B stay on days; C and D stay on nights.
| Week | Shift start day | Day crew | Night crew |
|---|---|---|---|
| 1 | Monday | A | C |
| 1 | Tuesday | A | C |
| 1 | Wednesday | B | D |
| 1 | Thursday | B | D |
| 1 | Friday | A | C |
| 1 | Saturday | Closed after 06:00 | No shift starts |
| 1 | Sunday | Closed | Closed |
| 2 | Monday | B | D |
| 2 | Tuesday | B | D |
| 2 | Wednesday | A | C |
| 2 | Thursday | A | C |
| 2 | Friday | B | D |
| 2 | Saturday | Closed after 06:00 | No shift starts |
| 2 | Sunday | Closed | Closed |
Friday's night shift finishes Saturday at 06:00. Operations remain closed until Monday at 06:00. Week 3 repeats Week 1, with A opening the day shift and C taking the night shift.
| Employee's crew | Week 1 hours | Week 2 hours |
|---|---|---|
| A and C | 36 | 24 |
| B and D | 24 | 36 |
Employees alternate three shifts and two shifts, averaging 30 scheduled hours weekly. Using only two crews instead would require each employee to work five twelve hour shifts: 60 hours, including 20 federal overtime hours under ordinary federal rules.
The four crew version avoids exceeding 40 scheduled hours in either week under these assumptions. It does not eliminate possible California daily overtime, other local requirements, or overtime caused by extra assignments.
Choose a shift pattern by coverage, weekly hours, and relief
Use the operating window and actual employee hours to narrow the choice. Fixed versus rotating assignments remain a separate decision.
| Demonstrated arrangement | Coverage | Weekly employee hours | Handoffs per operating day | Staffing tradeoff and evidence |
|---|---|---|---|---|
| Three crews, eight hours | 24/7 | 56 | 3 | No days off in the base pattern. BMS configurations; federal overtime. |
| Four crews, eight hours | 24/7 | 40 or 48 | 3 | Days off, but no spare relief capacity. Workbook calculation; BMS crew context; federal overtime. |
| Four crews, twelve hours | 24/5 | 24 or 36 | 2, except closure boundary | Lower weekly hours, longer shifts. Workbook calculation; BMS configuration context; federal overtime. |
For the 24/5 example, there are nine internal crew handoffs per operating week. Saturday shutdown and Monday startup need separate operating procedures.
Tab 3: Budget relief before assigning names
The completed example below covers one continuously staffed position using eight hour shifts. It assumes 15 additional paid minutes at each handoff and 30 minutes of separately staffed meal relief per shift. These are operating allowances, not legal break requirements.
| Editable input | Example value | Weekly staffing hours |
|---|---|---|
| Base coverage | 7 × 24 hours | 168 |
| Added handoff overlap | 21 × 0.25 hours | 5.25 |
| Added meal relief | 21 × 0.5 hours | 10.5 |
| Leave replacement | Enter forecast hours | 0 assumed |
| Training replacement | Enter forecast hours | 0 assumed |
| Total before absence allowances | 168 + 5.25 + 10.5 | 183.75 |
The meal calculation is additive because the original eight hour shifts remain fully paid. Required handoff work is compensable; unpaid meals require complete relief from duties under DOL Fact Sheet 22.
For identical posts, multiply 183.75 by the number of concurrent positions, then add total leave and training replacement hours. Calculate separately where coverage or relief needs differ. A qualified RN cannot be replaced by an available employee who lacks the required credential.
A filled calendar proves that assignments exist. It does not prove that relief coverage exists.
Keep between shift rest separate from meal and rest breaks
Between shift rest is time away from duty. Meal and rest breaks occur within a shift. A worker who eats while still responsible for a post has not necessarily received an unpaid meal period.
Operator view
Supporting evidence
DOL Fact Sheet 22
California overtime and exceptions
NIOSH guidance
The NIOSH recommendation comes from emergency responder fatigue guidance. It is not a nationwide legal minimum. California's general daily overtime rule also has exceptions, including applicable alternative workweek arrangements, so payroll must evaluate the actual arrangement.
Check three exceptions before reusing either template:
- Call offs: Covering the next shift can erase planned recovery time. Recheck the replacement worker's preceding and following assignments.
- Payroll boundaries: Split hours across the established workweeks when an overnight shift crosses the boundary. A start date label alone is insufficient for payroll.
- Daylight saving changes: Scheduled clock times may represent different elapsed hours. Recalculate paid hours and coverage for the affected shift.
24 hour shift scheduling software: A practical implementation roadmap
Add ownership columns to the workbook before publishing. Each decision needs a named owner and a recorded approval.
| Owner | Workbook record required before publication |
|---|---|
| Operations | Staffed positions, skill requirements, operating window, and cycle start |
| Payroll | Workweek boundary, paid handoffs, overtime treatment, and clock change handling |
| Supervisors | Named break relief, absence coverage, and escalation contact |
Pilot one complete repeating cycle and inspect its repeat boundary. Reconcile scheduled hours with timesheets, missed coverage, and actual relief use before expanding the pattern.
Teambridge is an all in one platform for hourly teams, tailored to each company. Use Teambridge scheduling to create and publish assignments, onboarding and credential tracking to review readiness, and time tracking and timesheets to reconcile worked hours.
For publication, the documented sequence is to open the Scheduling Table, select Publish all, choose the date range and notification options, then select Publish Shifts. Draft shifts appear grey and published shifts change color, according to Publishing a Shift. Confirm publishing access with your administrator first; the documentation does not specify the required role.
If publication fails or shifts remain drafts, do not treat the roster as released. Escalate to the administrator and verify the published state before communicating that coverage is confirmed.
Software does not supply missing staff, determine whether continuous duty is appropriate, or guarantee legal compliance. Validate the workbook's coverage, payroll weeks, and relief assignments before implementing the schedule in Teambridge.
About the author

Content Writer at Teambridge
Anis Nanai is a content writer at Teambridge, with a focus on workforce management and the realities of running hourly teams. He prioritizes conversations with customers, staying close to the market, and understanding how workforce needs are changing. His writing connects those concerns to practical decisions about scheduling, time tracking, staffing, and automation. He examines product developments through the questions that matter to operators: what does this solve, how would it work for my team, and what evidence supports it?
Company perspective: this author works at Teambridge. Customer outcomes are attributed to their published sources.
View LinkedIn profile






