The 2-2-3 looks clean on paper. Then someone calls out on day three. Here's how operators keep the Panama rotation intact when reality hits.
Most Panama schedule guides stop at the diagram. Two on, two off, three on, two off, two on, three off — four crews, 28-day cycle, day/night swap, done. That version of the schedule works fine in a slide deck. It does not survive a Tuesday call-out on the third night of a three-on stretch, a guard card that expired during a four-day off block, or a night-to-day handoff between two people who have never worked together.
This is the operator's version of the Panama rotation. We assume you already know the pattern. We are going to talk about what actually breaks it in production, and the operations work underneath that keeps the cycle intact.
Why the Panama Rotation Looks Clean on Paper and Falls Apart on Tuesday
The textbook diagram is tidy. The Panama shift pattern is a 2-2-3 rotating schedule where employees work two 12-hour shifts, have two days off, work three shifts, have two days off, work two shifts, and have three days off, repeating on a 28-day cycle. Four crews. Every position covered. Predictable weekend cadence.
The live operation is messier. One person calls out on the second day of a three-on stretch and you are now staring at three coverage decisions in sequence: tonight's hole, tomorrow night's hole, and whether the held-over worker now violates a consecutive-shift cap going into their next rotation. The crew on its three-off block is the cleanest backfill on paper, but two of them are out of state and one's BLS lapsed yesterday.
None of that is a flaw in the 2-2-3 pattern. It is a flaw in treating the pattern as a schedule template instead of a coverage strategy. The rotation is the easy part. Everything underneath it — backfill rules, credential tracking, handoff protocols, OT forecasting — is the work.
The 2-2-3 Mechanics Operators Actually Need to Memorize
For the quick reference: four crews, two 12-hour shifts (typically 6a–6p and 6p–6a), 14-day team rotation. Two crews on days, two on nights. The pattern repeats across 28 days, then swaps day and night assignments. Full cycle resets at 56.
Both schedules average 42 hours per week. Over the full 28-day cycle, each crew works 168 hours — an average of 42 hours per week. The 42-hour weekly average is higher than the standard 40-hour week, which has overtime implications. Under federal FLSA rules, that's roughly two hours of weekly overtime baked in.
A few naming notes that trip people up. Panama, Pitman, and 2-2-3 are functionally the same pattern with different lineages — the 2-2-3 schedule and the Panama schedule are the same rotating shift pattern with different names. The day/night swap cadence varies in some shops (every two weeks, every four, or never), so always confirm which version you are inheriting before you publish anything.
If you want the deeper primer, see our Panama Schedule Meaning breakdown and the DuPont vs. Panama comparison for the trade-offs against the four-on-four-off variant.
Note
The 42-hour weekly average is a 28-day average, not a per-week reality. It is a common misconception that the schedule averages 42 hours per week with overtime calculated bi-weekly; the FLSA mandates that overtime be calculated on a weekly basis. Plan OT against the 48-hour week, not the average.
Where the Rotation Breaks: Call-Outs, Credentials, and Handoff Drift
Three failure modes show up every cycle. They are not edge cases.
Call-outs on day three of a three-on stretch
The worker who calls out has already logged 24 hours that week and is staring at a third 12 on top. The held-over teammate covering for them is the worst possible candidate from an FLSA and fatigue standpoint — they just finished 12, are heading into their two-off, and now you are pushing them to 24 consecutive hours. Max consecutive shifts (4–5), mandatory rest between shifts (8–12 hours), max weekly hours (60–72) — safety should override FLSA limits.
Credentials that expire mid-rotation
Guard cards, BLS cards, forklift certifications, site-specific badges — most expire on a date, not at a shift boundary. A credential that lapses during a four-day off block is invisible until the worker tries to clock in for the next rotation. By then it is 5:47 a.m. on a Saturday and you have no backfill on the bench.
Handoff drift across the night-to-day swap
The Panama rotation pairs different crews together every cycle. With a Panama 12-hour shift schedule, the number of shift transitions is fewer compared to an 8-hour shift. This can lead to fewer errors associated with shift handovers, especially in industries where continuity is crucial. Fewer transitions, sure. But the transitions you do have are between rotating pairs, and the verbal handoff degrades fast when the day-shift lead has never worked under the night-shift lead currently briefing them.
Each failure mode costs something different. Call-outs cost OT dollars. Credentials cost compliance exposure and a missed shift. Handoffs cost incidents — security gaps, missed patient notes, dropped maintenance tickets — that do not show up on the schedule report at all.
Overtime Math: What the Panama Rotation Actually Costs You
The federal baseline is the easy version. The cornerstone of FLSA overtime is the requirement that non-exempt employees be paid at a rate of at least 1.5 times their regular rate of pay for all hours worked in excess of 40 in a single workweek. The 2-2-3 schedule has built-in overtime. In its 14-day cycle, an employee works one week of three 12-hour shifts (36 hours) and one week of four 12-hour shifts (48 hours). The 48-hour week automatically triggers 8 hours of overtime pay under the FLSA.
That math gets exponentially worse in daily-OT states. In California, daily overtime kicks in after 8 hours in a workday and continues up to 12 hours. Anything beyond 12 hours in a single day must be paid as double-time, or twice the employee's regular rate of pay. Per the California Department of Industrial Relations, this applies to every non-exempt employee, every workday — there is no averaging across the week.
Here is what a single covered call-out actually costs on a 12-hour shift in a California operation, assuming a $25/hour base rate.
| Backfill option | Hours billed | Rate breakdown | Total cost |
|---|---|---|---|
| Off-cycle worker (fresh) | 12 | 8 × $25 + 4 × $37.50 | $350 |
| Held-over crew member | 12 (after just finishing 12) | 12 × $50 (double-time, continuous) | $600 |
| Mandatory hold-over splitting shift with outgoing crew | 6 + 6 | 6 × $37.50 + 6 × $50 | $525 |
| 8-hour partial coverage + 4-hour gap | 8 | 8 × $25 + 4 × uncovered risk | $200 + exposure |
The held-over option is the worst financial outcome and also the worst safety outcome. The fresh off-cycle worker is the obvious answer — assuming you can find one whose credentials are current and who is not already at 40 weekly hours.
This is the math that decides whether Panama is actually cheaper than 8-hour 5-2 coverage. If your call-out rate is high and your fresh-backfill pool is thin, the predictable OT savings of Panama evaporate fast.
Ready to move?
Ready to see Teambridge in action?
Backfill Playbook: How to Patch a Hole Without Burning the Next Cycle
A shift supervisor needs an unambiguous decision tree at 5:47 a.m. Not a Slack thread. Run the options in this order:
- Open the shift to the off-crew on day two of their three-off block. They are the least fatigued, have the cleanest weekly hour position, and the OT math is the least painful. Filter by credentials, weekly hours, and rest period before you broadcast.
- Split the shift with the outgoing crew. Holding the outgoing lead for the first six hours buys you time to find a clean backfill for the second half. This caps the held-over worker at 18 consecutive hours instead of 24, and avoids the double-time cliff at hour 12 in CA.
- Open the shift to qualified workers across other sites via mobile pickup. This is where credential-aware scheduling earns its keep — surface only the workers who are licensed, badged, and trained for this specific post.
- Mandatory hold-over as last resort. This is the option that produces the incident report two weeks later. Use it once and you teach your crews that calling out on day three is somebody else's problem. Use it twice and you start losing the held-over worker, too.
At each step, the system needs to enforce two hard blocks before the shift is offered: credential validity through the end of the shift, and rest-period compliance from the worker's last clock-out.
Warning
A tired or expired worker filling a hole creates a bigger problem than the original gap. Mandatory hold-overs that push someone past a consecutive-shift cap or fatigue threshold expose you to incident liability that dwarfs the cost of leaving the shift partially uncovered.
For security operators in particular, the credential check is non-negotiable — see how Teambridge's security staffing setup handles guard card and post-order verification at clock-in.
Running Panama Across Multiple Sites or Clients
For staffing agencies and multi-site security or janitorial operators, Panama gets harder fast because crews are not fungible. Site-specific training, client-approved rosters, and badge access mean you cannot pull a body from another contract just because they are on a three-off block.
The operators who run Panama well across multiple sites do three things:
- Float pools cap at two or three sites. Cross-train workers across more than that and the credential matrix becomes unmaintainable. Two or three sites gives you backfill optionality without exploding the training overhead.
- Client-approved rosters live in the scheduling system, not a spreadsheet. When the supervisor opens a shift, the platform should only surface workers the client has cleared for that post. A worker who is credentialed for Building A but not Building C should not appear in the C pickup list.
- Credential-aware backfill is the default, not a check. The mobile pickup queue should be pre-filtered by license, badge, training, and rest period before the worker ever sees the shift.
This is the operating model the Teambridge Scheduling product is built around — surfacing only eligible workers when a hole opens, across sites and clients, without the supervisor having to remember the matrix.
Janitorial and facilities operations face a similar version of this with route-based coverage instead of post-based, but the principle is the same: a credentialed body in the wrong building is a no-show.
What to Automate Before You Roll Panama Out
If you are standing up Panama from scratch, or moving from 5-2 coverage to a 12-hour rotation, the operational layer needs to be in place before the first cycle starts. Reactive coverage on Panama is how you end up at 70-hour weeks and mandatory hold-overs by week three.
The non-negotiables:
- Rotation template that enforces 2-2-3 and the 28-day day/night swap automatically. No manual rotation math. The template publishes the next 56 days at minimum so workers can plan.
- Credential expiry alerts that fire before the shift, not at clock-in. A 30-day, 14-day, and 3-day cadence catches the worker on their off-block when there is still time to renew. See credential tracking in the platform.
- Mobile shift pickup for backfills. Workers on their off-block see open shifts in real time and claim them with a tap. Pick Panama when shift-to-shift cognitive load matters more than cumulative load — ED nursing, ICU, security patrols, dispatch. Mobile pickup is what keeps your fresh-worker pool active without supervisor phone trees.
- Rest-period and consecutive-shift caps as hard blocks. Not warnings. Hard blocks that prevent the schedule from publishing if violated.
- OT forecasting per pay period. The system should project weekly hours per worker across the next cycle and flag where OT is about to hit the 48-hour wall.
- Daily-OT and double-time rules per jurisdiction. If you operate across states, the time tracking layer has to apply the correct rules per worker, per site, automatically.
The Teambridge Mobile App handles the worker-side: shift pickup, credential uploads, clock-in with GPS verification, and rest-period visibility. The admin side handles enforcement.
Panama only delivers its promised work-life balance and predictable OT if the operations underneath it — backfill, credentials, handoffs — are tight.
Panama Is a Coverage Strategy, Not a Schedule Template
The pattern is fine. Two on, two off, three on, two off, two on, three off has worked across security, healthcare, manufacturing, and utilities for decades because it produces consistent 24/7 coverage with humane rest cadence.
The operators who break their Panama rotation are the ones who treat it as a template in a spreadsheet. They publish the rotation, train the supervisors on the pattern, and assume the schedule will run itself. Then a call-out lands on day three, the held-over worker hits double-time at hour 12, the credential expiry shows up at clock-in instead of two weeks before, and the handoff between two unfamiliar leads costs them an incident.
The operators who run it well treat Panama as a coverage strategy that needs an operational layer underneath it. Credential-aware backfill. Rest-period enforcement. Multi-site eligibility. OT forecasting. Mobile pickup for fresh workers on their off-block. None of that is in the diagram. All of it determines whether the rotation actually delivers what it promises.
If you are running Panama today and the pattern is fine but the operations are fragile, that is the gap to close — not the schedule itself.
