Skip to content
YpsiDatacenter.org YpsiDatacenter.org

Up-to-date information on the proposed University of Michigan / Los Alamos Datacenter Project

YpsiDatacenter.org YpsiDatacenter.org

Up-to-date information on the proposed University of Michigan / Los Alamos Datacenter Project

  • Home
  • Resources
    • About YpsiDatacenter.org
    • What Is a Data Center?
    • Project Timeline
    • Who’s Who
    • What They Said, and What the Record Shows
    • How Loud Is a Data Center?
    • How Much Water Does a Data Center Use?
    • Why We Oppose This Project
    • Why the Township Can’t Zone This — and Won’t Tax It
    • Responsible Opposition
    • The Nuclear Question
    • In the News
    • Sources & Links
  • Community Toolkit
    • Data Center Database
  • Take Action
    • Legislation
      • Bills We are Tracking
      • Contact Your Representatives
    • Sign Up for Updates
    • Contact Your Representatives
    • Our FOIA Guide Has Moved — and Grown
    • FOIA Center
    • Request a Yard Sign
    • Events
    • How to Use Your Ninety Seconds
    • Volunteer
  • Policies
    • Terms & Acceptable Use
    • Privacy Policy
  • News
  • Home
  • Resources
    • About YpsiDatacenter.org
    • What Is a Data Center?
    • Project Timeline
    • Who’s Who
    • What They Said, and What the Record Shows
    • How Loud Is a Data Center?
    • How Much Water Does a Data Center Use?
    • Why We Oppose This Project
    • Why the Township Can’t Zone This — and Won’t Tax It
    • Responsible Opposition
    • The Nuclear Question
    • In the News
    • Sources & Links
  • Community Toolkit
    • Data Center Database
  • Take Action
    • Legislation
      • Bills We are Tracking
      • Contact Your Representatives
    • Sign Up for Updates
    • Contact Your Representatives
    • Our FOIA Guide Has Moved — and Grown
    • FOIA Center
    • Request a Yard Sign
    • Events
    • How to Use Your Ninety Seconds
    • Volunteer
  • Policies
    • Terms & Acceptable Use
    • Privacy Policy
  • News
Close

Search

Subscribe

FOIA Request Examples: Weak, Better, and Why

The FOIA series

  • FOIA Crash Course — the overview
  • Part 1: How to Write a Request
  • Part 2: Tracking Requests and Working with Records Officers
  • Part 3: When It Gets Difficult
  • Part 4: Filing a Federal FOIA Request
  • Examples: Weak, Better, and Why (you are here)

In Michigan? Our Michigan guides cover the state’s law in detail: How to Write a Request and When It Gets Difficult.

The short version

The fastest way to learn to write a good FOIA request is to see the difference between a weak one and a better one. Every example below comes from a mistake I’ve made myself or watched someone else make. None of the weak versions are illegal or rude, and most would eventually get something back. The better versions get you the right records, faster and cheaper.

Square brackets mark the parts you’d fill in. Where an example cites a law, use your own state’s records law and its section numbers — your state resource page links to them.

Writing the request

1. Too broad

Weak: “All records about the data center.”

Better: “Emails between the Township Supervisor or Township Manager and any address at [developer’s email domain] that mention ‘[project name]’ or ‘[street name],’ sent or received between [start date] and [end date], including attachments.”

Why: “All records” forces staff to search every office and every file, which produces a huge fee estimate and a long wait. Naming the type of record, the people, the date range and the keywords tells them exactly where to look.

2. A question instead of a request

Weak: “How much water will the facility use?”

Better: “Records that state or estimate the projected daily or annual water use of the proposed facility at [address], including engineering studies, utility capacity requests and correspondence with [water authority], dated [start date] to present.”

Why: FOIA gets you existing records, not answers. A public body can legally reply “that’s a question, not a request.” Rephrase every question as “records that show…”

3. Asking them to create something

Weak: “A list of every meeting township officials have had with the developer.”

