Shields of Shame • Public Records Field Guide
The Body-Camera
Audit Trail Toolkit
A practical guide to the records behind the recording: who used a camera, when it recorded, when footage was uploaded, viewed, categorized, retained, redacted, exported, shared—or scheduled for deletion.
Why this record matters
The video shows a scene. The audit trail shows the evidence lifecycle.
Body-camera video is only one layer of evidence. The surrounding logs can show camera assignment, button presses, automatic triggers, recording start and stop, docking, upload, playback, access, metadata changes, retention changes, redaction, download, export and sharing. Different products use different names and do not record identical events, so a good request asks for functions—not just a vendor label.
Camera-level events: assignment, power, buttons, recording, battery, firmware, docking, upload and evidence IDs.
File-level history: access, playback, title/category changes, retention, redaction, export, sharing and deletion-related actions.
Account activity across records: logins, searches, access, streaming, downloads, administrative changes and report generation.
Case membership, tags, collaborators, external links, acknowledgments, exports and discovery deliveries.
Beyond Axon
Ask every platform the same functional questions
| System family | Names you may encounter | Records to ask for |
|---|---|---|
| Axon | Axon Evidence, Evidence.com, Body 2/3/4, Fleet, Respond | Evidence audit, user history, device audit, case audit, Respond audit, sharing/export and redaction activity |
| Motorola / WatchGuard | VideoManager EL/EX, CommandCentral Evidence/Vault, VISTA, V700 | Event/case audit, device audit, viewing/export/deletion activity, assignment history and retention rules |
| Digital Ally | EVO Web, VuVault, FirstVu, VuLink | Chain-of-custody report, request/acknowledgment log, upload/export history, device assignment and configuration |
| Utility | BODYWORN, EOS, ROCKET, POLARIS, HELIOS | Chain-of-custody history, access/share records, file versions, retention, redaction and case activity |
| Panasonic / i-PRO | Arbitrator, SafeServ, Unified Evidence Management / UDE | Audit by time/type/user, export log, device and file history, chain-of-custody and retention metadata |
| Connected surveillance | Fusus / Axon Fusus, LPR, RTCC platforms | Live/recorded views, searches, PTZ movement, clip downloads, screenshots, exports, logins and sharing |
Product names, screens and export options change. Ask the agency to identify the exact hardware, evidence-management platform, version, administrator and available report types before arguing that a particular report must exist.
The low-cost sequence
Request the map before requesting the mountain
- 1Lock the identifiers.
Incident/case number, officer, date, local-time window, camera serial, vehicle number and every evidence ID visible in filenames or overlays. - 2Ask for an inventory first.
A native electronic list of responsive evidence with ID, title, device, owner, capture/upload time, duration, category, retention rule, scheduled deletion date and current status. Also ask for the platform and report names. - 3Request the evidence-level audit for each ID.
This is usually the cleanest way to trace access, playback, edits, retention, redaction, exports, sharing and deletion-related actions without sweeping up an officer’s entire account history. - 4Add the device audit around the incident.
Use a tight window—often the shift plus docking/upload time. Ask for assignment, power, activation, start/stop, buffering, mute, markers, firmware, clock sync, docking and upload events. - 5Add targeted user and case histories.
Name the accounts and date range. Seek actions involving the identified evidence IDs, plus case additions/removals, searches, downloads, external shares and permission changes. - 6Request the derivative trail.
Redaction project history, clip creation, transcript activity, export manifests, download/share receipts, filenames, hashes or integrity-verification data, and the disposition of the unaltered original. - 7Reconcile against independent clocks.
Compare CAD, dispatch audio, radio logs, AVL/GPS, jail or evidence-room logs, incident reports, device assignment, personnel schedules and the footage timestamp. Preserve every time zone.
Copy and customize
Model request language
Under the applicable public-records law, please provide the following existing records in native electronic form for [incident/case number], [officer/user], [date and local-time window]:
1. An inventory/export listing every responsive body-worn, in-car and related evidentiary file, including evidence ID, title, source device/serial number, assigned user/owner, capture time, upload time, duration, category, retention rule, scheduled deletion date and current status.
2. The complete evidence/file audit trail for each identified evidence ID.
3. The device audit trail for each involved camera for [narrow start/end], including assignment, power, activation, recording start/stop, buffer/pre-event, mute, marker, clock-sync, firmware, dock, upload and deletion-from-device events.
4. User/account history limited to actions involving those evidence IDs and that date range, including access, playback/streaming, search, metadata changes, retention changes, redaction, download, export, sharing and deletion-related actions.
5. Any case audit, sharing log, download/export manifest, external-link history, acknowledgment/receipt log, redaction-project history, transcript activity and integrity/hash report for those files.
6. The retention schedule/policy and any legal hold, preservation flag or category rule applied to the evidence.
7. A data dictionary, report legend or vendor help page sufficient to interpret the fields and event names.
Please identify the camera vendor/model, evidence-management platform and available report names. Please preserve all responsive records while this request is pending.
Please provide searchable PDF, CSV or the system’s native export—not screenshots—using the platform’s existing export function where available. Preserve original timestamps, time-zone offsets, IDs and column headers. I do not request creation of a new analysis; I request existing reports, exports, logs and underlying electronic records.
Before incurring charges above $[cap], please provide a written, itemized estimate stating: each record category, page/row/file count, task, employee classification and hourly rate, estimated time, duplication/media cost, redaction basis, and the least-cost alternative. Please separate audit-report production from video review/redaction and delivery costs. If any part is withheld, produce the nonexempt remainder and cite each specific statutory exemption.
Use a short date range first. Do not insert accusations into the request. Ask for preservation when deletion may be approaching, but remember that a preservation request is not automatically a legal hold.
Fees: compare like with like
A quote, an invoice and a payment are three different facts
The correspondence reviewed by Shields of Shame shows why the categories must be separated. A fee attached to a request containing video does not prove that the agency charged for the audit report.
The agency wrote that it could produce some less labor-intensive Axon audit reports “for no charge,” while estimates for more comprehensive per-evidence reports remained. This demonstrates that report type and extraction method can change cost.
Approximately $10,300 was quoted for a combined, multi-category request—not audit trails alone. The response described 5,630 audit pages and a 30-second cursory review per page (about 46.9 hours), plus separate work for other records.
The $113.73 quote covered retrieval/download of 23 Axon videos, a flash drive and delivery. No separate audit-trail charge was identified in the correspondence reviewed.
A $23.50 amount was accepted for a combined request that included an Axon audit. The reviewed correspondence does not establish an audit-specific charge.
Fee challenge checklist
- Ask for each record category to be priced separately.
- Ask whether the report is generated by a built-in export and whether a narrower report can be produced without page-by-page review.
- Request the employee title, hourly rate, task and estimated minutes—not one unexplained total.
- Ask why audit logs need the same review as audiovisual content and what specific exempt fields require redaction.
- Offer evidence IDs and a tighter date range; ask for rolling production and a no-charge first installment.
- State a fee cap and require advance approval before costs exceed it.
Georgia and Florida
Open-records rules that shape the strategy
Georgia
The Attorney General says requests should go to the records custodian and are best made in writing. Agencies generally must produce records within three business days or provide a written timeline, cost and specific exemption. Fees must use the most economical means; search/retrieval charges cannot exceed the salary of the lowest-paid qualified full-time employee, and the first 15 minutes are free. Computer-based or generated information can be a public record, including material maintained by a private contractor for an agency.
Georgia AG Open Government FAQ ↗
How to make a Georgia request ↗
Florida
Florida law requires prompt acknowledgment and a good-faith response. If an exemption is asserted, the custodian must cite the statutory basis and produce the nonexempt remainder. Section 119.07 allows actual duplication cost and a reasonable special-service charge when the nature or volume requires extensive IT resources or extensive clerical/supervisory assistance. Florida’s body-camera exemption covers certain recordings in private places and provides access routes for recorded people and others described by statute; the statute sets a minimum 90-day retention period for body-camera recordings. Audit logs may require a different exemption analysis from the audiovisual recording itself.
Florida Statutes §119.07 ↗
Florida Statutes Ch. 119 / BWC provision ↗
Legal note: This is reporting and practical guidance, not legal advice. Exemptions, retention schedules and case status are fact-specific; verify the current statute and local policy before relying on a deadline or disclosure theory.
Evidence library
Search the supplied sample files
These files are examples of different log families. Names and personal or operational data may appear. Review and redact before republication; a public-record release does not eliminate ethical privacy concerns.
Lakeland PD — Kenneth Vanderpool
September 1–30, 2024 • 52 pages. Fields include user, action, evidence/case IDs, title, IP/owner and additional information. Shows Evidence/Transcript Accessed, Buffered, Streamed, title/metadata changes and Axon Body 3/Fleet 3 activity.
OPEN SAMPLE 2 ↗
Wrens PD — Scott Usry
February 12–November 15, 2024 • 94 pages. Shows Axon Body 4 assignment, access/streaming, authentication, categories, retention changes and scheduled deletion dates.
OPEN SAMPLE 3 ↗
Adobe Sign transaction history
May 7, 2025 • 1 page. Not a body-camera report. Demonstrates a different audit-log family: document creation, delivery, viewing, signature and completion timestamps.
OPEN SAMPLE 4 ↗
MARTA Police — device history
March–October 2021 • 534 pages. Axon device events include registration to MARTA Police, assignment to Nilson Moraes, firmware and clock sync, button presses, recordings, TASER-triggered recording, playback, docking, upload and deletion from device.
OPEN SAMPLE 5 ↗
Lakeland PD — one-day Body 3 trail
September 15, 2024 • 18 scanned pages • serial X60A69944. Generated by OPS Detective Paula Parker. Shows dock/charger state, power, sleep mode, clock sync, dashboard connection, start/stop and marker/button events.
OPEN SAMPLE 6 ↗
Richmond County SO — Keven Cheillada
January–December 2025 • 945 pages • Axon Body 4 serial D01AE758K. Contains 17,874 numbered events: dock/power/battery, storage, firmware, recording, evidence IDs, on-device categorization and other device state changes. Labeled “Official-Sensitive” and excludes confidential activity.
OPEN SAMPLE 7 ↗
Cherokee County / Charles Aaron Mills
September 23, 2026 • 9 pages. Not itself an audit export. A source-documented SOS dossier that explains how device audits fit beside complaints, POST records, internal affairs material, warrants and reporting.
OPEN SAMPLE 8 ↗
Wrens PD — Travis Braswell
August 21–November 14, 2024 • 57 pages. Shows Axon Body 4 title/category and retention events, scheduled deletion, access/buffer/stream actions, login security and report-download activity.
OPEN SAMPLE 9 ↗
How to export an evidence audit trail
Axon instructions dated December 4, 2024 • 2 pages. Shows the Evidence Details → Audit Trail → Audit Period → Run Audit → Download sequence and confirms PDF output.
OPEN SAMPLE 10 ↗
Lakeland PD — Nathan Smith
September 1–30, 2024 • 37 pages. Shows Axon Body 3 and Fleet 3 evidence, SSO login, assignments, evidence IDs, title/category/custom metadata, retention changes and scheduled deletion dates.
OPEN SAMPLE 11 ↗
Savannah PD — Ashley Wood
January 1, 2021–November 15, 2024 • 65 pages • Axon Body 2 serial X81345309. Shows firmware/time sync, assignment, start/stop, evidence-file IDs, power, battery/storage, upload history and final reassignment/status events.
OPEN SAMPLE 13 ↗
Atlanta PD and partner organizations
August 1–31, 2024 • 214,059 rows. Fields include log/user/organization/object IDs, timestamps, operation, duration, object type, change/detail/location data and notes. Activity includes live and recorded viewing, LPR searches, PTZ movement, logins, clip downloads, screenshots, exports and deletions.