LASD PARS

Policy Viewer

Policy No. 1100-000 Category: Documentation Revision: 2026-05-26

Documentation, Report Writing, Evidence Logs, and Incident Numbering


1. PURPOSE


Reports create realistic documentation and accountability. Reports should clearly explain what happened, why action was taken, and what evidence supports the decision.

2. REPORT QUALITY


Reports shall be:
A. Accurate.
B. Clear.
C. Detailed.
D. Professional.
E. Chronological.
F. Free from unnecessary slang.
G. Based on observed or reported facts.

3. BASIC INCIDENT REPORT TEMPLATE


Incident Number:
Date/Time:
Reporting Deputy:
Location:
Call Type:
Involved Parties:
Summary:
Probable Cause:
Actions Taken:
Evidence:
Charges:
Use of Force:
Supervisor Notifications:
Disposition:

4. NARRATIVE STANDARD


A good narrative should answer:
A. Who was involved?
B. What happened?
C. When did it happen?
D. Where did it happen?
E. Why did deputies respond?
F. How was the investigation handled?
G. What law/policy supports the action?

5. EVIDENCE LOG TEMPLATE


Item Number:
Description:
Location Found:
Collected By:
Date/Time:
Related Incident:
Disposition:

6. INCIDENT NUMBERING


Incident numbers should follow the department format assigned by command or CAD. If no CAD exists, use a consistent format such as:

YYYYMMDD-UNIT-RANDOM


Example: 20260526-21D14-042

7. SUPERVISOR REVIEW


Reports involving force, pursuits, felony arrests, complaints, or major incidents may require supervisor review.

8. FALSE REPORTS


Knowingly false reports are dishonesty and may result in termination.