📅 Book a 30-min Demo📞 Call/text (571) 293-0242
Government · AI Course · GOV-11

AI for FOIA and Public Records Requests

Use AI agents to log, search, de-duplicate and organize records for FOIA and state public records requests, while records officers make every exemption and release decision.

Last updated:

The Short Answer

AI can speed FOIA and public records responses by logging and acknowledging requests, searching record systems, de-duplicating results and flagging possible exemptions for review, while a records officer makes every withholding decision. ibl.ai runs this on agency infrastructure, on-premise or air-gapped, and you own all the code and the data, so requested records never leave agency control.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.

The full course design is published below — every module, its objectives and hands-on activity, the capstone, and every source it cites.

What is this course about?

Records requests keep rising while staff and statutory deadlines do not move. This course applies AI to the slow parts of a request, intake, search, de-duplication and review preparation, and keeps the legal decisions with records officers: what an agent may flag, what it must never decide, and how to keep a defensible record of review.

Who is this course for?

  • FOIA officers and public records coordinators
  • Agency counsel who review withholdings
  • Records managers
  • Agency IT staff who support search and redaction tools

What do I need before starting?

  • Working knowledge of your agency's records request process
  • Recommended: Records, FOIA, and AI (GOV-5)

What will I be able to do afterwards?

  • Measure where time goes across the request lifecycle
  • Design request intake and routing an agent can run
  • Document a search across record systems that the agency can defend
  • Configure exemption flagging that leaves every decision to a person
  • Keep a review record that supports the release decision

What does each module cover?

1

Where does the time go in a records request?

45 min

Intake, search, review, redaction and release measured against the statutory clock; federal FOIA sets 20 working days for a determination, and state laws differ.

Objectives

  • Map the request lifecycle
  • Measure time by stage
  • Identify the stages AI can shorten

Topics

Request lifecycleStatutory deadlinesBacklog analysisState law variation

Activity. Measure stage times from a sample of closed requests.

2

How do you triage and route an incoming request?

45 min

Logging, acknowledgment, scope clarification and tracks for simple, complex and expedited requests.

Objectives

  • Classify requests by complexity
  • Draft acknowledgment and clarification letters for review
  • Route requests to record custodians

Topics

Intake and loggingScope clarificationProcessing tracksExpedited processing

Activity. Have an agent classify twenty historical requests and compare with the actual handling.

3

How does an agent search across record systems?

45 min

Email, shared drives and case systems, with the search terms and locations documented.

Objectives

  • Translate a request into documented search terms
  • Search across systems with consistent methods
  • Record the search for later review

Topics

Search term designCross-system searchSearch documentationAdequacy of search

Activity. Run and document a search for one historical request.

4

How do you de-duplicate and organize a responsive set?

45 min

Threads, attachments and near-duplicates collapse a set to what a reviewer must read.

Objectives

  • De-duplicate exact and near-duplicate records
  • Group email threads and attachments
  • Order the set for review

Topics

Exact duplicatesNear-duplicatesEmail threadingReview ordering

Activity. De-duplicate a responsive set and measure the reduction.

5

How should an agent flag exemptions without deciding them?

45 min

Flags carry a reason and a passage; the withholding decision, including whether disclosure would cause foreseeable harm, stays with a person.

Objectives

  • Configure exemption flags with stated reasons
  • Measure flag precision and recall
  • Keep every decision with a records officer

Topics

Exemption categoriesFlag reasonsForeseeable harmHuman determination

Activity. Compare agent flags with a records officer's decisions on a closed request.

6

How do you redact and keep a defensible record of review?

45 min

Redaction, withholding logs and an audit trail that supports the release letter and any appeal.

Objectives

  • Apply redactions that cannot be reversed
  • Log every withholding with its basis
  • Keep an audit trail of review

Topics

RedactionWithholding logsAudit trailAppeals

Activity. Produce a withholding log for a reviewed set.

7

How do you communicate with requesters in plain language?

45 min

Status updates, estimated completion dates and proactive disclosure of frequently requested records.

Objectives

  • Draft status updates for review
  • Identify records to publish proactively
  • Write release letters in plain language

Topics

Status communicationEstimated completion datesProactive disclosurePlain language

Activity. Rewrite a release letter in plain language and list five records to publish proactively.

