How to Create a Rotating Schedule (With Examples)

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.

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
• Teams where perceived scheduling fairness matters
• Any operation with day, evening, and night shifts to cover

When they don't:

• Small teams under 8 people (rotation gets complicated fast)
• Businesses that only operate during business hours
• Teams where employees genuinely prefer fixed schedules

The 3 Most Common Rotating Patterns

1. The 2-2-3 (Panama Schedule)

The most popular rotating pattern. Works with 4 teams on 12-hour shifts over a 14-day cycle.

The pattern:

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.

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:

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.

How to Build Your Rotating Schedule (Step by Step)

Step 1: Figure out your coverage needs

Before picking a pattern, answer these:

• 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:

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:

(Simplified, actual 2-2-3 rotations are more detailed)

Step 5: Collect availability before you finalize

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 2 weeks notice before the rotation starts. 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.

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.

Scheduling software handles rotations by letting you:

• Build the pattern once and copy it forward
• 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.

Need help building a rotating schedule? Try our free schedule template or see how Turnozo handles shift scheduling.