Home › Insights › Handling a Public Records Request That Returns 50,000 Emails

Handling a Public Records Request That Returns 50,000 Emails

A small municipal records office at night, a single desk lamp casting warm light across a large monitor filled with dense email threads, with a laptop open beside it

Quick Answer

Treat a 50,000-email return as a sorting job first. Remove duplicates, group near-duplicates, let AI code the rest by exemption with a source link on every call, and have a person decide each exemption.

Reading comes last. Less of it, too. Legal checks first for what falls under the exclusions. Then batches go out, each one traceable, while the hardest emails wait for someone willing to sign for them.

Did this answer your question?

Key Points

  • Federal FOIA requests topped 1.5 million in 2024 , and Sunshine Week organizers found just 12.1% of processed requests were granted in full in fiscal 2024.
  • The National Archives' OGIS credited U.S. Customs and Border Protection with cutting its FOIA backlog 74 percent , from 34,307 requests to 9,024, in FY 2015 by sorting at intake.
  • Under North Carolina's G.S. 132-6(c), commingled confidential information is no ground for denial, and the agency bears the cost of separating it.
Three things records officers believe. Myth or fact?
Call each one, then see how other readers called it.
1 Buying FOIA software will clear a backlog of large email requests.
2 Work on a records request usually starts with legal, not with reading.
3 Some emails a town cannot release, even if it wants to.
A small municipal records office at night, a single desk lamp casting warm light across a large monitor filled with dense email threads, with a laptop open beside it

Fifty thousand emails, one desk, and the exemption calls still waiting.

Fifty thousand emails looks like a reading job. It isn't, not at first. It is a scoping job first: ask which mailboxes, which date range and which search terms produced that number, because the count alone says nothing about what the search caught or missed.

And the pile does not just go away. Under the Florida Attorney General's reading of state law, email that counts as a public record may be disposed of only under retention schedules set by the Division of Library and Information Services. Until a schedule says otherwise, it stays. It has to be handled.

The people holding the pile are often small. A records clerk with no IT department down the hall. A solo litigator staring at thousands of emails and chats, priced out of enterprise review platforms and unable to spend weeks on manual attorney review. Two sides of the same counter. One question: how do you get through it without missing the one email that matters?

I wrote this for that person. Below, I walk through:

  • how removing duplicates and near-duplicates shrinks the set before review starts
  • how AI issue-coding sorts what remains by exemption category, with every answer tied back to its source document
  • where a person has to make the call, and why no tool takes that call away

Then the harder part. Batches. Formats. Fees. And the emails that were never kept at all, the ones no review, fast or slow, can bring back.

Fifty thousand emails came back. Nobody reads that in time. Not really. The work is to shrink the pile, sort what is left by exemption, and put a person on the hard calls.

The pressure keeps building. Federal FOIA requests topped 1.5 million in 2024, and in fiscal 2024 just 12.1% of processed requests were fully granted. Partial release is the normal outcome now. Redaction is the job.

Redaction is where the fear sits, too. In a 2025 r/sysadmin thread, a records administrator described a single request holding "hundreds of mixed files: scanned PDFs, emails, attachments, spreadsheets, reports and random image formats," and a process that came down to "throw it in Adobe and hope for the best." A commenter answered flatly: "No product actually does this with better success than a human."

I think that commenter is right about the hard calls, and I think it still misses where the hours go. The human was never the problem. The pile is the problem, and some of that pile may already be gone, lawfully, under the retention schedules that decide how long public email has to be kept.

So the first question is not what the emails say. It is how many of them are really there.

Why is a 50,000-email records request not a reading problem?

AI-assisted review runs cents per document, against dollars per document and roughly $19K per gigabyte for manual review. Reading every email is the expensive path. And the slow one.

