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

Crisis Complaint

Crisis Complaint calls over time: volume, outcomes, and response speed

Crisis Complaint: 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 →
010,00020,0002009: 3,467 crisis complaint calls logged in CAD2010: 6,583 crisis complaint calls logged in CAD2011: 7,242 crisis complaint calls logged in CAD2012: 8,124 crisis complaint calls logged in CAD2013: 8,826 crisis complaint calls logged in CAD2014: 8,940 crisis complaint calls logged in CAD2015: 9,845 crisis complaint calls logged in CAD2016: 10,199 crisis complaint calls logged in CAD2017: 10,501 crisis complaint calls logged in CAD2018: 11,089 crisis complaint calls logged in CAD2019: 11,077 crisis complaint calls logged in CAD2020: 10,704 crisis complaint calls logged in CAD2021: 12,089 crisis complaint calls logged in CAD2022: 13,292 crisis complaint calls logged in CAD2023: 14,134 crisis complaint calls logged in CAD2024: 13,674 crisis complaint calls logged in CAD2025: 13,820 crisis complaint calls logged in CAD2026: 9,183 crisis complaint calls logged in CAD2009n=3,4672011n=7,2422013n=8,8262015n=9,8452017n=10,5012019n=11,0772021n=12,0892023n=14,1342025n=13,8202026n=9,183
crisis complaint calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodCrisis complaint calls logged in CAD
20093,467
20106,583
20117,242
20128,124
20138,826
20148,940
20159,845
201610,199
201710,501
201811,089
201911,077
202010,704
202112,089
202213,292
202314,134
202413,674
202513,820
20269,183
Crisis Complaint Calls Are Holding Near Their PeakSeattle Police logged 13,820 crisis complaint calls in 2025, the most recent full year, close to the 14,134 in 2023.

