Records Request Form Template
A public-records channel that captures specificity, format, and fee consent up front — because the statutory clock starts at a well-formed request.
Use this form to request records from our office. Specific requests are fulfilled fastest — every request is logged with its receipt date.
Departments, subject matter, document types — specificity shortens the search.
Public-records requests fail slowly and expensively. A vague request triggers a clarification letter; the clarification burns two weeks of a statutory deadline; a fee dispute surfaces mid-search and stalls everything again. Each stall is legal exposure for the office and frustration for the requester. This form front-loads the three decisions that cause them — scope, format, and fees — so the clock that starts at receipt runs against a request that can actually be fulfilled.
Why these fields. The records description is the heart, and its guidance does real work: naming departments, subjects, and document types converts "everything about the stadium project" into a search a clerk can execute, and the placeholder demonstrates what fulfillable looks like. The date range is separated into its own field because it is the single biggest lever on search cost — the same request spanning six months or six years differs by an order of magnitude. The format question prevents the last-mile stall: electronic, paper, and in-person inspection follow different workflows and fee schedules, so knowing early matters. The fee-handling choice is the form's sharpest edge — most stalled requests die in fee limbo, where the office fears doing unbillable work and the requester fears an unbounded invoice. Three explicit stances end that standoff, and choosing the waiver reveals a grounds field through a logic rule, since waiver decisions need the public-interest argument in writing.
What we left out. A "purpose of your request" question — many records statutes explicitly protect requesters from having to justify themselves, and asking anyway invites both legal challenge and distrust. Identity documents too: records rights generally attach to anyone who asks, so the correspondence email is all the identity the process needs.
Who uses this. City and county clerks, school districts, public universities, police records units, and any agency whose records officer currently excavates requests from a shared inbox — plus journalists and researchers on the sending side who benefit from a channel that cannot lose their request.
Make it yours. Align the fee options with your published fee schedule and put the schedule's link in the intro text. Turn on email notifications so the records officer sees requests the day they arrive — receipt date is a legal fact here, and the timestamped responses view is your register of it. The CSV export becomes the annual transparency report most agencies compile by hand: volume, subjects, and turnaround, one download. If requests routinely need routing, a webhook can open a tracked task in your case system at receipt.
The register is the defense. When a requester alleges a missed deadline, the timestamped log answers in seconds. A well-formed intake is not bureaucracy — it is the fastest route from request to records, for both sides of the counter.
Frequently asked questions
Why is there no question about the purpose of the request?
Records laws in many jurisdictions say requesters need not explain themselves, so the form deliberately never asks. The waiver-grounds field appears only when someone requests a fee waiver.
How does the office prove when a request was received?
Every submission is timestamped in the responses view — that receipt date anchors the statutory clock, and the CSV export doubles as the official request register.
What happens when someone requests a fee waiver?
A logic rule reveals a grounds field so the public-interest argument arrives in writing with the request, ready for the records officer to rule on without a follow-up letter.
Can long, detailed requests be composed safely?
Yes — partial entries are captured as people type, so a detailed description composed over several minutes is not lost to a closed tab or dropped connection.