Before anyone opens the first message, do three things, in this order:

  1. Shrink the set. Remove exact copies, group near-copies, and collapse each thread so a conversation is read once.
  2. Sort what is left. Code each email against the exemption categories your statute names, with the source email attached to every code.
  3. Put people on the hard calls. Send only the flagged, possibly exempt messages to a human reviewer, and release the rest as it clears.

Fifty thousand emails. It sounds like a reading job. It is not.

The common assumption is that a big return means a big stack and a long night, somebody at a desk under one lamp, reading, still reading. Most of that stack is the same email again. A reply. A forward. The same attachment sent to six people and kept six times. A near-duplicate is just that: an email that differs from another only a little, like a reply that quotes the whole message above it.

The North Carolina Press Association, in its 2023 guidance, described where the real delay sat. In one multi-year email request to a school board, an antiquated email system and confidential student and personnel information held everything back. Amanda Martin wrote the outcome plainly: "The compromise was that we received records in batches, as they were cleared of confidential information."

The bottleneck was never the reading. It was the clearing.

A review of 4 sources, from press-group guidance to our own platform notes, points the same way. The work that eats the calendar is deciding what must stay dark, message by message, and proving later that you decided it right. In our review pipeline, originals stay immutable, every file carries a content hash, and each step lands in an append-only audit trail. That matters more than it sounds. When you set a duplicate aside, somebody may ask you to prove it really was one.

Relevant pairs that defensible spine (Bates numbering, privilege handling, chain of custody) with RAG intelligence, meaning cited answers drawn from the documents themselves, in one tool. I would not let anyone open message one until the set has been shrunk and sorted. Reading first is how a records office loses a month and gains nothing.

If a statutory clock is already running, the queue math in meeting a FOIA deadline on a 20,000-record request shows how the deadline and the pile fit together. So the first question is not how fast you can read. It is how much of the pile is really there, and how much is just the same thing, again and again, all over the inbox.

What can software sort in a big email request, and what must a person decide?

Americans filed more than 1.5 million federal records requests in 2024. Only a sliver came back whole, and that sliver shows where the real labor in a big email request sits.

In fiscal 2024, just 12.1% of processed federal FOIA requests were granted in full, according to a March 2026 analysis by Sunshine Week organizers published in Utah News Dispatch. Most requests that reached substantive review were released only in part, often heavily redacted. Each partial release rests on exemption calls: decisions, record by record, about what the public may see.

The same analysis reports a warning from the National Archives' Chief Records Officer: AI is no substitute for a "professional's judgement on application of exemptions and foreseeable harm." People who handle redaction say much the same. In a December 2025 forum thread for systems administrators, one commenter wrote that honest redaction tools "only claim to be layers in a multi-step redaction and Data Loss Prevention strategy that always includes human review." Those are single voices on a forum, but they match the Archives' warning. We build AI review software, and we agree that the exemption call belongs to a person.

Making the call well is harder than it looks, because the rule governing a record often sits outside the records law, and mistakes run in both directions.

The errorHow it happensAn example from our sources
Releasing a record that should stay closedStaff read only the Public Records Act and miss confidentiality rules in other statutesIn North Carolina, personnel file confidentiality sits in Chapter 160A, and education statutes make parts of K-12 student records confidential (North Carolina League of Municipalities podcast, 2026)
Withholding a record that is publicA federal privacy law is applied to records it does not coverUNC cited FERPA to deny access to football players' parking tickets. A court ruled they were not education records, and UNC released them and paid substantial attorney fees (North Carolina Press Association)

When a requester sues, the League podcast speaker added, the city carries the burden of proving a record is not public. North Carolina's statute also decides who pays for the sorting. Under G.S. 132-6(c), no request "shall be denied on the grounds that confidential information is commingled with the requested nonconfidential information," and where separation is necessary, "the public agency shall bear the cost of such separation."

Other costs come from choices made before anyone reads a word. Amanda Martin, writing for the North Carolina Press Association, reports that in 2022 litigation one town converted requested emails into PDFs and tried to charge $10,000 for it. Her advice to requesters is to ask for .pst format, which means "you eliminate the conversion step," keeps attachments attached and leaves the records searchable. Unless attachments are requested by name, she warns, agencies "will blow right by and not produce them."

