Overtime creep at 12 guards: shift scheduling that stops it

Twelve guards. A handful of call-offs. One payroll run that suddenly has more overtime than you expected. If that sounds familiar, the problem probably is not a lazy team or a paperwork slip. The pattern shows up in three places: relief coverage, shift length, and open shifts never offered in a clear order.

In this post, we will walk through a simple two-week tagging exercise. You will learn how to track overtime from call-off coverage, four 12s that turn into 48 hours, and open shifts that sit unfilled until someone works a double. Then we will fix the pattern with standing relief slots, a written offer order, and 8- and 12-hour schedules that match the contract, not just a guard's preference. We will also look at templates, conflict detection, and state or provincial rules to check before you lock the week. By the end, you should see overtime coming before the pay run does.

Why overtime creep is a schedule problem, not a discipline problem

At 12 guards, four 12-hour shifts in one workweek is 48 hours, 8 over the weekly threshold. That is illustrative arithmetic from the weekly rule, not a sourced statistic. FLSA overtime is a weekly test: time and one-half over 40 in a fixed, recurring 168-hour workweek. Averaging two weeks is not allowed, so a heavy week cannot be offset by a light one.

You cannot waive it by agreement. A handbook line requiring pre-authorization, or counting only 8 hours a day, does not remove the obligation. A shift stipend or flat lump sum needs a careful look: depending on how it is structured, it may be included in the regular rate used to calculate overtime.

At 12 guards, you are the scheduler, dispatcher, and payroll clerk. One 22:00 call-off becomes a 16-hour shift for whoever answers the phone, and nobody sees the weekly total until the pay run. Enforcement is not theoretical: the DOL recovered more than $259 million in back wages for nearly 177,000 employees in FY2025, the most since 2019, with $184 million tied to FLSA violations.

Overtime creep is a schedule design problem. Start with a guard schedule that survives last-minute call-outs.

Tag overtime for two weeks: call-offs, shift length, open shifts

Find where overtime comes from. Audit two full workweeks, not one. One week can hide the pattern, audit two. Pick your workweek start (Sunday 00:00 is common) and write it down.

For every shift that runs over, record who covered it, why (call-off, shift length, or unposted open shift), and how many extra hours it produced. A shared note or a shift scheduling template with an overtime column is enough to start.

At the end, sort hours into three buckets: call-off coverage, shift length, and open shifts never posted. In most 12-guard firms one bucket carries most cost. Fix that one first. If call-offs dominate, Step 2: set coverage rules before the schedule goes live is the next read.

Count last-minute changes too: shifts rearranged close to start time are a signal worth tracking, even when no overtime is paid that night.

Call-off coverage: where the first extra hours appear

Now that the hours are tagged, start with the bucket that usually carries the most: call-offs. If a call-off arrives close to shift start and the nearest available guard has just finished their own 12-hour shift, that guard's workday doubles, and their weekly total can cross 40 before the week is half done.

Count how many call-offs land within a short window of shift start. That window is exactly what a standing relief slot absorbs, so the number tells you how many slots you need. Then look at who keeps answering the phone. At 12 guards, call-off coverage often concentrates on a small number of reliable people, and those guards' weekly totals are usually where the overtime bill lives. Check your own tags to confirm.

Finally, separate the planned call-off from the no-call no-show. A no-show needs a coverage rule and a documented response, not a schedule redesign. If call-offs keep landing on the same people, see how to build a guard schedule that survives last-minute call-outs before you move to shift length.

Shift length: four 12s is 48 hours, not 40

Call-offs are only part of it. Even without call-offs, the shift pattern alone can break 40. Four 12-hour shifts in a workweek is 48 hours, 8 over the threshold, so the fourth shift is partly overtime before anyone calls off, which is why 12 hour shift scheduling needs a rotation plan, not a roster with names in boxes.

Now check the pattern you run. Four on, three off gives 48 hours weekly. Three on, four off with a swing day depends on the swing count. Two days, two nights, four off averages 42, but a fixed workweek can catch 48 or 36.

Flat-rate posts need the same check: if the contract pays one amount per 12-hour shift, shift length alone may break 40 before any call-off.

Open shifts that never got posted

Shift length shows up in the pattern. An unposted open shift does not. Nobody can claim it, so it gets filled at the last minute by whoever is already on site, usually at hour 38 of their week. That is invisible overtime.

Tag every shift filled with less than a full day's notice before its start. That number is your practical open-shift count, and it is often larger than you expect.

Then check how shifts get offered. If shifts go out by text to one person at a time, in practice the selection tends to follow who replies first, not who has the fewest hours that week.

Finally, count the shifts that sat unfilled for days before someone took them. Those posts break coverage the first time your most reliable guard takes a holiday. Start with clear shift definitions so everyone knows what an open shift actually looks like.

Fix the pattern with standing relief slots

Fixing the unposted shift problem means building coverage into the schedule itself. Add one or two standing relief slots each week instead of leaving blank cells for a last-minute scramble. Each slot needs a named person and a defined post, not a maybe.

Place relief where your two-week audit showed call-offs cluster: the start of the workweek, the shift after a double, and any single-guard site.

