Reduce security guard callouts: nine fixes

The phone rings at 5am and the guard on the 6am post is not coming in. You work down the roster, and if nobody picks up you stand the post yourself. Security guard callouts never reach zero, but the rate is yours to move.

How bad is the callout problem, really?

Worth grounding this before you write a policy. The Bureau of Labor Statistics puts the total absence rate for protective service occupations at 2.9 percent of full-time wage and salary workers in an average week, against 3.2 percent across all occupations. Security is not an outlier for absence.

What makes it feel like one is the coverage model. An absent accountant means an email goes unanswered. An absent guard means a client's site is unmanned and somebody has to be physically standing there within the hour. Same absence rate, wildly different consequence.

So the goal is two-sided. Bring the rate down, and build an operation that absorbs the remainder without a 5am scramble.

Why do guards miss shifts?

The instinct is to crack down. Stricter policy, faster discipline. Punishment does not solve a problem that lives in someone's circumstances rather than their attitude, and four circumstances account for most of it.

Transportation. A car that will not start, a suspended license, a bus route that does not run at shift change. These are logistics, not character. Some operations have cut their rate just by learning which guards ride transit and scheduling them onto shifts the route actually serves.

Second jobs. BLS counted multiple jobholders at 5.2 percent of everyone employed in August 2026, and in an industry with a lot of part-time posts the share is higher than that. When two schedules collide, the job paying more wins. Knowing who has a second job, and when it runs, prevents the collision.

Childcare. Schools close for snow. Sitters cancel. Kids get sick at 4am. For a single parent working a post whose hours no daycare matches, that is not a decision they get to make.

They already quit. Attendance is the first symptom of a resignation, not the last. A guard who feels stuck on a post nobody wants stops showing up weeks before they stop working there. If your callouts cluster on one person, read the retention side of this before you read the discipline side.

Nine ways to cut the callout rate

1. Ask why, one guard at a time. Every callout gets a two-minute conversation at the next shift. Not a warning, a question. Do that for a month and the pattern names itself: three people with the same bus problem, or one site everybody dreads.
2. Keep an availability record and schedule against it. A guard who was never free on Friday nights, scheduled repeatedly for Friday nights, will eventually call out on a Friday night. That is a data problem. Availability changes as second jobs and family arrangements change, so it needs re-asking, not a one-time hiring form.
3. Publish schedules with real lead time. A schedule that lands two days before it starts generates callouts from guards who already committed to something else. Lead time costs you nothing and removes an entire category of conflict.
4. Keep the weekly pattern stable. Same days, same hours, week after week. Consistency is what lets a guard lock in a carpool and a childcare arrangement. Rotating people through unpredictable patterns quietly guarantees that both of those keep breaking.
5. Assign to the nearest site you can. A guard doing 45 minutes each way to a post that sits 10 minutes from someone else's house will start finding reasons. Geography is a retention lever disguised as a logistics detail.
6. Send a reminder the night before. A push notification the evening before catches the guard who had the wrong day in their head. It feels too simple to matter. It removes real no-shows.
7. Run an open shift board. When a callout lands, unassign the shift and put it where every eligible guard can see it. Somebody who wants the hours claims it from their phone, often before a supervisor has finished reading the message. Coverage gets solved sideways instead of down a phone list.
8. Enforce an attendance policy you can live with. Details below, but the short version is that an unenforced policy teaches guards the policy is decoration, and a policy that fires people for a genuine emergency teaches them you are not worth turning up for.
9. Carry enough roster depth to absorb the rest. Prevention has a floor. Below it, the only thing standing between an absence and a service failure is a bench. See the arithmetic below.

Number 7 is the one software does for you. In TeamMap, a shift left unassigned on the schedule shows up as an open shift a guard can take from their phone, and a shift nobody clocks into raises a no-show alert instead of a phone call at 5am.

What does a workable attendance policy look like?

Two failure modes, and most companies pick one.

The paper tiger promises termination on the third callout and has never terminated anybody. Guards read it correctly as noise. The other extreme fires a good guard whose mother had a stroke, and everybody else on the roster learns exactly what they are worth.

What works sits in between. Progressive steps, documented at each one: verbal, written, final, termination. Applied the same way to everybody, which is the part that actually does the work. A policy that bends for the supervisor's favorites is not a policy.

Grade the absences too. A guard who calls at 3am for a 7am shift gives you four hours to solve it. A guard who simply does not appear gives you none, and the client sees it. Those are not the same event and should not carry the same consequence.

Then pay for the behavior you want. An attendance bonus, first pick of shifts, the good post when it opens up. Reliability is the scarcest thing on a security roster, and people who have it should be able to tell that you noticed.

How much roster depth do you need?

Operators generally aim for something like 1.2 to 1.5 times minimum coverage, which for ten posts standing at once means twelve to fifteen people on the roster. That is a rule of thumb rather than a measured figure, and the right multiple depends on your own callout rate and how many of your posts need a site-specific qualification.

It looks expensive until you price the alternative. Every absence you cannot cover from the bench gets covered at time and a half, which is the direct line between this article and your overtime number.

Two things make the bench go further. A pool of part-timers who want occasional hours rather than a full schedule gives you people who are pleased to be called. And cross-training widens who can go where: a guard checked out on four sites is four times the coverage of a guard who only knows one. That depends on post orders good enough to work from cold, which most sites do not have.

Depth starts at hiring, though. If you are running at 1.0 coverage you are not managing callouts, you are absorbing them personally. Fix the pipeline first.

What to track

Callouts per guard, per site, per day of week, per shift. Four cuts of the same log, and each one answers a different question.

Per guard finds the individual conversation. Per site finds the post nobody wants, or the supervisor nobody wants. Per day of week finds the second-job conflict hiding in plain sight. Per shift finds the 6am start that no bus reaches. In the moment every callout feels random. Aggregated over a quarter, almost none of them are.