What Is a Panama Schedule? A Complete Guide

The first time I looked closely at a Panama schedule, what caught my attention was the weekend. Most shift rotations scatter days off in ones and twos, but the Panama gives every crew every other weekend off without touching their time off balance, which is why so many shift workers prefer it. If you run an operation that never closes, this guide shows you how the 2-2-3 rotation works, what it really costs in overtime, and whether your team can staff it.

The Panama schedule, better known in the industry as the 2-2-3, is one of the most common ways to cover a 24/7 operation with 12-hour shifts. It is a rotating pattern that keeps four crews cycling through days and nights so that someone is always on the floor. Its appeal is a short, predictable rhythm with frequent breaks, and its cost is the same thing every 12-hour rotation carries: long shifts and structural overtime that a business has to plan for.

You will also find a clear two-week Panama schedule example, the exact split of hours and overtime, the state and industry rules that make 12-hour shifts more expensive, which industries use the pattern, its pros and cons, how it compares to other rotations, and how to put it in place on a small team.

A rotating 12-hour schedule only works when the coverage, the paperwork, and the overtime math are all handled correctly. I built FirstHR to hold the employee records, onboarding, and signed shift policies around a rotation like this, while the schedule itself lives in your own scheduling tool. This is general information, not legal advice, so confirm specifics with counsel for your situation.

What Is a Panama Schedule?

A Panama schedule is a rotating shift pattern that provides continuous, around-the-clock coverage using four crews working 12-hour shifts across a 14-day cycle. Each crew follows the same repeating sequence of work and rest days and, notably, gets every other weekend off. It is known just as often by its numeric name, the 2-2-3 schedule, which describes the rhythm of the rotation directly.

The name is where the pattern gets a little mysterious, because its origin has never been documented with any certainty. The popular explanation ties it to round-the-clock operations in the Panama Canal Zone, but the accounts that repeat it cite no evidence, so treat the name as a widely used label, not as history. What matters is the pattern itself, which is precisely defined even if its history is fuzzy.

What makes the Panama a rotating schedule is that crews move through the pattern together and, in most implementations, alternate between day and night blocks over time rather than being fixed on one. That spreads the burden of night work more fairly than a permanent-nights setup. Add the every-other-weekend-off feature and the short two-week cycle, and you have the core of why the schedule is so widely used.

How the 2-2-3 Rotation Works

The 2-2-3 rotation is best understood one crew at a time: each crew works two days on, two off, three on, two off, two on, then three off, and the 14-day pattern repeats. That sequence is exactly what the name 2-2-3 encodes: blocks of two and three working days separated by rest. Seeing it laid out on a grid makes the rhythm click.

Read the grid and the shape becomes clear. The blocks of two and three alternate, and when the rotation is aligned to the calendar, the three-off block at the end of each fortnight is what delivers the every-other-weekend feature. Work also never runs more than three consecutive shifts before a break, which is a big part of why the schedule keeps cumulative fatigue lower than rotations with longer runs.

The National Institute for Occupational Safety and Health (NIOSH) makes the same point about fatigue. Its training for nurses on shift work notes that long stretches of work days build fatigue, particularly with shifts of 12 hours or more, and suggests two rest days after three consecutive 12-hour shifts. The Panama meets that mark: every three-shift block is followed by exactly two days off.

With four crews, the staggering is what produces continuous coverage. On any given day, two crews are working, one on days and one on nights, while the other two are off. As one crew moves into its rest block, another moves into a work block to cover it, so the operation never goes uncovered.

Because only two shifts cover each day, there are just two handoffs per day instead of the three a schedule of shorter shifts would need. Fewer handoffs means fewer of the communication gaps where information gets dropped between shifts. The whole design balances continuous coverage, fair distribution of nights, and frequent rest, at the one unavoidable cost of 12-hour shifts and the overtime they generate.

A Panama Schedule Example: Two Weeks at a Glance

Seeing all four crews together over a full two-week cycle makes the coverage concrete. In the table below, D is a day shift, N is a night shift, and a blank is a day off.

Trace any single crew across the two weeks and you see the 2-2-3 pattern: two shifts, two off, three shifts, two off, two shifts, three off. The three-shift block lands on Friday, Saturday, and Sunday, so crew A works the first weekend and has the second one off, while crew B does the reverse. That is the every-other-weekend feature made visible.

Trace any single column down and you see exactly one D and one N, which is the whole point: complete day-and-night coverage with no gaps. Four crews is the magic number here: it is the minimum needed to keep two working and two resting on every day of the fortnight.

One practical note on the day-and-night split. In the simplest version shown here, crews A and B stay on days while C and D stay on nights. Many operations rotate crews between days and nights over longer periods so that no group is stuck permanently on nights. Both are valid Panama schedules; the choice depends on whether you prioritize fairness of night work or the stability of a fixed shift.

