The Data Dashboard
Washington State Data Exchange for Public Safety
Introduction
Powered by leading data analytics technology, the WADEPS dashboard is a central repository of data about reportable use-of-force incidents and police-community interactions alongside contextualized data about community and agency characteristics.
The primary focus of the dashboard is the rate of force, which is a percentage of total police interactions.
The primary focus of the dashboard is the rate of force, which is a percentage of total police interactions.
Rate of Force
equals
Number of reportable use-of-force incidents
divided by
Total number of calls for service.
For example, 10 uses of force divided by 1,000 calls for service = a 1% rate of force.
* Watch a brief video about rates vs counts. *
Eight dashboard tabs provide visitors with different views of the overall data set to review data by agency, look at aggregated data for the entire state or a single county, explore the circumstances in which force was used, and more.
Each of the tabs includes individual filters for a wide variety of data points and the ability to select a date range: click on the dark gray “Control” bar at the top of each tab. Filters include details such as:
Each of the tabs includes individual filters for a wide variety of data points and the ability to select a date range: click on the dark gray “Control” bar at the top of each tab. Filters include details such as:
- Incident call type (why contact was initiated)
- Type of force used during the incident
- Location characteristics of the incident (indoor, outdoor, etc.)
- Officers on scene
- Arrest details
- Injury details
- Subject demographics
- Officer demographics
Raw data can be downloaded from each view: click on the three vertical dots at the top of the table of data and select a format. The entire WADEPS data set is available in one file upon request.
About the Dashboard
The WADEPS data dashboard is an incident-based rate-of-force tool which requires data about use-of-force incidents AND all calls for service to provide useful and meaningful analysis.
Eight tabs provide visitors with different ways to look at the data provided to WADEPS by law enforcement agencies in Washington state. Note: Changing filter selections will refresh the visible data. This may take a few seconds to refresh on the screen.
The dashboard is best viewed on a laptop or desktop computer.
Eight tabs provide visitors with different ways to look at the data provided to WADEPS by law enforcement agencies in Washington state. Note: Changing filter selections will refresh the visible data. This may take a few seconds to refresh on the screen.
The dashboard is best viewed on a laptop or desktop computer.
Participation
Monthly data only.
A map visualization of agency participation and compliance, available by county or by city.
A map visualization of agency participation and compliance, available by county or by city.
Overview Tab: Rate of Force
Combines reportable use-of-force incident data with incident-based computer-aided dispatch (CAD) data for all calls for service to calculate a rate of force. The default view is statewide. Enables users to draw insights by county, city, or agency during a selected time frame.
Data blocks include:
Data blocks include:
- Top Row :
Three statistics for Calls for Service (CAD data), Use-of-Force Incident count, and the overall Rate of Force for the selected filters. - Rate of Force by County (ROF):
A horizontal bar chart showing ROF for counties from highest to lowest.
NOTE: Only displays data for agencies who provided both CAD and UOF data. - Incidents of Force Used by Month:
Shows the monthly count of all incidents as a vertical bar chart. - Use-of-Force by Incident Type:
A horizontal bar chart of the initial primary reason for the police contact. - Weapon/Tool Deployment:
A horizontal bar chart of a subset of reportable force used. - Proximity/Contact Force:
A horizontal bar chart of a subset of reportable force used. - Rate of Force by Agency
A table view of data received by each agency and its associated rate of force.
Map View
View of use-of-force incident data, CAD data for all calls for service, and contextual data (such as socio-economic demographics and agency characteristics) on side-by-side maps.
Using drop-down controls above two side-by-side maps, users can select Rate of Force by county or Raw Count by County or by City. Tabular data is shown below the map. Rate of Force is not available by city at this time.
Left-side map: Rate of Force data.
Right-side map: Contextual data from the U.S. Census.
Using drop-down controls above two side-by-side maps, users can select Rate of Force by county or Raw Count by County or by City. Tabular data is shown below the map. Rate of Force is not available by city at this time.
Left-side map: Rate of Force data.
Right-side map: Contextual data from the U.S. Census.
Incident and Force Table
Details about the incident (when, where, why) and the type of force used. This view offers more than 60 data filters. Visible data is a subset of the full WADEPS database.
Subject Demographics & Outcomes Table
Details about the individual upon whom force was used, including threats to self or others, resistance, whether or not armed, injury, and incident details (when, where, agency involved) and the type of force used. This view offers more than 70 data filters. Visible data is a subset of the full WADEPS database.
Incident Classification Table
Additional details about the incident (when, where, why). This view offers more than 60 data filters. Visible data is a subset of the full WADEPS database.
Arrest Details Table
Details about whether the individual upon whom force was used was arrested and why. This view offers more than 60 data filters. Visible data is a subset of the full WADEPS database.
Officer Analysis Table
Details about the officer who applied force to an individual. This view offers more than 40 data filters. Visible data is a subset of the full WADEPS database.
Additional information
Why isn’t my local police department listed?
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 16 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.
Please 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.
Please contact your local agency for operational details.
What does the participation data mean?
Every month, agencies subject to the state law are required to provide data about reportable use-of-force incidents or indicate they have no reportable incidents for the month along with limited incident-based CAD data for all calls for service.
Participation is assessed on a monthly basis and does not account for data lag. Context is important.
For example, agencies have 30 days from the date of a reportable use-of-force incident to provide the data to WADEPS. An agency with zero reportable incidents in March, but two reportable incidents on April 15 and 27 has until May 14 and 26 to share the data with WADEPS. Additionally CAD data for April is due the first week in May. Therefore, the participation data for that agency during April may appear out of compliance until the use-of-force incident data is received and the CAD data for March is processed.
Participation is assessed on a monthly basis and does not account for data lag. Context is important.
For example, agencies have 30 days from the date of a reportable use-of-force incident to provide the data to WADEPS. An agency with zero reportable incidents in March, but two reportable incidents on April 15 and 27 has until May 14 and 26 to share the data with WADEPS. Additionally CAD data for April is due the first week in May. Therefore, the participation data for that agency during April may appear out of compliance until the use-of-force incident data is received and the CAD data for March is processed.
Can I download the data?
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 the table section and selecting the format. Note that the data downloaded will reflect any selections made in the filters available for that tab. The full WADEPS use-of-force data set is available in one file upon request.
Contextual data about law enforcement agencies is included in the Participation tab.
Contextual data about communities are mirrored from external sources:
* U.S. Census is available at census.gov
Contextual data about law enforcement agencies is included in the Participation tab.
Contextual data about communities are mirrored from external sources:
* U.S. Census is available at census.gov
Data available is from September 1, 2025, onward.
CAD data for September is due in October and is required to calculate Rates of Force.
* Agencies are still in the process of providing CAD data and WADEPS will add the data as it is processed. The addition of CAD data will affect the rate of force calculations.
* Agencies have up to 30 days from the date of a reportable use-of-force incident to provide data to WADEPS.
Potential Data Lag
The data displayed and available for download will be the most accurate in the WADEPS system at the time and is subject to change.
Each agency may adhere to its own data upload cycle within the mandatory reporting window. As a result, there may be instances of data lag. For example, a reportable use of force occurring on March 1 may not appear for several weeks. Not only do agencies have 30 days to submit the required incident data to WADEPS, some additional time may be required for the verification process within the WADEPS Reporting Tool.