Where volume has actually dropped, early sorting did much of the work. The National Archives' FOIA ombudsman office audited U.S. Customs and Border Protection and credited its fiscal 2015 turnaround to a second-day triage system, shifted resources, separate tracks for simple and complex requests, and a shared case-management platform. Auditors also told the agency to keep checking for duplicate requests during triage.

Backlog before the changes 34,307 requests
Backlog after fiscal 2015 9,024 requests
A 74% cut after sorting at intake. FOIA backlog at U.S. Customs and Border Protection in fiscal 2015, from the National Archives' Office of Government Information Services compliance assessment dated March 2016.

The comparison has limits. CBP sorted whole requests rather than emails inside one request, its quick track handled traveler records that made up 80 to 90 percent of volume, and the audit reports no similar gain for complex requests. The idea still works inside a single request. Martin describes a multi-year email request to a school board, slowed by an antiquated email system and by confidential student and personnel information: "The compromise was that we received records in batches, as they were cleared of confidential information."

Across these sources, the work in a large email request gathers at two points. One is processing before review: format, duplicates, queues and batches, mechanical work that software can take on. The other is the exemption call at the end, where an error in either direction can lead to court. A person should make that call, and the agency should record each decision so it can defend it later.

  • Put a named reviewer on every exemption decision, and record who made each call and on what statutory ground.
  • Check each proposed exemption against confidentiality rules outside the main records law, such as personnel and student-record statutes, and confirm a federal law like FERPA actually covers the record before relying on it.
  • In North Carolina, budget for separating confidential from public material as the agency's own cost. Elsewhere, ask counsel how your state's law assigns that cost.
  • Settle the production format before review starts. If the requester will take .pst, ask what PDF conversion would add besides time and expense, and confirm attachments are included.
  • Triage the set early and release cleared emails in batches instead of holding everything until the last exemption call.

How we checked this

We drew on a Sunshine Week analysis of federal FOIA data, a National Archives audit, North Carolina's records statute, a press association guide, a municipal league podcast and a systems administrators' forum thread. No figures in this section come from us. The 12.1% figure covers federal requests and may not reflect state or local email requests. The CBP results describe sorting of whole requests, with gains reported on the simple track. The forum comments and the UNC and school-board cases are individual accounts and cannot establish a pattern. The cost rule we cite is North Carolina's. We sell AI review software for document-heavy matters, so we have a stake in how this work gets divided. Still unknown: how accurately any software, ours included, flags exemption candidates in public records email. None of our sources measured that.

  1. Sunshine Week organizers, analysis of rising records requests in Utah News Dispatch, March 17, 2026.
  2. Amanda Martin, North Carolina Press Association, best practices for public records requests, January 31, 2023.
  3. North Carolina League of Municipalities, Municipal Equation podcast on public records law, February 26, 2026.
  4. North Carolina General Statutes, G.S. 132-6 on inspection and copies, retrieved November 14, 2026.
  5. Office of Government Information Services, National Archives, CBP FOIA compliance assessment, report dated March 9, 2016.
  6. r/sysadmin, forum thread on automated FOIA redaction, December 17, 2025.

What breaks when you rush a big email request against the clock?

Speed without a source trail is the trap. Every AI answer should link back to the exact document it came from, so a reviewer can verify it in one click.

Outlier Media's 2026 guide to FOIA shows how short the window can be. In Michigan, coordinators must answer within five business days. They can grant the request, grant part of it with a written explanation, deny it, or extend by up to 10 additional days. Silence counts too. No answer at all is a "constructive denial."

Five days. Fifty thousand emails. The arithmetic does not work, and everybody in the records office knows it, and nobody says it.

