What I found when we looked closer
Caldwell Police Department's 2024 annual report shows a department carrying a substantial documentation load before investigation software is even counted. The report says CPD handled 45,147 calls for service and 4,395 traffic stops in 2024, while also supporting a Detective Bureau, school-resource work across 11 schools, and an Operational Support Section focused on crime trends, gangs, and violent offenders.
That matters because Caldwell's reporting burden does not stop at the first patrol narrative. A call may need to move into detectives, school-safety coordination, traffic-collision mapping, or a proactive investigative effort without losing sequence or detail along the way.
Following one report through the building
The first thing we do with a new department is trace where a report goes after the officer hits submit. Here, it passes through 5 hands:
- 1Patrol officer
- 2Drone team footage
- 3Supervisor review
- 4Detective Bureau
- 5Operational Support Section
Every one of those readers needs the same facts from the first draft. That is what shaped what we built.
What we built for them
Caldwell logged 45,147 calls and 4,395 traffic stops in a year. Report turns each recording into a draft so officers are not retyping what the camera already captured.
Drone footage, body-camera video, and collision mapping are now part of the same incident. Insights puts them on one searchable timeline for the detective who inherits the case.
More cameras means more footage in public-records requests. Redact handles faces, plates, and audio across drone and body-camera video before release.
What we're watching
These are the signals that will tell us whether it's working here:
- Reports that cite drone and body-camera footage from the same incident
- Time to complete traffic-collision documentation
- Records-request turnaround for video
Figures on this page come from the department's own published materials. We only publish Code Four results after the department reviews them.
