Ask most property managers what their security guard did last Tuesday night and you'll get one of two answers. "I assume they did their rounds." Or a single line in a logbook: "0200 — all secure."
Neither one tells you anything. And when an incident happens — a break-in, a slip-and-fall in the parking garage, a tenant complaint, an insurance claim — that gap becomes your problem, not the guard company's.
A good shift report is the difference between security you assume and security you can prove. Here's what a real one should contain, what a weak one looks like, and the questions to ask your current vendor.
Watch: What did your security guard do last night?
Why the report matters more than the guard
You're not on site at 2 a.m. Neither is your property manager, your insurer, or your attorney. The shift report is the only record of what your security program actually did while nobody was watching. It's what you'll hand to:
- Your insurance carrier after a claim, to show the property was patrolled and the hazard was documented.
- Your attorney if a negligent-security claim is filed, since the question in those cases is usually what you knew and what you did about it.
- Your tenants or board when they ask whether the security spend is worth it.
- Police when they need a timeline.
If the report is thin, every one of those conversations starts from a weak position.
The seven things every shift report should include
1. Verified arrival and departure
Not a handwritten time. A timestamp captured on site, ideally with GPS or a site check-in, so there's no question the post was actually staffed for the full shift. Late arrivals and early departures are the most common hidden failure in guard contracts, and you'll never see them on paper unless the system records them.
2. Patrol rounds with times and locations
Every round should show where the officer went and when: perimeter, parking structure, loading dock, stairwells, roof access, whatever your post orders call for. Checkpoint scans or geotagged entries are better than a narrative written at the end of the shift from memory.
3. Door and access checks
Which doors were checked, which were found unsecured, and what the officer did about it. "Found east stairwell door propped open at 0140, secured, photographed" is useful. "Building secure" is not.
4. Observations, even when nothing happened
Lights out in the north lot. A vehicle parked in the same spot three nights running. A broken gate arm. A homeless encampment forming behind the dumpsters. These aren't incidents yet, but they're the early warnings that let you fix a problem before it becomes a claim. A good officer notices; a good report captures it.
5. Incidents, written so a stranger could follow them
When something does happen, the incident section should answer who, what, where, when, and what was done, in plain language, with times. Include whether police or medical were called, any report numbers, names of anyone involved or witnessing, and who on your side was notified. Write it as if it will be read in a deposition, because someday one might be.
6. Photos
A photo of the open door, the damaged fence, the spill in the lobby, or the vehicle in the fire lane is worth more than a paragraph. Photos should be timestamped and attached to the entry they support, not dumped in a folder.
7. Handoff notes
What does the next shift need to know? An expected delivery, a tenant working late, a door that won't latch. Handoff notes are what make coverage continuous instead of a series of disconnected eight-hour blocks.
What a weak report looks like
You've probably seen some version of this:
0000 – Rounds, all secure
0200 – Rounds, all secure
0400 – Rounds, all secure
0600 – Off post
Every line could have been written in five minutes at the end of the shift, or by someone who never left the car. There's no location detail, no observations, no photos, and nothing that would help you if something went wrong at 0315.
Who should see the report, and when
A report that sits in the guard company's system is only half useful. You should be able to read it the next morning, without asking. At STRAPT, every officer clocks in on site and files through a live reporting platform, so clients see patrols, checks, observations, and incidents as they're logged. Serious incidents trigger a call to the client contact in real time, not in a weekly summary.
If your current vendor sends reports weekly, monthly, or "on request," ask why. The technology to do it daily has been standard for years.
Five questions to ask your current security vendor
- How do you verify my guard actually arrived and stayed for the full shift? Look for GPS or site-based check-in, not a sign-in sheet.
- Can I see last Tuesday's report right now? If it takes a day to produce, the reporting isn't really for you.
- Do your officers take timestamped photos? If not, incident documentation will rely on memory.
- Who calls me when something happens overnight, and how fast? You want a name and a timeframe, not "dispatch will reach out."
- Who reviews the reports before I see them? A supervisor who reads reports catches lazy entries and spots patterns across shifts.
The bottom line
Guard hours are easy to buy. Accountability is harder. The shift report is where you find out which one you're actually paying for. If you can't open last night's report and know exactly what happened on your property, the problem isn't your property. It's your reporting.
We'll walk your site for free and show you a sample STRAPT shift report alongside our assessment. If your current vendor's reports look like the weak example above, you'll see the difference immediately. Request a free site assessment →