The Records Request Agent
Agents

The Records Request Agent

Skip to main content
Table of Contents
< All Topics
Print

The Records Request Agent

Last updated: November 20, 2026

Public-records work produces paper: letters, deadlines, follow-ups and page after page of released documents. The records request agent handles that paper. It drafts the requests, tracks the clock and logs what comes back. It never sends anything. A human always files.

What it is

The records request agent (records-request-agent) is an AI agent with a written job description. It mirrors two roles in a newsroom or committee office: the counsel who handles a document request, and the records clerk who keeps the log. It drafts, it tracks and it logs. It does not file.

Background on the laws it works under is in FOIA and Sunshine Laws.

When it runs

A human dispatches it on demand. A reporter needs a federal FOIA request, a state public-records request or an appeal drafted, a request’s deadlines tracked, or pages that arrived logged against their control numbers. The oversight investigation agent may recommend this agent in a handoff note, but it cannot start it. See The Oversight Investigation Pipeline Agent.

What it does

  1. Drafts. From the facts in its brief (subject, agency, date range, custodians, search terms) it writes a request or an appeal, using the structure and templates of our records-request drafting method. It never invents a fact, custodian or statute citation that it was not given or did not confirm through research.
  2. Tracks. It keeps one request tracker, a CSV in its run directory. For each request it computes the statutory deadline, any extended deadline, tolled days, the date a request is treated as constructively denied, and the appeal deadline. For a state request it uses that state’s clock only from a confirmed row in our quick-reference table or from the statute itself, checked through the research gateway. If neither is available it leaves the deadline blank and flags it. It never fills a state clock from memory.
  3. Logs. When the brief reports pages received, it adds a row to a production log, with a control-number range (one number per page) and the producer’s own page numbers beside it.
  4. Flags for counsel. It applies the “call counsel when” list in the litigation section of FOIA and Sunshine Laws: a clock that has run out on a central request, an appeal denied on a record that is not exempt, records at risk of being lost, a large security or law-enforcement withholding, or an outside deadline. When one fires, it writes a plain note naming the trigger and the tracker row. It stops there. It never decides to litigate and never contacts a lawyer.

Every letter it produces ends with a note telling the requester what to check before signing and sending it themselves.

Research

The agent researches only through our one research gateway, scripts/ca_research.py, after setting a budget. It uses search to find the custodian office and prior releases, extraction on logs it will cite, and a named data client only if that client actually exists. If a data client is unknown, it stops that line of research and records it as a finding. A refused request or a rate limit is also a finding, not an obstacle.

Skills it applies

  • FOIA and Sunshine Laws, published: strategy, routing a request to the right component, deadlines, reading withholdings, appeals and when to call counsel.
  • Two internal working skills, described in words only: one sets the structure of request and appeal letters, the tracker format and the follow-up scripts; the other sets our control-number format and the production-log format.

If any of these three skills is missing, the agent does not draft a request, compute a deadline or assign a control number from memory. It reports which file is missing and stops. We treat that as correct behavior.

Rules and gates it obeys

The agent works under the sourcing rules in Evidence, Sourcing and Language Rules and the runtime limits in AI and Research Runtime Guardrails. Anything it writes toward a knowledgebase draft is subject to Draft Checks and Human Review. In practice its main rule is the one every letter ends with: a human checks it, signs it and sends it.

What it may never do

  • File, submit, email or otherwise contact an agency on the requester’s behalf. It never represents itself as filing for the publication.
  • Write into the knowledgebase outside _drafts/, or write a knowledgebase document at all unless the brief explicitly asks for one.
  • Fabricate a custodian, date, statute citation or control number.
  • Print, log or copy a key value.
  • Commit, push, merge or publish anything.

Where a human decides

A human reads each draft, corrects it, signs it and files it. A human decides whether a litigation flag leads anywhere. The agent’s results file lists what it drafted or logged, any referral flag and any open question. A missing results file is a failed step.

Team persona

The role it mirrors is presented on the team page Ines Tavares — Records & FOIA Specialist. For the other agents in the investigation desk, see Agents and Automation: The AI That Works Here, and Its Limits.

Factual correction requests: If you believe information in this page is incorrect, please contact factcheck@citizenanalyst.ai with your name (optional), the specific claim, and any supporting documentation. We review all submissions and correct verified errors promptly.

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
Please Share Your Feedback
How Can We Improve This Article?