Documentation Package Production

Why Documentation Is the Foundation of Corrections Work

Every action you take as a corrections officer can be reviewed by supervisors, courts, civil attorneys, and oversight agencies. A clear, accurate documentation package protects you, protects the agency, and protects the rights of the people in your care. Poorly written or incomplete reports have cost officers their careers and exposed agencies to costly litigation. In this lab you will produce three interlocking documents—an Incident Report (IR), a Use-of-Force Report (UFR), and a Chain-of-Custody Log (CCL)—that together form a legally defensible documentation package.

The Incident Report: Your Foundation Document

The Incident Report is the primary narrative record of what occurred. Every correctional agency uses some version of this form, and all require the same core information organized around the Who-What-When-Where-Why-How framework you practiced in Course 7:

• Who – every person involved: staff, incarcerated individuals, witnesses, medical personnel. Use full names and ID numbers.
• What – the specific actions and events in the order they happened.
• When – exact times for each event. Use 24-hour (military) time to eliminate AM/PM ambiguity.
• Where – the precise location within the facility (housing unit, cell number, corridor designation).
• Why – the observable circumstances that prompted action. Do not speculate about motive; describe only what you directly observed.
• How – the methods used to respond, including verbal commands, escort techniques, restraints, and notifications made.

Write in the first person, past tense. "I observed" and "I directed" are correct. Avoid passive constructions such as "it was observed that," which obscure who did what. Use plain language; avoid jargon that an outside reviewer may not understand. Never include opinions, conclusions about guilt or innocence, or diagnostic labels. Write facts that a camera would have captured.

The Use-of-Force Report: Documenting Every Element

Whenever a use of force occurs—even a minimal level such as a firm grip to redirect an individual—a separate Use-of-Force Report is required. Omitting this document when force was applied is a critical error that can constitute falsification of records. The UFR must document:

1. The level of force applied, matched to your agency's use-of-force continuum.

2. Alternatives attempted before force (verbal commands, de-escalation steps).

3. The behavior or threat that made force necessary, described in observable terms.

4. Any injuries sustained by any party.

5. Medical evaluation offered and the individual's response (accepted or refused).

6. Supervisor notification, including the supervisor's name, rank, and the time notified.

All blocks on the form must be completed. A blank field is as dangerous legally as a wrong answer; if a field does not apply, write "N/A" and initial it.

The Chain-of-Custody Log: Protecting Evidence Integrity

When contraband or any physical item is recovered during an incident, its legal value as evidence depends entirely on an unbroken chain of custody. The Chain-of-Custody Log records:

• A description of the item (type, quantity, distinguishing features).
• The date, time, and location of recovery.
• The name and badge number of the officer who recovered it.
• Every subsequent transfer of the item—who gave it, who received it, date and time—with a signature block for each transfer.
• Final disposition (property room, destruction, transfer to investigator).

Never leave the log unsigned at any transfer point. A break in the chain—even a single unsigned handoff—can make the evidence inadmissible.

Legal Defensibility: What Reviewers Look For

A legal-defensibility checklist is a structured quality-control tool. Reviewers—whether an agency supervisor or a plaintiff's attorney—ask the same core questions:

• Are all times recorded in consistent 24-hour format and do they follow a logical chronological sequence?
• Are all names, ID numbers, and badge numbers complete?
• Is the language factual and free of opinion or protected-class references?
• Do all three documents tell the same story without internal contradictions?
• Are all signature blocks complete?
• Is the Use-of-Force Report present whenever force was applied?

Inconsistencies between documents are among the most damaging defects. If your IR says force ended at 1347 but your UFR records medical evaluation at 1340, that contradiction undermines your credibility.

The Document Audit: Peer Review Before Final Submission

Before submitting, you will exchange your full package with a classmate and apply the legal-defensibility checklist to their work. This mirrors real agency practice, where supervisors review reports before they are finalized. Flag every gap or error using the checklist, return the package to the author, and verify that corrections are made. Then correct any items flagged in your own package. Final submission must reflect all corrections.

Safety Reminders

Documentation itself is a safety issue. Accurate Use-of-Force Reports ensure medical staff have complete information about any injury. Accurate Chain-of-Custody Logs prevent dangerous contraband from being misplaced. Never alter a document after submission without following your agency's formal amendment procedure—unauthorized alterations can constitute a criminal offense. Use blue or black ink only for handwritten forms; other ink colors are frequently rejected by courts and agencies.