A practical guide to one of the most popular 12-hour shift patterns for 24/7 operations, including the overtime math.
A 2-2-3 work schedule (often written as a 223 schedule) is another name for the Pitman schedule. Employees work 12-hour shifts in a 14-day cycle: 2 days on, 2 days off, 3 days on, 2 days off, 2 days on and 3 days off. Four teams, two on days and two on nights, cover the clock 24/7. Each employee works 7 shifts, or 84 hours, every two weeks, which averages 42 hours a week: one week of 36 hours and one of 48 hours.
The Pitman schedule is used in 24/7 operations such as manufacturing, warehousing and distribution, security, emergency services, utilities and some healthcare roles. Two teams cover days and two cover nights, so a site always has one team on each 12-hour shift. It is popular because the pattern is easy to remember and gives regular long weekends. For other patterns, see types of work shifts.
| Week | Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|---|
| Week 1 | Work | Work | Off | Off | Work | Work | Work |
| Week 2 | Off | Off | Work | Work | Off | Off | Off |
The pattern repeats every two weeks. Team B works the opposite days to Team A on the same shift, so between them every day is covered. Teams C and D do the same on the other 12-hour shift.
There are two common versions. In the fixed version, two teams always work days and two always work nights. Employees keep a steady body clock, but night work is not shared. In the rotating version, teams switch between days and nights, often every few weeks. Night work is shared more fairly, but each switch disrupts sleep. Many sites let employees state a preference and combine both approaches where possible. Our glossary entry on rotating shifts explains the trade-offs.
Federal overtime is calculated per workweek, and averaging over two weeks is not allowed. With a Monday-to-Sunday workweek and the cycle above, an employee works 60 hours in week 1 and 24 hours in week 2, so 20 hours of overtime are due in week 1 even though the two-week average is 42.
| Workweek alignment | Week A hours | Week B hours | Overtime hours per 2 weeks |
|---|---|---|---|
| Workweek starts on the cycle’s first workday (as above) | 60 | 24 | 20 |
| Workweek starts two days later in the cycle | 36 | 48 | 8 |
Your workweek must be fixed and cannot be changed simply to reduce overtime, so plan the alignment when you first adopt the pattern and get advice if you are changing an existing workweek. In daily-overtime states, such as California, hours over 8 in a day may also be overtime; see daily overtime rules. Our overtime calculator helps estimate the cost.
Twelve-hour night shifts are demanding. Employees adapt better when the schedule is predictable, when they have a quiet place for breaks and when long stretches of nights are avoided. Encourage teams to plan sleep around their shifts, keep commutes in mind after a night shift and speak up if fatigue becomes a problem. Our glossary entry on the night shift covers common considerations.
Because each team works only seven shifts in two weeks, there is room to cover absences within the pattern, for example by asking someone from the other team on the same shift to pick up an extra day. Watch the weekly total, though: an extra shift in the 48- or 60-hour week adds more overtime than one in the short week. A short list of trained float staff and a clear, fair process for offering extra shifts keeps coverage reliable without wearing out the same people.
Both patterns use four teams and 12-hour shifts and average 42 hours a week. The DuPont schedule has a 28-day cycle with a seven-day break, but includes stretches of four shifts in a row and day/night switches within the cycle. The Pitman schedule has a shorter cycle, no more than three shifts in a row and regular three-day weekends. Teams often choose Pitman for its predictability and DuPont for its long break.
With EZTime scheduling, you can build each team’s shifts and repeat the pattern, and employees see their shifts in the mobile app. The time clock records actual hours, so weekly totals and overtime reflect what really happened, including late finishes and swaps.
Another name for the Pitman schedule: work 2 days, off 2, work 3, off 2, work 2, off 3, in a 14-day cycle with 12-hour shifts.
An average of 42 hours per week over two weeks, though actual weekly hours alternate.
Usually yes, for non-exempt employees, in the weeks where hours exceed 40. The amount depends on how the cycle aligns with your workweek.
Four: two for day shifts and two for night shifts.
Every other weekend, as a three-day block from Friday to Sunday.
The classic Pitman pattern uses 12-hour shifts. With 8-hour shifts you would need more teams and a different rotation to cover 24 hours.
It needs four teams to cover a site around the clock, so it suits operations with enough staff on each shift. Smaller teams can use the 2-2-3 rhythm for day coverage only.
Because EZTime links the schedule to the time clock, you can block early clock-ins or punches outside assigned shifts.