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

Other

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

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

Swipe sideways to see the full chart →
02,5005,0002009: 121 other calls logged in CAD2010: 193 other calls logged in CAD2011: 122 other calls logged in CAD2012: 165 other calls logged in CAD2013: 104 other calls logged in CAD2014: 92 other calls logged in CAD2015: 182 other calls logged in CAD2016: 208 other calls logged in CAD2017: 96 other calls logged in CAD2018: 27 other calls logged in CAD2019: 75 other calls logged in CAD2020: 50 other calls logged in CAD2021: 17 other calls logged in CAD2022: 49 other calls logged in CAD2023: 44 other calls logged in CAD2024: 53 other calls logged in CAD2025: 3,802 other calls logged in CAD2026: 3,708 other calls logged in CAD2009n=1212011n=1222013n=1042015n=1822017n=962019n=752021n=172023n=442025n=3,8022026n=3,708
other calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodOther calls logged in CAD
2009121
2010193
2011122
2012165
2013104
201492
2015182
2016208
201796
201827
201975
202050
202117
202249
202344
202453
20253,802
20263,708
Other Calls Are at Their Highest in YearsSeattle Police logged 3,802 other calls in 2025, the most calls in any full year on record.

Other: 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 · Report taken, no arrest: 0.8%2009 · Resolved on scene: 5.0%2009 · Other (unfounded / cancelled): 94.2%2010 · Report taken, no arrest: 0.5%2010 · Resolved on scene: 1.6%2010 · Unable to locate: 1.6%2010 · Other (unfounded / cancelled): 96.4%2011 · Resolved on scene: 0.8%2011 · Other (unfounded / cancelled): 99.2%2012 · Other (unfounded / cancelled): 100.0%2013 · Other (unfounded / cancelled): 100.0%2014 · Report taken, no arrest: 1.1%2014 · Resolved on scene: 8.7%2014 · Other (unfounded / cancelled): 90.2%2015 · Resolved on scene: 2.7%2015 · Unable to locate: 1.1%2015 · Other (unfounded / cancelled): 96.2%2016 · Arrest / citation: 0.5%2016 · Resolved on scene: 2.9%2016 · Other (unfounded / cancelled): 96.6%2017 · Resolved on scene: 2.1%2017 · Other (unfounded / cancelled): 97.9%2018 · Resolved on scene: 3.7%2018 · Unable to locate: 3.7%2018 · Other (unfounded / cancelled): 92.6%2019 · Resolved on scene: 10.7%2019 · Unable to locate: 1.3%2019 · Other (unfounded / cancelled): 88.0%2020 · Resolved on scene: 12.0%2020 · Other (unfounded / cancelled): 88.0%2021 · Other (unfounded / cancelled): 100.0%2022 · Unable to locate: 2.0%2022 · Other (unfounded / cancelled): 98.0%2023 · Report taken, no arrest: 2.3%2023 · Resolved on scene: 11.4%2023 · Unable to locate: 2.3%2023 · Other (unfounded / cancelled): 84.1%2024 · Resolved on scene: 7.5%2024 · Other (unfounded / cancelled): 92.5%2025 · Arrest / citation: 0.1%2025 · Report taken, no arrest: 0.3%2025 · Resolved on scene: 95.1%2025 · Unable to locate: 3.0%2025 · Other (unfounded / cancelled): 1.5%2026 · Report taken, no arrest: 0.4%2026 · Resolved on scene: 81.3%2026 · Unable to locate: 17.5%2026 · Other (unfounded / cancelled): 0.8%2009n=1212011n=1222013n=1042015n=1822017n=962019n=752021n=172023n=442025n=3,8022026n=3,708
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
PeriodEventsReport taken, no arrestResolved on sceneOther (unfounded / cancelled)Unable to locateArrest / citation
20091210.8%5.0%94.2%——
20101930.5%1.6%96.4%1.6%—
2011122—0.8%99.2%——
2012165——100.0%——
2013104——100.0%——
2014921.1%8.7%90.2%——
2015182—2.7%96.2%1.1%—
2016208—2.9%96.6%—0.5%
201796—2.1%97.9%——
201827—3.7%92.6%3.7%—
201975—10.7%88.0%1.3%—
202050—12.0%88.0%——
202117——100.0%——
202249——98.0%2.0%—
2023442.3%11.4%84.1%2.3%—
202453—7.5%92.5%——
20253,8020.3%95.1%1.5%3.0%0.1%
20263,7080.4%81.3%0.8%17.5%—
18% of Other Calls End “Unable to Locate,” Up From 0%Report-taken outcomes were 0% of calls in both 2016 and 2026. “Unable to locate” means officers could not find the incident or the person who called.

