Public Records Request
Turn a plain-English objective into a precise request with record categories, date ranges, custodians, identifiers, format requirements, and exclusions.
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.
Public Records Request FAQ
Answers focus on the practical search and request questions people ask before submitting a records request.
A public records request asks a government agency for identifiable records it maintains. A strong request clearly describes the records, relevant time period, and useful identifiers or custodians.
Include the agency, subject or matter, specific record categories, date range, known names or identifiers, preferred format when appropriate, and useful narrowing information.
An address, parcel number, case number, permit number, incident number, person, project name, or other agency identifier can substantially reduce ambiguity and help the custodian locate the right records.
Keep the original scope and compare the production against it. Missing categories, referenced-but-unproduced records, duplicates, redactions, and other gaps can become targeted follow-up items.
Explore adjacent records searches.
Turn this search into an actual request.
Start with the objective in plain English. The workspace handles the structure.
Build a records request →