Columbia City Council Meeting: Crime Data Dashboard Presentation (2025-11-04)
Columbia City Council Meeting: Crime Data Dashboard Presentation (2025-11-04)
On November 4, 2025, the Columbia City Council convened to review a detailed presentation from Columbia Police Department (CPD) leadership regarding the city's new Crime Data Dashboard and the complexities of crime statistics. The session focused on the nuances of data collection under the National Incident-Based Reporting System (NIBRS), the impact of staffing levels on reporting rates, and the distinction between reported incidents and actual underlying crime rates. Council members emphasized the need for contextual understanding to prevent data misinterpretation, particularly regarding recent increases in "Group B" (quality of life) offenses versus violent crimes.
Consent Calendar
- [No specific consent calendar items were discussed in the provided transcript segment; the meeting proceeded directly to the presentation and discussion.]
Public Comments & Testimony
- [No public comments or testimony were recorded in the provided transcript segment.]
Discussion Items
- Data Definitions and NIBRS Complexity: Assistant Chief Mark Fischer and Command Staff explained that crime statistics are highly dependent on variable definitions. For example, "calls for service" can range from 90,000 to 124,000 annually depending on whether self-initiated contacts (traffic stops) are included. Fischer emphasized that the dashboard prioritizes mapping "incidents" (single events) over "offenses" (specific charges within an event) to avoid visual clutter, meaning a single domestic disturbance involving multiple charges is plotted as one red dot representing the highest severity offense.
- Group B Offenses and Enforcement: The presentation highlighted a 59% year-over-year increase in "Group B" offenses (e.g., trespassing, liquor law violations, disorderly conduct, bad checks). Staff warned that these offenses are only reported to the state and federal government if an arrest is made. Council members and staff agreed that this increase is largely driven by targeted proactive enforcement initiatives in downtown and the Connolly Road Corridor, rather than an actual increase in criminal activity itself.
- Staffing and Underreporting: Command staff expressed strong concern that understaffing over the past several years has led to significant underreporting. They noted that when response times were slow, victims (particularly for larcenies) stopped calling the police. As staffing recovers and customer service improves, the agency anticipates an increase in reported crime numbers simply because victims will report incidents they previously abandoned due to poor response times.
- Data Accuracy and Timeframes: The dashboard is noted to be live up to three days ago but contains inaccuracies for the last 28 days because many crimes are discovered and reported days or weeks after the incident. Consequently, recent data points are almost always under-reported, not over-reported. Additionally, less than 10% of all calls for service result in a formal police report entered into the NIBRS system.
- Violent Crime Trends: While total reported crime has risen, Staff indicated that violent crime is up year-over-year (approximately 15% increase), driven primarily by aggravated assaults and domestic violence-related aggravated assaults. Conversely, homicide numbers remain historically low compared to previous years.
- Benchmarking and Policy Implications: Staff clarified that the data's primary utility for policy lies in benchmarking Columbia against comparable cities of similar size and demographics to justify budget and staffing requests. Council members cautioned against using raw data to claim trends without context, reiterating that an increase in reported minor offenses does not necessarily reflect a decline in community safety or an increase in actual crime.
Key Outcomes
- The Council acknowledged the complexity of the crime data and the necessity of context, specifically regarding the surge in Group B offenses and the impact of staffing on reporting rates.
- Staff committed to improving the transparency dashboard, including adding a summary of Group B offenses and a violent crime summary to the main view, as well as adding public-facing disclaimers and guides to prevent misuse.
- The Council approved a motion to recess and immediately enter into a closed session pursuant to Section 610.0211 and 610.02119.D of the Missouri Revised Statutes to discuss:
- Confidential communications with attorneys.
- Operational guidelines and specific response plans for critical incidents that could endanger public safety.
- A vote was taken to approve the closed session, with all council members present voting "Yes".
Meeting Transcript
Okay everyone. We're gonna go ahead and get started. We've got a form. So I'll call this into order for three case meeting. We've got a presentation from CPD and she should be able to leave your kicking this off. Hi everybody. So I think all of you know most of our command staff, but just in case you don't, we do have some new faces, and so um I'm gonna have them introduce themselves really quick and tell you what they're in charge of. Yeah. Uh Max doesn't have the sheet. So I have the second time she's shown available, then I start by that one. My name is Drake Correll. I'm over with Federal Standards Bureau, and I have uh the Academy, uh policy, the PIOs, yeah. Everybody wants Rick's job. And I'm Mark Fischer, uh, so I'm over our patrol bureau. I'm over our investigative bureau, so I have all our criminal investigation and also special investigations, which is narcotic street crimes, squat, etc. Assistant chief hunter couldn't be here tonight, but he is over kind of our uh patrol support operations, so things like our park police, our homeless outreach team, our school resource officers, special events, things of that nature. So we have this great online data tool that we've been working hard to refine. I think there's still some refinements we'd like to do to it. So feel free to jot down suggestions or things because we'll definitely take those into consideration. But uh assistant chief is general is going to talk to you in depth and answer questions about how best to use the tool and a lot of the you're gonna hear hear the word nuance a lot. So just be prepared for that. And um, I think it your preference, but I think it's easy. Yeah, it's they they want to choose a microphone. It'd probably be easier if you guys ask questions as they come up because it is gonna get really confusing. Probably if you don't councilman Foster, we have about an hour, a little under an hour for this. Is that I wasn't given an amount of chance. That should be the trick. Okay. So uh, because we can get as far deep into the weeds as you folks want to go uh on this. Um, but please, I hope this will be a little bit more of a conversation than uh um really kind of instructional training deal. So uh to start out with uh the the packet that I that are the papers I provided you here is is just summary of all of the talking points I kind of wanted to make. Um I thought about just giving you kind of like cheat sheets to walk away from with just some of the definitions, um, but then I ended up just giving you everything so that way you guys have some notes to refer back to at some point if that's if that's valuable for you. So um I thought we'd go through like kind of crime stats generally from the police's perspective, then get into uh the history of crime reporting because I think that that talks a little bit about why some of the way things are counted the way they are. Um, go into our crime data dashboard, which is really the focus of this is uh I was asked to kind of give some instruction on how to use this crime data dashboard and to so you can look at it yourselves or give guidance in that in that regard. Um, and then um just some kind of takeaways or recommendations I have with the crime data. So the first thing I want to kind of just start out with by saying is that defining the terms is everything for us. Um that when the terms are undefined, um, you're gonna get different answers to the same question because we're defining the terms differently. So the easiest way or the best example that I think that I can come up with is our calls for service data. So somebody says, hey, how many calls for service is the Columbia Police Department respond on in a year? It's like, well, that's that's a great question, but calls for service is still too much of an undefined term. That calls for service could mean calls where a citizen calls 911 or 311 requesting a police officer to come. Um it could include self-initiated contacts, uh, which means like traffic stops, is the traffic stop count for calls for service. Well, it depends on how you define the term. Um, or some of the other things like our following up, evidence processing, um, report writing, some administrative tasks. Does that count as for a calls for service? And so when somebody asks the police department how many calls for service did you go on, um, and we say 90,000 calls for service in the last 12 months, 116,000 or 124,000, those all could be accurate numbers, but it defend depends on how you define the term call for service. So another thing that's gonna come up with this data dashboard too is that there's conflicting priorities when presenting and examining data. So the Columbia Police Department has hundreds of thousands of records um that we we utilize uh you know from a year year to year basis. So the Columbia Police Department has hundreds of thousands of records that we we utilize uh you know from a year year to year basis, and if we just gave you all of those in an Excel document, like or a or a CSV file or some sort of database file, that's gonna be very hard to ingest and to examine. And so when we publish the data in this data dashboard, we had to make choices on how to present the data.
openpublica.com