Other: 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 62% of other 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. Because most other events are logged by officers, these charts describe only the small share that were called in. When a call priority is selected, only events of that priority are shown.

Call priority
Swipe sideways to see the full chart →
0 min12,500 min25,000 min2009: 95.3 min2010: 271.3 min2011: 302.4 min2012: 541.7 min2013: 13.6 min2014: 12.5 min2015: 307.7 min2016: 225.7 min2017: 14,660.2 min2018: 0.6 min2019: 20,521.0 min2020: 2.8 min2021: 4.1 min2022: 1.3 min2023: 34.9 min2024: 0.4 min2025: 61.3 min2026: 64.3 min2009: 129.8 min2010: 277.5 min2011: 479.3 min2012: 682.1 min2013: 1.7 min2014: 16.9 min2015: 401.4 min2016: 47.1 min2017: 18,851.3 min2018: 0.7 min2019: 22,386.5 min2020: 6.6 min2021: 5.3 min2022: 1.4 min2023: 39.1 min2024: 4.1 min2025: 81.7 min2026: 40.9 min2009n=402011n=652013n=322015n=522017n=272019n=122021n=52023n=262025n=6162026n=2,244
Average response timeAverage dispatch delay
Small sample: Only a small share of other events are called in. The year with the fewest had only 5, 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
20094095.3 min129.8 min
201091271.3 min277.5 min
201165302.4 min479.3 min
201257541.7 min682.1 min
20133213.6 min1.7 min
20142812.5 min16.9 min
201552307.7 min401.4 min
201693225.7 min47.1 min
20172714,660.2 min18,851.3 min
2018110.6 min0.7 min
20191220,521.0 min22,386.5 min
2020192.8 min6.6 min
202154.1 min5.3 min
2022171.3 min1.4 min
20232634.9 min39.1 min
2024320.4 min4.1 min
202561661.3 min81.7 min
20262,24464.3 min40.9 min
The Average Call Gets an Officer in 41 MinutesEven as calls rose 1728% between 2016 and 2025, average response time has decreased 13% in the past 10 years, from 47 minutes in 2016 to 41 in 2026. This counts only the 38% of other calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
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.

