Arrest Records Request
Request arrest reports, booking records, charging documents, and related law enforcement records.
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.
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.
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.
Arrest Records Request FAQ
Answers focus on the practical search and request questions people ask before submitting a records request.
Identify the law enforcement agency, the person, and the arrest date or booking number.
Availability varies by jurisdiction and case status. Some arrest records may be restricted, sealed, or expunged, particularly when charges are dismissed.
Mugshots may be available depending on the agency and applicable state law. Include a specific request for booking photographs if they are needed.
If the booking number is unknown, provide the person full name, the approximate arrest date, location, and any other known case identifiers.
Explore adjacent records searches.
Turn this search into an actual request.
Start with the objective in plain English. The workspace handles the structure.
Request arrest records →