6.1 Radio Procedures & Report Writing

Introduction to Professional Radio Communications

Effective communication is the cornerstone of a security professional's daily duties, playing an integral role in everything from routine patrols to major emergency responses. In the District of Columbia, where security personnel often operate in complex environments with overlapping jurisdictions, maintaining clear, concise, and professional radio communication is not merely a recommendation—it is a critical requirement. A security guard's two-way radio is their lifeline, connecting them to their dispatch, supervisors, and fellow officers. Consequently, understanding the principles of professional radio etiquette is essential.

The first rule of radio use is simple but frequently overlooked: listen before transmitting. By taking a moment to listen, an officer ensures they are not stepping on another transmission or interrupting an ongoing emergency communication. When the channel is clear, the officer should press the Push-to-Talk (PTT) button, pause for one second to prevent the first part of their message from being cut off (a phenomenon known as "clipping"), and then speak in a clear, calm, and measured voice. Transmissions should be kept as brief as possible, ideally under ten seconds, conveying only the most essential information. If a transmission requires more time, the officer should break it up into segments, pausing to allow dispatch to acknowledge or other officers to break in if there is an emergency.

Clear-Text Protocols Versus 10-Codes

Historically, law enforcement and private security agencies relied heavily on "10-codes" (such as 10-4 for "acknowledged," 10-20 for "location," or 10-33 for "emergency") to abbreviate communications. While some agencies still utilize these codes internally, the modern standard—heavily endorsed by the Department of Homeland Security and the Federal Emergency Management Agency (FEMA) through the National Incident Management System (NIMS)—is the absolute use of "plain language" or "clear-text."

Plain language ensures that communication is immediately understood by all personnel, regardless of their specific agency, training background, or primary duties. In a multi-agency response, which is incredibly common in DC due to the presence of local police, federal agencies, and private security forces, a specific 10-code might mean "routine traffic stop" to one agency and "officer down" to another, leading to disastrous confusion. Therefore, security professionals must prioritize clear-text protocols.

Instead of saying, "Dispatch, I am 10-97 at the 10-20," an officer should say, "Dispatch, I have arrived at the main lobby." Instead of "I have a 10-15," they should say, "I have a subject in custody." This straightforward approach eliminates ambiguity, speeds up comprehension, and significantly reduces the likelihood of critical errors during stressful, fast-moving situations.

The Phonetic Alphabet

When transmitting specific details over a radio, such as names, license plate numbers, or specific locations, environmental noise, radio static, or poor reception can easily obscure individual letters. To counter this, security professionals must be entirely fluent in the International Radiotelephony Spelling Alphabet, commonly known as the NATO phonetic alphabet. This system assigns a specific, distinct, and easily recognizable word to each letter of the alphabet, minimizing the risk of misinterpretation over the airwaves.

For example, if a guard needs to relay a suspicious vehicle's license plate "BGT-412," they would transmit, "Bravo - Golf - Tango - Four - One - Two." Memorizing this alphabet is a foundational skill that ensures complete accuracy when relaying vital information to dispatch or responding police units.

Fundamentals of Report Writing: The Six Ws

While radio communication handles the immediate transfer of operational information, report writing serves as the formal, permanent, and legal record of an incident. Security professionals write various types of reports daily, most notably Daily Activity Reports (DARs) and Incident Reports. An Incident Report is generated whenever a notable event occurs, such as a security breach, property damage, injury, medical emergency, physical altercation, or any interaction requiring police or emergency medical services presence. The primary objective of an incident report is to provide a comprehensive, objective, and chronological account of what transpired.

To achieve this standard, every incident report must definitively answer the fundamental "Six Ws" (and one H):

• Who: Identify all parties involved in the incident. This includes the reporting officer, other security personnel, victims, suspects, witnesses, and responding police or medical personnel. Include their full names, contact information, physical descriptions, employee ID numbers (if applicable), and their specific role in the incident.
• What: Detail exactly what occurred. What was the nature of the incident? What specific actions were taken by the suspects, victims, and the security officer? What property was damaged or stolen?
• When: Provide precise dates and times. A timeline is crucial. Document when the incident began, when the officer arrived on the scene, when authorities were notified, when they arrived, and when the incident was finally resolved.
• Where: Specify the exact location of the incident. In a large facility, writing "the parking garage" is entirely insufficient; "Level 2 of the North Parking Garage, Space 4B, near the east stairwell" is the required level of detail.
• Why: If known, state the apparent motive or cause of the incident. However, officers must be extremely careful to stick strictly to facts and direct statements made by the individuals involved, rather than guessing or assuming the psychological motivations of a suspect.
• How: Describe the sequence of events and methods used. How did the suspect gain unauthorized entry? How was the situation brought under control? How did the officer respond to the threat?

Objectivity and Professionalism in Reports

One of the most critical, yet frequently mishandled, aspects of report writing is maintaining strict objectivity. A security guard's report must completely separate factual observation from personal opinion. Subjective descriptors, assumptions, and emotional language have absolutely no place in a professional document that may be heavily scrutinized in a court of law, during a civil lawsuit, or by a client's legal team.

Consider the difference between subjective and objective reporting. A poorly written, subjective report might state: "The suspect was acting crazy and aggressive, and he was clearly very drunk. He wanted to fight me."

An excellent, objective report would instead state: "The subject was yelling profanities loudly, pacing rapidly in circles, and repeatedly clenching and unclenching his fists. I observed a strong odor of alcohol on his breath, his eyes were bloodshot, and he slurred his words when speaking. He stated to me, 'I am going to hit you.'"

The latter provides undeniable, observable facts rather than a subjective interpretation. It allows the reader (such as a judge or jury) to draw their own conclusions based on the documented evidence.

Similarly, officers must avoid using complex, overly formal language or outdated "police jargon" in a misguided attempt to sound more authoritative. The goal is clarity, not complexity. Sentences should be concise, active, and straightforward. For example, instead of writing, "The perpetrator was observed by the undersigned officer rapidly egressing the premises via the northern portal," an officer should simply write, "I saw the suspect run out the north door."

After drafting a report, the final and indispensable step is proofreading. A report riddled with spelling errors, poor grammar, incomplete sentences, or timeline inconsistencies severely undermines the officer's credibility and the document's legal validity. Officers must meticulously re-read their reports to ensure they are logically structured, chronologically accurate, and free of any grammatical mistakes before officially submitting them to their supervisor or the client.