Built for records & discovery units
Footage, audio, and reports, released right.
Mesa is the records coworker for records and discovery units. It assembles the incident file, transcribes and screens every record, ties each redaction to the exemption that justifies it, and keeps the deadlines that govern release one question away.
Mesa can watch the footage, listen to the audio, and read the file in one review. Each redaction it proposes carries the exemption and rationale behind it. The release is documented as it is built.
Use cases
How records units use Mesa
From intake to release, the work comes back screened, redacted, and cited.
Mesa can work an incident request from the portal to the release package. It reads the request as filed, assembles camera clips and dispatch audio alongside reports imported from where they live, transcribes and OCRs everything on arrival, and triages each record by review status before handing the file to a supervisor for approval.
Release with confidence
The release has to hold up after it leaves.
A records unit is answerable for what went out and for what was held back. Mesa is built so both decisions carry their reasoning with them, long after the request is closed.
See the full security postureDefensible on release
Every redaction and every full withholding ties to an exemption code and a rationale, so the decision can be explained months later.
Exports are snapshots
A release is an immutable copy with checksums. Revisiting a redaction next month never changes what already went out.
Access under the unit'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 incident.
A thirty-minute demo, run on real footage and the agency’s own exemptions. We’ll show what Mesa does with them.