So two bad habits creep in, quietly, the way they always do:

  • Black out everything. Agencies may redact for privacy and other reasons, the guide notes, "but some agencies get overzealous about it." Over-redaction feels safe. It is not. It invites the appeal.
  • Trust the machine blind. A tool that hands back a confident list with no trail is worse than slow. Nobody can check it. Nobody can stand behind it later.

Money pulls the same way. In 2009, the Michigan State Police billed the Mackinac Center for Public Policy almost $7 million for a single FOIA request, and the guide puts the range bluntly: "Costs may range from zero to millions of dollars." When the clock is short and the bill is long, shortcuts start to look like policy.

Contrary to the usual pitch, faster is not the same as safer. Faster with a source trail is. In our platform, every output links back to the exact document it came from, so the person signing the response can verify each call before it goes out. That one design choice changes what a deadline does to you. The pressure is still there. The guessing is gone.

I would not ask anyone to take that on faith. Our standing offer is plain: bring a messy collection and a hard question, then watch the tool read, code and cite your own evidence, not a case study about somebody else's. And the emails do not have to wander. Relevant can run inside your own AWS account under your own keys, which matters when the set is thick with personnel files and student records.

Ask one more thing before you commit. If an AI review vendor can swap models mid-matter, the coding you relied on in week one may not be the coding you can reproduce in week six, and a records response you cannot reproduce is a hard one to defend on appeal.

Under all of it sits a quieter question, the one nobody asks out loud at five o'clock on day four. Which of these emails were public records in the first place?

Which emails count as public records, and what do you sort first?

Sort before you read, and keep the set under your own control: single-tenant processing, no vendor retention, no model training, so nothing in those emails trains anyone's model or waives privilege.

Florida's Attorney General put the first rule plainly in a 2007 informal opinion. Emails "made or received by agency employees in connection with official business" are public records, open to disclosure unless an exemption applies. Electronic format changes nothing. But the Florida Supreme Court drew a line in State v. City of Clearwater (2003): private email stored on government computers does not automatically become a public record just because it sits there.

So the pile is not one pile. Some of it was never public at all.

Sorting works at scale. The National Archives' FOIA ombudsman, OGIS, showed how. In FY 2015, Customs and Border Protection cut its FOIA backlog by 74 percent, from 34,307 requests to 9,024, even as daily volume rose. The fixes were not heroic reading. They were a second-day triage system, a multi-track queue that put routine traveler-record requests on a simple track, and a check for duplicate requests during triage.

Conventional wisdom says a buried records office needs more readers. The CBP numbers point somewhere else. Order first. Readers second.

Inside one 50,000-email return, I would sort in three passes:

  1. Separate official business from private mail. Flag messages with no tie to the agency's work, so a person can confirm they fall outside the request rather than review them line by line.
  2. Pull duplicates at intake. Exact copies come out before review, the same way CBP caught repeat requests at the front door.
  3. Split a simple track from a complex one. Plainly releasable messages move out in early batches. Anything touching an exemption category waits for a person.

I care about this because the people staring at a 50,000-email return are rarely big agencies with an administrator down the hall. More often it is a small office, or a small firm on one side of the request, with one messy matter and no spare month. Our platform was built to be operable and affordable for exactly that solo or small-firm case, the segment enterprise platforms price out and cannot serve without an administrator.

If you come to this from litigation, the differences are worth a careful look in how the ESI workflow differs between FOIA requests and civil discovery, because the habits that serve a production do not always serve a records release.

Then comes the part no triage queue can do for you. Somebody has to ask what the collection never touched. Scotty Leamon, the public information officer for Florida's Coconut Creek Police Department, told The PIO Podcast in 2024 that posts in private neighborhood Facebook groups may not be captured by social media archiving vendors, even though records have to be kept.

Close-up photo of a reviewer's hands at a desk in soft warm lamp light, one hand resting on a computer mouse, the other holding a pen mid-air
Group the near-copies first. One exemption call can cover the whole thread.

