schedulingoperationsworkforce

Security Guard Shift Patterns Compared: 8s, 12s, DuPont, Panama, 4-on 4-off

Edison U. •

Most shift-pattern arguments are arguments about something else. The officer arguing for 12s wants fewer commutes. The branch manager defending whatever is already running wants to stop rebuilding the roster. Nobody is comparing the patterns on the terms that decide whether the post stays covered in February when two people are out.

This is that comparison. It assumes a continuous post — one officer, around the clock — because that is where the patterns actually differ.

Start with the number that governs all of them

A 24/7 post consumes 168 hours a week. A full-time officer at 40 hours covers 40 of them. That is 4.2 officers per post — before vacation, before training days, before the officer who quits without notice. Whatever pattern you pick, that number does not move. The patterns only decide how the 168 hours get sliced and who is standing there when a slice goes uncovered.

If you have not internalized the relief factor, start with scheduling 24-hour posts without coverage gaps — the rest of this article assumes it.

The comparison

PatternCrews for a 24/7 postAverage week per officerHow a calendar week actually landsWeekendsHandovers per dayWhat one call-off opens
8-hour, three shifts3 on duty, 4.2 bodies at 40h40 h, exactlyFlat. 5 × 8 = 40 every weekRotate through, or a fixed weekend crew38 hours
12-hour, two shifts442 h (168 ÷ 4)Depends entirely on the cycleDepends on the cycle212 hours
DuPont442 h48 / 72 / 48 / 0 across the four-week cycleOne full week off every four, weekend included212 hours
Panama (2-2-3)442 h60 / 24, or 36 / 48 — set by where the workweek startsA three-day weekend every other week, same days, permanently212 hours
4-on 4-off442 h36 or 48, in an order that never repeats against the calendarDrift through every day of the week212 hours

Two things in that table do most of the work.

Every 12-hour pattern averages 42 hours, not 40. Four crews into 168 hours is 42 apiece — two hours per officer per week, eight per post per week, built in before anybody calls off. DuPont, Panama and 4-on 4-off are all four-crew 12-hour rotations, so they all land on 42. The difference between them is not how many hours officers work. It is where those hours fall relative to your workweek boundary. Whether 42 crosses a threshold, and what that costs, depends on how your workweek is defined and on the rules in your jurisdiction — a payroll and counsel question before you price the contract, not after. See FLSA overtime and security companies for the orientation.

Eight-hour patterns divide cleanly and cost you a body. 5 × 8 = 40, flat, every week, no structural premium at all. The price is that you need a fractional person — the 0.2 — and three handovers a day instead of two. Three handovers means three chances for a late relief, three pass-downs, and a 2300 or 0700 changeover that has to happen in the dark.

Eight-hour shifts

The oldest arrangement and still the right one for a lot of posts. Three shifts, clean 40-hour weeks, no built-in premium, and the shortest exposure when something goes wrong: a call-off opens eight hours, and a hold-over produces a 16-hour double rather than a 24-hour one.

Where it hurts is people. Three crews plus relief on one post is more officers to recruit, badge, train on post orders and get client-approved. A five-day week means five commutes instead of three or four, which matters more than operators think when the post is forty minutes out and the windshield time is unpaid. And the 2300 handover is worse than an 1800 one — harder to supervise, harder to fill, and where late reliefs turn into hold-overs.

Use 8s when the post has activity peaks that do not run twelve hours, when the labor pool is deep, or when the client’s own staffing runs on the same three shifts.

Twelve-hour shifts, generically

Two crews on duty, four on the roster, two handovers a day, and each officer trading a longer day for more days off. That trade is why officers ask for 12s and why they are the default on static 24/7 contract posts.

The generic version — days and nights, fixed or rotating, without a named cycle — is what most branches run, and it is the baseline the three named patterns try to improve on. The mechanics, and the decisions that belong to the post rather than the officer, are in assigning 24-hour rotating and 12-hour shifts.

The structural weakness of every 12-hour pattern is the size of the hole. Twelve open hours cannot be absorbed by a supervisor covering “for an hour.” If nobody takes it you are choosing between a hold-over that produces a 24-hour day and an open post you have to tell the client about.

DuPont

