Skip to main content
§ 00Records & Transparency

Public Records Response Letters: Templates and Exemption Basics

Practical templates for acknowledgment, extension, partial release and denial letters, plus a simple habit: cite only the legal basis your city attorney has supplied.

Linda Park 11 min read
A city hall staff member pins a sheet explaining how to request public records to a lobby notice board while a resident walks past in the background.

When someone asks your city for public records, the records are only part of what they receive. The rest is the letter that comes with them, or the letter that explains why some of them are not coming. For the requester, that letter is the city speaking. It tells them whether they were heard, when to expect an answer, what was held back, and why.

For your office, the same letter has a second life. If a request turns into a dispute, the response letters are often the first documents a reviewing court, appeals officer, or state review office reads. A clear, well-supported letter shows that the city followed the law and treated the requester fairly. A vague one can make a correct decision look careless.

This guide covers the four letters most offices send most often: the acknowledgment, the extension, the partial release, and the denial. For each one you will find what it needs to contain, a plain template you can adapt, and common mistakes to avoid. It also covers one habit that matters more than any template: citing only the legal basis your city attorney has supplied, in the words your attorney approved.

A note before you start. Public records laws differ from state to state in their deadlines, their exemptions, their fee rules, and what a response must say. The templates here are starting points, not legal forms. Before you adopt any of them, have your city attorney review them against your state's law, and check with your state clerk association for guidance written for your state.

What a response letter has to do

Whatever kind of letter you are sending, it has four jobs.

  1. Identify the request. The requester, and anyone reviewing the file later, should be able to tell exactly which request this letter answers.
  2. State the status and what happens next. Received, in progress, extended, fulfilled in part, fulfilled in full, or denied. If something is still pending, give a date.
  3. Explain any decision not to release. Every withholding or redaction needs a legal basis and a short, understandable explanation.
  4. Tell the requester their options. Who to contact with questions, how to narrow or clarify, and, where a decision limits access, what review or appeal options exist under your state's law.

A letter that does all four is usually a good letter, even if it is short. A letter that skips one of them tends to generate a follow-up call, a second request, or a complaint.

Remember too that your response letters are themselves public records. Keep them with the request file and handle them under your retention schedule. Write every letter as if it might be read aloud at a council meeting or quoted in the local paper, because sometimes it will be.

Other letters in the family

Most offices also need a few related letters. They follow the same principles, so this guide does not give each its own section:

  • Clarification requests, when you cannot tell what records are being asked for.
  • Cost estimates or fee notices, where your state allows fees for copies or staff time.
  • Fulfillment or closing letters, confirming the request is complete.
  • No responsive records letters, covered briefly in the denial section below.

The parts every letter shares

Build all your templates on one common frame. Consistency helps requesters, who learn where to look for the information they need, and it helps staff, who can review a letter faster when every letter is built the same way.

  • City letterhead and the date the letter is sent. Use the actual send date, not the date it was drafted.
  • Request tracking number. Every request should have one, even in small offices that log requests in a spreadsheet.
  • Requester's name and contact information, as they provided it. Many states limit whether you can require identification or a reason for the request. Do not ask for more than your law allows, and do not add information the requester did not give you.
  • Date received. This is often the date the legal clock starts, so record it carefully.
  • The request, restated. Quote it or describe it as precisely as you can. If you summarize, do not narrow it.
  • Status and next date. One or two sentences.
  • Legal basis, where needed. Only in letters that delay, withhold, or redact.
  • Contact person. A name, title, phone number, and email. A general inbox is fine as a backup but should not be the only contact.
  • Review or appeal information, where needed. Use the language your attorney has approved.
  • Signature block. Name, title, and, where your state or city designates one, the officer responsible for public records.

Here is a skeleton you can use as the base for every template:

[City letterhead]

[Date sent]

[Requester name] [Requester contact information as provided]

Re: Public records request [tracking number], received [date received]

Dear [Requester name]:

[Body: status, explanation, next steps.]