Hours and the Overtime Built In

A Panama schedule averages 42 hours per week, but that average hides an uneven split that has real overtime consequences. Over the 14-day cycle, each crew works seven 12-hour shifts, which is 84 hours, or 42 per week on average. The catch for payroll is that the two weeks are not equal, and which shifts land in which week depends on where you set your workweek, not on the calendar grid above.

The critical rule, as with any rotating schedule, is that overtime under the Fair Labor Standards Act (FLSA), the federal wage and hour law, is calculated per workweek and cannot be averaged across weeks. According to the U.S. Department of Labor, non-exempt employees (those covered by the overtime rules) must be paid overtime for hours over 40 in a workweek, and averaging of hours over two or more weeks is not permitted.

The regulation behind that rule, 29 CFR 778.104, says each workweek stands alone, and it works the point through with a 30-hour week followed by a 50-hour week. The fortnight averaging to 42 hours changes nothing: the 48-hour week owes 8 hours of overtime, and the 36-hour week does not offset it.

Where the workweek starts decides the split. Under 29 CFR 778.105, a workweek can begin on any day and at any hour. If you start it at the beginning of a day shift, so that no shift straddles two weeks, five of the seven possible start days give the 36-hour and 48-hour weeks above.

This built-in overtime is predictable enough to budget for cleanly, and many employees value the reliable extra earnings from the heavier weeks. The mistake employers make is modeling the Panama as a flat 42-hour average and forgetting the weekly calculation, which under-budgets labor cost.

State and Industry Rules That Change the Math

Federal weekly overtime is only part of the compliance picture, and for a 12-hour schedule the state and industry rules are often the bigger cost. Several states require daily overtime, meaning overtime is owed for hours beyond a daily threshold regardless of the weekly total. On a 12-hour shift, an 8-hour daily threshold is crossed on every single shift, which can add cost the federal weekly rule alone would not.

California is the clearest example. According to the California Division of Labor Standards Enforcement, non-exempt employees earn time and a half for hours beyond 8 in a day up to 12, and double time for all hours beyond 12 in a day. On a 12-hour Panama shift, hours 9 through 12 are daily overtime regardless of the weekly total.

An alternative workweek schedule, the employee-approved California exception to daily overtime, does not rescue a 12-hour shift there. An approved schedule exempts a regularly scheduled day of no more than 10 hours within a 40-hour week; hours past 10 and up to 12 still pay time and a half. Only health care employers under Wage Orders 4 and 5 may schedule a 10-to-12-hour day without daily overtime.

Adopting an alternative workweek schedule is its own project. Under California Labor Code 511, the employer proposes the schedule, and it counts as adopted only if at least two-thirds of the affected employees in a readily identifiable work unit approve it in a secret ballot election. The employer then reports the result to the Division of Labor Standards Enforcement within 30 days after it is final. Other daily-overtime states add their own variations.

The practical takeaway is that a Panama schedule's true labor cost depends heavily on where and in what industry you run it. A setup that pencils out under federal rules alone can cost more in a daily-overtime state, and hospitals and residential care establishments have their own framework entirely.

Because state and industry overtime rules vary and change, the essential step before adopting the Panama is to model the full labor cost, including any state daily overtime and industry-specific rules, in every location where your employees work.

Which Industries Use the Panama Schedule

The Panama is concentrated in operations that run continuously and need steady, reliable staffing around the clock. Common users include manufacturing and continuous-process plants, healthcare facilities, security and public safety, utilities, emergency services, call centers, and logistics operations. The common thread is work that cannot stop and benefits from having people present regularly rather than away for long stretches.

Where those conditions hold, the 2-2-3's short cycle and frequent breaks make it a strong fit. Because the Panama never works more than three consecutive shifts, it keeps cumulative fatigue lower than rotations with longer runs. That matters most in settings like healthcare and security, where alertness is safety-critical and steady presence supports continuity of care or coverage.

This is also where the Panama tends to be preferred over longer-cycle rotations. A pattern like the DuPont, which gives a full week off but demands longer consecutive runs, suits process-driven industrial work where a long recovery break is prized. The Panama's more even distribution of work and rest tends to suit environments that need people present more continuously.

Pros and Cons of the Panama Schedule

Setting the compliance mechanics aside, the Panama has clear strengths and real drawbacks as a way of organizing shift work. Its profile is more moderate than the extremes of some rotations, trading the single biggest reward, such as the full week off a DuPont gives, for a steadier, more even rhythm. Here is an honest accounting of both sides.

