What Is CompStat? Origins, Principles, and Accountability

CompStat is a police management model that uses current crime data, geographic mapping, and regular high-pressure meetings to hold precinct and district commanders directly accountable for what happens on their streets. It was built at the New York City Police Department in 1994 under Commissioner William Bratton and his deputy Jack Maple, and it replaced a reactive style of policing with one organized around continuous measurement and fast response. Within five years of its launch, New York City homicides had dropped 67 percent, burglaries 53 percent, and robberies 54 percent.¹ By 2006, roughly 60 percent of U.S. police agencies had adopted some version of the model.²

Where CompStat Came From

Before 1993, precinct commanders in large departments often had no timely picture of crime in their own territory. Reports trickled up to headquarters weeks or months after incidents occurred, and leadership had little visibility into whether local tactics were working. Jack Maple changed that by requiring each of New York City’s 76 precincts to compile crime statistics and map incidents daily, then send the information to headquarters. By April 1994, the system was running on a continuous update cycle, and commanders were being summoned before executive leadership to explain conditions in their areas.

The crime reductions that followed drew national attention. The New York Times called them “a marvel of American law enforcement” and “simply breathtaking.”¹ CompStat was launched alongside quality-of-life enforcement targeting minor offenses, and separating the effect of each initiative from broader national crime trends has been debated ever since.

The Four Principles That Drive It

Maple summarized CompStat as four principles that cycle continuously rather than running once:

Accurate and timely intelligence. Data has to reflect what is happening now, not last quarter. Precincts feed crime reports, arrests, and complaints into a central system as close to real time as possible.
Effective tactics. Once patterns emerge from the data, commanders design responses targeted at those patterns rather than applying generic enforcement.
Rapid deployment. Personnel and specialized units shift to problem areas without the usual bureaucratic delay, because crime patterns move.
Relentless follow-up and assessment. Every tactic is scrutinized for results. If a strategy is not working, commanders are expected to adjust immediately rather than wait for a program review cycle.

The word “relentless” in the last principle carries weight. The cycle repeats weekly, and commanders who cannot show they tracked the results of their own decisions face uncomfortable questions in front of their peers.

What a CompStat Meeting Looks Like

The meetings are where CompStat’s accountability mechanism actually operates, and they are designed to be high-pressure. They run weekly in most departments, led by the chief or another senior executive, in a room equipped with large screens showing maps, charts, and statistical snapshots. Precinct or district commanders stand before those displays and walk through conditions in their area: what crimes are up, what crimes are down, what they did about it, and what happened as a result.¹

Executives probe with specific questions. A commander reporting a robbery spike should expect to be asked what pattern analysis revealed, which units were redeployed, whether detectives coordinated with patrol, and how the arrest rate compares to the prior period. Vague answers do not survive long. Lieutenants, detectives, and other personnel involved in an operation may be questioned directly.

Meetings also review internal metrics: overtime use, sick time, complaint trends, and compliance with department policies. That dual focus on crime outcomes and administrative performance separates CompStat from a simple crime-tracking dashboard. It functions as a management audit in front of an audience.

The Data Behind It

The original CompStat ran on a single desktop computer. Modern implementations rely on geographic information systems that layer incidents onto digital maps, revealing spatial clusters a spreadsheet cannot show. Temporal analysis adds another dimension, identifying when crime concentrates: specific hours, days of the week, seasonal patterns. Departments use those maps to deploy officers across shifts with precision.

The core metrics track serious offenses classified under the FBI’s Uniform Crime Reporting program, which federal law requires the Attorney General to compile as national crime statistics.³ The most closely watched are the eight Part I offenses: criminal homicide, rape, robbery, aggravated assault, burglary, larceny-theft, motor vehicle theft, and arson.⁴ Beyond those, departments feed in calls for service, arrests, summonses, and quality-of-life complaints submitted through 311 and similar channels.⁵

The source data itself has shifted. In January 2021, the FBI transitioned its Uniform Crime Reporting program from the older Summary Reporting System to the National Incident-Based Reporting System, which captures far more detail per incident, including up to 10 offenses along with victim and offender demographics, location, property, and weapon information.⁶ As of late 2024, approximately 76 percent of law enforcement agencies, covering about 87 percent of the U.S. population, report NIBRS-compliant data.⁷ For CompStat-style programs, richer input data is the upside; the downside is that recording all offenses in an incident, rather than only the most serious one, can make crime appear to rise even when it has not.

Command Accountability

CompStat’s most consequential innovation is not the technology. It is the deliberate transfer of responsibility for crime outcomes onto precinct and district commanders. Before CompStat, a spike in burglaries was something that happened in a neighborhood. After CompStat, it was something that happened on a specific commander’s watch, and that commander had to explain it.

Geographic accountability means commanders are expected to know every significant incident in their area from the most recent reporting period. They cannot deflect to outside causes without producing a mitigation plan. When a strategy fails, the question is not why it failed but what the commander did after recognizing it was failing. Leadership who cannot demonstrate progress, or who appear unfamiliar with conditions in their sector, face consequences ranging from formal reprimand to reassignment or demotion.

Spread Beyond the NYPD

CompStat spread quickly. By 2006, six of ten agencies surveyed nationally had implemented some form of it.² Major departments in Los Angeles, Philadelphia, Baltimore, and Newark built their own versions.

The model also crossed over into non-police government operations. Baltimore created CitiStat, applying the structure to the full range of city services. New Orleans used BlightStat to target abandoned properties, Los Angeles County’s Department of Public Social Services built DPSSTATS to track economic independence outcomes, and the Federal Emergency Management Agency created FEMAStat to carry lessons from disaster responses into preparedness. All of them share the same core logic: gather current data, assign specific people responsibility for results, and review performance face to face.

