Establishing secure connection…Loading editor…Preparing document…

Police Incident Report

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

POLICE INCIDENT REPORT

Administrative Information

Incident / Case Number:

Report Type:

Unit/Shift:

Incident Date, Time & Location

Date of Incident:   Time:

Reporting Officer

Name:

Badge / ID No.:

Contact Phone:

Incident Classification & Immediate Disposition

Disposition:

Arrest Made:

Citation Issued:

Involved Parties

Victim 1

Suspect 1

Witnesses

Narrative / Summary of Events

Evidence / Property

Weapon Present:

Injuries Reported:

Medical Transport:

Actions Taken & Follow-Up

Certification & Notices

I certify under penalty of law that the statements contained in this report are true and complete to the best of my knowledge. I acknowledge that knowingly providing false information in this report may subject me to administrative discipline and criminal penalties as provided by law.

Sensitive information contained herein (including but not limited to victim identity, juvenile records, and investigatory techniques) is restricted and shall be disseminated only in accordance with applicable departmental policy and law. Chain-of-custody entries for evidence must be recorded in the evidence log and are enforceable under agency protocols.

Administrative Review

Reporting Officer (Printed Name):

By:

Date:

Supervisor (Printed Name):

By:

Date:

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What a Police Incident Report Is and Why It Matters

A Police Incident Report is an official record created by law enforcement to document the facts, parties, actions, and observable evidence related to a reported incident. It typically includes identifying details (officer, agency, incident number), date and time, location, a factual narrative, witness and victim information, evidence logs, and administrative dispositions. Agencies use these reports for investigations, prosecutions, insurance claims, internal review, and public-record requests. Accurate, timely reports preserve chain of custody, support legal processes, and reduce exposure to later challenges or disputes.

Why a Complete Police Incident Report Is Important

A clear, accurate report preserves facts for investigations, supports charging decisions, and provides a defensible record for civil or insurance proceedings. Proper documentation reduces ambiguity and protects officer and agency credibility.

Why a Complete Police Incident Report Is Important

Who Prepares and Relies on Police Incident Reports

Several internal and external stakeholders prepare, review, or use incident reports for operational, legal, and administrative purposes.

  • Law enforcement officers and investigators who document on-scene observations and initial statements for investigation and prosecution.
  • Victims, witnesses, and complainants who rely on the report for insurance claims, legal actions, and official records.
  • Prosecutors, defense counsel, and civil attorneys who use the report as a primary evidentiary record during case review and litigation.

Reports also support records units, internal affairs, auditors, and public records requestors; distribution and retention rules vary by agency and jurisdiction.

Who Can Sign or Authorize the Report

Patrol Officer

An on‑scene patrol officer or primary investigator prepares and signs the narrative and action fields. Their signature attests to observed facts, statements taken, and any immediate actions; supervisory review often follows for completeness and accuracy.

Records Supervisor

A records division supervisor or authorized records clerk certifies final entry and distribution. They verify administrative fields, confirm redactions where required, and route copies to prosecutors, insurance carriers, or public records systems per agency policy.

Core Components of a Professional Police Incident Report

A consistent structure improves clarity and legal reliability. Use discrete sections and clear labels so readers can find facts quickly during investigation or review.

Header

Agency name, incident number, reporting officer, shift, precinct, and administrative metadata to uniquely identify the file and support chain of custody and record tracking.

Classification

Recorded offense codes, complaint type, and priority level to guide investigative resources and align the report with statutory charge elements and internal case management.

Narrative

A factual, chronological account of observable events and statements; avoids speculation, separates direct quotes from paraphrase, and lists times for each action or observation.

Parties & Contacts

Full names, dates of birth, addresses, phone numbers, and role (victim/witness/suspect) for every person mentioned, plus identifiers like driver’s license or booking numbers where relevant.

Evidence Log

Detailed inventory of physical evidence, digital files, photos, and BWC footage with collection times, locations, custodian names, and storage references to preserve admissibility.

Disposition & Follow-up

Document officer actions (arrest, citation, referral), required follow-up tasks, notifications to other units, and final administrative classification for case closure or escalation.

Essential Fields Every Police Incident Report Should Include

Incident Number: Unique agency identifier for the case
Date and Time: Exact incident and report timestamps
Location: Street address, city, and cross streets
Parties Involved: Victims, suspects, and witnesses named
Narrative: Factual, chronological event description
Evidence Attachments: Photos, videos, and physical evidence references

Step-by-Step: Completing a Police Incident Report