Keep the relief hours inside 40 for whoever is assigned. A relief slot that pushes a guard to 46 hours is planned overtime with a nicer name, and it does not fix the design.

Rotate the relief slot across three or four people rather than loading it on your most reliable guard. That spreads the premium hours and keeps one person from burning out.

Give the relief guard a real task on site so the shift is not dead time: a patrol round, checkpoint sweep, report review, or training on a post they may cover next. It is one of the key operational areas that separate a firm running smoothly from one running on adrenaline.

Write an offer order for open shifts

Standing relief slots absorb the predictable gaps. For everything else, the fix is deciding who gets asked, in what order, before the shift goes out.

Write the order down: weekly hours already worked first, then seniority, then availability. That sequence covers most situations at 12 guards. Check hours before anything else. Offer a shift to a guard sitting at 38 hours and you have created overtime. Offer the same shift to a guard at 28 hours and it lands at 40 exactly.

Post the open shift to eligible guards at once with a defined claim window, set it short enough to fill the shift, long enough to reach everyone. Now the scheduling decision gets made by order, not by who happened to see the text first. If you want this built into a repeatable weekly routine, see how to schedule security guards and shifts without chaos.

Keep an offer log: who was asked, when, and whether they accepted. If a pay dispute or labor complaint surfaces later, that log shows your process was consistent. Record refusals in writing too. An offered and declined note stops the same two people being asked every week while the quiet guard never gets a call.

Match 8- and 12-hour patterns to the contract

Start with the contract, not what your guards prefer. Post hours, days of coverage, and whether the client changes requirements midweek decide whether 8- or 12-hour shifts actually fit.

8-hour shifts keep more guards under 40 hours and give you more hands for call-off coverage. The tradeoff: you double the number of scheduling shifts to fill, hand over, and supervise.

12-hour shifts cut handovers and travel, and most guards like the longer blocks. But four 12-hour shifts still requires a short week or relief slot to stay inside 40.

At 12 guards, hybrid patterns work well. Use 12s on static posts and 8s on sites with heavy patrol requirements or a client who adds coverage midweek.

Lock the pattern to a repeating two- or four-week cycle, and write your workweek definition next to it. Moving the workweek start to shave overtime is the kind of move that fails FLSA compliance.

Use a shift scheduling template and conflict detection before the week starts

Once your pattern is locked, put it in a shift scheduling template. A template holds the repeating pattern and shows each guard's weekly hours before publishing, so you can see who is at 40 without adding up a column by hand.

Conflict detection catches what you miss at 23:00: double-booked guards, a shift that breaks the rest period, a 12-hour post given to someone at 36 hours, and open shifts with no owner.

Employee shift scheduling software earns its place here: mobile schedules guards read on day one, clock-in tied to the site so hours are verified, and payroll-ready timesheets built from those clock-ins. See Scheduling that guards actually follow for the adoption side.

Opspot is built for teams this size, with drag-and-drop shifts, reusable templates, conflict detection, and guard schedules on a phone.

Check state and provincial rules before you lock the pattern

The federal weekly rule is the floor, not the whole law. California and a handful of other states require daily overtime after 8 or 12 hours, which changes what a 12-hour pattern actually costs. A fourth 12 in a California workweek can be partly double time, not time and a half.

In Canada, each province sets its own employment standards for overtime thresholds, daily rules, and any averaging agreements. Check the applicable provincial authority directly before finalising any pattern.

If you operate across more than one state or province, design to the strictest rule you work under. One tight pattern beats three loose ones you have to track separately.

Then re-read any 12-hour post agreement that pays a flat amount regardless of hours worked. If any post is paid a flat or stipend amount regardless of hours, get a written opinion from your payroll provider or employment counsel on how it interacts with the regular rate and overtime calculation.

Spend one hour with your payroll provider or an employment lawyer. Get the answer in writing and build the pattern around it.

What to do next

Once you have the rule in writing, run this sequence. It turns the audit into a routine.

This week. Pick your workweek start (Sunday at 00:00 is common) and tag every overtime hour for two weeks into three buckets: call-off coverage, shift length, and open shifts that were never posted. Add the shift date, who covered it, and the extra hours.

Next week. Add one standing relief slot and write your offer order (hours first, then seniority, then availability).

Before the next pay run. Publish the pattern two weeks out, check each guard's weekly total, and confirm the state or provincial rule in writing.

Keep the overtime tags and offer log in one place. The next two-week audit should take 20 minutes, not an afternoon.

If building the schedule is the bottleneck, Opspot is free to start for up to 3 guards and $8 per guard per month on Pro. Guards read their shifts on their phones the same day.

Conclusion

Overtime creep is a scheduling pattern, not a discipline failure, track extra hours in three buckets: call-off coverage, shift length, and open shifts that never got posted. Then add a standing relief slot where call-offs cluster, write a clear offer order, and publish the pattern two weeks out. Check state or provincial rules and your shift scheduling template before locking it in. A tight schedule protects your budget, your guards, and your time. You can stop overtime creep before it becomes the norm.