Did It Actually Cut Crime?

The New York numbers are striking. Between 1993 and 1998, homicides dropped 67 percent, burglaries 53 percent, and robberies 54 percent. By 2012, New York City recorded 417 homicides, the lowest since reliable records began in 1963 and an 81 percent reduction from the 2,245 recorded in 1990. In a 2011 survey by the Police Executive Research Forum, 86 percent of agencies using CompStat-style programs reported decreases in property crime and 80 percent reported decreases in violent crime.¹

The complication is that crime was falling nationally during the same period for reasons unrelated to police management: demographic shifts, economic changes, mass incarceration, and other factors. Isolating CompStat’s independent contribution has proven difficult. Researchers generally agree CompStat improved internal management, forced faster information sharing, and made police leadership more aware of conditions in their jurisdictions. Whether those improvements caused the drop or coincided with a broader trend remains an open question, and the honest answer is probably some of both.

Where CompStat Gets Criticized

A management system that punishes commanders when crime numbers rise creates an obvious incentive to manipulate those numbers. A 2014 study surveying 1,770 retired NYPD officers found that 55.5 percent of those who served between 2002 and 2012 had personal knowledge of instances where crime reports were altered to make statistics look better than they were, compared with 30.3 percent reporting similar knowledge during the pre-CompStat era. The techniques included reclassifying a burglary as criminal trespass, splitting a robbery into separate larceny and assault reports to avoid counting a Part I offense, changing complaint language to downgrade a classification, or refusing to take a complaint at all. The researchers concluded that CompStat had “morphed into a culture of gaming numbers to keep the decreases going.”

The problem is a version of what is sometimes called Goodhart’s Law: when a measure becomes a target, it stops being a good measure. Agencies trying to avoid the trap generally rely on independent auditing of crime classifications, protections for officers who report discrepancies, and leadership that distinguishes between numbers rising because crime rose and numbers rising because the department started counting honestly.

The quota question is a related tension. In Floyd v. City of New York (2013), a federal district court found that the NYPD had effectively pushed officers to meet numerical targets for stops, tickets, and arrests, and that the system operated as a “predictable formula for producing unjustified stops.” The court held that New York’s stop-and-frisk practices, carried out under CompStat-era pressure, violated both the Fourth Amendment and the Equal Protection Clause. At least 22 states have since enacted laws banning enforcement quotas, prohibiting departments from penalizing officers for failing to meet numerical targets. Tennessee classifies the use of an unauthorized quota as a criminal offense. New Jersey bars posting arrest or citation data in common areas like station houses for the purpose of creating competition between officers.

CompStat’s architects argue the system measures outcomes, not activity for its own sake. In practice, the distinction between “track crime reduction results” and “produce more arrests” can collapse in a precinct where a commander’s job depends on numbers moving the right direction.

Co-implementation with community policing has produced its own friction. CompStat concentrates authority with commanders and focuses narrowly on crime metrics; community policing pushes decision-making down to individual officers and broadens the mission to relationship-building and non-enforcement problem solving. In a national assessment, staffing strain from trying to run both models at once was the most frequently cited challenge, reported by 16 percent of agencies that attempted it.² Some patrol officers reported that the emphasis on minor enforcement left them unable to handle routine service requests, and in at least one major city, community members, particularly African Americans, associated CompStat with aggressive enforcement that disproportionately targeted minorities.

As CompStat has absorbed predictive analytics, bias concerns have followed. Predictive policing tools trained on historical crime data inherit whatever biases exist in that data. If a neighborhood was over-policed for years, the historical record shows more crime there, the algorithm predicts more crime there, more officers deploy there, more arrests follow, and the cycle reinforces itself. A report from the U.S. Commission on Civil Rights found that this feedback loop “could create more problems of over-policing and put more people of color into the criminal justice system.” The report noted that at the peak of New York’s stop-and-frisk program, Black and Latino individuals were nine times more likely to be stopped than white individuals, and algorithms trained on that enforcement data would reproduce those disparities. Very few statutes currently regulate the use of such tools, even as up to a third of U.S. cities are using or considering them.⁸

Where CompStat Is Headed

CompStat’s next step is already in motion. Departments are piloting AI-driven forecasting models that go beyond mapping where crime has happened and attempt to predict where it will happen next. A 2026 pilot pairing a Florida police department with university researchers in criminology and artificial intelligence is testing a tool designed to anticipate crime patterns and support real-time patrol planning, with the goal of producing evidence for scaling the approach nationally.

Whether those tools deliver depends on solving the data integrity and bias problems that have shadowed CompStat from the start. A model trained on manipulated statistics or skewed enforcement data will produce predictions that are fast, confident, and wrong in exactly the ways that matter most.

1
Bureau of Justice Assistance. CompStat: Its Origins, Evolution, and Future in Law Enforcement Agencies
2
U.S. Department of Justice, Office of Community Oriented Policing Services. The Co-Implementation of Compstat and Community Policing: A National Assessment
3
Office of the Law Revision Counsel. 34 USC 41303 – Uniform Federal Crime Reporting Act of 1988
4
Federal Bureau of Investigation. UCR Offense Definitions
5
NYC Mayor’s Office. Mayor Adams and NYPD Commissioner Tisch Expand Quality of Life Teams Across All of Staten Island Following Successful Pilot Launch
6
Federal Bureau of Investigation. National Incident-Based Reporting System (NIBRS)
7
Congressional Research Service. Federal Support for Law Enforcement Agencies Transition to the National Incident-Based Reporting System
8
U.S. Commission on Civil Rights. The Civil Rights Implications of the Use of Algorithms in Policing and Criminal Justice