Built for city clerks
The record of everything the city does, kept moving.
Mesa is the records coworker for the clerk’s office. It works a request from intake to release, ties every redaction to the exemption that justifies it, and keeps the code, the ordinances, and the office’s own archive one question away.
Public records law is precise about what goes out, what stays back, and when. The details live in statutes, exemptions, and the published code. Mesa does the reading, the redacting, and the checking in between.
Use cases
How city clerks use Mesa
From records requests to codification audits, the work comes back reviewed, cited, and ready to release.
Mesa can work a records request end to end: import responsive records from Microsoft 365, SharePoint, or Google Drive, triage them by review status, apply the agency's playbook, and hand the file back for approval before anything goes out. The request itself is a folder, holding the request text, the date range, a preparer, and an approver.
Release with confidence
The record has to hold up after it leaves.
Releases and withholdings both get questioned, sometimes long after a request is closed. Mesa is built so each decision carries its reasoning with it.
See the full security postureDefensible on release
Every redaction ties to an exemption code and a rationale, so a withholding decision can be explained months later.
Nothing is overwritten
Redactions and annotations keep their full revision history, and a release is a snapshot of that moment. Revisiting a call next month never changes what already went out.
Access under the office's control
SSO, fine-grained roles, and per-request assignments decide who prepares and who approves.
Never used to train AI
Customer data is contractually prohibited from training any model, whether Caldera's or any AI vendor's.
See Mesa work a real request.
A thirty-minute demo, run on a real request and the agency’s own exemptions. We’ll show what Mesa does with it.