Security Guard Incident Reports: What to Include.

What Is a Security Guard Incident Report?.

A security guard incident report is a written account of a specific unusual occurrence during an assignment. That could be an unsecured door, a suspicious vehicle, an after-hours visitor, a property hazard, a disturbance, damage, an alarm response, or another event that deserves a detailed record. It is not a substitute for calling emergency services, following the property’s emergency plan, or escalating an issue to the right person. It records the security professional’s role and the facts available at the time.

Good reporting is especially valuable because the people reading it are often not present when the event occurs. A manager may need to make a decision the next morning. A client contact may need to know whether a concern was addressed. A supervisor may need to brief an incoming officer. The report should give each person the same reliable starting point without exaggeration or guesswork.

Incident Reports and Daily Activity Reports Serve Different Jobs.

Routine shift work is usually captured in a daily activity report or site log. That record may note patrol times, visitor checks, deliveries, access activity, regular equipment checks, and other expected work. It creates a picture of how the shift unfolded, even when nothing unusual occurs.

An incident report goes deeper on one event. It should identify the specific time, location, observations, response, notifications, and follow-up tied to that occurrence. A property may need both records. For example, a daily activity report might show that an officer completed a scheduled exterior round at 10:00 p.m. An incident report would explain that at 10:07 p.m. the officer found an exterior gate unsecured, checked the immediate area from a safe position, notified the approved contact, and documented the condition for follow-up.

Keeping those purposes distinct makes records easier to use. The daily log shows the rhythm of coverage. The incident report helps the client focus on an exception that requires attention. Clear post orders should tell officers which conditions need immediate escalation, routine documentation, or both.

Start With the Essential Facts.

A strong report starts with the details that let a reader place the event. Record the date, the time the issue was first observed or reported, the precise location, and the report writer’s role. If an event happened over a period of time, note the sequence of meaningful times instead of using one broad estimate. If a time comes from a caller, camera, access record, or another person, say so rather than presenting it as a direct observation.

Describe the location precisely enough for a manager to find it. “North parking area near the loading entrance” is more useful than “outside.” If people or vehicles are involved, record the information that is relevant and authorized for the site: names when known, neutral physical descriptions where needed, vehicle make or color, license information only when it was properly observed, and the role each person had in the event. Do not fill gaps with assumptions.

That discipline matters when coverage changes shifts. A report that says “a suspicious person was seen” leaves too much to interpret. A factual description of where the person was observed, what the officer saw, what happened after contact or notification, and what the officer did next gives the client a usable record without reaching a conclusion the officer cannot support.

Write the Narrative in Order.

The main narrative should follow the event from beginning to end. Start with how the officer became aware of the condition. Then state what the officer directly observed, the safety-conscious action taken, any notifications, and the immediate outcome. Short, chronological paragraphs are easier to review than a single dense block or a list of conclusions.

Use plain language. “At approximately 9:18 p.m., I observed the west service door open approximately six inches” is clearer than “the door was suspiciously unsecured.” The first statement tells the reader what was seen. It does not speculate about why the door was open or who was responsible. If the officer received information from a witness, distinguish that statement from the officer’s own observation, such as “The tenant stated that…”

Exact quotes can be helpful when the wording matters, but they should be limited to what is relevant. The same goes for photographs, camera references, alarm records, or other attachments. Note what material exists and follow the property’s approved procedure for handling it. An incident report is not the place to include sensitive site details, unnecessary personal information, or information beyond the officer’s authority to share.

Document the Response, Not Just the Problem.

Clients need to know what happened, but they also need to know how the assignment responded. Record the actions taken in the order they happened: maintaining a safe position, securing an area when authorized, contacting an approved site representative, calling emergency services when necessary, directing people away from a hazard, observing from a safe distance, or preserving the scene for the appropriate responders.

State who was notified and when. A report that ends at the initial observation can leave a property manager wondering whether anyone acted on a concern. A concise note that identifies the notification, time, and response gives the reader a clear handoff. If no contact was reached, document the attempted notification according to the site’s procedure instead of implying that follow-up occurred.

Security professionals should work within the assignment, training, and property procedures. Florida clients evaluating officer credentials can review the state’s Class D security officer requirements. Credentials and good reporting support a professional assignment, but neither replaces emergency services or the property’s own response plan when a situation calls for them.

Separate Facts, Statements, and Follow-Up.

Three parts of an incident record often get blurred together: what the officer observed, what another person reported, and what the client or manager needs to do next. Keeping them separate makes the report more trustworthy. An officer can write that a camera reference was provided, a witness gave an account, or a manager was notified without presenting that information as independently verified fact.

The follow-up section should be practical, not dramatic. It might note that a maintenance issue was referred to the correct contact, that a supervisor needs to review footage, that the property requested a recheck, or that the site should update a temporary access procedure. Avoid assigning blame or recommending action outside the officer’s role. The point is to make sure the right person sees the information and knows what remains open.

This is also why reports should be completed promptly under the provider’s procedures, while observations are fresh. If something needs to be clarified later, the proper approach is to add a dated supplemental record rather than quietly changing the original account. That protects the integrity of the record and helps the client understand the timeline.

Common Reporting Mistakes to Avoid.

The most damaging reporting mistakes are usually simple. Vague wording, missing times, a broad location, and unexplained gaps in the timeline make it hard for a manager to understand what occurred. So does language that sounds like a conclusion rather than an observation. Words such as “aggressive,” “suspicious,” or “obviously” can be misleading unless the report first describes the conduct that led the officer to use that description.

Another common problem is treating the report as a substitute for the immediate response. Documentation matters, but it comes after the officer follows the assignment’s safety and notification procedures. A report should never delay a call for emergency help, a required escalation, or the safe handling of a scene. Once the immediate situation is addressed, the record should make that sequence clear.

Finally, reports work best when they are specific without becoming a dump of irrelevant detail. Include information that helps a reader understand the incident, the response, and the next step. Leave out private information, access details, personal opinions, and unverified claims that do not belong in the operational record. That balance keeps the document useful to the client and respectful of the people involved.

What Property Managers Should Expect From Reporting.

Property managers do not need a pile of paperwork. They need reporting that is consistent, relevant, and aligned with the assignment. Before coverage begins, agree on who receives routine reports, what situations require immediate notification, what information should remain confidential, and which site contacts can approve an exception. Those expectations prevent the reporting process from becoming either vague or unnecessarily burdensome.

Look for reports that make the work visible without turning normal operations into noise. A useful record helps management notice patterns: repeated unsecured doors, persistent parking issues, recurring after-hours access requests, lighting concerns, or times when a visible presence is most valuable. It can inform a conversation about whether the property needs a dedicated officer, clearer procedures, or mobile patrol coverage that checks several locations at planned intervals.

The report should also reflect the experience visitors and staff receive. A professional security presence can be observant and thorough without being disruptive. That balance begins with the assignment itself, which is why a practical security guard hiring process should include reporting expectations alongside hours, access rules, and the type of coverage needed.

How Boskeeta Helps.

Boskeeta Security & Protection shapes coverage around the setting, daily activity, access expectations, and the client’s communication needs. That includes understanding which observations matter to the property, who should receive an update, and how the officer’s documentation supports a professional handoff. The goal is a clear, respectful record that helps the client make a timely decision, not generic paperwork for its own sake, while preserving the privacy and dignity of everyone involved.

Whether the assignment calls for a dedicated post, property-focused security, or mobile patrols, the conversation starts with the conditions on site and the outcome the client needs. Start with a security consultation or contact Boskeeta to discuss coverage that fits your property.