Better: “Calendar entries, meeting invitations and sign-in sheets for meetings between [named officials] and representatives of [developer] from [start date] to [end date].”

Why: A public body doesn’t have to compile a new list for you. Calendars and invitations already exist, and you can build the list yourself.

4. Guessing a document’s exact title

Weak: “The 2025 Water Capacity Study.”

Better: “Any study, report or memo assessing water or sewer capacity to serve the proposed facility at [address], prepared in 2025 or 2026, including drafts if final versions don’t exist.”

Why: If the document is actually titled something slightly different, a request for an exact title can come back “no responsive records.” Describe what the document does, not what you guess it’s called.

5. No date range

Weak: “Correspondence between the County Drain Commissioner and [engineering firm].”

Better: “Correspondence between the County Drain Commissioner’s office and [engineering firm] concerning [parcel or project], dated [start date] to [end date].”

Why: Without dates, a search can reach back decades. Start the range a few months before the project first surfaced, since planning usually starts well before the public hears about it.

6. Too many unrelated things at once

Weak: One request asking for the developer’s emails, the township’s legal bills, the planning commission’s notes, the tax abatement application and the fire department’s emergency plan.

Better: Five separate requests, one subject each.

Why: A combined request moves only as fast as its slowest part, and one item’s fee or exemption can hold up everything else. Separate requests come back separately, and the easy ones come back fast.

7. Accusatory tone

Weak: “Provide all records proving the backroom deal between the Supervisor and the developer.”

Better: “Communications between the Township Supervisor and [developer] concerning [project], dated [start date] to [end date].”

Why: A request isn’t the place to make your case. Neutral language gets processed like any other request, avoids putting staff on the defensive, and won’t embarrass you if the request ends up quoted in a meeting or a court filing. Let the records make the argument.

Getting what you actually meant

8. “Communications” without saying what counts

Weak: “Communications between the Planning Director and [consultant].”

Better: “Communications between the Planning Director and [consultant] about [project], dated [start] to [end]. For this request, ‘communications’ includes emails and their attachments, letters, memos, text messages, and calendar invitations, including text messages about official business on personal devices.”

Why: Some offices read “communications” as “email only.” Text messages about public business are public records even on a personal phone, but searches often skip them unless you ask.

9. Forgetting attachments

Weak: “Emails between [official] and [company] about [project].”

Better: “…including all attachments.”

Why: The email often just says “see attached.” The attachment is the document you actually want.

10. Asking for “the contract”

Weak: “The contract with the developer.”

Better: “All executed agreements between [public body] and [company or LLC] concerning [project or address], including amendments, exhibits, side letters, memoranda of understanding and nondisclosure or confidentiality agreements.”

Why: Projects rarely run on one contract. The important terms are often in an exhibit, an amendment or a separate confidentiality agreement. And if the developer operates through an LLC, use the LLC’s exact name.

11. Following the money

Weak: “How much has the township spent on this project?”

Better: “Invoices, purchase orders and payment records for legal, engineering or consulting services related to [project], dated [start] to [end].”

Why: Spending leaves a paper trail in specific record types. Legal invoices in particular often show when work on a project began — sometimes long before the public announcement — though descriptions of legal advice may be redacted.

Asking the right agency

12. The wrong office

Weak: Asking the township for the air permit application for a facility’s backup generators.

Better: Checking your state environmental agency’s online permit database first, then sending the request to the agency’s air quality office if it isn’t posted.

Why: A public body only has to search its own records. If the township never received a copy, the honest answer is “no records.” Ask the agency that issues the permit. See Environmental Concerns for who handles what.

13. Environmental records by address

Weak: “All environmental records for the properties on [road name].”

Better: One request per address: “For [street address] (site or facility ID [number], if known), all environmental assessments, sampling reports, cleanup or management plans and correspondence with the property owner.”

Why: Environmental records are filed by property. A road name can cover dozens of sites. Look up the site or facility ID in your state environmental agency’s database first; it makes your request precise. See Doing Your Own Research.

14. Overlooking the other end of the correspondence

