6.2 Incident Notes and Observation Capture

Notes Before Narrative

A report is only as accurate as the facts it uses. On the exam, the notes are supplied in the prompt. On the job, they come from direct observation, radio traffic, housing logs, camera review, witness statements, or supervisor direction. The skill is to preserve exactly what each source supports, and no more.

Start by separating direct observation from secondhand information. If you saw Lewis strike the window, the report can say "I observed Lewis strike the window." If Officer Grant told you, the report must say "Officer Grant reported that Lewis struck the window." This distinction tells the reader how the fact is known, which is exactly what investigators and courts need.

Mark Source and Certainty

Do not try to draft the final report while still decoding the notes. First tag every fact: was it observed, reported, found, counted, or reviewed? Then decide which facts are relevant. A note that someone wore blue shoes matters if the prompt asks for identification, but not if the issue is a count refusal and the person is already identified.

Observation capture must avoid vague category words. Instead of "disturbance," write what made it one: "three people shouted near the dayroom door after the recall announcement." Instead of "contraband," describe the item the prompt gives: a sharpened plastic strip, a taped packet, or a phone charger. Specificity is what separates a usable note from a label.

Timing and the Note-to-Report Method

Timing matters because memory drifts. Agency policy controls when notes are written, where they are stored, and whether they attach to the report. For exam purposes, the safe answer is always to document promptly, accurately, and per instructions rather than reconstruct from memory after unrelated events. Use a clean method:

• List all times first.
• Link each person to a role or location.
• Mark whether each fact was observed, reported, found, or reviewed.
• Remove duplicate facts unless they clarify sequence.
• Keep uncertain facts uncertain instead of forcing certainty.
• Flag opinion words for replacement with observable behavior.

A common trap treats every note as equally important. Reports are not storage bins for every detail; they are organized records of relevant facts. If a prompt includes a rumor, a staff joke, or an unsupported opinion, it is frequently planted to test whether you leave it out. Strong notes are modest. They do not solve every question. They preserve enough reliable, sourced information that the final report can be written in chronological, objective, and useful form, and that is exactly what report-writing items reward.

Relevant vs. Irrelevant Detail

Deciding what to include is itself a tested skill. A detail is relevant when it helps answer one of the report's core questions: who, what, when, where, how known, what staff did, and what resulted. A detail is irrelevant when it does none of those, even if it is true. The exam often plants a true-but-useless fact to see whether you will let it clutter the report.

When you are unsure, ask whether a supervisor reconstructing the event would need the detail. If yes, keep it. If the report reads the same without it, cut it. This discipline keeps the narrative tight and is the habit the entrance exam is built to reward.

Why Note Discipline Matters on the Job

In a real facility, the notes you take at 1412 may be read in a disciplinary hearing, a grievance, a use-of-force review, or a lawsuit years later, long after you have forgotten the shift. Memory fades and blends events, so the contemporaneous note, written promptly and accurately, often becomes the most reliable record. Officers who learn to capture observable, sourced facts during training carry that habit into a career where it protects them, their agency, and the people in custody. The entrance exam is an early checkpoint for that same skill, which is why agencies score it before they ever put a recruit on a unit.