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

Assist Other Agency

Assist Other Agency calls over time: volume, outcomes, and response speed

Assist Other Agency: 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 (27% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
010,00020,0002009: 4,272 assist other agency calls logged in CAD2010: 7,613 assist other agency calls logged in CAD2011: 7,828 assist other agency calls logged in CAD2012: 7,554 assist other agency calls logged in CAD2013: 7,848 assist other agency calls logged in CAD2014: 7,827 assist other agency calls logged in CAD2015: 8,277 assist other agency calls logged in CAD2016: 9,033 assist other agency calls logged in CAD2017: 9,992 assist other agency calls logged in CAD2018: 10,402 assist other agency calls logged in CAD2019: 11,555 assist other agency calls logged in CAD2020: 10,096 assist other agency calls logged in CAD2021: 9,396 assist other agency calls logged in CAD2022: 11,386 assist other agency calls logged in CAD2023: 14,351 assist other agency calls logged in CAD2024: 12,664 assist other agency calls logged in CAD2025: 13,483 assist other agency calls logged in CAD2026: 9,149 assist other agency calls logged in CAD2009n=4,2722011n=7,8282013n=7,8482015n=8,2772017n=9,9922019n=11,5552021n=9,3962023n=14,3512025n=13,4832026n=9,149
assist other agency calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodAssist other agency calls logged in CAD
20094,272
20107,613
20117,828
20127,554
20137,848
20147,827
20158,277
20169,033
20179,992
201810,402
201911,555
202010,096
20219,396
202211,386
202314,351
202412,664
202513,483
20269,149
Assist Other Agency Calls Are Holding Near Their PeakSeattle Police logged 13,483 assist other agency calls in 2025, the most recent full year, close to the 14,351 in 2023.

Assist Other Agency: 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: 6.3%2009 · Report taken, no arrest: 4.8%2009 · Resolved on scene: 83.5%2009 · Unable to locate: 1.7%2009 · Other (unfounded / cancelled): 3.7%2010 · Arrest / citation: 5.6%2010 · Report taken, no arrest: 4.8%2010 · Resolved on scene: 84.4%2010 · Unable to locate: 2.1%2010 · Other (unfounded / cancelled): 3.1%2011 · Arrest / citation: 4.4%2011 · Report taken, no arrest: 4.0%2011 · Resolved on scene: 86.3%2011 · Unable to locate: 2.0%2011 · Other (unfounded / cancelled): 3.3%2012 · Arrest / citation: 2.6%2012 · Report taken, no arrest: 4.8%2012 · Resolved on scene: 86.0%2012 · Unable to locate: 2.0%2012 · Other (unfounded / cancelled): 4.6%2013 · Arrest / citation: 1.5%2013 · Report taken, no arrest: 3.7%2013 · Resolved on scene: 87.4%2013 · Unable to locate: 1.9%2013 · Other (unfounded / cancelled): 5.5%2014 · Arrest / citation: 0.8%2014 · Report taken, no arrest: 4.6%2014 · Resolved on scene: 84.0%2014 · Unable to locate: 3.4%2014 · Other (unfounded / cancelled): 7.3%2015 · Arrest / citation: 0.6%2015 · Report taken, no arrest: 5.9%2015 · Resolved on scene: 82.7%2015 · Unable to locate: 3.8%2015 · Other (unfounded / cancelled): 7.1%2016 · Arrest / citation: 0.7%2016 · Report taken, no arrest: 4.8%2016 · Resolved on scene: 82.5%2016 · Unable to locate: 4.2%2016 · Other (unfounded / cancelled): 7.8%2017 · Arrest / citation: 0.8%2017 · Report taken, no arrest: 4.8%2017 · Resolved on scene: 82.0%2017 · Unable to locate: 4.4%2017 · Other (unfounded / cancelled): 8.1%2018 · Arrest / citation: 0.9%2018 · Report taken, no arrest: 5.4%2018 · Resolved on scene: 79.6%2018 · Unable to locate: 4.4%2018 · Other (unfounded / cancelled): 9.6%2019 · Arrest / citation: 0.5%2019 · Report taken, no arrest: 6.8%2019 · Resolved on scene: 78.6%2019 · Unable to locate: 5.2%2019 · Other (unfounded / cancelled): 8.9%2020 · Arrest / citation: 0.3%2020 · Report taken, no arrest: 13.7%2020 · Resolved on scene: 70.5%2020 · Unable to locate: 5.5%2020 · Other (unfounded / cancelled): 10.1%2021 · Arrest / citation: 0.4%2021 · Report taken, no arrest: 5.4%2021 · Resolved on scene: 73.4%2021 · Unable to locate: 6.9%2021 · Other (unfounded / cancelled): 14.0%2022 · Arrest / citation: 0.3%2022 · Report taken, no arrest: 6.6%2022 · Resolved on scene: 73.5%2022 · Unable to locate: 7.1%2022 · Other (unfounded / cancelled): 12.5%2023 · Arrest / citation: 0.2%2023 · Report taken, no arrest: 3.9%2023 · Resolved on scene: 75.2%2023 · Unable to locate: 7.5%2023 · Other (unfounded / cancelled): 13.1%2024 · Arrest / citation: 0.2%2024 · Report taken, no arrest: 3.3%2024 · Resolved on scene: 76.1%2024 · Unable to locate: 8.1%2024 · Other (unfounded / cancelled): 12.3%2025 · Arrest / citation: 0.3%2025 · Report taken, no arrest: 3.3%2025 · Resolved on scene: 78.5%2025 · Unable to locate: 7.6%2025 · Other (unfounded / cancelled): 10.3%2026 · Arrest / citation: 0.3%2026 · Report taken, no arrest: 3.9%2026 · Resolved on scene: 78.1%2026 · Unable to locate: 7.4%2026 · Other (unfounded / cancelled): 10.3%2009n=4,2722011n=7,8282013n=7,8482015n=8,2772017n=9,9922019n=11,5552021n=9,3962023n=14,3512025n=13,4832026n=9,149
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)
20094,2726.3%4.8%83.5%1.7%3.7%
20107,6135.6%4.8%84.4%2.1%3.1%
20117,8284.4%4.0%86.3%2.0%3.3%
20127,5542.6%4.8%86.0%2.0%4.6%
20137,8481.5%3.7%87.4%1.9%5.5%
20147,8270.8%4.6%84.0%3.4%7.3%
20158,2770.6%5.9%82.7%3.8%7.1%
20169,0330.7%4.8%82.5%4.2%7.8%
20179,9920.8%4.8%82.0%4.4%8.1%
201810,4020.9%5.4%79.6%4.4%9.6%
201911,5550.5%6.8%78.6%5.2%8.9%
202010,0960.3%13.7%70.5%5.5%10.1%
20219,3960.4%5.4%73.4%6.9%14.0%
202211,3860.3%6.6%73.5%7.1%12.5%
202314,3510.2%3.9%75.2%7.5%13.1%
202412,6640.2%3.3%76.1%8.1%12.3%
202513,4830.3%3.3%78.5%7.6%10.3%
20269,1490.3%3.9%78.1%7.4%10.3%
7% of Assist Other Agency Calls End “Unable to Locate,” Up From 4%Report-taken outcomes moved from 5% of calls in 2016 to 4% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Assist Other Agency: 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 27% of assist other agency 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 min25 min50 min2009: 11.2 min2010: 9.2 min2011: 7.6 min2012: 9.1 min2013: 12.6 min2014: 12.0 min2015: 14.8 min2016: 11.6 min2017: 9.8 min2018: 11.8 min2019: 10.9 min2020: 12.9 min2021: 14.3 min2022: 15.1 min2023: 16.6 min2024: 22.3 min2025: 26.8 min2026: 27.8 min2009: 17.7 min2010: 15.9 min2011: 14.0 min2012: 15.3 min2013: 22.6 min2014: 19.3 min2015: 22.6 min2016: 18.8 min2017: 17.5 min2018: 19.8 min2019: 18.6 min2020: 21.7 min2021: 23.4 min2022: 24.1 min2023: 25.7 min2024: 33.3 min2025: 38.0 min2026: 39.3 min2009n=2,2922011n=4,2732013n=5,5522015n=5,9592017n=7,5102019n=8,8642021n=8,1382023n=11,5062025n=9,0792026n=6,104
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
20092,29211.2 min17.7 min
20104,1129.2 min15.9 min
20114,2737.6 min14.0 min
20124,8619.1 min15.3 min
20135,55212.6 min22.6 min
20145,80312.0 min19.3 min
20155,95914.8 min22.6 min
20166,67711.6 min18.8 min
20177,5109.8 min17.5 min
20187,99111.8 min19.8 min
20198,86410.9 min18.6 min
20207,80612.9 min21.7 min
20218,13814.3 min23.4 min
20229,43115.1 min24.1 min
202311,50616.6 min25.7 min
20249,63422.3 min33.3 min
20259,07926.8 min38.0 min
20266,10427.8 min39.3 min
The Average Call Waits 39 Minutes for an Officer to ArriveAs calls rose 49% between 2016 and 2025, average response time has more than doubled in the past 10 years, from 19 minutes in 2016 to 39 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.

