This 8-hour 24/7 shift schedule template uses five team units. Each day has one day team, one evening team, one night team, and two teams off. Over 15 days, every team works nine shifts for 72 cycle hours and a 33.6-hour weekly average.
The table covers one position around the clock. If the operation needs two people on every shift, each team unit represents two employees and the base coverage becomes 336 person-hours per week. Add relief capacity before assigning names.
How the forward rotation works
Each team moves from day to evening to night, then receives two days off. The five-day sequence repeats three times in the table so all five teams complete the same number of each shift. After day 15, restart at day 1.
The rotation is mathematically balanced, but it does not prove that frequent time changes suit the employees or workplace. Review employee preferences, night-work demands, rest, commute, and any medical or contractual restrictions before using it.
Seven-day coverage and staffing assumptions
| Measure | Calculation | Result |
|---|---|---|
| Daily base coverage | 3 shifts × 8 hours | 24 hours |
| Weekly base coverage | 21 shifts × 8 hours | 168 hours |
| Theoretical 40h staffing | 168 ÷ 40 | 4.2 FTE |
| One team per cycle | 9 shifts × 8 hours | 72 hours |
| Average per team | 72 × 7 ÷ 15 days | 33.6 hours/week |
Five team units are the mathematical base for continuous single coverage, not a resilience target. They leave no substitute when someone is absent unless another employee, relief pool, manager, or overlapping role can cover the gap.
Fixed shifts versus rotating shifts
| Model | Strength | Planning cost |
|---|---|---|
| Five-team rotation | Shares days, evenings, nights, and weekends symmetrically | Every team changes time bands frequently |
| Fixed shift pools | Employees keep a more consistent day, evening, or night band | Each band needs enough people to cover days off, weekends, and absences fairly |
A simple fixed starting pool uses at least two people assigned to each shift band for single coverage, or six people total. If coverage is divided evenly, that is about 28 coverage hours per person each week before other duties. The right model depends on whether the job includes non-coverage work and what weekly hours employees expect.
Plan overlap and handoff explicitly
The sample shifts meet exactly at 07:00, 15:00, and 23:00. If the team must exchange keys, review incidents, count inventory, sanitize equipment, or complete another handoff, extend or overlap the real shifts and include that time in the hour totals.
Handle the 23:00–07:00 shift in Maxuod Shift
The current weekly scheduler cannot record a continuous cross-midnight shift as one exact entry. Keep 23:00–07:00 in the downloadable template and external time record, or use a documented split and reconcile the midnight boundary before relying on the employee hours calculator or payroll handoff. Do not substitute 23:55 for midnight without accounting for the missing five minutes.
Use the template as a coverage baseline
- Decide whether the operation needs rotating or fixed time bands.
- Choose the people and roles represented by each team unit.
- Add relief, handoff, breaks, training, and demand overlap.
- Attach a real start date and document overnight entries consistently outside the live total or with a reconciled split.
- Review dated weekly totals and local rules before publishing.