See all Use Cases

Public Records & FOIA Request Agent

Header image

Public Records & FOIA Request Agent

Automates intake, routing and drafting of public records (FOIA/CPRA) responses, so staff spend minutes, not days, on each request.

Public records laws give residents, journalists and businesses the right to request government documents, and they give agencies firm deadlines to respond. For most city clerks and records offices, that work is still manual. Each request has to be read, interpreted, logged, researched and answered, often by a small team that is also handling council support, elections and day-to-day administration. The Public Records & FOIA Request Agent, built on Generate by Iterate.ai, takes on the repetitive parts of that process so staff can focus on review and judgment.

At a glance

  • Best for: City clerks and records offices
  • Problem: Hundreds of records requests a year, tracked and answered by hand
  • Outcome: Average drafting time cut from 4–6 hours to about 30 minutes per request

The challenge

Staff manually track, sort and respond to hundreds of public records requests a year. Requests arrive in different formats and levels of detail. Some are narrow and easy to fulfill; others are broad, vague or touch several departments at once. Before a single record is pulled, someone has to work out what is actually being asked for and who holds it.

Delays cause compliance violations and frustrate residents. When a request sits in a queue, the agency risks missing its statutory response window, and residents lose confidence that their government is transparent and responsive.

  • Requests must be read and interpreted one at a time
  • Research means searching policies and past responses by hand
  • Routing to the right department depends on staff knowledge
  • Drafting each reply can take 4–6 hours

How the agent works

The agent handles a request from intake to draft in a single step, with staff review built in before anything is sent.

  1. Ingest. The agent reads the incoming request and identifies what records are sought, producing a short summary staff can scan at a glance.
  2. Research. It searches the agency's policy documents and prior responses to find relevant guidance and precedent.
  3. Draft or route. It drafts a compliant reply, or routes the request to the right department with a summary of what is needed.
  4. Staff review. Staff check the draft, make any edits and send it on time.

Key capabilities

  • Instant intake: Every request is summarized as soon as it arrives, so staff know what is being asked without reading it line by line.
  • Grounded research: Answers are based on the agency's own policy documents and prior responses.
  • Compliant drafts: The agent prepares a reply ready for staff review.
  • Smart routing: Requests that need records from another department are sent there with a summary attached.
  • One prompt: Intake, research and drafting happen in a single step.

Example scenario

A records office receives a request for all correspondence about a recent road resurfacing project. The agent summarizes the request, finds the agency's policy on correspondence records and a similar response from the previous year, and identifies Public Works as the department that holds the records. It routes the request to Public Works with a summary, and drafts an acknowledgment letter for the clerk. The clerk reviews the letter, adjusts the expected timeline and sends it the same morning.

Estimated impact

For an office handling around 300 requests a year, reducing drafting time from hours to minutes returns a significant amount of staff capacity.

  • 4–6 hrs → 30 min average drafting time per request
  • ≈ 1,500 hrs of staff time saved a year at 300 requests
  • 1 prompt from intake to draft or routing

Impact figures are estimates. Validate with your agency's own data.

Why Generate

Records requests often include residents’ personal information and documents that are not yet public. Generate keeps that material inside your agency’s environment while the agent reads, researches and drafts.

  • Private by design: Runs on-premise or in a cloud VPC, with zero data egress by design.
  • Works with your existing data: 55+ third-party connectors, 8 database integrations and direct support for enterprise files, with no data migration required.
  • Fast to deploy: Turnkey deployment in under 20 minutes, and agents spun up from templates in about 3 minutes.
  • Governed: Security capsules sandbox every session, with centralized policy enforcement and immutable audit trails.
  • Predictable costs: Inference runs on infrastructure you control, with no per-token cloud charges.

Who benefits

  • City clerks: Meet response deadlines with less manual effort.
  • Records staff: Spend time on review and judgment instead of searching and formatting.
  • Department staff: Receive routed requests with a clear summary of what is needed.
  • Residents: Get timely, consistent responses to their requests.

Frequently asked questions

Does the agent send responses on its own?

No. The agent drafts or routes each request, and staff review every draft before it is sent.

What information does the agent use?

It uses the agency's own policy documents and prior responses, so drafts reflect local rules and past practice.

Answer records requests in minutes, not days. Schedule a demo or try Generate for free.

‍