Frequently Asked Questions
Dive in and learn about WADEPS!
FAQ: Overview
– Law enforcement agencies must collect and report data specific to incidents where force is used by a sworn officer.
– All reported data must be validated to ensure accuracy and completeness.
– Make the collected data publicly available in a user-friendly format, allowing citizens to access and analyze the information.
– Enhance public safety by identifying patterns and trends not immediately apparent through traditional methods.
– Optimize resource allocation by pinpointing areas where efforts have the greatest potential to improved outcomes.
– Improve community engagement and trust by providing stakeholders with actionable insights and visualizations on police interactions.
– Streamline operations by automating manual processes, reducing errors, and increasing efficiency.
– Support state agencies such as the Office of Independent Investigations opens a new window (OII) with a central, standardized data repository.
FAQ: Data collection
FAQ: Data dashboard
FAQ: Overview
What is WADEPS?
WADEPS stands for Washington State Data Exchange for Public Safety.
Our primary purpose is to serve as a data custodian. We provide a cloud-based platform to effectively collect, analyze, and visualize data about police use-of-force interactions and to provide publicly available, easy-to-use visualizations of the data.
Our primary purpose is to serve as a data custodian. We provide a cloud-based platform to effectively collect, analyze, and visualize data about police use-of-force interactions and to provide publicly available, easy-to-use visualizations of the data.
Who is WADEPS?
We are an interdisciplinary team of experts in technology development and criminal justice research, experienced statisticians and data analysts, and communications and training professionals.
The Washington State Date Exchange for Public Safety is managed by Washington State University and supported by world-class, cloud-based technology.
We were selected as the data custodian through a competitive process managed by the Washington State Office of the Attorney General opens a new window, including Request For Proposal (RFP) and Request For Information (RFI) stages. The state granted responsibility for the program to WSU on August 15, 2023.
The Washington State Date Exchange for Public Safety is managed by Washington State University and supported by world-class, cloud-based technology.
We were selected as the data custodian through a competitive process managed by the Washington State Office of the Attorney General opens a new window, including Request For Proposal (RFP) and Request For Information (RFI) stages. The state granted responsibility for the program to WSU on August 15, 2023.
Why does Washington need a use-of-force database?
It’s required by state law. Senate Bill 5259 (sponsored by Senator T’wina Nobles), which was enacted in 2021 and signed into law as Chapter 10.118 RCW opens a new window in 2022, is the primary legislative authority governing the statewide collection and distribution of use-of-force data.
The legislation requires specific data about use-of-force incidents be collected and reported by all law enforcement agencies and all statewide data be complied in a centralized, publicly available database.
Key provisions of the bill:
The legislation requires specific data about use-of-force incidents be collected and reported by all law enforcement agencies and all statewide data be complied in a centralized, publicly available database.
Key provisions of the bill:
– Law enforcement agencies must collect and report data specific to incidents where force is used by a sworn officer.
– All reported data must be validated to ensure accuracy and completeness.
– Make the collected data publicly available in a user-friendly format, allowing citizens to access and analyze the information.
What are the benefits of a public safety data dashboard?
A central hub for collecting, analyzing, and sharing law enforcement interaction data can help agencies and the public quickly identify trends and patterns in policing use-of-force and police interactions, and to make more informed decisions and drive meaningful community outcomes.
Leveraging the power of data analytics and visualization tools can help:
Leveraging the power of data analytics and visualization tools can help:
– Enhance public safety by identifying patterns and trends not immediately apparent through traditional methods.
– Optimize resource allocation by pinpointing areas where efforts have the greatest potential to improved outcomes.
– Improve community engagement and trust by providing stakeholders with actionable insights and visualizations on police interactions.
– Streamline operations by automating manual processes, reducing errors, and increasing efficiency.
– Support state agencies such as the Office of Independent Investigations opens a new window (OII) with a central, standardized data repository.
FAQ: Data collection
What data is required to be collected?
The WADEPS data dictionary encompasses legislative and law enforcement recommendations and has been reviewed and approved by the WADEPS Data Governance Committee and the Office of the Attorney General.
The statute requires each law enforcement agency in the state to report incidents described in Chapter 10.118.030 RCW opens a new window (1)(a) through (t), as well as noted in subsection (3) “any additional incidents and data required by the statewide use of force data program developed in section 3, chapter 326, Laws of 2021”.
The approved recommendations (PDF) constitute the statewide use of force data program, as noted in Senate Bill 5259 (PDF) Section 3 (4). Including limited incident-based data on all calls for service was recommended by the state advisory group and approved by the Office of the Attorney General.
The statute requires each law enforcement agency in the state to report incidents described in Chapter 10.118.030 RCW opens a new window (1)(a) through (t), as well as noted in subsection (3) “any additional incidents and data required by the statewide use of force data program developed in section 3, chapter 326, Laws of 2021”.
The approved recommendations (PDF) constitute the statewide use of force data program, as noted in Senate Bill 5259 (PDF) Section 3 (4). Including limited incident-based data on all calls for service was recommended by the state advisory group and approved by the Office of the Attorney General.
How many law enforcement agencies are in Washington?
Initially, WADEPS identified 301 agencies with general law enforcement authority operating within the state. Their areas of service include local, county, state, port, transit, airport, university, and tribal lands.
Twelve are state agencies with law enforcement divisions (not including the Washington State Patrol), two of which are prohibited from using force.
The 28 tribal police departments are encouraged but not required by state law to participate in the use-of-force data collection program.
Twelve are state agencies with law enforcement divisions (not including the Washington State Patrol), two of which are prohibited from using force.
The 28 tribal police departments are encouraged but not required by state law to participate in the use-of-force data collection program.
Don’t law enforcement agencies already collect data about policing activities?
Most agencies generate and collect information about calls for service and officer engagement—including the use of force— however, there are variations in methods and/or definitions and not all of the data is easily accessible by the public.
The WADEPS platform standardizes data collected on the use of force and makes it available so that agencies, policy makers, and engaged citizens can make useful analyses and comparisons.
The WADEPS platform standardizes data collected on the use of force and makes it available so that agencies, policy makers, and engaged citizens can make useful analyses and comparisons.
How much extra work will be required of agencies and officers?
Our goal is to make the required data collection process as seamless and efficient as possible for agencies and officers. WADEPS is working with agencies to leverage existing data collection processes in an effort to reduce duplicate data entry activities.
We are also working with volunteers from multiple agencies to design and review future automation opportunities for the sharing of both computer-aided dispatch data (CAD) and required use-of-force incident data.
We are also working with volunteers from multiple agencies to design and review future automation opportunities for the sharing of both computer-aided dispatch data (CAD) and required use-of-force incident data.
How will the data collection happen?
Agencies will be able to securely submit use-of-force incident data using a WADEPS custom CSV template, a WADEPS web application, and/or automatically through a managed solution with their dispatch center or public safety answering point software vendor.
Our goal is to automate as much of the data collection process as possible to reduce the administrative burden on officers and agencies and minimize duplication of processes already in place.
Our goal is to automate as much of the data collection process as possible to reduce the administrative burden on officers and agencies and minimize duplication of processes already in place.
Who submits the required data on use-of-force incidents?
The policy or protocol for each agency will determine who is responsible for providing incident data to WADEPS.
After use-of-force incident data is submitted to the WADEPS system, an agency-appointed supervisor must validate the information through the WADEPS Reporting Tool prior to the data being displayed in the public data dashboard.
After use-of-force incident data is submitted to the WADEPS system, an agency-appointed supervisor must validate the information through the WADEPS Reporting Tool prior to the data being displayed in the public data dashboard.
How often will data be added to WADEPS?
Use-of-force data, contextual incident-based dispatch (CAD) data, and agency compliance data will be updated monthly. Active officer rosters are updated twice per month. Other contextual data sets will be updated annually.
Potential data lag: Each agency will be able to adhere to its own data upload cycle within the mandatory reporting window. As a result, there may be instances of data lag. The data viewed on the dashboard will be the currently available information at the time, and will be subject to change as new data is received.
Potential data lag: Each agency will be able to adhere to its own data upload cycle within the mandatory reporting window. As a result, there may be instances of data lag. The data viewed on the dashboard will be the currently available information at the time, and will be subject to change as new data is received.
Will WADEPS provide context for use-of-force incidents?
Yes, a key feature of the WADEPS dashboard will be its contextual analysis capability. Adding contextual data to the WADEPS platform will enable users to compare “apples to apples” as well as identify nuances between agencies—similar to comparing Red Delicious® apples to Granny Smith apples, or McIntosh to Cosmic Crisp®.
Contextual data will include agency operational characteristics (such as the number of officers), local community characteristics, and socioeconomic indicators, and WADEPS is analyzing and coding agency use-of-force policies for better comparison. The limited incident-based computer-assisted dispatch (CAD) data for all calls for service will enable calculation of rates of force based on multiple factors.
WADEPS is not designed to answer questions perfectly. Rather, the information available through WADEPS will enable data discovery and encourage follow-up and research.
Contextual data will include agency operational characteristics (such as the number of officers), local community characteristics, and socioeconomic indicators, and WADEPS is analyzing and coding agency use-of-force policies for better comparison. The limited incident-based computer-assisted dispatch (CAD) data for all calls for service will enable calculation of rates of force based on multiple factors.
WADEPS is not designed to answer questions perfectly. Rather, the information available through WADEPS will enable data discovery and encourage follow-up and research.
What is CAD data?
CAD stands for computer-aided dispatch and refers to both the process and the computer software that many public safety agencies use to effectively and efficiently respond to calls for service. CAD software already logs many of the incident-related data points required in WADEPS.
How is CAD data transmitted to WADEPS?
The WADEPS program is not seeking full access to any agency’s CAD system. Only selected incident-based data elements will be ingested into the WADEPS database. This process will help automate part of the required use-of-force data collection process, making it easier and less burdensome for law enforcement officers and agencies, and providing valuable context about overall agency activity.
What about individual privacy?
The purpose of the dashboard is to identify trends and outcomes, not individual people or incidents. Data displayed in the dashboard and available as downloads from the WADEPS website will be de-identified. WADEPS is committed to balancing the need for accessible public safety data with the importance of protecting the individual privacy of both community members and officers.
Using recognized research-based protocols approved by the Washington State University Institutional Review Board opens a new window, personally identifiable information such as the specific physical address of the incident, individual names, and the unique incident number will be anonymized in the database, on the public data dashboard, and in downloaded data sets. This protocol protects community members, subjects, and officers alike.
Using recognized research-based protocols approved by the Washington State University Institutional Review Board opens a new window, personally identifiable information such as the specific physical address of the incident, individual names, and the unique incident number will be anonymized in the database, on the public data dashboard, and in downloaded data sets. This protocol protects community members, subjects, and officers alike.
What protections are in place to ensure agencies do not violate HIPAA?
Our research-based approach has been approved by the Washington State University Institutional Review Board opens a new window (IRB) and meets stringent standards for maintaining privacy within collected data.
WADEPS will only collect administrative records documenting the frequency and nature of police interactions with the public and when those interactions are associated with a reportable use of force. WADEPS will not collect personally identifiable information (PII) for those interacting with police.
WADEPS will only collect administrative records documenting the frequency and nature of police interactions with the public and when those interactions are associated with a reportable use of force. WADEPS will not collect personally identifiable information (PII) for those interacting with police.
FAQ: Data dashboard
What will I be able to see on the public data dashboard?
All users—community members, officers, agency administrators, and policymakers alike—have access to the same data and be able to select, view, compare, and download data related to law enforcement activities and the reportable use of force at the local, regional, and state level.
Users will be able to interact with the dashboard by selecting the type of data, the agencies to be included, and/or the time frame.
Users will be able to interact with the dashboard by selecting the type of data, the agencies to be included, and/or the time frame.
I need help understanding the data.
Funding for WADEPS includes a collaboration with the Center for Interdisciplinary Statistics Education and Research (CISER) at Washington State University to provide statistical education for all users.
Why does my local police department not have data?
Data for local agencies which are fully operated by another, often larger, law enforcement agency is reported by the parent organization. For example, the King County Sheriff’s Office provides operational services for 17 local agencies within the county, including police departments for the cities of Burien, Kenmore, Newcastle, SeaTac, and Woodinville, two transit authorities, and the King County airport.
The city in which an incident occurs is included in the data shared with WADEPS, however, officers are considered employees of the parent organization and the responding agency data is reported under the parent organization name.
Contracted agencies are noted in the “Who is Reporting” tab in the dashboard. Contact your local agency for operational details.
The city in which an incident occurs is included in the data shared with WADEPS, however, officers are considered employees of the parent organization and the responding agency data is reported under the parent organization name.
Contracted agencies are noted in the “Who is Reporting” tab in the dashboard. Contact your local agency for operational details.
What does “reporting status” mean?
WADEPS uses six categories when measuring participation and compliance with the law:
1. Required
2. Force Data Only
3. Contracted
4. Optional
5. Not Authorized to Use Force
6. Not Applicable
1. Required: An agency with general or limited law enforcement authority, operated by a governmental unit (municipal, county, state, etc.) within Washington state. Defined in RCW 10.118.020
2. Force Data Only: Several state agencies do not use computer-aided dispatch (CAD) or other methods to track officer-community interactions or calls for service. These agencies are excluded from rate of force calculations.
3. Contracted: An active law enforcement agency with its own local identity (such as police department uniform, patch, and/or vehicle graphics) but whose officers are officially employed by a larger parent agency. For example, the King County Sheriff’s Office provides all services and personnel for 17 smaller agencies such as the Woodinville Police Department and the Port of Seattle Police Department. Reportable use-of-force and CAD data for a “contracted” agency are included in the data received from its parent agency.
4. Optional: Tribal law enforcement agencies operating in Washington are not subject to state law but may opt to participate in data sharing with WADEPS.
5. Not Authorized to Use Force: State agencies with general or limited law enforcement authority whose officers are specifically not authorized to use force. These agencies are excluded from rate of force calculations.
6. Not Applicable: Agencies that are strictly administrative, inactive, or have been dissolved.
1. Required
2. Force Data Only
3. Contracted
4. Optional
5. Not Authorized to Use Force
6. Not Applicable
1. Required: An agency with general or limited law enforcement authority, operated by a governmental unit (municipal, county, state, etc.) within Washington state. Defined in RCW 10.118.020
2. Force Data Only: Several state agencies do not use computer-aided dispatch (CAD) or other methods to track officer-community interactions or calls for service. These agencies are excluded from rate of force calculations.
3. Contracted: An active law enforcement agency with its own local identity (such as police department uniform, patch, and/or vehicle graphics) but whose officers are officially employed by a larger parent agency. For example, the King County Sheriff’s Office provides all services and personnel for 17 smaller agencies such as the Woodinville Police Department and the Port of Seattle Police Department. Reportable use-of-force and CAD data for a “contracted” agency are included in the data received from its parent agency.
4. Optional: Tribal law enforcement agencies operating in Washington are not subject to state law but may opt to participate in data sharing with WADEPS.
5. Not Authorized to Use Force: State agencies with general or limited law enforcement authority whose officers are specifically not authorized to use force. These agencies are excluded from rate of force calculations.
6. Not Applicable: Agencies that are strictly administrative, inactive, or have been dissolved.
What does the “Who is Reporting?” data mean?
Every month, agencies subject to the state law are required to provide data about reportable uses of force (or indicate they have no reportable uses for the month) along with limited incident-based computer-aided dispatch (CAD) data for all calls for service.
Context is important.
1) Agencies have 30 days from the date of a reportable use-of-force incident to provide the required data to WADEPS. For example, an agency with a reportable event on April 27 has until May 26 to share the data with WADEPS.
2) Monthly reporting status tables are updated daily, but the overall percentage is based on the latest full-month that data should be complete. For example, the reporting completion percentage for the month of April is not calculated until June 1, after the 30-day reporting window has closed.
Similarly, calls-for-service (or CAD) data is expected on a monthly basis. For example, data for all of April is due the first week in May.
Context is important.
1) Agencies have 30 days from the date of a reportable use-of-force incident to provide the required data to WADEPS. For example, an agency with a reportable event on April 27 has until May 26 to share the data with WADEPS.
2) Monthly reporting status tables are updated daily, but the overall percentage is based on the latest full-month that data should be complete. For example, the reporting completion percentage for the month of April is not calculated until June 1, after the 30-day reporting window has closed.
Similarly, calls-for-service (or CAD) data is expected on a monthly basis. For example, data for all of April is due the first week in May.
What about incidents under investigation?
For reportable use-of-force incidents under internal or external investigation, the required incident and officer data and the administrative outcome must be provided to WADEPS within 30 days after the completion of the investigation. Data visualizations on the number of incidents under investigation are in development.
Can I download the data?
1. Raw data can be downloaded from each of the different dashboard views by clicking on the three vertical dots in the upper right corner of any section and selecting the format. Note that the data provided will reflect any selections made in the filters.
2. The full WADEPS reportable use-of-force data set is quite large, with more than 200 variables for each use-of-force record. It can be downloaded as one file. Click here to initiate an automatic download.
3. Summary CAD data is available upon request.
4. Contextual data about law enforcement agencies can be downloaded from the “Who’s Reporting” tab.
2. The full WADEPS reportable use-of-force data set is quite large, with more than 200 variables for each use-of-force record. It can be downloaded as one file. Click here to initiate an automatic download.
3. Summary CAD data is available upon request.
4. Contextual data about law enforcement agencies can be downloaded from the “Who’s Reporting” tab.