8

Building the request-processing workflow

45 min

The lab: an end-to-end workflow on a closed request, from intake to release package.

Objectives

  • Configure intake, search, de-duplication and flagging
  • Run a review with a records officer
  • Measure time saved against the baseline

Topics

Workflow configurationHuman reviewTime measurementPilot plan

Activity. Process a closed request end to end and compare with the original handling time.

What is the capstone project?

Records request workflow and pilot plan

Design an AI-assisted request workflow for your agency: intake and routing, documented search, de-duplication, exemption flagging with human decisions, a withholding log and requester communications, with a measured baseline.

Deliverable: A workflow design, a processed sample request with its withholding log, and a pilot plan approved by the agency's FOIA officer.

How are learners assessed?

  • Search documentation reviewed for completeness by a records officer
  • Exemption flags compared with human decisions on a closed request
  • Withholding log checked for a stated basis on every entry

What ships with the course?

Facilitator guide

Session-by-session running order, discussion prompts, and the questions that reliably derail a room.

Learner workbook

Exercises, checklists, and the templates each module's activity produces.

Hands-on lab environment

A sandboxed ibl.ai deployment so exercises run against real agents, not screenshots.

Assessment bank

Scenario questions and rubric criteria mapped to each stated learning outcome.

Source bibliography

Every primary regulation and standard cited on this page, linked and dated.

Which AI agents does this course use?

The hands-on modules run against agents already deployable on the ibl.ai platform for government.

Where does the course material come from?

Every module is grounded in primary sources — the regulation, standard, or research itself, not a summary of it. Each was resolved at authoring time.

Delivery notes

Binding guidance for anyone preparing and delivering this course.

  • State public records laws differ in deadlines, exemptions and fees. Deliver module 1 with the learner's own state statute alongside the federal one.
  • Module 5 is the line the course exists to hold: an agent flags, a person decides. Any demonstration that blurs it undermines the course.
  • Use closed requests for every lab. Never run a live request through a pilot before counsel approves the workflow.
  • Coordinate with GOV-5, which covers AI-generated material as records; this course covers AI as a tool for processing requests.

Why run AI training on a platform you own?

You own the course, not a licence to it

Course content, learner data, and the platform run inside your perimeter — you own all the code and the data.

Model-agnostic delivery

Run the course's AI components on any LLM — Claude, GPT, Llama, Gemini, Command — and switch anytime.

No per-seat training licences

Usage-based or self-hosted, so cost tracks actual use rather than headcount.

Deploy anywhere

Cloud, private VPC, on-premise, or fully air-gapped — including for cohorts that cannot use public AI tools.

Frequently asked questions

What does the AI for FOIA and Public Records Requests course cover?

Records requests keep rising while staff and statutory deadlines do not move. This course applies AI to the slow parts of a request, intake, search, de-duplication and review preparation, and keeps the legal decisions with records officers: what an agent may flag, what it must never decide, and how to keep a defensible record of review. It runs 6 hours across 8 modules, at intermediate level, and closes with a capstone: Records request workflow and pilot plan.

Who should take AI for FOIA and Public Records Requests?

It is written for FOIA officers and public records coordinators, Agency counsel who review withholdings, Records managers, Agency IT staff who support search and redaction tools. Prerequisites: Working knowledge of your agency's records request process; Recommended: Records, FOIA, and AI (GOV-5).

Can we run this course on our own infrastructure?

Yes. ibl.ai is model-agnostic and deploy-anywhere — cloud, private VPC, on-premise, or fully air-gapped — and you own all the code and the data. Cohort data, submissions, and any material learners upload stay inside your perimeter, which matters for government teams that cannot send work to a public AI tool.

How do we get access to AI for FOIA and Public Records Requests?

Request access and we will set it up for your cohort — hosted by ibl.ai, or running against your own deployment. Tell us the group size and timing you need, and whether it should run inside your own perimeter.

How much does AI training for government cost on ibl.ai?

There is no per-seat pricing — you pay for usage or self-host and pay only for the infrastructure, so a 5,000-person rollout does not cost 5,000 licences. 1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

Request access to AI for FOIA and Public Records Requests

Tell us about your cohort and we will set it up — hosted by ibl.ai, or running against your own deployment, where you own all the code and the data.