Follow a consistent sequence to gather, document, review, and file the report so it meets agency standards and preserves admissibility.

  • 01
    Step 1: Secure scene and gather witness statements; note exact times.
  • 02
    Step 2: Collect and log evidence with identifier and custodian.
  • 03
    Step 3: Draft a factual, chronological narrative; include direct quotes.
  • 04
    Step 4: Supervisor reviews, approves, and records final disposition.

Where to File or Send the Completed Report

Reports typically follow internal routing rules that determine storage, dissemination, and access. Confirm your agency's chain-of-submission and retention policies.

  • Records Unit: Primary filing location for preservation and public records access.
  • Prosecutor: Forward copies when charges are pursued or evidence review is needed.
  • Insurance/Claims: Provide redacted copies to third parties per agency release policy.
  • Internal Affairs: Route complaints or use-of-force incidents for administrative review.

Typical Digital Workflow Settings for Online Incident Reports

Configure your digital form to enforce required fields, preserve evidence links, and control access based on role.

Field Configuration
Required Fields Make incident number, date/time, location, and narrative mandatory
Authentication Use agency SSO or multi-factor for officer access
Attachments Handling Allow photo/video upload with automated filename incident-tagging
Audit Trail Enable timestamped edit history and approver notes

Digital Filing and eSubmission Considerations

Secure platforms should support audit trails, role-based access, and common file formats for evidence attachment.

  • File Formats: Support PDF, JPG, MP4, and DOCX for attachments
  • Integrations: Connectors for RMS, evidence lockers, and case management
  • Authentication: SSO, MFA, and advanced signer authentication options

Validate compatibility with your records management system, evidence repository, and public records portal before deployment.

Timing Expectations and Internal Deadlines

Timely completion and routing of incident reports improves investigative outcomes and meets administrative obligations. Agency policies define exact deadlines.

Immediate Filing:

Complete preliminary reports or notes at scene within the same shift

Full Narrative:

Finalize detailed narrative within 24–72 hours per most agency policies

Supervisor Review:

Supervisor should review and sign within 24 hours after submission

Evidence Processing:

Log and submit physical evidence to property room immediately

Public Request Response:

Fulfill records requests within agency-prescribed FOIA/CPRA timeframe

Key Processing Milestones for a Police Incident Report

Track each milestone from creation through archival so stakeholders can monitor status and meet legal requests.

01

Creation

Officer documents initial facts and evidence; generates incident number.

02

Supervisor Review

Supervisor verifies completeness, corrects errors, and approves the record.

03

Records Entry

Records unit ingests the report into RMS and indexes metadata.

04

Release/Archive

Report is released per policy or archived for retention and future requests.

Common Mistakes to Avoid When Preparing Reports

  • Vague narratives that omit times, precise locations, or separating direct quotes from paraphrase create credibility issues.
  • Inconsistent timestamps and conflicting accounts across fields hinder timeline construction and investigative reliability.
  • Missing witness contact details or incomplete physical evidence descriptions prevent follow-up and degrade evidentiary value.
  • Failing to attach body-worn camera footage or photographic evidence reduces the report's completeness and admissibility.

Consequences of Incomplete or Incorrect Incident Reports

Internal Discipline: Policy violations and corrective action
Case Impact: Weakened prosecution or dismissed charges
Civil Liability: Increased risk of civil claims or damages
Evidence Exclusion: Chain-of-custody problems may exclude items
FOIA Exposure: Sensitive data risk if redaction is incomplete
Criminal Liability: Falsifying reports can result in criminal charges

Realistic Use Cases for Police Incident Reports

Practical examples show how reports serve investigations, claims, and internal review across scenarios.

Traffic Collision

Officer documents collision scene and statements

  • Includes photos and diagram of vehicle positions
  • The indexed report enabled quick insurance processing and supported a prompt fault determination by the investigating supervisor.

Domestic Disturbance

Responding officer records victim and witness interviews

  • Evidence logged and BWC linked
  • The detailed narrative and evidence trail supported charging decisions and provided a clear record for victim services referrals.

eSignature Vendor Pricing and Feature Snapshot

Compare starting prices and key capacity differences for commonly used eSignature providers. Confirm vendor plans for exact feature sets and enterprise options.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes (tiered) Varies by plan Varies by plan Varies by plan Varies by plan
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA required) Varies by plan Varies by plan Varies by plan Varies by plan
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Frequently Asked Questions About Police Incident Reports

Answers to common questions about access, corrections, e-signing, and evidence handling to help officers and requestors navigate the process.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.