Define
Turn the objective into precise record categories, dates, custodians, identifiers, formats, and exclusions.
Describe what you are trying to find in plain English. We help turn that into a precise request, track the agency response, organize the production, and identify what still needs attention.
Every workflow follows the same simple lifecycle so first-time requesters get guidance while experienced users can inspect every important detail.
Turn the objective into precise record categories, dates, custodians, identifiers, formats, and exclusions.
Check the agency, jurisdiction, scope, and likely searchability before a request is sent.
Preserve acknowledgements, deadlines, extensions, fees, productions, denials, and communications.
Compare what you requested with what the agency actually produced and surface evidence-backed gaps.
Featured starting points for some of the most common records requests.
Turn a plain-English objective into a precise request with record categories, date ranges, custodians, identifiers, format requirements, and exclusions.
Explore workflowCreate a focused public-records request for code violations, complaints, inspections, notices, photographs, permits, citations, communications, and enforcement history for a property or case.
Explore workflowBuild a targeted request for property, parcel, assessor, recorder, ownership, and related public records tied to a property or parcel.
Explore workflowWe keep the original request, agency response, produced records, references, redactions, and unresolved categories together so you can see what still needs attention.
Research permits, code enforcement, inspections, planning files, and property records tied to an address or parcel.
Build precise requests, preserve agency responses, and audit productions for unanswered categories and gaps.
Keep requests, communications, records, identifiers, timelines, and production analysis together.
Start in plain English without needing to know the exact records workflow or agency terminology.
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.
Yes. Addresses, parcel numbers, permit numbers, incident numbers, case numbers, project names, people, and other agency identifiers can make a request substantially more precise.
The request and production stay together so you can compare the original scope against what was produced and identify missing categories, references to unproduced records, redaction questions, and follow-up needs.
You do not need to know the exact workflow name. Start with the objective in plain English and move into the right records workflow.
Start a Records Request →