Security guard shift handoff SOP template

The suspicious vehicle that circled the lot four times at 11pm is worth nothing if the night officer never hears about it. Most shift handoffs are a nod in a doorway and a set of keys. Here is a written SOP you can post tomorrow.

Why security shift handoffs fail

Almost always for one of three reasons, none of them exotic.

The relief arrives at the exact minute the shift starts, so there is no overlap in which to brief anyone. The outgoing officer is tired and gives the two-sentence version. Or the important thing was never written down, so it lives only in the head of someone who is now driving home.

A written handoff fixes all three, but only if the overlap is scheduled and paid. Which brings up the part most operators get wrong.

SOP purpose, scope and timing

This standard operating procedure sets the requirements for security officer shift changes: continuity of coverage, transfer of information that matters, and accountability for equipment and post condition. It applies to all security personnel at scheduled shift changes, unscheduled relief, and temporary post coverage.

Ten to fifteen minutes is what most posts settle on. Pick your own number, put it on the schedule, and hold it. A handoff window that exists only in the SOP gets skipped by week three.

Before relief arrives: the outgoing officer

1. Close out every pending incident report. Not "start" them. Close them.
2. Bring the daily activity log current to the minute.
3. Write down anything still running that the next officer has to watch.
4. Inventory equipment and keys against the log.
5. Note maintenance issues and safety hazards observed during the shift.
6. List pending tasks and follow-ups, with who owns each one.

Reports written the next day from memory are the ones that fail under scrutiny. Writing them while the detail is fresh is a handoff requirement, not a preference.

The face-to-face briefing

Verbal, in person, against this list, in this order. The list is what stops a tired officer from skipping the item they think is unimportant.

1. Active incidents and ongoing situations

• Incidents that occurred during the shift
• Situations still being monitored
• Follow-up actions expected and who is doing them
• Persons of interest or banned individuals on or near the property

2. Operational status

• Alarm status, including any zones bypassed and why
• Doors and gates currently secured or deliberately unsecured
• Areas with special access requirements today
• Deliveries, contractors or events expected on the incoming shift

3. Equipment status

• Radio working, and the channel it is on
• Vehicle fuel, condition and anything new since the last shift
• Flashlight, keys and access cards accounted for
• Anything broken, intermittent, or reported and not yet fixed

4. Facility conditions

• Leaks, burned-out lights, doors not latching
• Safety hazards, and whether the client has been told
• Areas needing extra attention on patrol tonight

5. People and contacts

• Who is on site: building manager, maintenance, cleaners, contractors
• VIPs or special visitors expected
• Emergency contacts for this shift, verified as current

That last line matters more than it looks. Contact lists rot quietly, and 3am is a bad time to find out. Keep the shift's version aligned with the escalation matrix rather than a printout from last spring.

Equipment transfer

Both officers verify jointly. Not "the outgoing officer says it's fine."

Item	What gets verified
Radio	Powers on, test transmission answered, correct channel
Keys	Count matches the key log, every one accounted for
Access cards	Tested at one real access point
Flashlight	Lights, and has enough battery for the shift
Vehicle	Fuel level, mileage, walk-around damage check
Body camera	Battery level and available storage
First aid kit	Sealed or stocked to the list
Report forms	Enough on hand for a full shift

Keys are the item that generates real losses, and the count is only meaningful if it is against a maintained register. A key control policy is what makes that line enforceable. Vehicle condition at handoff is the same story for a patrol fleet: damage found at 6am belongs to whoever last signed for the car.

Log review and documentation

The incoming officer reads, not skims:

• Today's daily activity log entries
• Pass-down notes from previous shifts
• Incident reports from the past 24 to 48 hours
• Special instructions and current bulletins

This step is only fast if the log is written to a standard. A DAR with a fixed format turns a ten-minute read into a two-minute one.

Both officers then sign the handoff log, recording:

• Time of handoff
• Confirmation the briefing was completed
• Equipment inventory verified
• Any exception or discrepancy, described rather than initialed away

Shift handoff log template

What if relief does not show up?

1. Notify the supervisor or dispatch at the scheduled shift time. Not twenty minutes later, hoping.
2. Remain on post until relieved by a supervisor or a replacement.
3. Document the no-show in the activity log with the time you reported it.
4. Continue normal duties. The post does not go quiet because the shift ran long.

A supervisor answering that call at 6am with no plan is the symptom. If it happens more than occasionally, the problem is upstream in coverage, and reducing callouts is the actual fix.

Emergency handoffs

Injury, family emergency, anything that means an officer leaves now:

• Contact the supervisor first, before anything else
• Give the replacement an abbreviated verbal briefing covering active situations only
• Point them at the written log and the post orders for everything else
• Complete the written documentation as soon as circumstances allow

This is the case that proves whether your logs are any good. If a stranger can pick up the post from the written record alone, they are. If they cannot, the emergency handoff is where you find out. Test it deliberately during a post inspection rather than during an actual emergency.