A rotating schedule is a system where employees cycle through different shifts (day, evening, night) or different days off over a set period. Instead of working the same hours every week, each team rotates through a pattern. This distributes weekend and night shifts more fairly across the team.
The 2-2-3 pattern (also called the Panama schedule) is one of the most widely used. Teams alternate working 2 days on, 2 days off, then 3 days on over a 14-day cycle. It gives every employee a 3-day weekend every other week and provides 24/7 coverage with just 4 teams.
It depends on the business. Rotating schedules distribute unpopular shifts (nights, weekends) fairly, which reduces complaints about favoritism. But fixed schedules let employees build stable routines, which some workers prefer. For 24/7 operations that need night coverage, some form of rotation is usually necessary.
Give your team at least 4 weeks notice before the switch. Explain why you're changing and which pattern you're using. Start the rotation on a Monday so it's easy to track. Use scheduling software to build and share the rotation so everyone can see their upcoming shifts from their phone.
Yes. Tools like Turnozo let you build a rotation pattern, save it as a template, and copy it forward each cycle. Employees see their upcoming shifts on their phone, and you adjust exceptions without rebuilding the entire rotation from scratch.
Get practical ideas
Open a ready-made prompt to summarize the article and apply it to your team.
You run a 24/7 operation and you're tired of the same three people getting stuck with every Friday night. Or your night crew is burning out because they never rotate off. Or your spreadsheet "rotation" is really just you guessing who hasn't worked weekends in a while.
A proper rotating schedule fixes all of this. Shifts get distributed fairly, coverage stays consistent, and you stop fielding complaints about favoritism.
Here's how to build one that actually works, with examples for 2-2-3, DuPont, Pitman, 4-on-4-off, and Continental rotations.
Fast answer: define your coverage needs, choose a rotation pattern, split employees into equal teams, map the full cycle, collect availability, publish the schedule early, and set rules for swaps, callouts, overtime, and rest periods before the first rota goes live.
What Is a Rotating Schedule?
A rotating schedule cycles employees through different shifts or different days off on a repeating pattern. Instead of "Sarah always works nights," everyone takes turns.
The rotation happens on a fixed cycle, typically 14 or 28 days. Each team works the same total hours, just at different times during the cycle.
When rotating schedules make sense:
24/7 operations (care homes, warehouses, security)
Businesses with unpopular shifts nobody wants permanently
The most popular rotating pattern. Works with 4 teams on 12-hour shifts over a 14-day cycle.
The pattern:
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Week 1
ON
ON
off
off
ON
ON
ON
Week 2
off
off
ON
ON
off
off
off
Each team follows this pattern but starts on a different day, so all shifts are always covered. Every employee gets a 3-day weekend every other week.
Best for: Manufacturing, warehouses, care homes, any operation that needs 24/7 coverage without five separate teams.
The tradeoff: 12-hour shifts are long. Some employees love the extra days off. Others burn out on the long days.
Before choosing a long rotation, compare the pattern with the shift-work prevalence and night-work health evidence. The useful question is not whether one template is universally "best," but how often it combines nights, long shifts, unstable hours, and short recovery windows.
2. The DuPont Schedule
A 28-day cycle with 4 teams on 12-hour shifts. The big selling point: one full week off every 28 days.
The pattern (per team, 28-day cycle):
4 night shifts, 3 days off
3 day shifts, 1 day off, 3 night shifts
3 days off, 4 day shifts
7 days off
Best for: Operations where employees value long stretches off. Popular in manufacturing and chemical plants.
The tradeoff: The transition from nights to days mid-cycle is rough. The week off is great, but the schedule leading up to it can feel punishing.
3. The Pitman Schedule
A 14-day cycle similar to 2-2-3 but with a different distribution.
The pattern:
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Week 1
ON
ON
off
off
off
ON
ON
Week 2
off
off
ON
ON
ON
off
off
Best for: Teams that want every other weekend off as a guaranteed block.
The tradeoff: Similar to 2-2-3 but the 3-day mid-week gap can feel scattered for some people.
4. The 4-On-4-Off Schedule
The simplest 24/7 pattern. 4 teams on 12-hour shifts with an 8-day cycle. Work 4, rest 4, repeat.
The pattern:
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Team A
Day
Day
Day
Day
off
off
off
off
Team B
off
off
off
off
Day
Day
Day
Day
Team C
Night
Night
Night
Night
off
off
off
off
Team D
off
off
off
off
Night
Night
Night
Night
Best for: Warehouses, security, and operations that value simplicity over flexibility. Employees know exactly when they work months ahead.
The tradeoff: 4 consecutive 12-hour shifts is physically demanding. And because the cycle doesn't align with the weekly calendar, weekends off are random.
5. The Continental Schedule (3-Shift, 8-Hour)
For operations that can't do 12-hour shifts. Uses 4 teams on 8-hour shifts over a 28-day cycle. Each team rotates through mornings, evenings, and nights.
The rotation (per team, simplified):
7 morning shifts (6 AM to 2 PM)
2 days off
7 evening shifts (2 PM to 10 PM)
2 days off
7 night shifts (10 PM to 6 AM)
3 days off
Best for: Healthcare, manufacturing plants with union agreements limiting shift length, and teams where 12-hour shifts cause safety concerns (heavy machinery, patient care).
The tradeoff: 7 consecutive shifts of any type is tiring. The night-to-morning transition after only 3 days off is the roughest part. Some teams modify this with shorter runs (5 on, 2 off) but that requires a 5th team.
Which Pattern Should I Pick?
If your situation is...
Use this pattern
First time rotating, want something simple
2-2-3
Team values long breaks over short cycles
DuPont (7 days off every 28)
Every-other-weekend off is the priority
Pitman
Maximum simplicity, predictable months ahead
4-on-4-off
12-hour shifts aren't an option
Continental (8-hour)
Small team (8-12 people), 2 shifts only
Alternating weeks (week A days, week B nights)
When in doubt, start with the 2-2-3. It's the most widely used for a reason.
Which Rotation Pattern Fits Your Team?
Answer 3 questions to find the right pattern.
Question 1 of 333%
How long are your shifts?
3 questions left
How to Build Your Rotating Schedule (Step by Step)
How Many People Do You Need for 24/7 Coverage?
Calculate the minimum team size for your rotation based on shifts and coverage requirements.
Positions to fill daily
$6
Minimum team size (with days off)
$12
Recommended (with absence buffer)Most expensive
$13
You need at least 12 people split across 4 teams. Each team gets 3 people per shift. With a 10% absence buffer, aim for 14.
How many shifts per day? (2 shifts of 12 hours, or 3 shifts of 8 hours?)
How many people do you need per shift?
Do weekends need the same coverage as weekdays?
Multiply it out. If you need 3 people per shift and you run 3 shifts a day, that's 9 positions to fill per day. With days off factored in, you probably need 12-15 people minimum.
Step 2: Pick your rotation pattern
Use this as a guide:
Pattern
Teams
Shift Length
Cycle
Best For
2-2-3
4
12 hours
14 days
Most 24/7 operations
DuPont
4
12 hours
28 days
When long breaks matter
Pitman
4
12 hours
14 days
Weekend-focused teams
4 on, 4 off
4
12 hours
8 days
Simple, predictable
Continental
4
8 hours
28 days
When 12-hour shifts are too long
If your team is small (under 16 people), stick with the 2-2-3 or Pitman. Simpler patterns are easier to maintain and easier for employees to remember.
Step 3: Assign teams
Split your staff into equal groups. Label them A, B, C, D (or whatever works). Each team follows the same pattern but offset by one position.
Important: Balance the teams by skill level. Don't put all your senior people on Team A and all the new hires on Team D. Every team needs someone experienced enough to handle problems.
Step 4: Map it out
Build the full cycle on a calendar. Here's what a 2-2-3 looks like for all 4 teams over 2 weeks:
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Team A
Day
Day
-
-
Night
Night
Night
Team B
-
-
Day
Day
Day
-
-
Team C
Night
Night
Night
-
-
Day
Day
Team D
-
-
-
Night
-
-
-
(Simplified, actual 2-2-3 rotations are more detailed)
Even in a rotation, people have constraints. Someone might have a medical appointment every other Thursday. Another person can't do nights for health reasons. Collect this upfront so you can make adjustments before publishing, not after.
Step 6: Publish and communicate
Give your team at least 4 weeks notice before a major rotation change when you can. Two weeks is the bare minimum for minor tweaks, but a full pattern change affects sleep, childcare, second jobs, and transport. Share the full cycle so people can plan around it. If you're using scheduling software, publish it once and let everyone check their phone.
Step 7: Build in a way to handle exceptions
Rotations look perfect on paper. Then someone gets sick, someone quits, and someone else needs to swap shifts. Your rotation needs a plan for this:
Shift swaps: Let employees trade shifts with each other (with your approval)
Open shifts: When someone calls out, post the shift as open and let available people claim it
Overtime rules: Decide in advance how you handle coverage gaps, whether you ask for volunteers first or assign mandatory overtime
Common Mistakes (and How to Avoid Them)
Rotating too fast. Switching from nights to days every few days wrecks sleep patterns. The research on night shift health is clear: forward rotation (days to evenings to nights) with at least 2-3 consecutive days on the same shift is healthiest.
Ignoring employee input. Posting a rotation without asking anyone's preferences is a fast way to lose your best people. The schedule doesn't have to make everyone happy, but people need to feel heard.
No template, rebuilding every cycle. If you're recreating the rotation from scratch every 2-4 weeks, you're wasting hours. Save the pattern as a template and copy it forward. Adjust exceptions, don't rebuild.
Unbalanced teams. If Team A has 3 senior carers and Team D has none, you'll have coverage problems every time Team D works nights. Audit team composition regularly, especially after turnover.
Ignoring rest periods and overtime rules. A rotation can look fair on a spreadsheet and still create illegal or unsafe short turnarounds. Check local labor rules, union agreements, and maximum-hours policies before publishing.
Tools to Manage Rotating Schedules
A rotating schedule that lives in a spreadsheet works until it doesn't. The moment someone swaps a shift or calls in sick, your spreadsheet is out of date and nobody knows it.
Publish to everyone's phone so the schedule is always current
Let employees request swaps and see their upcoming shifts
Track actual hours worked against what was scheduled
If you're running a rotation for more than 10 people, the time saved vs. spreadsheets pays for itself in the first month.
Start With the Simplest Pattern That Covers Your Needs
The biggest mistake is picking a complicated rotation because it looks thorough. Start simple. The 2-2-3 covers most 24/7 operations with 4 teams and 12-hour shifts. If that doesn't fit, try the Pitman. Only move to DuPont or Continental if you have specific reasons (employee demand for longer breaks, 8-hour shift requirements, etc.).
The best rotation is the one your team actually understands and can follow. Build it, publish it, and handle exceptions as they come.
