The 2-2-3 Work Schedule (Panama Schedule), Explained

How the 2-2-3 rotation works

The pattern repeats every 14 days for each team: work 2, off 2, work 3, off 2, work 2, off 3. Because shifts are 12 hours, two teams cover each calendar day — one on days (commonly 6 AM–6 PM or 7 AM–7 PM), one on nights — and you need four teams total to cover 24/7: two rotating through days, two through nights.

Here's one team's two weeks in prose. Week 1: work Monday and Tuesday, off Wednesday and Thursday, work Friday, Saturday, and Sunday. Week 2: off Monday and Tuesday, work Wednesday and Thursday, off Friday, Saturday, and Sunday. Then the cycle restarts. The second team on the same shift works the exact inverse, so every day is always covered.

You'll also see the same pattern written as 2-3-2 — it's the identical cycle, just described starting from a different day. The full four-team Panama plan repeats cleanly every 28 days, and many operations rotate teams between days and nights at a slower interval (such as monthly or quarterly) so nobody is stuck on nights permanently.

The hours math: why it averages 42 a week

Each team works 7 shifts of 12 hours every 14 days — 84 hours per two weeks, an average of 42 hours per week. But the average hides the alternation: one week is 3 shifts (36 hours) and the next is 4 shifts (48 hours). That alternating 36/48 rhythm drives everything about paying this schedule correctly.

Total coverage works out too: four teams × 84 hours per fortnight = 336 team-hours, exactly matching the 336 hours in two weeks of round-the-clock single-post coverage (24 × 14). That's the appeal — full 24/7 coverage with no scheduling gaps and a pattern employees can memorize.

One practical note: define your shift start times so a "day" belongs to one shift cleanly. The night shift that starts Saturday at 6 PM and ends Sunday at 6 AM should be recorded as one shift, not split across two timesheet days, or your weekly totals will be a mess.

Overtime implications of 12-hour shifts

Under federal law (FLSA), overtime is 1.5× the regular rate for hours over 40 in a workweek. On a 2-2-3 schedule, the 48-hour week triggers 8 hours of overtime, and the 36-hour week triggers none. You cannot average the two weeks to 42 and skip overtime — each workweek stands alone, so plan on paying 8 OT hours every other week per employee.

Worked example: an employee earning $20/hour on this rotation. The 36-hour week pays 36 × $20 = $720. The 48-hour week pays 40 × $20 + 8 × $30 = $800 + $240 = $1,040. Across two weeks that's $1,760 for 84 hours — effectively about $20.95/hour once overtime is baked in. Budget labor at that blended rate, not the base rate.

Some states add daily overtime rules that can apply to 12-hour shifts, and a few have special provisions for healthcare or alternative workweek arrangements — confirm with your state labor department before adopting the schedule. Also decide upfront how unpaid meal breaks work on a 12-hour shift, since a 30-minute unpaid meal turns a 12-hour shift into 11.5 paid hours and changes the weekly math.

Pros and cons of the Panama schedule

Pros: employees get 26 three-day weekends a year and are off half of all days; nobody works more than three consecutive days; the pattern is predictable months in advance; and shift handoffs drop to two per day instead of three, which means fewer transition errors in operations like manufacturing, dispatch, security, and healthcare.

Cons: 12-hour shifts are tiring, and fatigue shows up in the back half of the third consecutive shift; the alternating 36/48 weeks make paychecks uneven unless you communicate clearly; built-in overtime raises labor cost versus 8-hour patterns; and night-shift teams need a fair rotation plan or you'll lose them.

Variants exist if pure 2-2-3 doesn't fit. Some operations run a 3-2-2-3 style arrangement or related fixed patterns; others use the DuPont or Pitman variations of four-team 12-hour coverage. The tradeoffs are similar — any four-team, 12-hour, 24/7 pattern lands at the same 42-hour average.

Running a 2-2-3 schedule without spreadsheet pain

On paper, the rotation is simple; in practice, the pain is exceptions — swaps between teams, sick calls on a 12-hour post that must be backfilled, and tracking who is owed which holiday. A spreadsheet can show the pattern, but it can't tell you that approving a swap just put someone at 60 hours in a workweek.

This is where scheduling software earns its keep: build the rotation once as a repeating pattern, and the system projects it forward indefinitely, flags overtime before you publish, and handles swap requests with rules. Pairing it with a time clock matters even more on 12-hour shifts, because small punch errors (12 hours vs 12 hours 20 minutes) are all happening in overtime territory on the 48-hour weeks.

If you're evaluating the move to 2-2-3, run the math first: take your current weekly labor hours, price them at the blended rate from the example above, and compare. The schedule usually wins on coverage and morale, but go in with the real cost.

Frequently asked questions

Keep reading