By · Last updated 2026-04-09

Back to BlogLegal Tech

FOIA Backlog: Automated Gov Redaction

US FOIA requests hit 1.5 million in FY2024 — a 25% increase. Backlogs grew 33% to 267,056 pending requests. The government spent $723 million processing.

April 9, 20268 minute read
FOIA automationgovernment document redactionpublic records compliancebatch Word processingfederal agency efficiency

The Federal FOIA Backlog Crisis

US federal agencies got 1.5 million FOIA requests in FY2024 — up 25% from the year before. Pending backlogs grew 33% to 267,056 requests. Agencies spent an estimated $723 million to handle them.

That shows a capacity gap. About 5,638 FOIA staff work across all federal agencies. With 1.5 million requests per year, each person handles roughly 266 requests annually. That is just over one per working day. There is no slack for large, complex requests. There is no buffer for 33% backlog growth. Staff cuts at many agencies are making it worse.

Why Each Request Takes So Long

Most federal documents are Word files. Legal memos, policy decisions, and correspondence all live in Word. Staff must read each page. They must apply each exemption. Then they must check their work before release.

Exemption 6 alone covers names, addresses, Social Security numbers, and birth dates. A single 50-page file may have dozens of data points that each need a separate review call. Multiply that by thousands of documents and the processing time becomes structural — not a one-off problem.

Fewer staff, same volume. The backlog math does not improve on its own.

What Automation Changes

The ATF — Bureau of Alcohol, Tobacco, Firearms and Explosives — credited automated redaction tools with 20–30% productivity gains in their processing workflow. That is a real result. And it likely understates the gain for agencies still on fully manual review.

An automated pass through a document is fast. The system finds names, ID numbers, and other covered data. It flags each one. Staff then check flagged items instead of reading every line. The scan takes seconds. Human time shifts to judgment calls — where it adds real value.

For a batch request of 8,000 documents related to a policy decision, that shift is the difference between feasible and impossible on normal staffing levels.

Matching the Right Tool to the Job

Government FOIA work has clear needs. Documents must stay in Word format. Formatting must survive the process. Tracked changes, footnotes, and embedded objects must all come through intact. A corrupted file gives requestors grounds for a challenge.

Large requests need batch capability. Running hundreds of documents per pass is the floor, not the ceiling. And staff across an agency must apply the same exemption rules every time — which means shared, locked preset configurations.

Preset-based redaction workflows do exactly this. One preset covers names, addresses, and Social Security numbers under Exemption 6. Another covers deliberative material under Exemption 5. Staff pick the right preset and review results — instead of making each category call from scratch on every document. For the broader compliance picture, see the security and compliance overview.

The ATF result shows what this looks like in practice. Twenty to thirty percent more output from the same team. That kind of gain matters when request volume rises 25% per year and staffing does not keep up.

The backlog will not fix itself. The tools to slow it down are available now.

Sources

Ready to protect your data?

Start anonymizing PII with 285+ entity types across 48 languages.

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.