Home / Redaction for Axon agencies
Keep Evidence.com. Change How You Redact.
Your body-worn cameras work. Your evidence system works. The redaction is what does not scale, and replacing a whole DEMS to fix one step is a disproportionate answer.
The Situation
An agency on Axon has the camera fleet, the storage and the chain of custody already solved. What arrives at the records unit is a public-records request, and the redaction tooling bundled with the evidence system was designed for occasional use rather than for a backlog.
Two things then happen. Frame-by-frame work becomes the bottleneck, and the formats outside body-worn video — police reports, scene photographs, 911 audio, interview recordings — go to a second tool or a manual process. A request that spans four media types becomes four workflows.
What Changes
- Redaction moves off the evidence system, so the bottleneck is removed without migrating evidence
- Every format in one place — video, audio, documents, images, and the report that accompanies them
- Bulk rather than file-by-file, queued and worked overnight, permissioned separately per format
- Exemption codes on every redaction, printed onto the output and into the transcript
- The evidence system stays authoritative. Redactor produces the release copy; the record of custody in your DEMS is undisturbed
How It Fits
Files move by API or by bulk upload, redact, and return. Agencies typically run one of three patterns:
- Export, redact, release — the release copy never goes back
- Export, redact, re-ingest — the redacted copy returns to the evidence system as a derived asset
- API-driven — the transfer is automated in both directions
An Axon Evidence.com integration record exists in the integration registry and is available on request rather than shipped, so the third pattern is scoped per deployment.
Why Not Just Use the Bundled Tool
| Bundled redaction | Redactor |
|---|---|
| Video, and in practice one file at a time | Video, audio, documents and images, in bulk |
| No exemption codes on the output | Statutory code on every redaction, printed on the file |
| No coverage report against a framework | Reports what share of the CJIS or FOIA class set was caught |
| Cloud only | Cloud, private cloud, on-premises or air-gapped |
| Redaction priced with the evidence platform | Priced as redaction, on volume you control |
What This Does Not Do
- It does not replace your DEMS, and it is not trying to. Evidence management, retention and custody of the master record stay where they are.
- The Axon Evidence.com integration is an on-request record rather than a shipped connector. Scope it before assuming automation.
- A release that matters still goes through review. Automation removes the bottleneck, not the judgement.
Bring Us a Real Request
Send the file types from one actual public-records request and we will run the whole thing.