If you have questions about this request, please contact [name, title] at [phone] or [email]. Please include your request number, [tracking number], in any correspondence.

Sincerely,

[Name] [Title] [Department]

Keep the language plain throughout. Write "we found 42 pages" instead of "a total of 42 pages of responsive documentation have been identified." Write "we removed" instead of "redactions have been applied." You are writing to a resident, a reporter, or a business owner, not to a judge.

The acknowledgment letter

The acknowledgment tells the requester three things: you received their request, here is how you understood it, and here is when they can expect a response.

Some states require a written acknowledgment within a specific period. Others require only that the agency respond, fully or with a reason for delay, by a deadline. Even where an acknowledgment is not required, sending one is good practice. It catches misunderstandings early, before staff spend hours searching for the wrong records, and it gives you a dated record that the request was received and logged.

What to include

  • The request restated in the requester's own words, or as close as possible.
  • The date received and the tracking number.
  • What happens next, and the date by which you expect to respond or provide a status update.
  • Any fee or format information that applies, using language your attorney has approved.
  • A contact person.

Template: acknowledgment

Dear [Requester name]:

Thank you for your public records request. We received it on [date received] and have assigned it tracking number [tracking number].

You asked for: "[request, quoted as submitted]."

We are now searching for records that match your request. We expect to respond by [date], or to contact you before then with an update. [If applicable: You asked to receive records by email. We will send them that way unless the format of the records makes that impossible, in which case we will contact you about other options.]

If we have misunderstood your request, or if you would like to add to it or narrow it, please let us know.

When the request needs clarification

Sometimes you cannot tell what records the requester wants. "All emails about the park" could mean one park or twelve, one month or ten years. In that case, ask specific questions instead of guessing.

  • Ask about the subject, the time period, the people or departments involved, and the type of records.
  • Offer examples of how the request could be narrowed, without pressuring the requester to narrow it.
  • Say plainly that you will keep working on the parts of the request you do understand, if that is possible.

Whether a clarification request pauses your response deadline varies by state. In some states it does, in some it does not, and in some it depends on the circumstances. Confirm your state's rule with your city attorney before you write language about deadlines into a clarification template.

The extension letter

An extension letter tells the requester that you need more time, why, and exactly how much. It is the letter most likely to frustrate people, so it is worth writing carefully.

Many state laws allow extensions only for specific reasons, and some limit how long an extension can be or how many times you can extend. Common reasons recognized in many states include a large volume of records, records stored offsite or in older systems, the need to consult with another agency or a third party whose information is involved, and the time needed to review records for exempt information. Your template should list only the reasons your state actually recognizes. Ask your attorney for that list and the approved wording for each.

What makes a good extension letter

  • A specific date. "As soon as possible" is not a date. Neither is "in the coming weeks."
  • A real reason. Choose the reason that applies to this request, and add a sentence of plain explanation. "The request covers about 3,000 emails, and each one must be reviewed before release" is far more useful than a bare reference to volume.
  • Rolling release, where practical. Offer to send records in batches as they are ready. Many requesters prefer partial records now over complete records later.
  • An honest offer to narrow. You can explain that a narrower request could be answered sooner. Make it an offer, not a condition.

Template: extension

Dear [Requester name]:

We are writing about your public records request [tracking number], received [date received], for "[request, quoted]."

We need additional time to respond. [Reason, using language approved by the city attorney.] In plain terms, [one or two sentences explaining the specific situation, such as the number of records or the need to consult another agency].

We now expect to complete our response by [specific date]. [If applicable: We will send records in batches as they are ready. The first batch should reach you by [date].]

If it would help, we are glad to talk with you about ways to focus the request, which may allow us to respond sooner. You are not required to change your request.

Pitfalls to avoid

  • Sending an extension after the original deadline has passed. In many states the extension must be sent before the deadline.
  • Using the same generic reason on every extension.
  • Extending again without new information. If you need a second extension, explain what changed.
  • Missing the new date you set. If it starts to slip, contact the requester before the date, not after.

The partial release letter

