Account

What new tool do you want?

Date & Time

Shift Schedule / Rota Maker

Generate a rotating shift schedule for your teams — 2-2-3 Panama, DuPont, 4-on-4-off, 24/48 and more — with coverage and hours per week.

How to use

  1. 1Pick a rotation pattern and start date, and name your teams.
  2. 2Copy the schedule into a spreadsheet or print it for the break room.

How it's calculated

Each team follows the same repeating cycle, offset so that shifts are covered every day. Average weekly hours = shifts per cycle × shift length ÷ cycle weeks.

Frequently asked questions

What is a 2-2-3 (Panama) schedule?

Teams work 2 days, have 2 off, work 3, have 2 off, work 2 and have 3 off over 14 days — every other weekend off, averaging 42 hours a week on 12-hour shifts.

What is the DuPont schedule?

A 4-week cycle of 12-hour shifts for four teams: 4 nights, 3 off, 3 days, 1 off, 3 nights, 3 off, 4 days, then 7 days off.

Does it handle overtime rules?

No — it shows the pattern and average hours. Check local labor rules for overtime and rest requirements.

Why 'average hours per week' isn't the shift length

A rota's weekly average depends on the full cycle, not any single week in it — because most rotations don't repeat every 7 days. The tool divides total hours worked across one full cycle by the number of weeks the cycle spans: average = (on-shifts × shift length) ÷ (cycle days ÷ 7). That's why a 'Panama' 2-2-3 schedule, which never actually gives anyone a plain 5-day week, still has a clean long-run average.

A worked example: Panama vs. 24-on/48-off

The Panama cycle is DDOODDDOODDOOO — 14 days, with 7 of them worked on 12-hour shifts. That's (7 × 12) ÷ (14 ÷ 7) = 84 ÷ 2 = 42 hours a week, and because the cycle is 14 days long, each team gets a full weekend off every other week. A fire department's 24-on/48-off cycle (XOO, 3 days long) looks lighter at a glance — one working day in three — but at 24-hour shifts that's (1 × 24) ÷ (3 ÷ 7) = 24 × 7/3 ≈ 56 hours a week, noticeably above a standard 40-hour week. That gap is exactly why many departments add periodic 'Kelly days' — extra days off — to bring the long-run average down.

What the generator doesn't check

It lays out coverage and the average workweek, but it has no idea what your jurisdiction's overtime, minimum-rest, or maximum-consecutive-shift rules are. The DuPont schedule, for instance, includes a run of four night shifts in a row — legal in many places, restricted in others. Treat the output as the pattern to review against your own labor rules, not a compliance check.

How every team ends up covering a different slice of the same cycle

Every team follows the identical repeating pattern string, but each one starts reading it from a different offset — cycle length divided by number of teams — so a 2-team, 14-day Panama rota offsets the second team by exactly 7 days into the same 14-day sequence. That single trick is the entire mechanism behind full-day coverage: rather than writing a separate pattern for each team, the generator reuses one sequence and staggers where each team begins reading it, which guarantees the gaps in one team's schedule line up with another team's working days as long as the offset evenly divides the cycle length.

Related tools

More: Date & Time