Security Guard Scheduling: Shifts, Coverage Windows and Handovers

The coverage window comes from the property, not a template

A coverage window is the block of hours a post actually needs to be filled. It is not the same question as how many officers a property needs; a community can settle on one officer at a time and still get the window wrong by starting the shift two hours before the risk does or ending it two hours before the risk stops. The window is set by reading what has actually happened: when calls come in, when doors are found propped, when the lot fills and empties, when the office closes and the property is left to itself. A garden community with a pool and a courtesy line usually needs its window to open before the pool closes and to run past the hour disturbances tend to happen, not simply “nights.” A construction site needs its window to open when the crews leave and the fence becomes the only thing between the yard and the street, not at a round number like six.

Manager and dispatch build the window together on the walk-through, using whatever record exists: incident history, resident complaints, a maintenance log of doors found unlocked. Where there is no record yet, the first month of daily reports becomes one, and the window is narrowed or widened from what those reports show rather than left as a guess.

Shift length trades fresh officers against fewer handovers

Once the window is set, the next decision is how to fill it: one long shift, or two or three shorter ones. An eight-hour shift keeps officers close to their sharpest hours and gives a manager three points in the day to raise something with a fresh person, but it means three handovers instead of one or two. A twelve-hour shift halves the handovers and the scheduling complexity, at the cost of asking an officer to stay attentive through the back half of a long night. A ten-hour pattern splits the difference and is common on posts that run a genuinely long window, such as an evening-through-overnight community post.

Shift length	Handovers per 24-hour post	Where it tends to fit
Eight hours	Three	High-traffic posts, lobbies, event coverage where alertness in the last hour matters most
Ten hours	About two and a half	Evening-and-overnight community and commercial posts
Twelve hours	Two	Long, quiet windows such as construction sites or fire watch rounds

None of these is correct in the abstract. A twelve-hour pattern on a post with a busy midnight-to-two window asks the same officer to be sharpest at the point furthest from a break; an eight-hour pattern on a quiet overnight post adds handovers without adding value. The post orders record which pattern was chosen and why, so the choice can be checked against what the daily reports actually show once the post has run for a few weeks.

The handover is scheduled time, not a hallway exchange

A handover is the minutes when one officer’s post becomes another officer’s post, and it is where round-the-clock coverage most often breaks down quietly. If the outgoing officer leaves before the incoming one arrives, the property has no coverage for however long the gap runs, and it happens twice a day, every day, until someone notices. Price Protection’s post orders schedule the incoming officer to arrive before the outgoing one leaves, so there is always an overlap rather than a relay race.

What passes between the two officers in that overlap matters as much as the timing. The outgoing officer briefs anything unresolved: a contractor still on site, a resident who threatened to come back, a gate that would not latch on the last round. The activity log is signed over so the record of the shift reads as one continuous account rather than two separate ones with a blank spot between them. Keys, access cards, the radio and any equipment issued at the post are counted and handed across, not left in a drawer for whoever shows up. Both names and the time go into the record, so if a question ever comes up about who was on post at a specific minute, the answer is written down rather than reconstructed from memory.

Weekends and seasons change the whole pattern, not just the hours

A schedule built around a Tuesday is not automatically right for a Saturday. Weekend nights at an apartment community often bring more calls and more amenity traffic than a weekday evening, which argues for either a longer window or, on the busiest nights, a second officer rather than the same single post stretched thinner. A retail corridor’s holiday weeks and a community’s summer turn season are the same kind of exception: the underlying window shifts because the property’s own rhythm shifts, and the schedule that was correct in March is not automatically correct in July or December.

The fix is not to run every window at its busiest setting year-round, which spends hours where they are not needed. It is to build the base schedule from the property’s typical week and layer named exceptions on top of it: a weekend addition, a holiday block, a turn-season extension, each with its own start and end date and its own handover into and out of the regular pattern. Dispatch keeps the calendar and the post orders current with each change, so the officer arriving for a Friday shift is working from the schedule that actually applies that week, not the one that applied when the contract started.

Getting the schedule right at the start

The clearest way to set a first schedule is to bring what is already known: when problems have happened, when the property empties out, which days differ from the rest of the week, and any dates already known to need more coverage. A supervisor uses that, together with what is seen on the walk-through, to propose a coverage window and a shift pattern, and the post orders record both along with the handover routine that keeps the window whole around the clock. The schedule is not fixed at that point; it is reviewed against the reports it produces and adjusted as the property’s own pattern becomes clearer.