By · Last updated 2026-05-23

Back to BlogTechnical

FOIA: 80% Faster with Batch Redaction

US federal agencies received 1.5 million FOIA requests in FY2024 at an average cost of $482 per request. Batch PII redaction reduces processing time from.

May 23, 20269 minute read
FOIA redactiongovernment recordsbatch processingpublic recordsdocument redaction

How Agencies Cut FOIA Processing Time by 80% with Batch Redaction

Updated for 2026

US federal agencies got 1.5 million FOIA requests in FY2024. That is 25% more than FY2023. The DOJ backlog passed 100,000 open requests. The average cost per request was $482. Large requests can cost far more — sometimes hundreds of thousands of dollars.

Manual redaction drives that cost. A lawyer or paralegal spends 30–45 minutes per document. That is the bottleneck. Automation breaks it. See our compliance overview for how anonym.legal supports public records work.

The Public Records Redaction Problem

Agencies must redact exempt information before releasing records. Two main exemptions cover most personal data.

Exemption 6 protects personnel and medical files. It covers names, home addresses, personal emails, phone numbers, and personal IDs.

Exemption 7(C) protects law enforcement records. It covers officers' details, witnesses, informants, and investigation subjects.

Exemption 6 drives most routine redactions. Every name, address, phone, or email of a private person must be checked. That check runs on every document in the request.

Manual Process Costs

A county gets a request for 2,500 email records from a city council review.

Per-document steps:

  • Read the document: 5–10 minutes
  • Find PII under Exemption 6: 3–5 minutes
  • Redact each item: 5–15 minutes
  • Log the decisions: 2–3 minutes

Total per document: 15–33 minutes. For 2,500 documents: 625–1,375 staff hours. At $80–200 per hour, labor runs $50,000–275,000.

Five reviewers at eight hours a day need 16–34 weeks. That is 4–8 months for one request.

This is why agency backlogs exist. It is not indifference. It is a resource gap. Manual review has no other speed. There is no way to go faster without changing the process.

The Automated Redaction Workflow

Batch PII redaction changes the math. The process has three clear phases.

Phase 1: Automated Redaction

Upload all 2,500 documents. Apply an Exemption 6 preset. Set it to flag:

  • Personal names (PERSON entity type)
  • Home addresses (LOCATION)
  • Personal emails (EMAIL_ADDRESS)
  • Personal phone numbers (PHONE_NUMBER)
  • Social security numbers (US_SSN)
  • Medical record numbers (MEDICAL_RECORD)
  • Date of birth (DATE_OF_BIRTH)

2,500 standard emails finish in 3–6 hours. Run the batch overnight and results are ready by morning. See our entities page for all entity types.

Phase 2: Exception Review

Automated redaction is not perfect. Context matters. "John Smith" the council member is a public official. He may not need redaction. "John Smith" the private citizen who wrote in is protected.

The legal team reviews the automated output — not the raw documents. They check:

  • Files where redaction may be too broad or too narrow
  • Records near law enforcement (Exemption 7)
  • Privilege issues (Exemptions 4–5)

About 10–15% of documents need attorney review. That is 250–375 files at 20 minutes each. Total: 83–125 attorney hours.

Phase 3: Production

Review the final documents. Release the response package.

Time and Cost Comparison

ManualAutomated + review
Timeline4–8 months2–4 weeks
Labor cost$50,000–275,000$5,000–25,000
Tool costNoneBatch token pricing

The 80% cost cut is real for large responses where Exemption 6 is the main task. It may be less for smaller or simpler requests. See our pricing page for batch tiers.

Preset Configuration

A standard Exemption 6 preset uses these entity types.

Include: PERSON, EMAIL_ADDRESS, PHONE_NUMBER, LOCATION, US_SSN, MEDICAL_RECORD, DATE_OF_BIRTH

Exclude or flag: official government emails, office phone numbers, names of officials in their official role

Redaction method: a black bar matches the standard appearance. [REDACTED - Exemption 6] text also documents the rule applied.

Consistency rule: use the same config on every document in the batch. Redacting a name in one file but not another creates legal risk. It can force you to reprocess the whole set.

State and Local Laws

California CPRA, New Jersey OPRA, and similar state laws create the same needs. State deadlines are often tighter. California gives agencies 10 days. Federal law gives 20 days.

Small governments have fewer resources. A county with two to five lawyers cannot absorb 1,375 hours for one records request. Batch redaction makes compliance possible at all. Our security and compliance page covers data handling for local governments.

Batch redaction creates a clear record. It logs the entity types used, the documents processed, and the time of each run. You get a full trail for every batch.

When a requester challenges a redaction before OGIS or in court, a clear process is easier to defend than manual notes. See our FAQ for questions about audit log rules.

Conclusion

The DOJ backlog is 100,000 requests waiting for attorney time that has not arrived. Batch redaction does not remove legal work. It removes the mechanical part. That is the part where staff scan thousands of pages for names and addresses. Legal judgment stays with humans.

Moving attorney effort from mechanical to analytical tasks cuts backlogs. It raises consistency and lowers costs at every level of government.

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.