/ Articles

A guard's report is often the only record of what happened on a post. When it is vague, the client, the next shift and anyone reviewing the incident later have nothing solid to work from.
This guide is for supervisors and security operations managers who own security guard report writing across their sites. It covers what state rules ask for, what a usable report contains, two example reports, and a training approach that keeps the habits in place between reviews.
Table of Contents
Report writing shows up in state guard training rules, but each state words it differently. Two examples:
In California, a newly licensed or employed guard must complete two of the mandatory courses within 30 days, and the remaining two within the first six months. Both clocks run from the day the guard registration card is issued or the day the guard begins employment.
California also requires eight hours of annual continuing education, including at least two hours reviewing appropriate use of force, and the employer may provide it. In that section, the page adds one line that speaks directly to supervisors: "Employer-provided training should be supported by evaluation of the licensed guards' skills." A completed course hour is the floor. Whether a guard can write a clear report on a real shift is something regular review shows.
Other states set their own curricula, so check your state licensing board's current rule. Your post orders and client contracts usually add the rest: which forms to use, when a report is due and who receives it.
The checklist below is our own working summary for supervisors, not a regulator's list. A report passes when a reader who was not there can tell exactly what happened.
Two report types cover most of a guard's writing. A daily activity report (often called a DAR) logs the whole shift: patrols, visitors, conditions and hand-offs. An incident report covers one event in full detail and stands on its own.
The sample below is an illustrative example written for this article. The site, times and events are invented, and no real person or incident is described.
Daily activity report (example). Distribution warehouse, day shift, 0600 to 1400.
| Time | Entry |
|---|---|
| 0600 | On duty. Received radio and key sets 1 to 4 from night officer. Pass-down log notes the dock door 6 sensor is faulty. |
| 0630 | Exterior patrol complete. All perimeter gates locked. Light out on north lot pole 3; logged for facilities. |
| 0815 | HVAC contractor arrived. ID matched approved visitor list. Visitor badge V-12 issued. |
| 1045 | HVAC contractor departed. Badge V-12 returned. |
| 1205 | Interior patrol. Dock door 6 found partly open. Secured. Supervisor notified by radio at 1210. Incident report filed. |
| 1400 | Off duty. Pass-down to relief: dock door 6 incident, pole 3 light. Radio and keys handed over. |
Every entry has a time, a place and an outcome. The 1205 entry points to a separate incident report, because a DAR line is too short to carry an event in full.
This sample is also illustrative, written by us, with no real names, site or event. It shows the same dock door finding written two ways.
Weak version: "Dock door was open again. Someone probably left it up. Fixed it."
Usable version (example): "At 1205, during an interior patrol, I found dock door 6 raised about two feet. I checked the dock area and saw no one. At 1208 I lowered and locked the door. At 1210 I notified the shift supervisor by radio. The pass-down log at 0600 listed the door 6 sensor as faulty. I did not review camera footage."
The table compares common habits in weak reports with what to write instead.
| Weak habit | Write instead |
|---|---|
| "Again", "as usual" | The specific facts of this event only |
| "Someone probably left it" | What was observed; say what is not known |
| "Fixed it" | The exact action taken and the time |
| No notification noted | Who was told, how, and when |
| No reference to earlier entries | The related log entry or pass-down note |
Notice what the usable version leaves out: no guess about who opened the door, and no claim that the guard checked footage. A later reader can trust every line because nothing in it goes beyond what the guard did and saw.
Report writing is a skill guards build through practice and feedback. The approach below is our own suggestion for a supervisor, built around the reports guards already write.
Give every post the same template for each report type and a short written standard (the checklist above works). Tie it to the post orders so guards know which events require an incident report and when it is due.
Pick a set number of recent reports per guard each week and mark them against the checklist. In our reading, this fits the spirit of California's line about evaluating guards' skills, although that line sits in the rules for employer-provided annual training.
Take a weak report, remove anything that identifies people, and rewrite it with the guard. Show the before and after side by side, as in the example above.
Note which checklist item each weak report missed: times, locations, notifications, quotes or guesses. A pattern across a shift or site tells you what to reteach. A training needs assessment uses the same logic at the organization level.
If a site keeps missing notification times, cover notification times. Guards on public-facing posts may also need related skills such as de-escalation training.
Weekly review catches errors after they happen. The rules behind a good report (what to include, which events need a report, when it is due) also need to stay ready on the shift when the incident happens.
That is where Blank Slate fits. Blank Slate is a cognitive-readiness platform built on AI-optimized spaced retrieval. Spaced retrieval combines spaced repetition (reviewing material at intervals) with retrieval practice (answering from memory instead of rereading).
It works on top of the training content you already have, such as your report standard and post orders. Guards answer short questions in brief sessions (about 60 seconds), 3-4 times a week, adding up to a few minutes a week. The platform's True Knowledge Level™ shows what a person or team knows now.
It has been tested with security guards. In a year-long case study of 70 data-center security guards presented at MODSIM World 2025, guards who started below the team median went from about 56% to over 90% accuracy (Smith, MODSIM World 2025). They closed the gap with the high performers after about 180 days, using three sessions a week, six questions each.
The firm also reported a 40% reduction in operational incidents in the year after deployment. That figure is company-reported, and the paper notes the specific data were confidential (MODSIM World 2025).
Blank Slate does not replace the state-required training hours, your report reviews or on-the-job practice. It reinforces and measures what guards retain between them. It also coexists with your LMS: the LMS records what guards completed, and Blank Slate shows what they still know (see the difference). See how this works across a guard force on the private security page.
To find where your team's gaps are today, request a Knowledge Gap Audit: a free, short assessment taken in the browser that returns a one-page readiness snapshot.
It should state who was involved, what happened in order, exact times and locations, the actions taken and who was notified. Direct quotes go in quotation marks. Guesses and opinions stay out, and anything the guard does not know is stated as unknown.
A daily activity report logs the whole shift: patrols, visitors, conditions and hand-offs, one timed line each. An incident report covers one event in full detail and stands on its own. A DAR entry usually points to the incident report.
It depends on the state, so check your own licensing board. California lists report writing under its 4-hour Observation & Documentation course. It is one of four mandatory courses: two are due within 30 days and the other two within six months of card issue or hire. Virginia lists documentation in its 18-hour unarmed officer course.
No rule cited here sets a review frequency, so it is a supervisor's decision. A fixed weekly sample per guard, marked against one checklist, shows patterns early. Increase reviews for new guards or sites where the same items keep getting missed.
A clear report depends on the guard remembering the standard on the shift it matters. A Knowledge Gap Audit is free: a short assessment in the browser that returns a one-page readiness snapshot of what the team knows today, where gaps may exist and where to focus first.