The 2-2-3 Panama rotation is easy to draw and hard to run. Here's the coverage math, the baked-in overtime, and the swap rules that keep four crews from collapsing on week three.
The 2-2-3 Panama schedule is one of the most common ways operators run 24/7 coverage in security, healthcare, manufacturing, and utilities. It looks clean on a whiteboard: four crews, two 12-hour shifts, every other weekend off. It does not stay clean once real people, callouts, and overtime rules collide with it.
Most guides walk through the pattern and stop there. This one focuses on what actually breaks — the coverage math across four crews, the overtime that's baked in before anyone picks up an extra shift, the fatigue spike on the third consecutive 12, and the swap chaos that turns a tidy rotation into a Monday morning scramble.
Why 24/7 Operations Keep Landing on the Panama Schedule
Continuous coverage is a hard problem. A hospital, a guarded site, a refinery, a data center — none of them can close at 6 PM. The traditional fix was fixed day and night shifts, which grinds the night crew down over time and creates a permanent two-class workforce.
The Panama rotation tries to split the difference. Every crew rotates through both days and nights, weekends off come in a predictable cadence, and the pattern fits inside a clean 14-day cycle. Workers get every other Friday, Saturday, and Sunday off in a row — a three-day weekend twice a month that no five-day schedule can match.
That predictability matters more than ever. Workers across hourly industries consistently report feeling locked out of decisions about their own schedules, and unpredictable hours are one of the top drivers of turnover in shift-based work. A rotation everyone can read off a fridge magnet two months ahead is a real retention lever.
The origin is the Panama Canal Zone, where the US military needed continuous coverage with a fair rotation. That's the entire history lesson. What matters now is whether the pattern actually holds up under operational load.
How the 2-2-3 Pattern Actually Works Across Four Crews
The mechanics are simple. Four crews — call them A, B, C, D — split two 12-hour shifts, typically 6 AM to 6 PM and 6 PM to 6 AM. Two crews are on at any given time: one on days, one on nights. The other two are off.
Each crew follows the same 14-day pattern, offset from the others. The pattern is 2 on, 2 off, 3 on, 2 off, 2 on, 3 off. Hence 2-2-3.
Here's how it lays out for a single crew across two weeks:
| Day | Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|---|
| Week 1 | D | D | — | — | D | D | D |
| Week 2 | — | — | D | D | — | — | — |
That's the day-shift half of the rotation. Crews on the night side run the same pattern offset, and most operators flip a crew from days to nights every 14 or 28 days so no one lives permanently on graveyard.
The four crews are staggered so that at every hour of every day, exactly one day crew and one night crew are working. Two crews are always recovering. That's the whole trick.
The Coverage Math: Staffing Headcount for a True Panama Rotation
This is where agencies get burned. The math looks easy and isn't.
Start with minimum coverage per shift. If a security site needs three guards on post at all times, that's three per shift. With four crews, the floor is 3 × 4 = 12 guards. That gets you a rotation on paper.
It does not get you a rotation that survives contact with reality. PTO, callouts, training, no-shows, and credential lapses are not edge cases — they're the baseline. A realistic Panama deployment for a 3-post site needs 14 to 15 guards, with the extras serving as a float pool.
Here's a quick sizing reference operators can pull from:
| Minimum coverage per shift | Bare-minimum headcount (×4 crews) | Recommended with float |
|---|---|---|
| 2 | 8 | 10–11 |
| 3 | 12 | 14–15 |
| 5 | 20 | 23–25 |
| 8 | 32 | 37–40 |
The float pool is not optional. The most common Panama failure mode is starting with the minimum headcount, losing two people to a credential lapse and a sick week in the same cycle, and burning the remaining crew on mandatory overtime until they quit. The rotation looks healthy in week one and collapses in week three.
Warning
If you're staffing a Panama rotation at the bare minimum, you are not running a Panama schedule. You are running a fragile single-point-of-failure system that will start cannibalizing crews the first time someone calls out.
Built-In Overtime: The 42-Hour Week Problem
Do the math on the rotation itself. Across the 14-day cycle, each crew works seven 12-hour shifts. That's 84 hours over two weeks, or 42 hours per week on average. Two of those hours are overtime under federal rules before anyone picks up an extra shift.
That's the federal floor. Several states make it worse.
California, Colorado, Nevada, and Alaska all have daily overtime thresholds that trigger before the 40-hour weekly mark. In California specifically, employment beyond eight hours in any workday requires one and one-half times the regular rate for hours worked in excess of eight up to and including 12 in any workday, and double the regular rate for hours worked in excess of 12 in any workday. That means every single 12-hour shift on a Panama rotation generates four hours of daily overtime, regardless of weekly totals.
Stack that against the rotation:
| Week | Shifts worked | Straight time | Daily OT (CA) | Total hours |
|---|---|---|---|---|
| Week 1 | 4 × 12 | 32 | 16 | 48 |
| Week 2 | 3 × 12 | 24 | 12 | 36 |
| Cycle avg/week | 3.5 | 28 | 14 | 42 |
Under California rules, roughly a third of every Panama shift is paid at 1.5×. Now factor in a single coverage shift to backfill a callout — that hits double-time under the seventh-consecutive-day rule the moment a worker crosses six worked days in a row. Seventh consecutive day overtime must be paid when the employee works 6 hours or more on any of the prior 6 days in the workweek, or works 30 hours or more during the prior 6 days of the workweek.
The operator takeaway: price the baked-in OT into the bid rate. Agencies that quote a Panama site at straight time plus a thin margin discover by month two that their margin is gone, eaten by predictable overtime they could have modeled on day one. Run automatic OT calculation in your time tracking system so the daily and weekly thresholds get caught at clock-out, not at payroll close.
Ready to move?
Ready to see Teambridge in action?
Fatigue on the Third Consecutive Shift — and What to Do About It
The 3-on stretch is the structural weak point of the Panama pattern. The first 12 is normal. The second 12 is tired. The third 12 is where incidents happen.
The research is consistent. Accident and injury rates are 18% greater during evening shifts and 30% greater during night shifts when compared to day shifts, and working 12 hours per day is associated with a 37% increased risk of injury. NIOSH-aligned guidance pushes further: shifts over 12 hours should be avoided and no more than 3 consecutive 12-hour shifts should be scheduled before a recovery period. The 2-2-3 pattern sits right at that ceiling — which is fine when it's followed, and dangerous when a swap turns three consecutive into four or five.
The risk isn't theoretical. Compared with 8-hour shifts, 12-hour shifts increased the risk by 28%, with risk increasing by 17% for the third consecutive night shift and 36% for the fourth. Sources like the OSHA worker fatigue guidance document the same trend across industries.
Practical mitigations operators can actually enforce:
- Cap consecutive shifts at the pattern. No more than three 12s in a row, full stop. Swaps that would create a fourth get rejected at the schedule layer, not at the supervisor's discretion.
- Enforce minimum inter-shift rest. A standard floor is 11 to 12 hours between shifts. Quick-returns — a late shift followed by an early shift — compress sleep and are one of the most fatiguing patterns the literature identifies. Panama doesn't usually create them, but a poorly-validated swap can.
- Rotate day-to-night blocks no faster than every 28 days. Faster rotation never lets circadian rhythm catch up.
- Build a 48-hour recovery after a 3-on night stretch. Consider two rest days after three consecutive 12-hour shifts. The 2-off in the Panama pattern already does this — the problem is when swaps eat into it.
- Surface fatigue risk on the schedule itself. A flag in the schedule that says "this is your third consecutive 12" beats a policy document no one opened.
These matter most where consequences are sharpest: healthcare staffing, security operations, and light industrial sites where a single fatigued worker can put others at risk.
Swap Chaos: Why Panama Rotations Fall Apart on Week Three
Here's the failure mode no template warns you about. A worker on Crew B asks to swap a Thursday night with a worker on Crew D. Both supervisors say yes. The swap looks fine.
Except Crew D is offset from Crew B by six days. The worker who picked up Thursday now has a 5-on stretch starting Tuesday. The worker who gave up Thursday now has a single-shift orphan three days before their next scheduled block. Neither violation shows up until the following week's timecard.
This is the structural problem with swaps on a multi-crew rotation: the offsets that make the coverage work are the same offsets that turn a clean swap into a hidden compliance breach. Swap approvals should check cumulative hours, rest opportunity, and cumulative fatigue load — not just headcount.
The operator rules that keep swaps clean:
- Skill and credential match required. A guard with an unarmed license can't swap into an armed post. An RN with a med-surg cert can't swap into ICU. The system checks; the coordinator shouldn't have to remember.
- Swap blackout on the third shift of a 3-on stretch. No one trades into a fourth consecutive 12.
- Automatic recheck of weekly OT and rest-period rules after the swap is proposed, not after it's approved.
- Both workers see the same swap state in their app. No "I thought you took it" callouts at 5:55 AM.
- Hard cutoff for swaps within X hours of shift start. Anything inside that window goes to the coordinator as a callout, not a swap.
This is the kind of validation that has to live in the scheduling system itself. A swap policy in a PDF doesn't catch a hidden 5-on. Software that checks every proposed swap against the rules before it lands on the schedule does.
Tip
The cleanest way to test your swap rules: pick a random week, simulate three swaps, and check the resulting schedule for OT violations and rest-period gaps two weeks out. If the answer takes more than five minutes to compute, your rules aren't in the system — they're in someone's head.
Running Panama Across Multiple Sites or Clients
For staffing agencies and multi-site operators, every layer of complexity multiplies. Each site's Panama rotation has its own crew offsets, post orders, shift differentials, and credential requirements. A float pool worker who can cover Site A on a Tuesday cannot necessarily cover Site B on a Wednesday — different post orders, different client paperwork, possibly different state OT rules.
For security staffing, this means guard license types, site-specific post orders, and weapons qualifications all have to be matched at the schedule layer. For healthcare staffing, it's unit-specific competencies, immunization records, and facility-issued credentials. None of this is optional. A coverage gap caused by a credential mismatch is the same as a no-show — except it shows up at the worst possible moment.
Credential expiry is the silent killer of Panama coverage. A guard license that expires on day 9 of a 14-day cycle pulls a worker off the schedule mid-rotation and forces a callout backfill. The only defense is alerting on expiries before they happen, tied directly to the schedule. The onboarding system should handle credential capture and renewal alerts before someone's first shift, not after a missed post.
Float pool sizing for multi-site operations also has to assume site-specific training time. A worker added to the float pool on Monday is not coverage for Tuesday if they haven't been through the site orientation. Build that lag into the headcount math.
What to Automate Before You Roll Out a Panama Rotation
If you take one thing from this, it's that Panama is not a schedule you run in a spreadsheet. The pattern is simple enough to draw; the operations are not.
Before the first crew clocks in, automate these:
- Rotation template with crew offsets pre-built. A, B, C, D crews, 14-day cycle, day-to-night flip cadence set. Not rebuilt by hand every quarter.
- Automatic OT and rest-period guardrails. Federal weekly OT, state daily OT (CA, CO, NV, AK at minimum), seventh-day rules, and minimum inter-shift rest enforced at the schedule layer.
- Swap rules enforced in the app. Skill and credential matching, consecutive-shift caps, post-swap OT recheck — no manual review required for clean swaps, automatic rejection of dirty ones.
- Fatigue flags on consecutive shifts. Visible to the worker and the coordinator before a third 12 starts.
- Credential expiry alerts tied to the schedule. Surface the conflict at least two cycles before the license lapses.
- Real-time push of changes to the worker app. A swap, callout, or schedule update reaches the worker's phone immediately, not via a coordinator's text chain at 3 AM.
A Panama rotation that gets these six right runs predictably for years. One that doesn't burns through crews, eats margin in unmodeled overtime, and ends up replaced by a less efficient schedule that supervisors trust more.
If you're running Panama in a spreadsheet today, the question isn't whether it will break. It's which week. Operators ready to move off spreadsheets can start with the Teambridge platform — scheduling, time tracking, credentialing, and worker comms in one system, built for shift work that runs every hour of every day.