Other: 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 62% of other events, because they have no wait. Because most other events are logged by officers, these charts describe only the small share that were called in. 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: 27.5%2009 · 0–5 min: 60.0%2009 · 5–30 min: 7.5%2009 · 30–60 min: 2.5%2009 · Over 8 hr: 2.5%2010 · No recorded response: 24.2%2010 · 0–5 min: 68.1%2010 · 5–30 min: 2.2%2010 · 1–4 hr: 1.1%2010 · Over 8 hr: 4.4%2011 · No recorded response: 36.9%2011 · 0–5 min: 53.9%2011 · 5–30 min: 3.1%2011 · 30–60 min: 1.5%2011 · Over 8 hr: 4.6%2012 · No recorded response: 35.1%2012 · 0–5 min: 45.6%2012 · 5–30 min: 8.8%2012 · 30–60 min: 3.5%2012 · Over 8 hr: 7.0%2013 · No recorded response: 18.8%2013 · 0–5 min: 71.9%2013 · 5–30 min: 9.4%2014 · No recorded response: 32.1%2014 · 0–5 min: 32.1%2014 · 5–30 min: 14.3%2014 · 30–60 min: 21.4%2015 · No recorded response: 23.1%2015 · 0–5 min: 26.9%2015 · 5–30 min: 5.8%2015 · 30–60 min: 1.9%2015 · 1–4 hr: 38.5%2015 · Over 8 hr: 3.9%2016 · No recorded response: 14.0%2016 · 0–5 min: 46.2%2016 · 5–30 min: 7.5%2016 · 30–60 min: 6.5%2016 · 1–4 hr: 21.5%2016 · 4–8 hr: 4.3%2017 · No recorded response: 22.2%2017 · 0–5 min: 51.9%2017 · 5–30 min: 22.2%2017 · Over 8 hr: 3.7%2018 · No recorded response: 9.1%2018 · 0–5 min: 90.9%2019 · No recorded response: 8.3%2019 · 0–5 min: 58.3%2019 · 5–30 min: 25.0%2019 · Over 8 hr: 8.3%2020 · No recorded response: 21.1%2020 · 0–5 min: 63.2%2020 · 5–30 min: 10.5%2020 · 30–60 min: 5.3%2021 · No recorded response: 20.0%2021 · 0–5 min: 60.0%2021 · 5–30 min: 20.0%2022 · 0–5 min: 88.2%2022 · 5–30 min: 11.8%2023 · No recorded response: 15.4%2023 · 0–5 min: 61.5%2023 · 5–30 min: 11.5%2023 · 30–60 min: 3.9%2023 · 1–4 hr: 3.9%2023 · Over 8 hr: 3.9%2024 · No recorded response: 25.0%2024 · 0–5 min: 68.8%2024 · 5–30 min: 3.1%2024 · 1–4 hr: 3.1%2025 · No recorded response: 3.4%2025 · 0–5 min: 9.7%2025 · 5–30 min: 38.6%2025 · 30–60 min: 17.5%2025 · 1–4 hr: 23.4%2025 · 4–8 hr: 4.9%2025 · Over 8 hr: 2.4%2026 · No recorded response: 1.2%2026 · 0–5 min: 3.0%2026 · 5–30 min: 67.6%2026 · 30–60 min: 14.7%2026 · 1–4 hr: 10.9%2026 · 4–8 hr: 2.1%2026 · Over 8 hr: 0.5%2009n=402011n=652013n=322015n=522017n=272019n=122021n=52023n=262025n=6162026n=2,244
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of other events are called in. The year with the fewest had only 5, 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 minOver 8 hr1–4 hr4–8 hr
20094027.5%60.0%7.5%2.5%2.5%——
20109124.2%68.1%2.2%—4.4%1.1%—
20116536.9%53.9%3.1%1.5%4.6%——
20125735.1%45.6%8.8%3.5%7.0%——
20133218.8%71.9%9.4%————
20142832.1%32.1%14.3%21.4%———
20155223.1%26.9%5.8%1.9%3.9%38.5%—
20169314.0%46.2%7.5%6.5%—21.5%4.3%
20172722.2%51.9%22.2%—3.7%——
2018119.1%90.9%—————
2019128.3%58.3%25.0%—8.3%——
20201921.1%63.2%10.5%5.3%———
2021520.0%60.0%20.0%————
202217—88.2%11.8%————
20232615.4%61.5%11.5%3.9%3.9%3.9%—
20243225.0%68.8%3.1%——3.1%—
20256163.4%9.7%38.6%17.5%2.4%23.4%4.9%
20262,2441.2%3.0%67.6%14.7%0.5%10.9%2.1%
Fewer Calls Wait Over an Hour: 13%, Down From 26%13% of calls took more than an hour to get a response in 2026, compared with 26% in 2016. This counts only the 38% of other calls since 2009 that were called in; the rest were logged by officers themselves and have no wait.
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.