What I found when we looked closer
Glenarden Police Department's public materials show a department centered on community-facing work: suspicious-activity calls routed through the communication center, automated speed enforcement, accident reports written within 72 hours, and neighborhood problem-solving led directly by the department. That means the reporting burden is not only about serious arrests. It is also about handling the steady flow of calls and complaints that shape how residents experience the department.
For an agency like Glenarden, documentation quality matters because community trust is built in the follow-up. If reports are slow, incomplete, or hard to review, the department loses time on the back end and residents feel it on the front end.
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 4 hands:
- 1Officer
- 2Records
- 3Resident or insurer
- 4Neighborhood follow-up
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
Glenarden publicly commits to writing accident reports within 72 hours. Drafting from the recording at the scene makes that commitment easier to keep on a busy week.
Suspicious-activity and nuisance calls are often a short conversation and a few photos. Flash captures them in the field so they do not pile up as end-of-shift paperwork.
What we're watching
These are the signals that will tell us whether it's working here:
- Crash reports delivered inside the 72-hour commitment
- Routine calls documented before end of shift
- Resident follow-ups closed per month
Figures on this page come from the department's own published materials. We only publish Code Four results after the department reviews them.
