Data last updated 07/05/2024

We encourage users to review the full methodology which is accessible here or via web. Our methodology was last updated on June 6, 2024.

We have included extracts to summarize our methodology below:

MPV definition of police violence

Any incident where a law enforcement officer (off-duty or on-duty) applies, on a civilian, lethal force resulting in the civilian being killed whether it is considered “justified” or “unjustified” by the U.S. Criminal Legal System.

A few disclaimers: 

  1. Vehicular force. Cases when vehicles are used as a form of lethal force or cases when the vehicle is deliberately driven in a manner that is directed at civilian(s) and/or the vehicle the civilian(s) are in (e.g. PIT maneuvers) are included. However, civilians who were killed by a civilian driver or crashed without being hit directly by police during a police pursuit are not coded as incidents of police violence. We have started to internally track Vehicular Chase incidents and will continue to collect and analyze that data.
  2. Suicide by Cop.  Cases where a civilian is killed by a law enforcement officer when they’re labeled as having a mental health crisis or in a state where they’re characterized as “Suicidal” (sometimes referred to as “Suicide by Cop”) are included as incidents of police violence.
  3. Possible suicide. We have started to collect incidents where a reported death is characterized as a “suicide” and provide it to another team to separately review the specifics.
  4. Off-duty.  Cases where a law enforcement officer kills a civilian while they’re “off-duty” is considered an incident of police violence. Additionally, it is worth noting that 97% of the incidents in MPV occurred while a police officer was acting in a law enforcement capacity. Thus, while MPV does include data on off-duty officers, it does not include killings by vigilantes or security guards who are not off-duty police officers. This is a gap in the field that should be further investigated, especially at the intersection of “Stand Your Ground Laws.”

Data collection

Mapping Police Violence sources data from a number of sources. While we strive to employ official data sources from local and state government agencies, we believe it is important to continue collecting data from publicly-accessible media sources. This allows us to identify gaps in government data, and further triangulate and validate the data.

After conducting an internal comparison of different news aggregators, we decided to use Google Alerts as our primary method for detecting news media mentions of police violence. We are continuing to develop and improve our own automated systems to filter out irrelevant news articles, maximize the comprehensiveness of the articles we do detect, and reduce potential human coding errors.

The steps we now follow to collect data are:

  • 1
    Journalists report incidents

    Local or syndicated press reports publicly on details of a law enforcement encounter which is available online.

  • 2
    News articles ingested to data lake

    Retrieve articles using a broad set of keywords relating to police violence using Google Alerts; store them in the data lake.

  • 3
    Articles filtered for relevance

    Automations developed in-house scrape full article text, remove duplicate articles, and identifies and removes irrelevant articles.

  • 4
    Articles assigned to researchers

    Custom Airtable automations developed in-house assign filtered articles to researchers for review.

  • 5
    Two-step incident review

    1st researcher enters new incident information into Airtable from assigned articles. 2nd researcher checks for accuracy and fills in missing/updated info. Incidents then made public automatically.

Cadence of updates to the live tracker

It is important to note that incidents are reviewed at different times. This can be for several reasons, including delays between an incident occurring and being mentioned in the news, or second reviewers flagging incidents for further review due to possible reliability concerns. Thus, the date presented on the live tracker does not reflect the most recent internally reviewed incident. Our research and product team do their best to keep the live tracker as comprehensive and up-to-date as possible.

When we publish incident data

Given that initial news reporting on incidents tend to be police-centric and significantly differ in narrative and details, we believe there is a responsibility to allow for a sufficient amount of time to pass prior to publishing incidents that may misrepresent the true details of the incident. This is both critical for data integrity and to honor the families and loved ones of victims to not present inaccurate, distorted, or false accounting of details.  We believe data quality and accuracy should supersede speed of publishing given the sensitivity of the data.

General disclaimers

The same data limitations noted by FE also apply to MPV given the similarities of how the data is sourced and generated.

Additional disclaimers and clarifications are noted below:

  1. Date of incident versus date of death. We use the date of police lethal action for the incident record even if the victim passes at a later date due to the injuries.
  2. Fatal outcome after law enforcement encounter. If a victim dies as a result of actions taken by law enforcement, regardless of whether the death occurs during the encounter or subsequently—such as en route to the hospital or even weeks later—the incident is classified as an instance of police violence and included in the database. This includes situations where the lethal action led to a delayed death (e.g., Eric Garner).
  3. Data on officers and case outcomes. MPV captures information on all involved officers in each case, including the name and race of each officer, any prior deadly force incidents involving that officer that have been reported by the media, and whether the case resulted in any administrative discipline, civil suits and/or misconduct settlements. Additionally, MPV tracks cases where officers have been charged with a crime related to an incident of fatal police violence. This data is collected during ongoing monitoring of media reports related to each case in our database.
  4. Cross-referencing data between sources to update, validate, and detect errors.
  5. Weekly review and cleaning.

A note on the police violence data sources and replication

We posit that the data collected, coded, and made available belongs to the public. It is not and should not be owned by any platform. We encourage communities, organizations, and other individuals to develop their own databases. This only strengthens the integrity and validity of the data by allowing us to study the differences across datasets and improve data collection efforts when there are attempts to harmonize and study the data. For example, a recent study has found that while the three major police violence datasets are similar, they have started to become more dissimilar over recent years (Comer and Ingram, 2022).

Thus, we are always open to partnerships and collaborations to improve the methodology and/or share best practices. We center collaboration and co-creation over ego, which can be a departure from orthodox academic norms and culture.

We want to acknowledge and thank Samuel Sinyangwe, a Campaign Zero co-founder for leading this work and the development of the initial methodology. We also want to acknowledge and thank D. Brian Burghart, founder of Fatal Encounters, who advised the initial development of the project and continues to advise and collaborate on the methodology.

Previous methodology

Our previous methodology primarily sourced data from Fatal Encounters, The Washington Post, publicly-accessible media sources, and official data sources from local and state agencies required to report this data (e.g., California Department of Justice).

We are working to make our methodology more rigorous and efficient by partnering with different organizations and automating how we collect and validate data. We’re constantly striving to improve our methods and systems. Please contact us if you have any suggestions or would like to partner in any way.