Fifty thousand emails, and one wrong release?

On the North Carolina League of Municipalities podcast, a guest warned that well-meaning officials read only the Public Records Act and miss confidentiality rules written elsewhere. One miss is enough. Relevant e-Discovery dedups, codes and cites your set against the exemptions that apply, so confidential material waits for a person before any batch goes out.

What should you do before the next 50,000 emails arrive?

Name who answers records requests, and who covers for them. Map every place your office's email lives, including archives and retired systems. Ask which of those places your search tools actually reach.

And know what speed cannot buy. On the MAGAMind Podcast in 2025, a requester described asking Maricopa County for emails reaching back years and being told they "only go back to twenty twenty." Another guest listed what the group kept running into: "denials, price gouging. These records don't exist."

No review pipeline brings back mail a retention schedule already let go. Nothing does.

So my view is narrower than the vendor pitch and harder than the old habit. Faster review will not make full grants common again; they are already the exception. What it can do is get every surviving email in front of the right person sooner, with the exemption question already framed and the source one click away. The pile shrinks. Not every decision leaves a message behind. So train the people who will answer the next request now. Scotty Leamon, a police public information officer in Coconut Creek, Florida, called knowing public records requests, including how much time you have to respond, one of the most important starting skills for the job.

Summarize This Article With AI

Open this article in your preferred AI engine for an instant summary.

Frequently Asked Questions

What else do people ask about a 50,000-email records request?

Most follow-up questions circle the same three things: what a machine can sort, what a person must decide, and what was never there to find.

Can AI redact a public records email set on its own?

No. It can flag likely PII, addresses and case numbers across thousands of messages. People who run records offices still say no tool beats a human on the final call, and I agree with them. The machine finds. The person signs.

What is a near-duplicate email?

A near-duplicate is a message that is almost, but not exactly, the same as another one: a reply that quotes the whole thread, a forward with one line added. Grouping them means one exemption decision covers the group.

Should I redact a passage or withhold the whole email?

Redact when only part is protected. Exempt records may be held back. Confidential records must be. If the call is challenged in court, the burden sits with the city, not the requester.

Who should touch a large request first?

Legal. A commenter in a 2025 r/sysadmin thread described each FOIA request as a project that starts with legal checking nothing requested is on the list of exclusions, and added: "If you can't manage the workload, hire appropriately."

What if the emails I asked for no longer exist?

Ask which retention schedule applies. In some states, public-record email may be disposed of only under an approved schedule. Gone is not always wrong. It still has to be shown.

Written by

Michael

Kansky

Michael Kansky is a serial software entrepreneur who has spent more than two decades building and bootstrapping profitable SaaS and services companies.

Connect on LinkedIn

Read next

A lone attorney sits at a plain wooden desk in a quiet law office at dusk, leaning back in her chair with a pen in hand and a thoughtful, focused expressionEdiscovery

AI First-Pass Review vs a 5-Person Review Team

An AI first pass checked by one attorney can match a five-person team's recall on a mid-size matter in far fewer hours, if sampling proves it. Privilege is different.November 16, 202622 min read
Laptop showing native email and spreadsheet files next to a stack of printed TIFF page images on a small law firm conference tableEdiscovery

Native Production Isn't the Risk the Playbook Says It Is

Native production is usually the cheaper, safer choice once a Rule 502(d) order and a protective order are in place. Most native risks are process failures, and a privilege review catches them.November 15, 202621 min read
Two printed keyword hit reports with differing counts laid side by side on a law office conference table before a meet-and-conferEdiscovery

Hit Counts Don't Match? Run a 5-Point Search Equivalence Test

Two hit counts can be compared only when five settings match: what counts as a hit, family expansion, deduplication scope, tokenization and stemming, and the index and OCR state behind the search.November 15, 202621 min read

See it on your matter

Bring us a messy collection - mailboxes, scans, phones, recordings - and watch it become one searchable, defensible record.