Four crews, a 28-day cycle, fourteen 12-hour shifts per crew, and one full calendar week off every four — the strongest recruiting feature of any common security rotation.

The weekly landing is the thing to look at: 48, 72, 48, 0. One week in four has six shifts in it, back to back through a day-to-night flip. That is where fatigue, sick calls and premium hours concentrate. The zero week is real time off, but it also means the crew that is out is genuinely unavailable — your bench that week is three crews, not four.

DuPont works when you have four full crews and a relief officer who is not one of them. It punishes small forces hard — where exactly it breaks is in the DuPont schedule for 24/7 security posts.

Panama (2-2-3)

Fourteen-day cycle, seven 12-hour shifts, and the one feature no other pattern offers: a three-day weekend every other week, on the same days, forever. Officers can plan a life around it, and retention tends to be the easiest thing about a Panama post.

The cycle is a clean multiple of the calendar week, which means you can actually choose how the hours land. Depending on where the workweek boundary sits, the same officer working the same shifts sees either a 60-hour week followed by a 24-hour one, or a 36 followed by a 48. Identical work, materially different premium exposure. Very few operators know they have that lever.

What Panama costs you is continuity. Two-on and three-on blocks mean the person who saw the problem is often not the person who has to deal with it, and the pass-down has to carry the weight that memory carries on longer blocks — the real subject of the Panama schedule explained.

4-on 4-off

Four 12s, four days off, an eight-day cycle. Half the year off, and the pattern officers pick when you let them.

The eight-day cycle is the whole story. It never aligns with a seven-day week, so weekends and holidays fall wherever they fall, and the officer’s calendar week swings between 36 and 48 hours in a sequence that does not repeat against your payroll period. You cannot set a boundary to smooth it the way you can with Panama. Same 42-hour average, least predictable of the three.

It is also the least forgiving on a call-off, because both the on-block crew and the off-block crew are exactly where you would not want them: the on-block officer is mid-run and the off-block officer is on day two of four. Detail in the 4-on 4-off schedule: pros and cons.

Which one survives a call-off

This is the question that should decide it, and it almost never gets asked.

  • 8s open the smallest hole and have the deepest pool of people who can take it without crossing a threshold. Easiest to fill, cheapest to fill.
  • Panama has the most people plausibly available on any given day, because the off-blocks are short and staggered. A crew is usually one text message away.
  • 12-hour generic and 4-on 4-off depend entirely on whether your off-block officer picks up the phone. If they do not, you are holding someone over for 24 hours or you have an open post.
  • DuPont is the worst case in the zero week. One quarter of your crew capacity is deliberately unreachable, and the crew coming off the 72-hour week is the last group you should be calling.

The honest conclusion: no pattern is resilient. A relief officer is. The pattern determines the size and shape of the hole; whether it gets filled is a roster question. If one post generates a fill every single week, you are short a body, and no rotation will fix that.

How to choose

Pick the pattern that matches the post, then check it against three constraints in this order:

  1. Can you actually staff four crews plus relief? If not, DuPont and 4-on 4-off are off the table regardless of how much officers want them.
  2. Where does your workweek boundary sit? On Panama it is a lever. On DuPont it decides whether the 72-hour week is one week or two. On 4-on 4-off it is noise.
  3. What does the client tolerate on handover? Three handovers a day on a sensitive post is three more chances for an unfamiliar officer at the desk.

Then publish it where officers can see it and where fills get recorded when they happen, not reconstructed on Monday. That is the difference between a pattern that works on paper and one that works in the field — guard scheduling software that assigns to the post rather than the person, and guard time and attendance that keeps hour totals current all week so you find out about premium hours while you can still do something about them. What to do with that visibility is the subject of controlling overtime in a security guard company.

Wage and hour obligations, workweek definitions and any state rules beyond the federal baseline vary by jurisdiction and by how your workforce is classified. Everything above is operational arithmetic, not legal or payroll advice — confirm your own obligations before you build a pattern into a contract.

If you want to see how these patterns look when the schedule, the fills and the hour totals live in one place, explore CGuardPro or get in touch.

Run the whole operation in one place

Shifts, attendance, patrols, incident logs and clients on one platform — with the guard app on site and the client portal on the other side.

  • Attendance with selfie and GPS
  • QR patrols and a digital logbook
  • Client portal included

Keep reading