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

Assist the Officer

Assist the Officer calls over time: volume, outcomes, and response speed

Assist the Officer: 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 (49% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
0751502009: 111 assist the officer calls logged in CAD2010: 82 assist the officer calls logged in CAD2011: 70 assist the officer calls logged in CAD2012: 118 assist the officer calls logged in CAD2013: 82 assist the officer calls logged in CAD2014: 78 assist the officer calls logged in CAD2015: 70 assist the officer calls logged in CAD2016: 74 assist the officer calls logged in CAD2017: 72 assist the officer calls logged in CAD2018: 71 assist the officer calls logged in CAD2019: 67 assist the officer calls logged in CAD2020: 41 assist the officer calls logged in CAD2021: 32 assist the officer calls logged in CAD2022: 43 assist the officer calls logged in CAD2023: 47 assist the officer calls logged in CAD2024: 52 assist the officer calls logged in CAD2025: 60 assist the officer calls logged in CAD2026: 54 assist the officer calls logged in CAD2009n=1112011n=702013n=822015n=702017n=722019n=672021n=322023n=472025n=602026n=54
assist the officer calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodAssist the officer calls logged in CAD
2009111
201082
201170
2012118
201382
201478
201570
201674
201772
201871
201967
202041
202132
202243
202347
202452
202560
202654
Assist the Officer Calls Are Down 49% From Their 2012 PeakSeattle Police logged 118 assist the officer calls in 2012 and 60 in 2025, the most recent full year.

Assist the Officer: 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.9%2009 · Report taken, no arrest: 2.7%2009 · Resolved on scene: 75.7%2009 · Unable to locate: 4.5%2009 · Other (unfounded / cancelled): 16.2%2010 · Resolved on scene: 40.2%2010 · Unable to locate: 1.2%2010 · Other (unfounded / cancelled): 58.5%2011 · Arrest / citation: 4.3%2011 · Report taken, no arrest: 4.3%2011 · Resolved on scene: 31.4%2011 · Unable to locate: 1.4%2011 · Other (unfounded / cancelled): 58.6%2012 · Arrest / citation: 1.7%2012 · Report taken, no arrest: 3.4%2012 · Resolved on scene: 53.4%2012 · Unable to locate: 1.7%2012 · Other (unfounded / cancelled): 39.8%2013 · Report taken, no arrest: 3.7%2013 · Resolved on scene: 59.8%2013 · Unable to locate: 1.2%2013 · Other (unfounded / cancelled): 35.4%2014 · Report taken, no arrest: 1.3%2014 · Resolved on scene: 64.1%2014 · Unable to locate: 1.3%2014 · Other (unfounded / cancelled): 33.3%2015 · Report taken, no arrest: 1.4%2015 · Resolved on scene: 58.6%2015 · Other (unfounded / cancelled): 40.0%2016 · Report taken, no arrest: 2.7%2016 · Resolved on scene: 63.5%2016 · Other (unfounded / cancelled): 33.8%2017 · Report taken, no arrest: 2.8%2017 · Resolved on scene: 50.0%2017 · Unable to locate: 2.8%2017 · Other (unfounded / cancelled): 44.4%2018 · Report taken, no arrest: 1.4%2018 · Resolved on scene: 56.3%2018 · Other (unfounded / cancelled): 42.3%2019 · Arrest / citation: 1.5%2019 · Report taken, no arrest: 3.0%2019 · Resolved on scene: 64.2%2019 · Unable to locate: 3.0%2019 · Other (unfounded / cancelled): 28.4%2020 · Report taken, no arrest: 4.9%2020 · Resolved on scene: 56.1%2020 · Unable to locate: 4.9%2020 · Other (unfounded / cancelled): 34.1%2021 · Report taken, no arrest: 9.4%2021 · Resolved on scene: 50.0%2021 · Unable to locate: 3.1%2021 · Other (unfounded / cancelled): 37.5%2022 · Arrest / citation: 2.3%2022 · Report taken, no arrest: 4.7%2022 · Resolved on scene: 30.2%2022 · Other (unfounded / cancelled): 62.8%2023 · Arrest / citation: 2.1%2023 · Resolved on scene: 34.0%2023 · Unable to locate: 6.4%2023 · Other (unfounded / cancelled): 57.4%2024 · Arrest / citation: 5.8%2024 · Report taken, no arrest: 1.9%2024 · Resolved on scene: 38.5%2024 · Unable to locate: 11.5%2024 · Other (unfounded / cancelled): 42.3%2025 · Report taken, no arrest: 6.7%2025 · Resolved on scene: 40.0%2025 · Unable to locate: 20.0%2025 · Other (unfounded / cancelled): 33.3%2026 · Report taken, no arrest: 1.9%2026 · Resolved on scene: 44.4%2026 · Unable to locate: 14.8%2026 · Other (unfounded / cancelled): 38.9%2009n=1112011n=702013n=822015n=702017n=722019n=672021n=322023n=472025n=602026n=54
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)
20091110.9%2.7%75.7%4.5%16.2%
201082——40.2%1.2%58.5%
2011704.3%4.3%31.4%1.4%58.6%
20121181.7%3.4%53.4%1.7%39.8%
201382—3.7%59.8%1.2%35.4%
201478—1.3%64.1%1.3%33.3%
201570—1.4%58.6%—40.0%
201674—2.7%63.5%—33.8%
201772—2.8%50.0%2.8%44.4%
201871—1.4%56.3%—42.3%
2019671.5%3.0%64.2%3.0%28.4%
202041—4.9%56.1%4.9%34.1%
202132—9.4%50.0%3.1%37.5%
2022432.3%4.7%30.2%—62.8%
2023472.1%—34.0%6.4%57.4%
2024525.8%1.9%38.5%11.5%42.3%
202560—6.7%40.0%20.0%33.3%
202654—1.9%44.4%14.8%38.9%
15% of Assist the Officer Calls End “Unable to Locate,” Up From 0%Report-taken outcomes moved from 3% of calls in 2016 to 2% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Assist the Officer: 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 49% of assist the officer 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: 19.4 min2010: 4.3 min2011: 5.4 min2012: 14.8 min2013: 9.4 min2014: 11.9 min2015: 4.1 min2016: 7.6 min2017: 4.9 min2018: 15.2 min2019: 7.4 min2020: 6.9 min2021: 25.1 min2022: 5.5 min2023: 13.7 min2024: 61.8 min2025: 42.4 min2026: 21.7 min2009: 27.0 min2010: 9.8 min2011: 11.1 min2012: 23.5 min2013: 17.7 min2014: 17.8 min2015: 11.0 min2016: 14.6 min2017: 10.8 min2018: 25.7 min2019: 16.0 min2020: 14.8 min2021: 40.5 min2022: 13.7 min2023: 29.8 min2024: 91.3 min2025: 64.9 min2026: 34.5 min2009n=492011n=352013n=312015n=272017n=352019n=282021n=182023n=312025n=392026n=40
Average response timeAverage dispatch delay
Small sample: Only a small share of assist the officer events are called in. The year with the fewest had only 18, 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
20094919.4 min27.0 min
2010474.3 min9.8 min
2011355.4 min11.1 min
20124814.8 min23.5 min
2013319.4 min17.7 min
20143311.9 min17.8 min
2015274.1 min11.0 min
2016317.6 min14.6 min
2017354.9 min10.8 min
20183715.2 min25.7 min
2019287.4 min16.0 min
2020226.9 min14.8 min
20211825.1 min40.5 min
2022335.5 min13.7 min
20233113.7 min29.8 min
20243961.8 min91.3 min
20253942.4 min64.9 min
20264021.7 min34.5 min
The Average Call Waits 34 Minutes for an Officer to ArriveDespite a 19% drop in calls between 2016 and 2025, average response time has more than doubled in the past 10 years, from 15 minutes in 2016 to 34 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 the Officer: 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 49% of assist the officer 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: 14.3%2009 · 0–5 min: 26.5%2009 · 5–30 min: 44.9%2009 · 30–60 min: 4.1%2009 · 1–4 hr: 8.2%2009 · 4–8 hr: 2.0%2010 · No recorded response: 25.5%2010 · 0–5 min: 25.5%2010 · 5–30 min: 46.8%2010 · 30–60 min: 2.1%2011 · No recorded response: 8.6%2011 · 0–5 min: 37.1%2011 · 5–30 min: 45.7%2011 · 30–60 min: 5.7%2011 · 1–4 hr: 2.9%2012 · No recorded response: 16.7%2012 · 0–5 min: 27.1%2012 · 5–30 min: 43.8%2012 · 30–60 min: 6.2%2012 · 1–4 hr: 4.2%2012 · 4–8 hr: 2.1%2013 · No recorded response: 29.0%2013 · 0–5 min: 22.6%2013 · 5–30 min: 41.9%2013 · 1–4 hr: 6.5%2014 · No recorded response: 18.2%2014 · 0–5 min: 21.2%2014 · 5–30 min: 48.5%2014 · 30–60 min: 3.0%2014 · 1–4 hr: 9.1%2015 · No recorded response: 14.8%2015 · 0–5 min: 22.2%2015 · 5–30 min: 59.2%2015 · 30–60 min: 3.7%2016 · No recorded response: 25.8%2016 · 0–5 min: 19.4%2016 · 5–30 min: 51.6%2016 · 1–4 hr: 3.2%2017 · No recorded response: 22.9%2017 · 0–5 min: 42.9%2017 · 5–30 min: 25.7%2017 · 30–60 min: 5.7%2017 · 1–4 hr: 2.9%2018 · No recorded response: 27.0%2018 · 0–5 min: 21.6%2018 · 5–30 min: 40.5%2018 · 30–60 min: 5.4%2018 · 1–4 hr: 2.7%2018 · 4–8 hr: 2.7%2019 · No recorded response: 21.4%2019 · 0–5 min: 25.0%2019 · 5–30 min: 35.7%2019 · 30–60 min: 17.9%2020 · No recorded response: 22.7%2020 · 0–5 min: 27.3%2020 · 5–30 min: 36.4%2020 · 30–60 min: 13.6%2021 · No recorded response: 11.1%2021 · 0–5 min: 5.6%2021 · 5–30 min: 55.5%2021 · 30–60 min: 16.7%2021 · 1–4 hr: 5.6%2021 · 4–8 hr: 5.6%2022 · No recorded response: 42.4%2022 · 0–5 min: 9.1%2022 · 5–30 min: 42.4%2022 · 30–60 min: 3.0%2022 · 1–4 hr: 3.0%2023 · No recorded response: 22.6%2023 · 0–5 min: 16.1%2023 · 5–30 min: 48.4%2023 · 30–60 min: 3.2%2023 · 1–4 hr: 6.5%2023 · 4–8 hr: 3.2%2024 · No recorded response: 20.5%2024 · 0–5 min: 15.4%2024 · 5–30 min: 38.5%2024 · 30–60 min: 10.3%2024 · 1–4 hr: 7.7%2024 · 4–8 hr: 2.6%2024 · Over 8 hr: 5.1%2025 · No recorded response: 20.5%2025 · 0–5 min: 5.1%2025 · 5–30 min: 51.3%2025 · 30–60 min: 7.7%2025 · 1–4 hr: 10.3%2025 · 4–8 hr: 2.6%2025 · Over 8 hr: 2.6%2026 · No recorded response: 12.5%2026 · 0–5 min: 12.5%2026 · 5–30 min: 52.5%2026 · 30–60 min: 15.0%2026 · 1–4 hr: 5.0%2026 · 4–8 hr: 2.5%2009n=492011n=352013n=312015n=272017n=352019n=282021n=182023n=312025n=392026n=40
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of assist the officer events are called in. The year with the fewest had only 18, 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
20094914.3%26.5%44.9%4.1%8.2%2.0%—
20104725.5%25.5%46.8%2.1%———
2011358.6%37.1%45.7%5.7%2.9%——
20124816.7%27.1%43.8%6.2%4.2%2.1%—
20133129.0%22.6%41.9%—6.5%——
20143318.2%21.2%48.5%3.0%9.1%——
20152714.8%22.2%59.2%3.7%———
20163125.8%19.4%51.6%—3.2%——
20173522.9%42.9%25.7%5.7%2.9%——
20183727.0%21.6%40.5%5.4%2.7%2.7%—
20192821.4%25.0%35.7%17.9%———
20202222.7%27.3%36.4%13.6%———
20211811.1%5.6%55.5%16.7%5.6%5.6%—
20223342.4%9.1%42.4%3.0%3.0%——
20233122.6%16.1%48.4%3.2%6.5%3.2%—
20243920.5%15.4%38.5%10.3%7.7%2.6%5.1%
20253920.5%5.1%51.3%7.7%10.3%2.6%2.6%
20264012.5%12.5%52.5%15.0%5.0%2.5%—
The Average Call Waits 22 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 22 minutes in 2026, more than double what it was in 2016. 8% of calls took more than an hour to get a response in 2026, compared with 3% 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.