Assist Other Agency: 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 27% of assist other agency 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: 8.2%2009 · 0–5 min: 25.8%2009 · 5–30 min: 54.2%2009 · 30–60 min: 6.7%2009 · 1–4 hr: 4.6%2009 · 4–8 hr: 0.4%2009 · Over 8 hr: 0.0%2010 · No recorded response: 6.7%2010 · 0–5 min: 29.3%2010 · 5–30 min: 53.1%2010 · 30–60 min: 6.6%2010 · 1–4 hr: 4.1%2010 · 4–8 hr: 0.2%2010 · Over 8 hr: 0.0%2011 · No recorded response: 7.1%2011 · 0–5 min: 31.7%2011 · 5–30 min: 52.4%2011 · 30–60 min: 5.2%2011 · 1–4 hr: 3.3%2011 · 4–8 hr: 0.2%2011 · Over 8 hr: 0.0%2012 · No recorded response: 8.7%2012 · 0–5 min: 29.5%2012 · 5–30 min: 52.6%2012 · 30–60 min: 5.2%2012 · 1–4 hr: 3.6%2012 · 4–8 hr: 0.3%2012 · Over 8 hr: 0.0%2013 · No recorded response: 8.5%2013 · 0–5 min: 27.6%2013 · 5–30 min: 52.0%2013 · 30–60 min: 6.0%2013 · 1–4 hr: 5.2%2013 · 4–8 hr: 0.7%2013 · Over 8 hr: 0.1%2014 · No recorded response: 10.0%2014 · 0–5 min: 26.0%2014 · 5–30 min: 52.8%2014 · 30–60 min: 6.0%2014 · 1–4 hr: 4.6%2014 · 4–8 hr: 0.5%2014 · Over 8 hr: 0.1%2015 · No recorded response: 10.2%2015 · 0–5 min: 25.3%2015 · 5–30 min: 51.5%2015 · 30–60 min: 6.2%2015 · 1–4 hr: 5.5%2015 · 4–8 hr: 0.9%2015 · Over 8 hr: 0.2%2016 · No recorded response: 11.2%2016 · 0–5 min: 27.4%2016 · 5–30 min: 50.0%2016 · 30–60 min: 6.1%2016 · 1–4 hr: 4.5%2016 · 4–8 hr: 0.6%2016 · Over 8 hr: 0.1%2017 · No recorded response: 11.2%2017 · 0–5 min: 27.8%2017 · 5–30 min: 49.9%2017 · 30–60 min: 6.0%2017 · 1–4 hr: 4.6%2017 · 4–8 hr: 0.5%2017 · Over 8 hr: 0.0%2018 · No recorded response: 13.6%2018 · 0–5 min: 28.3%2018 · 5–30 min: 46.3%2018 · 30–60 min: 5.7%2018 · 1–4 hr: 5.3%2018 · 4–8 hr: 0.6%2018 · Over 8 hr: 0.1%2019 · No recorded response: 12.5%2019 · 0–5 min: 29.8%2019 · 5–30 min: 46.7%2019 · 30–60 min: 5.0%2019 · 1–4 hr: 5.4%2019 · 4–8 hr: 0.5%2019 · Over 8 hr: 0.1%2020 · No recorded response: 14.6%2020 · 0–5 min: 24.2%2020 · 5–30 min: 49.2%2020 · 30–60 min: 5.8%2020 · 1–4 hr: 5.1%2020 · 4–8 hr: 0.9%2020 · Over 8 hr: 0.2%2021 · No recorded response: 18.7%2021 · 0–5 min: 21.0%2021 · 5–30 min: 48.2%2021 · 30–60 min: 5.3%2021 · 1–4 hr: 5.8%2021 · 4–8 hr: 0.8%2021 · Over 8 hr: 0.2%2022 · No recorded response: 18.1%2022 · 0–5 min: 24.5%2022 · 5–30 min: 45.2%2022 · 30–60 min: 4.9%2022 · 1–4 hr: 6.2%2022 · 4–8 hr: 0.8%2022 · Over 8 hr: 0.3%2023 · No recorded response: 20.3%2023 · 0–5 min: 24.0%2023 · 5–30 min: 44.7%2023 · 30–60 min: 4.4%2023 · 1–4 hr: 4.9%2023 · 4–8 hr: 1.2%2023 · Over 8 hr: 0.4%2024 · No recorded response: 19.5%2024 · 0–5 min: 20.0%2024 · 5–30 min: 45.5%2024 · 30–60 min: 6.0%2024 · 1–4 hr: 6.6%2024 · 4–8 hr: 1.8%2024 · Over 8 hr: 0.7%2025 · No recorded response: 18.1%2025 · 0–5 min: 19.2%2025 · 5–30 min: 44.3%2025 · 30–60 min: 7.3%2025 · 1–4 hr: 8.5%2025 · 4–8 hr: 1.7%2025 · Over 8 hr: 0.8%2026 · No recorded response: 16.9%2026 · 0–5 min: 18.6%2026 · 5–30 min: 44.7%2026 · 30–60 min: 7.8%2026 · 1–4 hr: 9.5%2026 · 4–8 hr: 1.6%2026 · Over 8 hr: 0.9%2009n=2,2922011n=4,2732013n=5,5522015n=5,9592017n=7,5102019n=8,8642021n=8,1382023n=11,5062025n=9,0792026n=6,104
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
20092,2928.2%25.8%54.2%6.7%4.6%0.4%0.0%
20104,1126.7%29.3%53.1%6.6%4.1%0.2%0.0%
20114,2737.1%31.7%52.4%5.2%3.3%0.2%0.0%
20124,8618.7%29.5%52.6%5.2%3.6%0.3%0.0%
20135,5528.5%27.6%52.0%6.0%5.2%0.7%0.1%
20145,80310.0%26.0%52.8%6.0%4.6%0.5%0.1%
20155,95910.2%25.3%51.5%6.2%5.5%0.9%0.2%
20166,67711.2%27.4%50.0%6.1%4.5%0.6%0.1%
20177,51011.2%27.8%49.9%6.0%4.6%0.5%0.0%
20187,99113.6%28.3%46.3%5.7%5.3%0.6%0.1%
20198,86412.5%29.8%46.7%5.0%5.4%0.5%0.1%
20207,80614.6%24.2%49.2%5.8%5.1%0.9%0.2%
20218,13818.7%21.0%48.2%5.3%5.8%0.8%0.2%
20229,43118.1%24.5%45.2%4.9%6.2%0.8%0.3%
202311,50620.3%24.0%44.7%4.4%4.9%1.2%0.4%
20249,63419.5%20.0%45.5%6.0%6.6%1.8%0.7%
20259,07918.1%19.2%44.3%7.3%8.5%1.7%0.8%
20266,10416.9%18.6%44.7%7.8%9.5%1.6%0.9%
The Average Call Waits 28 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 28 minutes in 2026, more than double what it was in 2016. 12% of calls took more than an hour to get a response in 2026, compared with 5% 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.