Crisis Complaint: 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: 1.4%2009 · Report taken, no arrest: 40.1%2009 · Resolved on scene: 49.5%2009 · Unable to locate: 7.2%2009 · Other (unfounded / cancelled): 1.8%2010 · Arrest / citation: 1.1%2010 · Report taken, no arrest: 42.3%2010 · Resolved on scene: 48.3%2010 · Unable to locate: 6.7%2010 · Other (unfounded / cancelled): 1.6%2011 · Arrest / citation: 0.5%2011 · Report taken, no arrest: 44.0%2011 · Resolved on scene: 47.1%2011 · Unable to locate: 7.2%2011 · Other (unfounded / cancelled): 1.2%2012 · Arrest / citation: 0.5%2012 · Report taken, no arrest: 39.9%2012 · Resolved on scene: 51.1%2012 · Unable to locate: 7.2%2012 · Other (unfounded / cancelled): 1.1%2013 · Arrest / citation: 0.6%2013 · Report taken, no arrest: 40.8%2013 · Resolved on scene: 49.3%2013 · Unable to locate: 8.1%2013 · Other (unfounded / cancelled): 1.3%2014 · Arrest / citation: 0.6%2014 · Report taken, no arrest: 51.4%2014 · Resolved on scene: 38.0%2014 · Unable to locate: 8.8%2014 · Other (unfounded / cancelled): 1.2%2015 · Arrest / citation: 0.5%2015 · Report taken, no arrest: 68.6%2015 · Resolved on scene: 21.5%2015 · Unable to locate: 8.2%2015 · Other (unfounded / cancelled): 1.3%2016 · Arrest / citation: 0.4%2016 · Report taken, no arrest: 74.5%2016 · Resolved on scene: 14.9%2016 · Unable to locate: 8.6%2016 · Other (unfounded / cancelled): 1.6%2017 · Arrest / citation: 0.7%2017 · Report taken, no arrest: 77.1%2017 · Resolved on scene: 12.3%2017 · Unable to locate: 8.1%2017 · Other (unfounded / cancelled): 1.9%2018 · Arrest / citation: 0.7%2018 · Report taken, no arrest: 80.5%2018 · Resolved on scene: 10.1%2018 · Unable to locate: 7.0%2018 · Other (unfounded / cancelled): 1.6%2019 · Arrest / citation: 0.8%2019 · Report taken, no arrest: 76.3%2019 · Resolved on scene: 11.9%2019 · Unable to locate: 9.1%2019 · Other (unfounded / cancelled): 1.9%2020 · Arrest / citation: 0.6%2020 · Report taken, no arrest: 75.0%2020 · Resolved on scene: 12.8%2020 · Unable to locate: 9.9%2020 · Other (unfounded / cancelled): 1.8%2021 · Arrest / citation: 0.3%2021 · Report taken, no arrest: 72.3%2021 · Resolved on scene: 13.8%2021 · Unable to locate: 11.7%2021 · Other (unfounded / cancelled): 1.9%2022 · Arrest / citation: 0.4%2022 · Report taken, no arrest: 63.8%2022 · Resolved on scene: 15.5%2022 · Unable to locate: 18.7%2022 · Other (unfounded / cancelled): 1.6%2023 · Arrest / citation: 0.4%2023 · Report taken, no arrest: 59.3%2023 · Resolved on scene: 15.3%2023 · Unable to locate: 23.2%2023 · Other (unfounded / cancelled): 1.8%2024 · Arrest / citation: 0.5%2024 · Report taken, no arrest: 53.3%2024 · Resolved on scene: 17.3%2024 · Unable to locate: 27.2%2024 · Other (unfounded / cancelled): 1.7%2025 · Arrest / citation: 0.4%2025 · Report taken, no arrest: 47.7%2025 · Resolved on scene: 21.4%2025 · Unable to locate: 28.7%2025 · Other (unfounded / cancelled): 1.8%2026 · Arrest / citation: 0.6%2026 · Report taken, no arrest: 50.0%2026 · Resolved on scene: 20.5%2026 · Unable to locate: 27.2%2026 · Other (unfounded / cancelled): 1.7%2009n=3,4672011n=7,2422013n=8,8262015n=9,8452017n=10,5012019n=11,0772021n=12,0892023n=14,1342025n=13,8202026n=9,183
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)
20093,4671.4%40.1%49.5%7.2%1.8%
20106,5831.1%42.3%48.3%6.7%1.6%
20117,2420.5%44.0%47.1%7.2%1.2%
20128,1240.5%39.9%51.1%7.2%1.1%
20138,8260.6%40.8%49.3%8.1%1.3%
20148,9400.6%51.4%38.0%8.8%1.2%
20159,8450.5%68.6%21.5%8.2%1.3%
201610,1990.4%74.5%14.9%8.6%1.6%
201710,5010.7%77.1%12.3%8.1%1.9%
201811,0890.7%80.5%10.1%7.0%1.6%
201911,0770.8%76.3%11.9%9.1%1.9%
202010,7040.6%75.0%12.8%9.9%1.8%
202112,0890.3%72.3%13.8%11.7%1.9%
202213,2920.4%63.8%15.5%18.7%1.6%
202314,1340.4%59.3%15.3%23.2%1.8%
202413,6740.5%53.3%17.3%27.2%1.7%
202513,8200.4%47.7%21.4%28.7%1.8%
20269,1830.6%50.0%20.5%27.2%1.7%
27% of Crisis Complaint Calls End “Unable to Locate,” Up From 9%Report-taken outcomes moved from 74% of calls in 2016 to 50% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Crisis Complaint: 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 crisis complaint 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 min75 min150 min2009: 14.0 min2010: 12.0 min2011: 12.7 min2012: 16.5 min2013: 17.4 min2014: 20.2 min2015: 22.0 min2016: 18.1 min2017: 19.7 min2018: 23.3 min2019: 27.8 min2020: 27.5 min2021: 43.7 min2022: 57.0 min2023: 74.4 min2024: 112.1 min2025: 104.6 min2026: 84.9 min2009: 19.5 min2010: 17.6 min2011: 18.6 min2012: 22.5 min2013: 23.8 min2014: 26.9 min2015: 28.5 min2016: 24.8 min2017: 26.5 min2018: 31.0 min2019: 35.4 min2020: 35.9 min2021: 50.7 min2022: 59.2 min2023: 77.0 min2024: 114.6 min2025: 107.0 min2026: 86.8 min2009n=3,0202011n=6,3052013n=7,9152015n=8,8372017n=9,5812019n=10,0852021n=11,3682023n=13,2702025n=12,9432026n=8,595
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
20093,02014.0 min19.5 min
20105,64512.0 min17.6 min
20116,30512.7 min18.6 min
20127,22516.5 min22.5 min
20137,91517.4 min23.8 min
20148,13420.2 min26.9 min
20158,83722.0 min28.5 min
20169,13418.1 min24.8 min
20179,58119.7 min26.5 min
201810,00023.3 min31.0 min
201910,08527.8 min35.4 min
20209,93127.5 min35.9 min
202111,36843.7 min50.7 min
202212,49857.0 min59.2 min
202313,27074.4 min77.0 min
202412,719112.1 min114.6 min
202512,943104.6 min107.0 min
20268,59584.9 min86.8 min
The Average Call Waits 87 Minutes for an Officer to ArriveAs calls rose 36% between 2016 and 2025, average response time has grown about 4-fold in the past 10 years, from 25 minutes in 2016 to 87 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.

