A request comes in. Mesa gets to work.

The end-to-end, AI-native public records workflow — collect, redact, respond — grounded in your jurisdiction’s law and ready for the audit trail. Built for your timelines, in days instead of years.

See the workflow

Public records have become the DDoS attack on government. AI is making them costless to send and ten times harder to fulfill. Your team is drowning in the deluge — Mesa pulls them out.

How Mesa works

From request to release, end to end.

Every public records request — FOIA, CPRA, or your state’s analogue — runs through the same six steps. Mesa’s agents carry each one, on the systems your team already uses.

Intake

NextRequest

PRR-2026-0241

Westover Tribune

Lakebridge Ave resurfacing · Q1 2026

Discover

Purview4,184 in scope

SharePoint312 in scope

NextRequest1 thread

Triage

Candidates4,496

After dedup3,820

Threads collapsed2,940

Responsive142

Redact

PDFLakebridge_PreBid_Memo.pdf5

DOCXValley_Paving_Review.docx6

MP4Council_2026-02-17.mp41:48

Review

M. Reyes

Senior Records Analyst

Ready · Due Apr 15

Release

Determination sent · Apr 12

Packet of 142 records published to NextRequest.

Audit log entry written

AI-driven redaction across every modality.

Documents, email, audio, video — one workflow
PDFs, Word docs, CSVs, Outlook and PST mailboxes, body-cam footage, recorded calls. The same playbook applies across every file type, with object tracking on video and time-range redaction on audio.
Talk to it like a colleague
"Redact the figures as trade secrets." "Anything attorney-client privileged in this folder?" The agent reads the playbook, applies the right exemption code, attaches a rationale, and shows its work.
An audit trail by default
Every redaction is tied to a reviewer, a timestamp, and a statutory citation. Every override is captured. The packet that ships is the packet you can defend.

Your statutes and exemptions, intelligently applied.

Mesa playbook editor — § 7927.705 Deliberative process expanded with statute text, controlling case law, AG opinions, and internal policy linked inline.

From statute to redaction
Playbooks encode the actual law — statutes, regulations, AG opinions, internal guidance — not just regex patterns for SSNs. The agent reads the law and reasons from it.
Reasons through the gray areas
Arizona's judicial balancing tests, California's CPRA exemptions, federal FOIA — the agent walks the case law, weighs privacy against public interest, and attaches the controlling citation.
One playbook, every case
Apply a playbook to a single document or an entire folder. Reuse it across teams. Update it once and every reviewer downstream sees the change.

Gather the responsive records, without the spreadsheet.

The agent does the keyword work
Tell Mesa what the request is asking for. The agent searches Outlook, SharePoint, Drive, body-cam archives, agenda systems — and brings back a triaged set, not a raw dump.
Organized for review
Scope flags, reviewer assignment, and a clear audit of every match. The set you hand to your team is already triaged and ready.
Show your work
The agent logs each query, the systems it touched, and the matches it considered, so scope is defensible if a requester challenges it.

Sharper with every case you close.

Mesa playbook telemetry — reviewer agreement trending up over the trailing six quarters, with override rates by exemption and a feed of recent AG opinions.

Learns from your corrections
Every override your team makes feeds back into the playbook as a suggested revision. The agent gets sharper week by week — trained on your office's judgment, not someone else's.
Watches the law for you
Scheduled jobs flag new AG opinions, statutory amendments, and case law that change the redaction posture. The playbook stays current without anyone remembering to update it.
Measurably better, on the record
Per-playbook accuracy, reviewer time, and override rate are tracked over time. Hand the metrics to counsel; cite them in your annual report.

Case study · San Francisco Assessor-Recorder

7.4 million pages, nine staff, one quarter.

San Francisco’s Office of the Assessor-Recorder is using Mesa to clear AB 1466 — California’s mandate to find and redact racially restrictive covenants in every recorded property document. The corpus: 11,650 record books, 7.4 million pages, fewer than 0.4% of which contain covenant language. Other counties have signed mid-seven-figure vendor contracts and budgeted years for the same work.

62 → 9

person-years to person-weeks

128K+

staff hours saved

4 mo

of active work

7 in 10

packets approved with no edits

Compliance & governance

Built for the records you can’t get wrong.

Public records are sensitive on both sides — the personal information you must protect and the public information you must release. Mesa treats both as production-critical.

See the full security posture

Audit trail by default

Every redaction, release, and override is captured to a tamper-evident audit log, exportable on demand.

Never used to train AI

Customer data is contractually prohibited from training any model — ours or any AI vendor's.

Retention and legal holds

Set the retention schedule, place legal holds at the folder or record level, and trust the platform to enforce both consistently across the workflow.

Least-privilege access

SSO, fine-grained roles, and exportable audit logs. Every read is recorded to a tamper-evident trail.

Connectors

Plugs into the systems your records team already runs.

If your stack isn’t here yet, .

Get your team back to the work that matters.

Public records is the heaviest, lowest-leverage burden on agency staff. Mesa carries the mechanical load so your team can spend their judgment where the public actually needs it.

Read the SF case study