Writing a request that actually gets answered

Most public-records requests never get refused. They just stall — and the reason is almost always something the requester did in the first three sentences.

There's a particular kind of silence people run into. You send a request, you get an acknowledgement, and then nothing. Weeks pass. You follow up and get told it's "being processed." Eventually someone says the request was too broad, or asks you to clarify, or quotes a fee big enough to end the conversation.

None of that is a refusal. It's a request that was easy not to answer. The fix is almost entirely in how you write it.

Ask for records, not answers

This is the mistake that swallows most first attempts. A records law gives you the right to existing documents. It does not oblige anyone to explain themselves, answer questions, do research for you, or create something new.

So a request phrased as a question — "why was this contract approved?", "who decided to cancel the route?" — can be answered honestly with "we have no record responsive to that." The agency isn't being slippery. You asked for an explanation, and an explanation isn't a record.

Don't ask what happened. Ask for the documents that would exist if it happened.

Reframe it. If a decision was made, something exists: minutes, an agenda item, a staff memo, a signed contract, an email thread, an invoice, a change order. Ask for those. Let the documents tell you why.

Before and after

• Too vague: "All information about the bus route changes."
• Answerable: "Board meeting minutes and agenda packets from 1 January 2026 to 30 June 2026 that reference transportation routing; any staff memoranda to the Board on route changes in that period; and any contracts or amendments with transportation vendors signed in that period."

The second one can be searched. Someone can walk to a filing cabinet or a shared drive and come back with a yes or a no. That's the test — could a person who knows nothing about your situation go and look?

Give it a date range and a place to look

Two things turn a request from a research project into a task: when, and where.

A date range does more work than anything else you can add. "All emails about the property" is a request to search an entire mail system for all time. "Emails between the zoning administrator and the applicant between 3 March and 30 April 2026" is a search someone can actually run.

Naming where you think the records live helps too — a department, a named position, a specific meeting. You don't have to be right. You just have to make it easy for the person looking to know where to start.

Ask for the format you actually want

If records exist electronically, say you'll take them electronically. It's usually cheaper for you and easier for them — and it avoids arriving at a counter to find a per-page copying charge waiting.

Say it plainly in the request: that you'll accept PDF or native electronic files by email or download, and that you don't need paper copies.

Say you want a fee estimate first

Fee estimates end more requests than denials do. Someone asks for two years of emails, gets quoted several hundred dollars, and stops.

Include a line asking to be told the estimated cost before any work is done, and asking for it broken down. Two things follow. You don't get an unexpected bill. And you find out where the cost sits — if the search is cheap but redaction is expensive, you can narrow to the part that isn't.

A large estimate is not the end. It's information about scope. Narrow the date range, drop a custodian, ask for one category first — and the number usually moves a long way.

Put it in writing, and keep proof

Phone calls are not records requests. Even where an oral request is technically allowed, you'll be unable to prove what you asked for or when, and the response clock becomes an argument instead of a fact.

Send it in writing. Keep the sent copy, note the date and the method, and keep whatever proof of delivery you have — a delivery receipt, a confirmation email, a certified mail receipt. If the request ever becomes a dispute, the date you sent it is the first thing that matters and the easiest thing to lose.

Make the deadline start

Every state sets a response window, and the clock generally starts when the right body receives a proper request. Two things commonly stop it starting: the request went to a general info address nobody owns, or it went to the wrong entity entirely.

Send it to the named records custodian or clerk where there is one. Where there isn't, send it to the body's official address and name the request for what it is in the subject line, so it can't be mistaken for general correspondence.

A request sitting in the wrong inbox isn't late. As far as the law is concerned, it often hasn't been made.

A short checklist

• Asks for documents, not explanations
• Has a date range
• Names a department, position or meeting where you think records sit
• States the format you'll accept
• Asks for a broken-down fee estimate before work starts
• Is in writing, with proof of when it was sent
• Went to the actual custodian, and says it's a records request

Seven lines. Most requests that stall are missing four of them.

What this guide doesn't cover

Deadlines, allowable fees, exemptions and appeal routes are set by each state's own law and they differ significantly. Nothing above depends on those specifics — it's about writing a request that can be worked, which is the same everywhere. For the rules that apply where you are, use a state resource.