A report written at 3:15 a.m. after a disorderly patron, a vehicle break-in, or a medical response may be reviewed weeks later by a property manager, investigator, attorney, insurer, or licensing authority. Security incident report writing is therefore not routine paperwork. It is a professional record of what you observed, what you did, who you notified, and why your actions were reasonable under the circumstances.

For security officers in Virginia, Washington, DC, and Maryland, a clear report protects more than a client account. It protects your credibility, supports your employer’s response, and demonstrates the judgment expected of a trained professional. The objective is not to write the longest report. The objective is to create an accurate, complete, readable record that can stand on its own.

Start With Facts, Not Conclusions

An incident report should allow a person who was not present to understand the event from beginning to end. Begin with the basic facts: the date, time, exact location, assignment or post, people involved, and the nature of the call or observation.

Write what you personally saw, heard, smelled, or did. If another person gave you information, identify that person and make clear that it was a statement, not your independent observation. For example, write, “Ms. Carter stated that she saw a male remove a package from the lobby,” rather than, “The male stole a package.” The first sentence accurately identifies the source. The second reaches a conclusion that may not yet be established.

This distinction matters. Security officers may detain, observe, preserve a scene, request law-enforcement response, and protect people and property within the limits of their assignment and applicable law. They should not use report language to make unsupported legal findings. Terms such as “suspect,” “victim,” “assault,” or “theft” may be appropriate when used according to agency policy or when reporting what law enforcement advised, but facts should always carry the report.

Avoid opinions, labels, and emotional language. “The subject was acting crazy” is vague and unprofessional. “The subject paced near the entrance, shouted repeatedly, clenched both fists, and ignored three verbal requests to step back from the door” gives the reader useful, observable information.

Build the Report in Chronological Order

Most strong reports follow the event as it happened. That order helps prevent missing details and makes the report easier for supervisors and clients to review. Start with how you became aware of the incident. State your location and assignment, then describe your initial observation or the information received.

Next, document the actions you took. Include verbal commands, notifications to dispatch or a supervisor, requests for emergency services, scene-control measures, welfare checks, access-control actions, and any assistance provided. If force, restraints, defensive equipment, or a weapon was involved, follow your employer’s reporting policy exactly and complete all required supplemental documentation.

Then record the outcome. Did the individual leave the property? Was law enforcement called? Was EMS requested? Were witnesses identified? Was a damaged door secured? Did management assume responsibility for the scene? Finish with the notifications made, the report number if one was provided, and your final status.

Precise times are valuable when available. Use a radio log, access-control record, dispatch entry, body-worn camera system, or other authorized record to confirm the timeline. Do not guess. If you do not know the precise time, use a reasonable approximation and say so when your policy permits, such as “at approximately 2215 hours.”

Use Professional Language in Security Incident Report Writing

Security incident report writing should be clear enough for a client to understand and formal enough for official review. Short sentences are often better than complicated ones. Use complete names when known, correct titles when relevant, and specific locations such as “north parking deck, level two, near stairwell B” instead of “parking lot.”

Descriptions should be objective and detailed without becoming speculative. When documenting a person, include identifiable characteristics that were actually observed: approximate age, height, build, clothing, hair, tattoos, direction of travel, and distinguishing behavior. Do not include protected characteristics unless they are necessary to identification or the incident and are reported professionally.

Quotes can be important, especially when a person makes a threat, refuses a command, claims ownership, admits conduct, or provides a complaint. Use quotation marks for words you recall accurately. If you cannot recall the exact statement, do not present it as a direct quote. Write that the person “stated words to the effect of” and record the substance of the statement.

Grammar and spelling matter because they affect confidence in the report. A minor error will not erase a truthful observation, but repeated errors, unclear pronouns, and unfinished sentences can make an officer appear careless. Before submission, read the report once as if you were the supervisor receiving it with no prior knowledge of the event.

Document Actions and Authority Carefully

A report must explain not only what occurred but also what the security officer did in response. This is particularly important after a detention, ejection, use of restraints, physical intervention, defensive-equipment display or deployment, firearm-related event, injury, or police contact.

State the facts that led to your decision. If you directed a person to leave, document the behavior, the instruction given, whether the person acknowledged it, and the response. If you contacted police, state the reason for the request and the agency or officer information received, if available. If a person was detained, document the conduct observed, the location, the time, the safety measures used, and when law enforcement or a supervisor arrived.

Do not try to justify an action with broad statements such as “for officer safety” without explaining the specific concern. A better report identifies the behavior: “Due to the subject repeatedly reaching toward the waistband area after being instructed to keep both hands visible, I maintained distance and requested an additional officer.” Specific facts allow reviewers to assess whether the response was appropriate.

Your authority, required reports, and notification procedures can vary by assignment, employer policy, contract, credential, and jurisdiction. A shopping center post, hospital assignment, residential community, executive-protection detail, and special-police position do not operate under identical rules. Know the written post orders before an incident occurs, and use the report forms required by your agency.

Preserve Evidence and Record the Chain of Events

When an incident involves possible criminal conduct, injury, property damage, or a serious policy violation, the report should identify evidence and its disposition. This may include photographs, video cameras, access-control logs, damaged property, recovered items, witness contact information, or written statements.

Document what you preserved, where it was located, who received it, and when the transfer occurred. If you did not collect an item because law enforcement took control of the scene, say so. If video was available, identify the camera number or coverage area and notify the person responsible for retention under site policy. Do not state that footage “proves” an event unless you personally reviewed it and can accurately describe what it showed.

Keep personal assumptions out of the evidence section. A broken window is an observation. The cause of the broken window may be unknown until law enforcement, management, or an investigator completes a review.

Review Before You Submit

A disciplined final review catches the errors that create the most problems later. Confirm that names, dates, times, locations, directions of travel, and notification details are consistent throughout the report. Make sure every person mentioned is identified clearly enough that the reader knows who did what.

Check that the narrative answers the practical questions: What happened? When and where did it happen? Who was involved? What did you observe? What actions did you take? Who was notified? What was the result? If the report cannot answer one of these questions, it may need more work.

Never alter facts to make an incident appear more serious, less serious, or more favorable to a particular person. If you discover a mistake after submission, use the correction or supplemental-report procedure established by your employer. Do not erase, backdate, or silently rewrite an official record.

A Report Is Part of Your Professional Reputation

Clients and supervisors may never see every patrol completed correctly or every potential issue prevented through alert observation. They will see the report when something goes wrong. That document shows whether the officer remained observant, followed procedure, communicated clearly, and understood the limits of the role.

Treat each report as part of your professional record. Reality-based security training prepares officers to make decisions under pressure; disciplined documentation makes those decisions understandable after the pressure has passed.