Seattle Police
Call volumeOutcomesHow long it tookHow long it took, in full

Bias

Bias calls over time: volume, outcomes, and response speed

Bias: Call Volume

Call volume is the number of events logged in the Seattle Police Department’s Computer-Aided Dispatch (CAD) system. It counts calls from the public (by 911, phone, text or alarm) as well as officer-initiated activity, once per event, grouped by the call type assigned when the call was dispatched, before any investigation. It is not the same as the number of crimes reported.

Included: Every event logged in CAD: calls from the public and events officers logged themselves (19% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
015302009: 11 bias calls logged in CAD2010: 5 bias calls logged in CAD2013: 2 bias calls logged in CAD2014: 9 bias calls logged in CAD2015: 5 bias calls logged in CAD2016: 6 bias calls logged in CAD2017: 10 bias calls logged in CAD2018: 16 bias calls logged in CAD2019: 9 bias calls logged in CAD2020: 8 bias calls logged in CAD2021: 16 bias calls logged in CAD2022: 14 bias calls logged in CAD2023: 11 bias calls logged in CAD2024: 15 bias calls logged in CAD2025: 26 bias calls logged in CAD2026: 13 bias calls logged in CAD2009n=112013n=22015n=52017n=102019n=92021n=162023n=112025n=262026n=13
bias calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodBias calls logged in CAD
200911
20105
20132
20149
20155
20166
201710
201816
20199
20208
202116
202214
202311
202415
202526
202613
Calls for Bias Average About 11 a YearSeattle Police logged 176 bias calls between 2009 and 2026, with a high of 26 in 2025.

Bias: What Happened When Officers Responded

Outcomes show how each call ended, based on the disposition officers recorded when the call was closed: an arrest or citation, a report taken with no arrest, resolved on scene, unable to locate (officers could not find the incident or the person who called), or other (unfounded or cancelled). Each bar shows the share of that period’s calls.

Included: Every event, called in or officer-initiated, using the disposition recorded when the event was closed. Excluded: Nothing.

Swipe sideways to see the full chart →
100%50%0%2009 · Arrest / citation: 9.1%2009 · Report taken, no arrest: 63.6%2009 · Resolved on scene: 18.2%2009 · Other (unfounded / cancelled): 9.1%2010 · Report taken, no arrest: 40.0%2010 · Unable to locate: 20.0%2010 · Other (unfounded / cancelled): 40.0%2013 · Report taken, no arrest: 100.0%2014 · Report taken, no arrest: 55.6%2014 · Resolved on scene: 11.1%2014 · Other (unfounded / cancelled): 33.3%2015 · Report taken, no arrest: 20.0%2015 · Other (unfounded / cancelled): 80.0%2016 · Report taken, no arrest: 33.3%2016 · Unable to locate: 16.7%2016 · Other (unfounded / cancelled): 50.0%2017 · Report taken, no arrest: 70.0%2017 · Other (unfounded / cancelled): 30.0%2018 · Report taken, no arrest: 87.5%2018 · Resolved on scene: 6.2%2018 · Other (unfounded / cancelled): 6.2%2019 · Report taken, no arrest: 44.4%2019 · Unable to locate: 11.1%2019 · Other (unfounded / cancelled): 44.4%2020 · Arrest / citation: 25.0%2020 · Report taken, no arrest: 25.0%2020 · Unable to locate: 12.5%2020 · Other (unfounded / cancelled): 37.5%2021 · Report taken, no arrest: 56.2%2021 · Other (unfounded / cancelled): 43.8%2022 · Arrest / citation: 14.3%2022 · Report taken, no arrest: 64.3%2022 · Unable to locate: 7.1%2022 · Other (unfounded / cancelled): 14.3%2023 · Report taken, no arrest: 63.6%2023 · Unable to locate: 9.1%2023 · Other (unfounded / cancelled): 27.3%2024 · Report taken, no arrest: 73.3%2024 · Resolved on scene: 6.7%2024 · Unable to locate: 6.7%2024 · Other (unfounded / cancelled): 13.3%2025 · Report taken, no arrest: 53.8%2025 · Resolved on scene: 11.5%2025 · Unable to locate: 15.4%2025 · Other (unfounded / cancelled): 19.2%2026 · Report taken, no arrest: 53.8%2026 · Unable to locate: 15.4%2026 · Other (unfounded / cancelled): 30.8%2009n=112013n=22015n=52017n=102019n=92021n=162023n=112025n=262026n=13
Arrest / citationReport taken, no arrestResolved on sceneUnable to locateOther (unfounded / cancelled)
View as table
What happened when officers responded — same numbers as the chart above
PeriodEventsArrest / citationReport taken, no arrestResolved on sceneOther (unfounded / cancelled)Unable to locate
2009119.1%63.6%18.2%9.1%—
20105—40.0%—40.0%20.0%
20132—100.0%———
20149—55.6%11.1%33.3%—
20155—20.0%—80.0%—
20166—33.3%—50.0%16.7%
201710—70.0%—30.0%—
201816—87.5%6.2%6.2%—
20199—44.4%—44.4%11.1%
2020825.0%25.0%—37.5%12.5%
202116—56.2%—43.8%—
20221414.3%64.3%—14.3%7.1%
202311—63.6%—27.3%9.1%
202415—73.3%6.7%13.3%6.7%
202526—53.8%11.5%19.2%15.4%
202613—53.8%—30.8%15.4%
7% of Calls for Bias End “Unable to Locate”Across 2009 to 2026, report-taken outcomes were 59% of calls. “Unable to locate” means officers could not find the incident or the person who called.

Bias: How Long It Took

Response time is how long it took, from the moment a called-in event was queued with dispatch, until the first officer arrived on scene. Dispatch delay is the first part of that wait: the time before an officer was assigned and sent. Both lines show the average, which a small number of very long waits pull up, so it runs higher than the typical (median) call.

Included: Only events called in by the public and dispatched to an officer. The averages use those with a recorded officer arrival. The n= under each bar is the number of called-in events. Excluded: Events officers logged themselves (on view), which are 19% of bias events, because they have no wait. Called-in events with no recorded arrival (for example, cancelled before an officer arrived) are left out of the averages. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
0 min200 min400 min2009: 21.4 min2010: 25.1 min2013: 27.8 min2014: 182.0 min2015: 42.2 min2016: 9.5 min2017: 72.9 min2018: 56.9 min2019: 40.8 min2020: 50.6 min2021: 84.4 min2022: 110.4 min2023: 70.4 min2024: 98.3 min2025: 213.6 min2026: 50.1 min2009: 28.7 min2010: 38.1 min2013: 33.8 min2014: 359.3 min2015: 52.1 min2016: 18.9 min2017: 91.7 min2018: 38.9 min2019: 48.7 min2020: 93.3 min2021: 110.6 min2022: 117.0 min2023: 61.8 min2024: 108.0 min2025: 244.8 min2026: 46.4 min2009n=112013n=22015n=52017n=92019n=82021n=132023n=112025n=192026n=12
Average response timeAverage dispatch delay
Small sample: Only a small share of bias events are called in. The year with the fewest had only 2, so averages can swing widely; the n= under each year shows its count.
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
20091121.4 min28.7 min
2010425.1 min38.1 min
2013227.8 min33.8 min
20142182.0 min359.3 min
2015542.2 min52.1 min
201639.5 min18.9 min
2017972.9 min91.7 min
20181356.9 min38.9 min
2019840.8 min48.7 min
2020650.6 min93.3 min
20211384.4 min110.6 min
202212110.4 min117.0 min
20231170.4 min61.8 min
20241398.3 min108.0 min
202519213.6 min244.8 min
20261250.1 min46.4 min
36% of Called-In Calls for Bias Get a Response Within 30 Minutes5% were answered in under 5 minutes, across all years on record.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

Bias: How Long It Took, in Full

The same response times, broken into bands so the slowest calls are visible. Each bar shows the share of called-in events by how long the first officer took to arrive after the event was queued, including the ones that took hours. “No recorded response” means no arrival was ever logged.

Included: Only events called in by the public and dispatched to an officer, including those with no recorded arrival (shown as “No recorded response”). Excluded: Events officers logged themselves (on view), which are 19% of bias events, because they have no wait. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
100%50%0%2009 · No recorded response: 9.1%2009 · 0–5 min: 9.1%2009 · 5–30 min: 54.5%2009 · 30–60 min: 18.2%2009 · 1–4 hr: 9.1%2010 · No recorded response: 25.0%2010 · 5–30 min: 25.0%2010 · 30–60 min: 50.0%2013 · 5–30 min: 50.0%2013 · 30–60 min: 50.0%2014 · No recorded response: 50.0%2014 · 4–8 hr: 50.0%2015 · No recorded response: 40.0%2015 · 0–5 min: 20.0%2015 · 1–4 hr: 40.0%2016 · No recorded response: 33.3%2016 · 5–30 min: 66.7%2017 · No recorded response: 33.3%2017 · 5–30 min: 33.3%2017 · 30–60 min: 11.1%2017 · 1–4 hr: 11.1%2017 · 4–8 hr: 11.1%2018 · No recorded response: 7.7%2018 · 5–30 min: 53.8%2018 · 30–60 min: 23.1%2018 · 1–4 hr: 15.4%2019 · No recorded response: 25.0%2019 · 5–30 min: 50.0%2019 · 30–60 min: 12.5%2019 · 1–4 hr: 12.5%2020 · No recorded response: 33.3%2020 · 0–5 min: 16.7%2020 · 5–30 min: 33.3%2020 · 4–8 hr: 16.7%2021 · No recorded response: 38.5%2021 · 5–30 min: 15.4%2021 · 30–60 min: 15.4%2021 · 1–4 hr: 30.8%2022 · 5–30 min: 33.3%2022 · 1–4 hr: 50.0%2022 · 4–8 hr: 16.7%2023 · No recorded response: 36.4%2023 · 0–5 min: 9.1%2023 · 5–30 min: 18.2%2023 · 30–60 min: 9.1%2023 · 1–4 hr: 27.3%2024 · No recorded response: 23.1%2024 · 5–30 min: 7.7%2024 · 30–60 min: 23.1%2024 · 1–4 hr: 38.5%2024 · 4–8 hr: 7.7%2025 · No recorded response: 31.6%2025 · 0–5 min: 10.5%2025 · 5–30 min: 26.3%2025 · 1–4 hr: 10.5%2025 · 4–8 hr: 10.5%2025 · Over 8 hr: 10.5%2026 · No recorded response: 33.3%2026 · 0–5 min: 8.3%2026 · 5–30 min: 33.3%2026 · 1–4 hr: 25.0%2009n=112013n=22015n=52017n=92019n=82021n=132023n=112025n=192026n=12
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of bias events are called in. The year with the fewest had only 2, so shares can swing widely; the n= under each year shows its count.
View as table
How long it took, in full — including the calls that took hours — same numbers as the chart above
PeriodCalled-in eventsNo recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
2009119.1%9.1%54.5%18.2%9.1%——
2010425.0%—25.0%50.0%———
20132——50.0%50.0%———
2014250.0%————50.0%—
2015540.0%20.0%——40.0%——
2016333.3%—66.7%————
2017933.3%—33.3%11.1%11.1%11.1%—
2018137.7%—53.8%23.1%15.4%——
2019825.0%—50.0%12.5%12.5%——
2020633.3%16.7%33.3%——16.7%—
20211338.5%—15.4%15.4%30.8%——
202212——33.3%—50.0%16.7%—
20231136.4%9.1%18.2%9.1%27.3%——
20241323.1%—7.7%23.1%38.5%7.7%—
20251931.6%10.5%26.3%—10.5%10.5%10.5%
20261233.3%8.3%33.3%—25.0%——
28% of Called-In Calls for Bias Wait Over an Hour for a ResponseAcross 2009 to 2026, 28% of called-in events took more than an hour to get a response.
Call priority (SPD Policy 4.065)
Priority 1 · Immediate
Poses a threat to life.
Priority 2 · Urgent
Situations that could escalate if help does not arrive soon.
Priority 3 · Prompt
Response time is not critical; usually a victim waiting to speak with officers.
All calls
Also includes priorities 4 to 9: lower-priority requests, callback reports, and automatic entries such as traffic stops and administrative codes.

“CAD” is Computer-Aided Dispatch, the system Seattle Police use to log and time every call for service — every number on this page comes from it. 2009 and 2026 may be partial years (data begins mid-2009; the latest year runs through the site's last data pull). “n=” under each year is the number of events logged that year in the volume and outcomes charts, and the number of called-in events dispatched to an officer in the response-time charts. Events officers log themselves (on view) are included in volume and outcomes and left out of response times, because they have no wait. The response-time bands measure time from call queued to first unit on scene; “no recorded response” means no arrival was ever logged. Hover any point for its exact value.