Writing Court-Ready
Police Reports
A practical reference guide for Canadian police officers and agencies. Covers everything a charge file needs to withstand Crown scrutiny, Charter challenges, and defence cross-examination — from the first sentence to the last exhibit entry.
The Gold Standard Checklist
A court-resistant report checks ten boxes, every time. Missing any one of these creates a gap that defence counsel will exploit. Use this as your pre-submission mental checklist before every charge file leaves your hands.
📍 Occurrence Metadata
- File number, occurrence ID, CAD reference
- Precise date, start and end times
- Exact location with civic address or GPS
- All involved members identified by name/badge
- Cross-references to video, photos, RMS entries
⏱️ Chronological Narrative
- Step-by-step sequence with timestamps throughout
- Clear transitions (arrival → observation → interaction → decision)
- No time gaps without explanation
- Notes contemporaneous or explained if written later
- Internal consistency — no contradictory times
👁️ Objective Observations
- Sensory facts only — what you saw, heard, smelled
- Observations kept separate from conclusions
- Measurements where possible (distance, lighting, weather)
- Demeanour described in behavioural terms
- No opinion dressed as fact
⚖️ Before–Grounds–After
- Pre-ground observations documented separately
- Grounds explicitly stated and connected to facts
- Each action (detain/arrest/search) tied to its authority
- No hindsight reasoning used to justify earlier actions
- Proportionality articulated for each escalation
💬 Statements & Rights
- Verbatim quotes for admissions, threats, consent, refusal
- Charter caution delivered and response documented
- Right to counsel timing recorded
- Spontaneous vs questioned statements distinguished
- Recording reference noted if applicable
🔗 Evidence Linkage
- Each piece of evidence connected to a specific element or ground
- "Connect the dots" — don't just list exhibits, explain them
- Physical and digital evidence both addressed
- Video/photo references include timestamp and storage location
- Lab submissions referenced with submission date
📦 Exhibits & Continuity
- Where found, by whom, exact condition at seizure
- Packaging method, seal numbers, exhibit tag
- All transfers documented with date, time, person
- Storage location confirmed
- Digital: hash values, download method, device continuity
✏️ Integrity Controls
- Corrections made with single line-through, initials, date
- Late entries identified and explained
- Handwritten notes linked to RMS entry
- No unexplained white-outs or alterations
- Legible and complete throughout
👥 People & Identification
- Full legal name, DOB, address for all parties
- Physical descriptions contemporaneous and specific
- Role of each person clearly defined
- Relationship mapping documented
- Witness separation steps noted
📁 Disclosure Readiness
- Every referenced attachment actually exists and is locatable
- Photo/video URLs or exhibit numbers included
- Warrants, ITO references included where applicable
- Canvass logs, statement copies noted
- Crown can reconstruct the file from the report alone
Before – Grounds – After
This is the single most important structural concept in report writing — and the most common place reports fail. Courts test whether your suspicion existed at the time, based on what you observed before acting. Using later-learned information to justify earlier actions is what defence calls "hindsight grounds" — and courts agree with them.
Pure Observation
Document everything you observed before forming any suspicion. Objective facts only. No conclusions. No legal labels.
- What you saw, heard, smelled
- Environmental context (lighting, weather, location type)
- Behaviour in factual, descriptive terms
- Information received (dispatch, witness, database)
"At 23:15 I observed a male pacing behind a closed business. He repeatedly looked over his shoulder and attempted the door handles of three parked vehicles."
✗ Common Failure
- Starting the narrative after grounds were formed, leaving no record of what created the suspicion.
The Decision Moment
Explicitly connect your observations to your legal conclusion. Courts need a logical bridge — not just facts, and not just a conclusion.
- State what you believed
- Reference the specific observations that led there
- Name the offence you suspected
- Apply the correct legal standard (RAS vs. RPG)
"Based on the above observations, I formed a reasonable suspicion that the male was attempting to commit theft from vehicles, and I exercised my authority to detain for investigative purposes."
✗ Common Failure
- "I had reasonable grounds to believe…" — stated with no connection to the facts above.
Actions Taken
Once grounds exist, document every action and its justification. Each step must be proportionate and tied to a lawful authority.
- What action was taken (detain, arrest, search, demand)
- Why that action was proportionate
- Legal authority for the action
- Charter obligations triggered and fulfilled
"Given my suspicion of theft offences and concern for officer safety, I detained the male and conducted a pat-down search for weapons. I advised him of his right to counsel and caution under s.10(b) of the Charter at 23:17 hrs."
✗ Common Failure
- Documenting a search without stating the authority. "I searched the accused" — under what power?
The Grounds Ladder
Different police actions require different legal thresholds. Applying the wrong standard — or failing to articulate the right one — exposes your actions to Charter challenge. Know which rung you're on and document accordingly.
Actus Reus & Mens Rea
Every criminal offence has two components that Crown must prove beyond a reasonable doubt. Your report must contain evidence supporting both. Missing either one — or documenting them vaguely — creates reasonable doubt before the case even reaches court.
Actus Reus
// "the guilty act"The physical element of the offence — the conduct, circumstance, or consequence that the Criminal Code prohibits. This is the backbone of charge selection and charge validation. Start here.
Every charge has a specific actus reus formula. If the act isn't clearly described in the report, the charge isn't supported — regardless of what the officer believed.
The act itself — what the accused physically did. "Struck the complainant with a closed fist" not "assaulted."
The required conditions — e.g., "without consent," "knowing it was stolen," "while in a dwelling-house." Must be explicit.
Required only for some offences — e.g., bodily harm for s.267(b). Describe the injury specifically, not just "the complainant was injured."
Mens Rea
// "the guilty mind"The mental element — what the accused intended, knew, or was reckless about. You cannot read minds. Document indicators of mental state only — what was said, done, or apparent from the circumstances.
Never write "the accused intended to…" without supporting evidence. Let the facts speak. The trier of fact draws the inference from the documented behaviour.
Evidence Linkage — Connect the Dots
Listing exhibits is not enough. Your report must explain what each piece of evidence shows and which element or ground it supports. Crown prosecutors need to be able to prosecute from the report — without calling you to fill in the blanks.
🎥 Video Evidence
Must include: Where footage was obtained (business name, camera ID), time range captured, what relevant events are visible, how it was preserved (download method, hash value if applicable), where the file is stored, and who has custody.
Failure: "Video was obtained from the business." — What does it show? Where is it? Who has it?
📱 Digital Evidence
Must include: Device description and condition at seizure, who had possession, passcode obtained (if yes, how), continuity from seizure to storage, extraction method, hash values, what relevant content was found and where.
Failure: "The accused's phone was seized." — Is it locked? Who extracted data? What was found?
🔬 Physical Exhibits
Must include: Where found (exact location relative to accused/scene), who found it, condition at time of seizure, packaging method, seal number, exhibit tag, all transfers with date/time/person, storage location, and what element of the offence it supports.
Failure: "Drugs were found on the accused." — Where exactly? Condition? Packaging? Lab submission?
🧾 Witness Evidence
Must include: Full identifier for each witness, what they observed (not your summary of their summary), verbatim key statements, whether they were separated before interviewing, and where formal statements are stored.
Failure: "A witness confirmed the assault." — Who? What exactly did they say? Were they a credible observer?
🩺 Medical Evidence
Must include: Your own observations of injuries (specific, descriptive, not medical diagnoses), whether complainant sought treatment, hospital/clinic name, treating physician if known, photo references, and how injuries connect to the force described.
Failure: "The complainant had injuries." — What injuries? Where on the body? Observed by you or reported only?
📊 CPIC / Database Results
Must include: What query was run, what result was returned (relevant portions only — not full CPIC printing), how the result contributed to your grounds or decision-making, and the time the query was run.
Failure: Using CPIC results to form grounds without documenting what the result actually said.
Statements, Cautions & Charter Rights
Statement evidence is among the most litigated in criminal trials. Every word matters — including the words you didn't write down. Defence will challenge paraphrase, question timing, and attack voluntariness. Document the exact words, the exact time, and the exact context.
📝 Verbatim Key Statements
- Admissions recorded in exact words, in quotation marks
- Threats or incriminating statements — word for word
- Consent given or refused — exact words and context
- Spontaneous statements noted with precise time and location
- What question was asked before an answer, where applicable
✗ Never Write
- "He admitted to the assault." — Record what he actually said.
- "She agreed to the search." — Record her exact words of consent.
⚖️ Charter Cautions (s.10)
- Exact time caution was given (not "upon arrest" — give the time)
- Which caution was given (arrest caution / secondary caution)
- Whether the accused indicated understanding
- Right to counsel: whether they invoked, waived, or requested duty counsel
- Whether questioning was suspended pending counsel access
✗ Common Failure
- "The accused was read his rights." — When? Which rights? Did he understand? Did he ask for a lawyer?
🔇 Silence & Refusals
- If the accused said nothing — document that they declined to comment
- Refusal to provide identification — documented specifically
- Refusal of breath demand — exact words of refusal
- Do not draw inferences from silence in the report
- Distinguish between refusing to answer and spontaneous comments
🎙️ Recorded Statements
- Note that a recorded statement was taken
- Location of recording (RMS, disc, digital storage)
- Caution administered prior to — document in notes
- Key admissions from recording summarized in report
- Transcript reference if available
Top 20 Charge Reference
Quick-reference templates for Canada's most frequently charged Criminal Code offences. Each entry shows exactly what your report needs to support the charge — and what's most often missing. Click a charge to expand.
- Describe the physical act precisely (what force, where on body, how)
- Complainant's non-consent in their own words where possible
- Injuries — observed by you, described specifically
- Photos, video, witness references
- Medical attention sought — note if complainant declined
- "An assault occurred" — without describing the physical act
- Non-consent implied but never stated
- Vague descriptors ("he was aggressive") without specific behaviours
- Weapon description — type, size, colour, condition, serial if applicable
- How weapon was used (swung, pointed, brandished, struck)
- Distance between accused and complainant during weapon use
- Continuity if weapon seized — where found, packaging, seals, storage
- Complainant's account of weapon use in their words
- Weapon mentioned but not linked to the assault act
- No continuity documented when weapon seized
- "He had a knife" — without describing how it was used in the assault
- Injury description — your observations specifically (not just "she said she was hurt")
- Medical assessment references if applicable
- Photos — taken by you, ambulance, hospital — all referenced
- Linkage sentence: how described force caused the observed injury
- Duration/impact of injury on complainant noted
- "Bodily harm" asserted with no injury description
- Injury documented but not linked to the specific force applied
- Only complainant's report of injury — no independent observation
- Verbatim threat — exact words are essential. Paraphrase destroys the charge.
- How threat was communicated — preserve screenshots, voicemails, messages
- Context of threat — preceding argument, relationship, history
- Complainant's reaction (not legally required, but highly relevant)
- Digital evidence continuity if threat was electronic
- "He threatened her" — without recording the exact words said
- Digital threat mentioned but not preserved or continuity not documented
- Context missing — isolated words without surrounding circumstances
- Verbatim demands or threats made during the robbery
- Description of force used and how it enabled the taking
- Timeline connecting the force/threat to the moment of taking
- Property description, value estimate, and source of value
- Video references; weapon continuity if weapon used
- Threat described but not linked to the taking of property
- Property not identified or value not documented
- Demand paraphrased rather than recorded verbatim
- Ownership/possession facts — who owned it and how is that established
- Item description with identifiers, serial numbers where applicable
- Value estimate and source (owner statement, receipt, market value)
- How the taking occurred — from where, by what act
- Recovery status and current location of property
- Ownership not documented — assumed but not established
- Value threshold not documented (under vs. over $5,000 affects UCR coding)
- Taking act described vaguely — "took the item" without specifics
- Exact false representation made — what was said or done that was untrue
- How victim relied on the representation (what they did as a result)
- Financial records, communications, transaction history
- Loss amount — source and calculation method documented
- Pattern of similar conduct where applicable
- Deceit described generally without identifying the specific false statement
- Loss amount asserted without documentation of how it was calculated
- Victim reliance not established — they received the goods but were deceived?
- Point of entry — window, door, wall — how it was secured and how it was breached
- Tool marks, damage — photographed and described
- Place type confirmed — dwelling-house status documented
- What offence was committed or intended inside — evidence supporting this
- Ownership/occupancy of premises established
- Entry described but "break" element not established (how was security breached?)
- Place type assumed rather than confirmed
- Intent inside not documented — entry established but no evidence of intended offence
- Describe damage — location on property, extent, photos
- Repair estimate or value impact — and source of that estimate
- Link accused conduct to damage (witness, video, forensic)
- Ownership of damaged property established
- Property value for UCR classification (over/under $5,000)
- "Property was damaged" with no description of what was done or the extent
- No photos or repair estimate referenced
- No linkage between the accused's actions and the damage
- Where found — exact location relative to accused (on person, within reach, in vehicle)
- Who else had access to the location — establish accused's control
- Item description and basis for classification
- Authorization status — CFRO query, PAL check
- Full continuity — seizure, packaging/seals, storage, transfers
- Possession not linked to accused — found in shared space with no control analysis
- Classification not supported — assumed rather than confirmed
- Continuity gaps — seized but storage and transfer not documented
- Exact location found — on person, specific pocket, compartment, container
- Who else had access to that location
- Description — colour, form, packaging, approximate weight
- Field test result (reagent type, result, date) or lab submission number
- Full continuity — seizure details, packaging, seals, storage, transfers
- "Drugs found" without specific location or access analysis
- No field test or lab submission referenced
- Continuity breaks — seized but no packaging or storage documented
- Possession/control facts tying item to accused — exclusive access documented
- How confirmed stolen — CPIC serial query, owner identification, BOLO match
- Knowledge indicators documented as observed behaviours or statements
- Property description with identifiers that enabled the stolen confirmation
- Continuity if property seized
- Stolen status assumed — no confirmation method documented
- Possession not linked to accused in shared space
- Knowledge indicators missing — no evidence accused knew it was stolen
What Gets Reports Kicked Back
These are the patterns that consistently result in files being returned from Crown, charges being stayed, or evidence being excluded. If your report has any of these problems, address them before submission.
⏱️ The "When" Problem
- Missing exact times for key steps — arrival, demand, caution, detention, arrest
- Unclear sequence — what happened before grounds formed vs. after
- No indication of when notes were written (contemporaneous vs. reconstructed)
- Timeline ambiguity undermines every Charter analysis
👤 The "Who/What/Where" Problem
- Incomplete identifiers — "male, 30s, dark jacket" instead of full descriptors
- Vague locations — no civic address, no room/direction context
- Missing relationship mapping — who is who and how they connect
- Unclear who said or did what in multi-person incidents
⚖️ The "Why You Did It" Problem
- Conclusions without observations — "I believed drugs were present" with no factual basis
- Boilerplate grounds language that doesn't connect facts to legal threshold
- Missing documentation of informational inputs (dispatch, witness, CPIC)
- Hindsight reasoning — using post-action discoveries to justify prior decisions
💬 The "Exact Words" Problem
- Paraphrasing admissions instead of recording verbatim key phrases
- Missing cautions, or no record that they were delivered and understood
- Mixing what the witness said with what the officer inferred
- Charter timing not documented — "upon arrest" is not a time
🔗 The "Chain of Custody" Problem
- Seizure details missing — no location, condition, or packaging documented
- Gaps in transfer logs — who had it, when it moved, where it went
- Digital evidence: no hash, no download method, no continuity of device
- Exhibit referenced in narrative but not found in exhibit log
📋 The "Missing Element" Problem
- Charge selected but key actus reus element not documented
- Bodily harm charged but injury not described specifically
- Robbery charged but force not connected to the taking
- Consent element missing — assumed but never established
10-2 Validates This — Automatically.
Every element in this guide is what 10-2 checks against every report, in real time, before it's submitted. Less rework. Stronger files. Greater confidence in court.
Request a Demo Back to Main Site