For many requests involving personnel matters, police activity, contracts, or resident complaints, the most common outcome is a partial release. You provide most of the records, but some information is redacted or some documents are withheld in full.

The partial release letter has to account for every piece of information that did not reach the requester. That does not mean explaining each blacked-out line in a separate paragraph. It does mean the requester should be able to tell what kind of information was removed, from where, and on what legal basis.

What to include

  • What you are releasing, in clear terms: how many records or pages, in what format.
  • What you withheld or redacted, by category.
  • The legal basis for each category, using the citation your attorney supplied.
  • A short plain-language explanation of why that basis applies.
  • Review or appeal information, if your state provides for it.
  • Whether the request is now complete or more records are coming.

Template: partial release

Dear [Requester name]:

This letter responds to your public records request [tracking number], received [date received], for "[request, quoted]."

We located [number] records, totaling [number] pages. We are releasing [number] pages in full and [number] pages with some information removed. We are withholding [number] records in full. The released records are [attached / available at link / enclosed].

We removed or withheld the following information:

  1. [Category of information, such as personal phone numbers and home addresses of private individuals.] Legal basis: [citation as supplied by the city attorney]. [One sentence in plain language explaining how this applies.]
  2. [Category.] Legal basis: [citation]. [Plain explanation.]

A list of the records and pages affected is attached.

[Review or appeal language approved by the city attorney.]

[This completes our response to your request. / We will send the remaining records by [date].]

Use a withholding index

For anything more than a handful of redactions, attach a short index, sometimes called a redaction log or privilege log. Some states require one in certain situations. Even where it is not required, it makes your decisions easier to understand and easier to defend, and it helps your own office if the request is ever reviewed.

Record Pages What was withheld Legal basis (from city attorney) Status
Email, Jan. 14, from Public Works director 3 Personal cell number of a resident [Approved citation] Released with redaction
Inspection report, Site 4 7 to 9 Security system details [Approved citation] Released with redaction
Memo from city attorney to manager 1 to 4 Entire document [Approved citation] Withheld in full

The examples above are illustrations of format only. Whether any of those categories is protected in your state is a question for your city attorney.

Redact carefully

A partial release letter is only as good as the redactions behind it. A few practical habits:

  • Redact narrowly. Remove the protected information, not the whole sentence or page around it, unless your attorney advises otherwise.
  • Use redaction tools that actually remove the underlying text from electronic files, and check the output. Drawing a black box over text in a document does not always delete the text beneath it.
  • Keep an unredacted copy and a redacted copy in the request file, so you can show exactly what was removed.
  • Have a second person review redactions on sensitive releases before they go out.

The denial letter

A full denial, where you withhold every responsive record, should be uncommon. Most public records laws start from a presumption that records are open, and many expect agencies to release any portion of a record that is not itself exempt. When a full denial is the right answer, the letter needs the most care of any letter you send.

What a denial letter must do

  • State clearly that the request is denied, in full.
  • Identify the records being withheld, at least by type and approximate number, unless doing so would itself reveal protected information. Your attorney can advise on that situation.
  • Give the specific legal basis, as supplied by your attorney.
  • Explain in plain language how that basis applies to these records.
  • Where your state expects it, confirm that you considered whether any portion could be released.
  • Tell the requester how to seek review or appeal, including any deadlines, using approved language.
  • Provide a contact person.

Template: denial

Dear [Requester name]:

This letter responds to your public records request [tracking number], received [date received], for "[request, quoted]."

We located [number / description of] records that match your request. After review, we are withholding these records in full.

Legal basis: [citation as supplied by the city attorney].

[Two or three sentences in plain language explaining what the records are, as far as can be said, and why the legal basis applies to them.]

We reviewed the records to determine whether any portion could be released. [Approved explanation of why no portion can be separated and released.]

[Review or appeal language approved by the city attorney, including any deadlines.]

If you have questions about this decision, please contact [name, title] at [phone] or [email].

When there are no responsive records

