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

Hazards

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

Hazards: 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 (9% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
02,5005,0002009: 1,287 hazards calls logged in CAD2010: 2,277 hazards calls logged in CAD2011: 2,081 hazards calls logged in CAD2012: 2,162 hazards calls logged in CAD2013: 3,703 hazards calls logged in CAD2014: 4,462 hazards calls logged in CAD2015: 4,141 hazards calls logged in CAD2016: 4,295 hazards calls logged in CAD2017: 4,518 hazards calls logged in CAD2018: 4,188 hazards calls logged in CAD2019: 4,361 hazards calls logged in CAD2020: 2,980 hazards calls logged in CAD2021: 3,868 hazards calls logged in CAD2022: 3,548 hazards calls logged in CAD2023: 3,254 hazards calls logged in CAD2024: 3,767 hazards calls logged in CAD2025: 3,693 hazards calls logged in CAD2026: 2,311 hazards calls logged in CAD2009n=1,2872011n=2,0812013n=3,7032015n=4,1412017n=4,5182019n=4,3612021n=3,8682023n=3,2542025n=3,6932026n=2,311
hazards calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodHazards calls logged in CAD
20091,287
20102,277
20112,081
20122,162
20133,703
20144,462
20154,141
20164,295
20174,518
20184,188
20194,361
20202,980
20213,868
20223,548
20233,254
20243,767
20253,693
20262,311
Calls for Hazards Are Down 18% From Their 2017 PeakSeattle Police logged 4,518 hazards calls in 2017 and 3,693 in 2025, the most recent full year.

Hazards: 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: 0.3%2009 · Report taken, no arrest: 1.2%2009 · Resolved on scene: 74.0%2009 · Unable to locate: 21.3%2009 · Other (unfounded / cancelled): 3.1%2010 · Arrest / citation: 0.3%2010 · Report taken, no arrest: 2.3%2010 · Resolved on scene: 71.9%2010 · Unable to locate: 22.3%2010 · Other (unfounded / cancelled): 3.3%2011 · Arrest / citation: 0.1%2011 · Report taken, no arrest: 2.4%2011 · Resolved on scene: 75.6%2011 · Unable to locate: 18.1%2011 · Other (unfounded / cancelled): 3.8%2012 · Arrest / citation: 0.3%2012 · Report taken, no arrest: 1.7%2012 · Resolved on scene: 71.8%2012 · Unable to locate: 23.1%2012 · Other (unfounded / cancelled): 3.1%2013 · Arrest / citation: 0.1%2013 · Report taken, no arrest: 0.9%2013 · Resolved on scene: 81.9%2013 · Unable to locate: 12.9%2013 · Other (unfounded / cancelled): 4.2%2014 · Report taken, no arrest: 1.0%2014 · Resolved on scene: 83.2%2014 · Unable to locate: 13.9%2014 · Other (unfounded / cancelled): 1.9%2015 · Arrest / citation: 0.1%2015 · Report taken, no arrest: 1.4%2015 · Resolved on scene: 78.7%2015 · Unable to locate: 16.9%2015 · Other (unfounded / cancelled): 2.9%2016 · Arrest / citation: 0.2%2016 · Report taken, no arrest: 1.2%2016 · Resolved on scene: 76.2%2016 · Unable to locate: 20.3%2016 · Other (unfounded / cancelled): 2.2%2017 · Arrest / citation: 0.1%2017 · Report taken, no arrest: 1.3%2017 · Resolved on scene: 75.6%2017 · Unable to locate: 19.8%2017 · Other (unfounded / cancelled): 3.1%2018 · Arrest / citation: 0.2%2018 · Report taken, no arrest: 1.1%2018 · Resolved on scene: 71.0%2018 · Unable to locate: 23.9%2018 · Other (unfounded / cancelled): 3.7%2019 · Arrest / citation: 0.3%2019 · Report taken, no arrest: 1.2%2019 · Resolved on scene: 70.1%2019 · Unable to locate: 24.9%2019 · Other (unfounded / cancelled): 3.6%2020 · Arrest / citation: 0.1%2020 · Report taken, no arrest: 1.0%2020 · Resolved on scene: 69.8%2020 · Unable to locate: 25.5%2020 · Other (unfounded / cancelled): 3.6%2021 · Arrest / citation: 0.2%2021 · Report taken, no arrest: 1.6%2021 · Resolved on scene: 63.3%2021 · Unable to locate: 31.6%2021 · Other (unfounded / cancelled): 3.2%2022 · Arrest / citation: 0.2%2022 · Report taken, no arrest: 1.5%2022 · Resolved on scene: 58.9%2022 · Unable to locate: 36.3%2022 · Other (unfounded / cancelled): 3.1%2023 · Arrest / citation: 0.1%2023 · Report taken, no arrest: 1.3%2023 · Resolved on scene: 54.6%2023 · Unable to locate: 38.3%2023 · Other (unfounded / cancelled): 5.6%2024 · Arrest / citation: 0.2%2024 · Report taken, no arrest: 2.2%2024 · Resolved on scene: 51.2%2024 · Unable to locate: 42.6%2024 · Other (unfounded / cancelled): 3.9%2025 · Arrest / citation: 0.2%2025 · Report taken, no arrest: 1.6%2025 · Resolved on scene: 55.8%2025 · Unable to locate: 38.7%2025 · Other (unfounded / cancelled): 3.7%2026 · Arrest / citation: 0.2%2026 · Report taken, no arrest: 1.8%2026 · Resolved on scene: 54.1%2026 · Unable to locate: 40.4%2026 · Other (unfounded / cancelled): 3.5%2009n=1,2872011n=2,0812013n=3,7032015n=4,1412017n=4,5182019n=4,3612021n=3,8682023n=3,2542025n=3,6932026n=2,311
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 sceneUnable to locateOther (unfounded / cancelled)
20091,2870.3%1.2%74.0%21.3%3.1%
20102,2770.3%2.3%71.9%22.3%3.3%
20112,0810.1%2.4%75.6%18.1%3.8%
20122,1620.3%1.7%71.8%23.1%3.1%
20133,7030.1%0.9%81.9%12.9%4.2%
20144,462—1.0%83.2%13.9%1.9%
20154,1410.1%1.4%78.7%16.9%2.9%
20164,2950.2%1.2%76.2%20.3%2.2%
20174,5180.1%1.3%75.6%19.8%3.1%
20184,1880.2%1.1%71.0%23.9%3.7%
20194,3610.3%1.2%70.1%24.9%3.6%
20202,9800.1%1.0%69.8%25.5%3.6%
20213,8680.2%1.6%63.3%31.6%3.2%
20223,5480.2%1.5%58.9%36.3%3.1%
20233,2540.1%1.3%54.6%38.3%5.6%
20243,7670.2%2.2%51.2%42.6%3.9%
20253,6930.2%1.6%55.8%38.7%3.7%
20262,3110.2%1.8%54.1%40.4%3.5%
40% of Calls for Hazards End “Unable to Locate,” Up From 20%Report-taken outcomes moved from 1% of calls in 2016 to 2% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Hazards: 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 9% of hazards 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 min50 min100 min2009: 24.8 min2010: 19.3 min2011: 15.5 min2012: 18.6 min2013: 72.7 min2014: 44.6 min2015: 55.0 min2016: 51.7 min2017: 33.4 min2018: 40.9 min2019: 42.6 min2020: 41.8 min2021: 40.9 min2022: 51.1 min2023: 53.2 min2024: 68.8 min2025: 61.0 min2026: 57.5 min2009: 29.8 min2010: 25.8 min2011: 21.7 min2012: 25.5 min2013: 79.0 min2014: 48.2 min2015: 61.2 min2016: 59.5 min2017: 40.9 min2018: 47.5 min2019: 50.2 min2020: 49.6 min2021: 47.2 min2022: 57.9 min2023: 61.7 min2024: 76.0 min2025: 69.5 min2026: 66.6 min2009n=1,0882011n=1,6702013n=3,3942015n=3,8232017n=4,1022019n=3,9772021n=3,5452023n=2,9862025n=3,4672026n=2,158
Average response timeAverage dispatch delay
View as table
How long it took — same numbers as the chart above
PeriodCalled-in eventsAverage dispatch delayAverage response time
20091,08824.8 min29.8 min
20101,89619.3 min25.8 min
20111,67015.5 min21.7 min
20121,81418.6 min25.5 min
20133,39472.7 min79.0 min
20144,20044.6 min48.2 min
20153,82355.0 min61.2 min
20163,78151.7 min59.5 min
20174,10233.4 min40.9 min
20183,83040.9 min47.5 min
20193,97742.6 min50.2 min
20202,67141.8 min49.6 min
20213,54540.9 min47.2 min
20223,25951.1 min57.9 min
20232,98653.2 min61.7 min
20243,48568.8 min76.0 min
20253,46761.0 min69.5 min
20262,15857.5 min66.6 min
The Average Call Waits 67 Minutes for an Officer to ArriveDespite a 14% drop in calls between 2016 and 2025, average response time has increased 12% in the past 10 years, from 60 minutes in 2016 to 67 in 2026, driven largely by dispatch delays.
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.

Hazards: 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 9% of hazards 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: 12.0%2009 · 0–5 min: 11.9%2009 · 5–30 min: 53.0%2009 · 30–60 min: 12.2%2009 · 1–4 hr: 9.8%2009 · 4–8 hr: 1.0%2010 · No recorded response: 10.5%2010 · 0–5 min: 15.0%2010 · 5–30 min: 56.4%2010 · 30–60 min: 9.1%2010 · 1–4 hr: 8.3%2010 · 4–8 hr: 0.7%2010 · Over 8 hr: 0.1%2011 · No recorded response: 9.9%2011 · 0–5 min: 19.1%2011 · 5–30 min: 54.6%2011 · 30–60 min: 10.2%2011 · 1–4 hr: 5.9%2011 · 4–8 hr: 0.3%2011 · Over 8 hr: 0.1%2012 · No recorded response: 8.6%2012 · 0–5 min: 14.6%2012 · 5–30 min: 54.1%2012 · 30–60 min: 12.8%2012 · 1–4 hr: 9.5%2012 · 4–8 hr: 0.3%2012 · Over 8 hr: 0.1%2013 · No recorded response: 6.0%2013 · 0–5 min: 22.3%2013 · 5–30 min: 39.7%2013 · 30–60 min: 9.0%2013 · 1–4 hr: 14.7%2013 · 4–8 hr: 4.8%2013 · Over 8 hr: 3.6%2014 · No recorded response: 8.5%2014 · 0–5 min: 29.5%2014 · 5–30 min: 38.6%2014 · 30–60 min: 7.8%2014 · 1–4 hr: 10.0%2014 · 4–8 hr: 4.3%2014 · Over 8 hr: 1.3%2015 · No recorded response: 10.3%2015 · 0–5 min: 23.1%2015 · 5–30 min: 38.7%2015 · 30–60 min: 9.2%2015 · 1–4 hr: 12.8%2015 · 4–8 hr: 3.7%2015 · Over 8 hr: 2.3%2016 · No recorded response: 14.4%2016 · 0–5 min: 19.2%2016 · 5–30 min: 41.6%2016 · 30–60 min: 9.4%2016 · 1–4 hr: 11.5%2016 · 4–8 hr: 2.7%2016 · Over 8 hr: 1.3%2017 · No recorded response: 11.4%2017 · 0–5 min: 21.7%2017 · 5–30 min: 42.3%2017 · 30–60 min: 11.3%2017 · 1–4 hr: 10.6%2017 · 4–8 hr: 1.9%2017 · Over 8 hr: 0.9%2018 · No recorded response: 13.2%2018 · 0–5 min: 18.8%2018 · 5–30 min: 41.0%2018 · 30–60 min: 11.6%2018 · 1–4 hr: 11.8%2018 · 4–8 hr: 2.5%2018 · Over 8 hr: 1.0%2019 · No recorded response: 11.6%2019 · 0–5 min: 18.3%2019 · 5–30 min: 41.9%2019 · 30–60 min: 11.9%2019 · 1–4 hr: 12.1%2019 · 4–8 hr: 2.3%2019 · Over 8 hr: 1.8%2020 · No recorded response: 10.7%2020 · 0–5 min: 18.0%2020 · 5–30 min: 43.1%2020 · 30–60 min: 11.8%2020 · 1–4 hr: 12.4%2020 · 4–8 hr: 2.8%2020 · Over 8 hr: 1.3%2021 · No recorded response: 12.2%2021 · 0–5 min: 14.0%2021 · 5–30 min: 43.9%2021 · 30–60 min: 12.4%2021 · 1–4 hr: 14.6%2021 · 4–8 hr: 2.1%2021 · Over 8 hr: 0.8%2022 · No recorded response: 15.6%2022 · 0–5 min: 10.2%2022 · 5–30 min: 41.5%2022 · 30–60 min: 13.1%2022 · 1–4 hr: 15.9%2022 · 4–8 hr: 2.5%2022 · Over 8 hr: 1.2%2023 · No recorded response: 15.4%2023 · 0–5 min: 9.3%2023 · 5–30 min: 40.1%2023 · 30–60 min: 12.4%2023 · 1–4 hr: 18.2%2023 · 4–8 hr: 3.5%2023 · Over 8 hr: 1.1%2024 · No recorded response: 12.9%2024 · 0–5 min: 8.1%2024 · 5–30 min: 34.3%2024 · 30–60 min: 14.7%2024 · 1–4 hr: 23.6%2024 · 4–8 hr: 5.2%2024 · Over 8 hr: 1.3%2025 · No recorded response: 10.7%2025 · 0–5 min: 8.7%2025 · 5–30 min: 37.1%2025 · 30–60 min: 15.2%2025 · 1–4 hr: 22.4%2025 · 4–8 hr: 4.5%2025 · Over 8 hr: 1.3%2026 · No recorded response: 9.2%2026 · 0–5 min: 9.6%2026 · 5–30 min: 38.6%2026 · 30–60 min: 15.6%2026 · 1–4 hr: 21.3%2026 · 4–8 hr: 4.2%2026 · Over 8 hr: 1.4%2009n=1,0882011n=1,6702013n=3,3942015n=3,8232017n=4,1022019n=3,9772021n=3,5452023n=2,9862025n=3,4672026n=2,158
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
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
20091,08812.0%11.9%53.0%12.2%9.8%1.0%—
20101,89610.5%15.0%56.4%9.1%8.3%0.7%0.1%
20111,6709.9%19.1%54.6%10.2%5.9%0.3%0.1%
20121,8148.6%14.6%54.1%12.8%9.5%0.3%0.1%
20133,3946.0%22.3%39.7%9.0%14.7%4.8%3.6%
20144,2008.5%29.5%38.6%7.8%10.0%4.3%1.3%
20153,82310.3%23.1%38.7%9.2%12.8%3.7%2.3%
20163,78114.4%19.2%41.6%9.4%11.5%2.7%1.3%
20174,10211.4%21.7%42.3%11.3%10.6%1.9%0.9%
20183,83013.2%18.8%41.0%11.6%11.8%2.5%1.0%
20193,97711.6%18.3%41.9%11.9%12.1%2.3%1.8%
20202,67110.7%18.0%43.1%11.8%12.4%2.8%1.3%
20213,54512.2%14.0%43.9%12.4%14.6%2.1%0.8%
20223,25915.6%10.2%41.5%13.1%15.9%2.5%1.2%
20232,98615.4%9.3%40.1%12.4%18.2%3.5%1.1%
20243,48512.9%8.1%34.3%14.7%23.6%5.2%1.3%
20253,46710.7%8.7%37.1%15.2%22.4%4.5%1.3%
20262,1589.2%9.6%38.6%15.6%21.3%4.2%1.4%
27% of Calls Wait Over an Hour for an Officer27% of calls took more than an hour to get a response in 2026, compared with 15% in 2016.
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.