Crisis Complaint: 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 crisis complaint 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: 3.0%2009 · 0–5 min: 25.2%2009 · 5–30 min: 56.6%2009 · 30–60 min: 8.3%2009 · 1–4 hr: 6.6%2009 · 4–8 hr: 0.3%2009 · Over 8 hr: 0.0%2010 · No recorded response: 2.5%2010 · 0–5 min: 29.2%2010 · 5–30 min: 55.3%2010 · 30–60 min: 6.9%2010 · 1–4 hr: 5.7%2010 · 4–8 hr: 0.4%2010 · Over 8 hr: 0.0%2011 · No recorded response: 2.5%2011 · 0–5 min: 28.2%2011 · 5–30 min: 55.3%2011 · 30–60 min: 7.5%2011 · 1–4 hr: 6.2%2011 · 4–8 hr: 0.4%2011 · Over 8 hr: 0.0%2012 · No recorded response: 3.0%2012 · 0–5 min: 25.2%2012 · 5–30 min: 53.9%2012 · 30–60 min: 9.2%2012 · 1–4 hr: 8.0%2012 · 4–8 hr: 0.6%2012 · Over 8 hr: 0.0%2013 · No recorded response: 2.7%2013 · 0–5 min: 25.2%2013 · 5–30 min: 53.6%2013 · 30–60 min: 9.1%2013 · 1–4 hr: 8.6%2013 · 4–8 hr: 0.7%2013 · Over 8 hr: 0.1%2014 · No recorded response: 2.3%2014 · 0–5 min: 22.9%2014 · 5–30 min: 56.0%2014 · 30–60 min: 8.6%2014 · 1–4 hr: 9.0%2014 · 4–8 hr: 1.1%2014 · Over 8 hr: 0.2%2015 · No recorded response: 2.4%2015 · 0–5 min: 22.4%2015 · 5–30 min: 56.2%2015 · 30–60 min: 8.6%2015 · 1–4 hr: 8.9%2015 · 4–8 hr: 1.2%2015 · Over 8 hr: 0.3%2016 · No recorded response: 2.4%2016 · 0–5 min: 21.9%2016 · 5–30 min: 57.1%2016 · 30–60 min: 8.8%2016 · 1–4 hr: 9.0%2016 · 4–8 hr: 0.8%2016 · Over 8 hr: 0.1%2017 · No recorded response: 2.5%2017 · 0–5 min: 21.3%2017 · 5–30 min: 57.0%2017 · 30–60 min: 8.8%2017 · 1–4 hr: 9.3%2017 · 4–8 hr: 1.0%2017 · Over 8 hr: 0.2%2018 · No recorded response: 2.3%2018 · 0–5 min: 19.7%2018 · 5–30 min: 57.2%2018 · 30–60 min: 8.8%2018 · 1–4 hr: 10.2%2018 · 4–8 hr: 1.5%2018 · Over 8 hr: 0.3%2019 · No recorded response: 3.2%2019 · 0–5 min: 18.6%2019 · 5–30 min: 54.5%2019 · 30–60 min: 9.0%2019 · 1–4 hr: 12.3%2019 · 4–8 hr: 2.0%2019 · Over 8 hr: 0.4%2020 · No recorded response: 3.6%2020 · 0–5 min: 16.4%2020 · 5–30 min: 55.4%2020 · 30–60 min: 9.7%2020 · 1–4 hr: 12.5%2020 · 4–8 hr: 2.1%2020 · Over 8 hr: 0.3%2021 · No recorded response: 5.7%2021 · 0–5 min: 13.0%2021 · 5–30 min: 51.9%2021 · 30–60 min: 9.9%2021 · 1–4 hr: 15.0%2021 · 4–8 hr: 3.4%2021 · Over 8 hr: 1.1%2022 · No recorded response: 8.9%2022 · 0–5 min: 12.0%2022 · 5–30 min: 46.6%2022 · 30–60 min: 10.3%2022 · 1–4 hr: 16.8%2022 · 4–8 hr: 4.1%2022 · Over 8 hr: 1.2%2023 · No recorded response: 10.5%2023 · 0–5 min: 10.9%2023 · 5–30 min: 44.8%2023 · 30–60 min: 9.4%2023 · 1–4 hr: 16.2%2023 · 4–8 hr: 5.4%2023 · Over 8 hr: 2.8%2024 · No recorded response: 10.0%2024 · 0–5 min: 8.1%2024 · 5–30 min: 38.4%2024 · 30–60 min: 9.9%2024 · 1–4 hr: 20.6%2024 · 4–8 hr: 7.8%2024 · Over 8 hr: 5.2%2025 · No recorded response: 9.9%2025 · 0–5 min: 9.2%2025 · 5–30 min: 37.3%2025 · 30–60 min: 11.0%2025 · 1–4 hr: 21.0%2025 · 4–8 hr: 7.2%2025 · Over 8 hr: 4.4%2026 · No recorded response: 8.3%2026 · 0–5 min: 10.9%2026 · 5–30 min: 40.6%2026 · 30–60 min: 11.1%2026 · 1–4 hr: 19.6%2026 · 4–8 hr: 6.4%2026 · Over 8 hr: 3.1%2009n=3,0202011n=6,3052013n=7,9152015n=8,8372017n=9,5812019n=10,0852021n=11,3682023n=13,2702025n=12,9432026n=8,595
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
20093,0203.0%25.2%56.6%8.3%6.6%0.3%0.0%
20105,6452.5%29.2%55.3%6.9%5.7%0.4%0.0%
20116,3052.5%28.2%55.3%7.5%6.2%0.4%0.0%
20127,2253.0%25.2%53.9%9.2%8.0%0.6%0.0%
20137,9152.7%25.2%53.6%9.1%8.6%0.7%0.1%
20148,1342.3%22.9%56.0%8.6%9.0%1.1%0.2%
20158,8372.4%22.4%56.2%8.6%8.9%1.2%0.3%
20169,1342.4%21.9%57.1%8.8%9.0%0.8%0.1%
20179,5812.5%21.3%57.0%8.8%9.3%1.0%0.2%
201810,0002.3%19.7%57.2%8.8%10.2%1.5%0.3%
201910,0853.2%18.6%54.5%9.0%12.3%2.0%0.4%
20209,9313.6%16.4%55.4%9.7%12.5%2.1%0.3%
202111,3685.7%13.0%51.9%9.9%15.0%3.4%1.1%
202212,4988.9%12.0%46.6%10.3%16.8%4.1%1.2%
202313,27010.5%10.9%44.8%9.4%16.2%5.4%2.8%
202412,71910.0%8.1%38.4%9.9%20.6%7.8%5.2%
202512,9439.9%9.2%37.3%11.0%21.0%7.2%4.4%
20268,5958.3%10.9%40.6%11.1%19.6%6.4%3.1%
The Average Call Waits 85 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 85 minutes in 2026, more than double what it was in 2016. 29% of calls took more than an hour to get a response in 2026, compared with 10% 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.