Records Requests
Law enforcement · police records request

Police Records Request

Request incident reports, arrest records, dispatch materials, body-camera records, 911 calls, photographs, and related police records with enough specificity to make the request searchable.

$12.99Essential · Police records request — incident-specific request with law enforcement domain
Specific scope · Search-ready identifiers · Evidence-first tracking · Production audit ready
SEARCH-READY SCOPE

Build the request around the records job, not a vague request for “everything.”

A strong records request identifies the agency, record type, time period, and identifiers or custodians that make the records searchable. Official agencies commonly ask for practical inputs such as addresses, parcel or case numbers, dates, permit numbers, custodians, and a clear description of the records sought. This workflow turns those inputs into a structured request.

01Incident reports
02Police reports
03Arrest and booking records
04CAD / dispatch records
05Body- and dash-camera records
POLICE RECORD TYPES

Ask for the records system by system.

Depending on the agency and applicable law, a targeted request can cover incident reports, arrest and booking records, CAD or dispatch records, body-camera and dash-camera recordings, 911 calls, photographs, witness statements, supplements, and case correspondence.

01Incident and offense reports
02CAD / dispatch records
03Body- and dash-camera media
04911 calls and communications
05Photographs and scene media
06Witness, victim and supplemental records
MAKE THE INCIDENT SEARCHABLE

Numbers, dates, location, people, and vehicles reduce ambiguity.

A police-records request becomes easier to route and search when it anchors the incident to identifiers the agency already uses.

01Incident / report number
02Incident date and time window
03Location
04Person / vehicle identifiers
WHAT YOU ACTUALLY DO

Turn the search into a request that an agency can act on.

Enter what you know, identify the records, review the generated scope, and preserve the final request. The goal is a clear, searchable description of the records you want and the information that helps the custodian find them.

01Describe the matter
02Select records and scope
03Review and validate
04Approve and mail
AFTER PRODUCTION

Receiving files is not the same as verifying a complete production.

Preserve the original request, organize the response, and review the production for missing categories, references to records that were not produced, duplicates, identifier inconsistencies, timeline gaps, and redaction or withholding language.

Request scope preserved
Agency response timeline
Production organization
Gap detection
Redaction review
Follow-up preparation
FREQUENTLY ASKED QUESTIONS

Police Records Request FAQ

Answers focus on the practical search and request questions people ask before submitting a records request.

How do I request a police report?

Start with the police agency, incident date, location or incident number, and a plain-English description of the event. People or vehicle identifiers can make the request more precise.

Can I request body-camera footage?

Potentially. The workflow can identify body-camera records and their associated incident, dates, and identifiers. Whether footage is releasable depends on the agency and applicable law.

Can I request 911 calls and dispatch records?

Yes, where maintained and legally requestable. They are separate request categories so the agency can search the relevant systems.

What if I do not know the incident number?

Use the incident date, location, people involved, vehicle identifiers, or a clear description of the event.

RELATED RECORDS WORKFLOWS

Explore adjacent records searches.

READY TO BUILD IT

Turn this search into an actual request.

Start with the objective in plain English. The workspace handles the structure.

Build a Police Records Request →