Weak: Giving up when an exempt office — such as the Governor’s office or the Legislature — won’t release a letter.

Better: Requesting the same letter from the agency, township or university that received it.

Why: Every letter has two ends. If one end is exempt from FOIA, the other often isn’t.

Federal requests

15. Leaving out your fee category

Weak: A federal request with no mention of fees.

Better: “I am requesting these records as an individual for noncommercial purposes. I request a waiver of all fees because these records concern [project], a proposal affecting [community], and I will share them publicly at [website or forum] to help residents understand the federal government’s role. Please notify me before incurring fees above $[amount].”

Why: Federal fees depend on who you are and why you’re asking. Stating your category and making a specific public-interest case for a fee waiver can save you real money. A vague “please waive fees” usually isn’t enough. See Part 4.

16. Asking for “expedited processing” without a reason

Weak: “Please expedite this request.”

Better: Requesting expedited processing only when there’s a real compelling need, explaining it specifically — including any decision date that makes the records urgent — and certifying the statement as true.

Why: The bar for expedited processing is high. An unsupported request will be denied and won’t speed anything up.

Follow-ups, narrowing and appeals

17. Responding to a big fee estimate

Weak: “This is outrageous. I’m not paying $2,000 for public records.”

Better: “Thank you for the estimate on request [number]. To reduce the cost, I’d like to narrow it to emails sent or received by [two named people] between [shorter date range]. Could you tell me how many pages that would involve and send an updated itemization? I’d also be glad to receive records on a rolling basis.”

Why: The first response ends the conversation; the second keeps it going and usually cuts the cost dramatically. Always narrow in writing, and keep the original request’s number so the clock doesn’t restart.

18. Following up on a missed deadline

Weak: Waiting quietly for weeks after the deadline passes.

Better: “I’m following up on request [number], received [date]. Under [your state’s records law and section], a response was due on [date]. Could you let me know the status and when I can expect the records?”

Why: A polite, dated reminder that cites the deadline is often all it takes. It also creates a written record that you followed up, which matters if you later appeal.

19. Building on what you’ve already found

Weak: Filing the same broad request again after it came back incomplete.

Better: “An email dated [date] from [person], released in response to request [number], refers to ‘the attached site analysis.’ I request a copy of that site analysis and any later versions.”

Why: The best second request is built from the first response. Pointing to a specific reference in a released record makes the document easy to find and very hard to deny exists.

20. Writing an appeal

Weak: “I disagree with your decision. Release everything.”

Better: “Under [your state’s appeal provision], I appeal the partial denial of request [number]. The response withheld [describe] in full under the exemption for internal deliberations, but did not release the factual material those records contain, as the law requires, or explain why the exemption applies to each record. I ask that you release the withheld records, or at minimum their factual portions.”

Why: An appeal has to use the word “appeal” and say why the decision was wrong. The more precisely you tie your objection to what the law requires, the harder it is to deny. See Part 3.

A quick checklist

Before you hit send, check that your request has:

  • a specific type of record, not “all records”;
  • named people or offices;
  • a date range;
  • keywords, addresses or project names;
  • a request for attachments and, where relevant, text messages;
  • neutral wording and only one subject;
  • the right agency; and
  • for federal requests, your fee category and any fee waiver request.

Back to: FOIA Crash Course

Start Here
What is a Data Center?
Just the Facts
Project Links
Who's Who

Recent Posts

  • The Letter That Spoke for Ypsilanti Township
  • Not Yet: What the Regents Are Being Asked to Approve Thursday
  • “LANL Has Made No Commitment of Funds”
  • Four Years of Regents Minutes
  • How the Words Changed

Archives

  • November 2026
  • October 2026
  • September 2026
  • August 2026

Categories

  • Documents & Records
  • Legislation & Advocacy
  • Public Meetings
  • Responses
  • Uncategorized

Privacy Policy • Terms & Acceptable Use

Copyright 2026 — YpsiDatacenter.org. All rights reserved.

Get action alerts

One small, specific task at a time — a call or an email that takes five minutes. Unsubscribe anytime.