A "no records" response is not the same as a denial, and in some states it is treated differently. But it deserves the same care, because a requester who is told "nothing exists" will want to know how hard you looked.

  • Say plainly that no responsive records were located.
  • Describe the search: departments and systems checked, date ranges, search terms used.
  • Do not suggest that records exist but are being withheld.
  • If another agency is more likely to hold the records, say so where you can.

This is the habit that holds the whole system together. Staff should not choose exemptions on their own, and should not paraphrase legal citations from memory. The legal basis in every letter should come from your city attorney, in the words your attorney approved.

That is not because clerks lack judgment. Experienced records staff are often the first people to recognize a record that needs protection. It is because exemptions are legal conclusions. Applying the wrong one, citing one that has been amended, or stretching one beyond its meaning can expose the city to liability, and it can also deny a resident information they had a right to see. Getting it right protects both the city and the public.

Build an approved exemption language library

Most offices see the same handful of situations over and over. Instead of asking your attorney to write fresh language every time, ask for a library of approved entries. Each entry should include:

  • The citation, exactly as the attorney wrote it. Do not shorten it or reformat it.
  • A plain-language explanation suitable for a resident, one or two sentences long.
  • When it applies. The types of records and information it covers.
  • When it does not apply. Common situations where staff might be tempted to use it but should not.
  • Whether it is mandatory or discretionary. In some states, certain information must be withheld, while other information may be withheld at the agency's discretion. That difference matters.
  • Date approved and the attorney who approved it.
  • Date of next review.

Categories that commonly appear in state public records laws include personal privacy, certain personnel information, ongoing law enforcement investigations, attorney-client communications, security-sensitive information, and confidential commercial information submitted by businesses. Some federal laws also protect certain health, student, or criminal history information. Which of these exist in your state, what they cover, and how they are worded is entirely a matter of your state's law and your attorney's advice. Treat this list as a prompt for the conversation, not as a list of exemptions you can use.

Rules for using the library

  • Use the entry only when the situation clearly matches. If you are unsure, ask.
  • Send anything new to the attorney. A new type of record, a new situation, or a requester who has already challenged a decision should get a specific review.
  • Never use a catch-all. "Exempt under state law" or "confidential" without a specific basis gives the requester nothing to understand or challenge, and in many states it is not a sufficient response.
  • Do not rely on a local policy alone. In many states, a city cannot create an exemption by ordinance or internal policy. Your attorney can tell you whether any local rules have legal weight in your state.
  • Apply exemptions narrowly. An exemption that covers one piece of information in a record usually does not cover the whole record.

Keep a short decision note

For each partial release or denial, keep a brief internal note in the request file: who reviewed the records, which library entry or specific attorney advice was used, and the date. Whether that note is itself disclosable is a question for your attorney, but having it makes your decisions traceable and helps the next person who handles a similar request.

Keeping your template set accurate and readable

Templates drift. Someone edits a letter for one request, saves it over the master copy, and six months later the office is sending language nobody approved. A little discipline prevents that.

Control the templates

  • Assign one owner for the template set, usually the records officer or clerk.
  • Store masters in one location, with editing limited to the owner.
  • Put a version date in each template's footer so you can tell at a glance which version a letter used.
  • Keep superseded versions, so you can show what language was in use on any given date.
  • Review at least yearly, and again after any change to your state's public records law, any relevant court decision, or any update from your attorney. The end of your state's legislative session is a natural time to check.

Write for the person reading it

Your letters go to longtime residents, first-time requesters, reporters, attorneys, and people who are angry about something unrelated to records. Write for all of them.

  • Use short sentences and ordinary words. Put legal citations on their own line so the explanation around them stays readable.
  • Lead with the answer. "We are releasing 40 pages, with some information removed" belongs in the first paragraph, not the fourth.
  • Avoid defensive phrasing. "The city is not obligated to" reads very differently from "The law does not require us to create new records, but we can tell you what records we do have."
  • Offer accessible formats and, where your city provides language assistance, translation on request.
  • Thank people. A records request is a resident taking part in their government. That deserves a thank-you, even when the answer is no.