The advantages cluster around balance and predictability. Every other weekend off is a genuine, no-vacation-required benefit, and the short 14-day cycle lets people plan their lives with confidence. Capping consecutive work at three shifts keeps fatigue more manageable than longer-block rotations, and the two-handoff structure reduces the communication errors that happen at shift changes. For workers who value frequent breaks and steady rhythm, the Panama is attractive.

The drawbacks cluster around the demands of 12-hour shifts and the four-crew requirement. Twelve-hour shifts are long and tiring, particularly the night blocks, and the frequent day-to-night transitions can disrupt sleep for some people. The structural overtime, while predictable, is a real cost. And the four-crew minimum is a genuine barrier for smaller operations. Whether these tradeoffs work depends entirely on the workforce and the nature of the operation.

Panama vs DuPont vs Pitman vs 4-on-4-off

The Panama is one of several four-crew rotations, most of them built on 12-hour shifts, and choosing between them is one of the most common decisions for an operation setting up 24/7 coverage. They mostly share the same average hours; the real difference is the rhythm of work and rest. The table below lays out how the main patterns compare.

A few distinctions are worth calling out. The Panama and the Pitman are, for practical purposes, the same 2-2-3 pattern, and the names are often used interchangeably. The DuPont is the main alternative to weigh: it trades the Panama's even, frequent breaks for one long seven-day break per cycle, at the cost of up to four consecutive shifts and a demanding 72-hour week. The 4-on-4-off is simpler but pushes consecutive shifts to four.

If steady presence and lower cumulative fatigue matter most, as they often do in healthcare and security, start with the Panama. If a long recovery break is the prize, as it often is in process-driven industrial operations, look at the DuPont. Either way, the right one depends on the specific demands of your operation and the preferences of your crews.

Is a Panama Schedule Right for Your Small Business?

The honest truth about the Panama on a small team is that a true version requires four crews, and that is a hard constraint. If you cannot staff four balanced crews, you cannot run a genuine Panama as designed. This is the first thing to confront with limited headcount, and it is the point most guides written for large plants skip entirely. Run through this checklist to see whether the pattern actually fits your situation.

If you cannot check all of these, the standard Panama is probably not your answer, and that is useful to know early. Smaller operations that still need round-the-clock coverage usually turn to modified patterns: fewer crews with more planned overtime, a simpler two-crew day-and-night split without the full rotation, or part-time and relief staff to fill gaps. Each trades some of the Panama's benefits, particularly the clean every-other-weekend-off feature, for feasibility at a smaller scale.

The most useful question for a smaller operation is whether it genuinely needs continuous 24/7 coverage or whether the real need is extended-hours coverage a simpler schedule could meet. Continuous coverage is expensive and staffing-intensive however you arrange it. Adopting a demanding rotation because it is well known, rather than because the coverage need truly requires it, is a common and costly mistake. Being honest about the actual requirement is what saves smaller operations real money.

How to Implement a Panama Schedule in Six Steps

If the Panama fits, implementing it well is mostly a matter of doing a few things in the right order. Rushing to the rotation grid before confirming the coverage need and the overtime cost is how operations end up with a schedule that looks tidy on paper and drains money in practice. Here is the sequence that works.

The step people most often shortchange is the fourth, modeling the full cost. It is tempting to look at the 42-hour average and assume the labor cost is close to a normal full-time schedule, then discover the real number only after payroll runs. Doing the math before rollout, with the actual weekly split and the rules for your state and industry, is what protects your margins and prevents unpleasant surprises.

Steps three, four, and five produce one document between them, and it belongs somewhere other than a spreadsheet tab nobody opens again. The workweek boundary is a choice you make once and then have to apply consistently, so write down what you picked, what it produces on this rotation, which state rules you checked and with whom, and who approved the resulting cost. When somebody questions a paycheck eighteen months from now, this is the page that answers it.

Onboarding and Compliance Without a Dedicated HR Team

Running a rotating 12-hour schedule creates a set of people-operations tasks that are easy to underestimate, especially without a dedicated HR person. You need to track which crew each employee is on, onboard new hires onto an unfamiliar rotation, document shift and overtime policies, collect any required consents, and give employees a way to see their own schedule and request swaps. On a small team, these tasks usually land on the owner or a manager already stretched thin.

This is where getting the underlying systems right pays off. Employee records that hold crew assignments and shift preferences keep the rotation organized as people join and leave. A clear onboarding process gets new hires up to speed on what a 12-hour rotation actually involves, including practical fatigue and sleep guidance, before their first shift. Storing shift policies and any signed agreements in one place, rather than scattered emails, keeps you covered if a question ever arises about what an employee agreed to.

The broader point is that a shift schedule is a people-operations system, and the grid of days is only its visible part. The employee records, onboarding, document storage, and self-service around it are what make the rotation sustainable over time, so put them in place before the first crew starts its first block.

Frequently Asked Questions