How Do You Write a Public Records Request an Agency Can Actually Process?

If you send a public-records request that asks "why," you may get a technically correct response saying the agency doesn't have to answer questions. The process works much better when you ask for the existing records that would let you answer the question yourself.

You may know exactly what feels wrong: the city chose a contractor nobody expected, a policy changed without a clear explanation, or a meeting produced a decision that doesn't match what you heard. So you write, "Why did you do this?" and receive a response that feels deliberately unhelpful.

The agency may not have to create that explanation for you. But it may have the scoring sheets, emails, proposals, minutes, and contracts that show how the decision happened.

Think of the request as a test of an explanation, not a demand for the agency to write one. Your working idea might be, "The lowest price did not win because the city used other scoring criteria." The useful records are the ones that could confirm, complicate, or disprove that idea.

Turn the question in your head into records on paper

Search the agency website, reading room, open-data portal, meeting archive, reports, contracts, budgets, and previously released records. The information may already be available immediately and without a processing fee.

For federal records, the FOIA.gov request guide recommends checking public information first. State and local public-records laws use different names and procedures, so follow the law for the agency that holds the record.

Sketch a document map before you submit: what began the process, who evaluated it, what recommendation was made, who approved it, and what final agreement resulted. That may point you to a solicitation, submissions, scoring, staff memo, meeting record, award notice, and contract without requiring you to request "all documents related to" an entire subject.

Send the request to the record holder

Identify the agency, division, office, or records custodian likely to maintain the material. An agency cannot produce another agency's files merely because the subject is related.

Use the official portal, email, or mailing address and follow any published requirements. Keep the confirmation and tracking number.

Describe records, not a dispute

State the type of record, subject, date range, people or offices involved, location, contract or case number, and preferred electronic format. Use known titles and search terms when you have them.

So instead of asking, "Why did the city choose this contractor?" request the scoring sheets, proposals, evaluation records, award notice, contract, and relevant communications for the named procurement and dates. Now you've given the records officer something concrete to search.

Keep the scope useful

An extremely broad request can require searches across years, offices, accounts, and formats, increasing delay and cost. Narrow the period and record types to what could change your understanding, then file a follow-up if the response reveals a new lead.

You should ask the records officer to contact you before exceeding a fee limit. Also state whether you seek a fee waiver and the legal basis when the applicable law provides one.

Handle clarification and denial carefully

Respond promptly when the agency asks for clarification. If records are withheld or redacted, review the cited exemption, appeal rights, and deadline rather than assuming every missing page is unlawful.

Keep the request firm, neutral, and specific. You're not giving up on the question that brought you here; you're translating it into records the custodian can actually search and you can later use.

When the records arrive, preserve their filenames, order, cover letters, redaction markings, and source. A single email can look decisive after being detached from the thread, while a missing attachment or date range may change what it means.

And remember that records do not interpret themselves. They can reveal the documented path of a decision, but silence in the file may mean no record was created, a search missed it, an exemption applies, or the conversation happened elsewhere. State what the response proves and what it still leaves open.