Pre-send checklist

Before any letter goes out, run through this list. It takes a couple of minutes and catches most errors.

Check Why it matters
Tracking number and date received are correct Ties the letter to the right request and the right deadline
Request is quoted or restated accurately, not narrowed Prevents disputes about what was asked
Send date is within the legal deadline Late responses can create problems in many states
Any delay reason is one your state recognizes Unsupported extensions may not hold up
Every withholding has a legal basis from the attorney's approved language Keeps decisions consistent and defensible
Each legal basis has a plain-language explanation Helps the requester understand the decision
Redactions are verified in the output file Prevents accidental disclosure of protected information
Withholding index is attached where needed Accounts for every record and page affected
Review or appeal language is included where required Tells the requester their options
Contact name, phone, and email are current Gives the requester a real person to reach
Template version date is current Confirms you are using approved language

Next steps

You do not need to rebuild everything at once. A practical order:

  1. Collect what you have. Gather every response letter your office has sent in the past year or so and sort them into acknowledgments, extensions, partial releases, denials, and others. You will quickly see where the language varies.
  2. Draft a common frame using the shared elements above, and adapt the four templates to your office's style.
  3. Meet with your city attorney. Ask for review of the templates, the list of extension reasons your state recognizes, approved review or appeal language, and a first set of exemption library entries for the situations you see most.
  4. Check with your state clerk association for state-specific guidance, model language, or training on your public records law.
  5. Set up template control: one owner, one location, version dates, and a yearly review on the calendar.
  6. Train everyone who sends letters, including department staff who respond to requests directly, on the templates, the library, and the rule that new situations go to the attorney.

Good response letters come from finding records quickly and knowing what the city has said before. If your office is looking at tools that help with that, Govera's institutional memory search covers a city's full archive with citations back to the source document, staff review every output, and every action is audit logged. Whatever tools you use, the letter that goes out should still reflect your staff's judgment and your attorney's legal basis, written so any resident can understand it.

Frequently Asked

Questions clerks ask

Do we have to send an acknowledgment letter for every public records request?

It depends on your state. Some public records laws require a written acknowledgment within a set period, and others only require a response by a deadline. Even where it is not required, a short acknowledgment is good practice. It confirms what the requester asked for, gives them a tracking number and a contact, and creates a clear record that your office received the request on a specific date. Confirm your state's requirements with your city attorney.

Can a records clerk decide which exemption applies to a document?

Clerks often spot records that may need protection, and that judgment is valuable. The final decision about whether an exemption applies, and how it should be cited, should come from your city attorney or the legal counsel your city designates. A good practice is to keep a library of exemption language the attorney has approved, and to send anything new or unusual for specific review before a letter goes out.

Is it enough to say a record is exempt under state law?

Usually not. Many states require a denial or redaction to identify the specific legal basis, and a vague reference gives the requester no way to understand or challenge the decision. Use the exact citation your city attorney supplies, add a plain-language sentence explaining how it applies, and tell the requester what review or appeal options exist. Check your state's specific requirements with your attorney or state clerk association.

What should a letter say when we have no responsive records?

Say clearly that no records responsive to the request were located, then describe the search: which departments, systems, and date ranges were checked, and what search terms were used. Do not imply records exist but are being withheld. If another agency is likely to hold the records, say so where you can. In some states this letter has its own legal treatment, so confirm with your city attorney how to phrase it.

How often should we review our records response templates?

Review the full set at least once a year, and again whenever your state legislature amends the public records law, a court decision affects how exemptions are applied, or your attorney updates approved language. Put a version date in each template's footer and keep the old versions, so you can show which wording was in use when a particular letter was sent.

Linda Park

Open Government Advocate

Linda works on civic engagement and open meetings, helping residents follow what their government does. She writes about transparency that builds trust.

Reviewed October 7, 2026

Keep reading

See it on your own record

Give your clerks their time back

Govera drafts from your city's own documents and cites every line. Book a short demo and see it with your records.

Schedule a Call