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

Threats/Harassment (No Bias)

Threats/Harassment (No Bias) calls over time: volume, outcomes, and response speed

Threats/Harassment: 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 (18% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
02004002009: 368 threats/harassment (no bias) calls logged in CAD2010: 170 threats/harassment (no bias) calls logged in CAD2011: 101 threats/harassment (no bias) calls logged in CAD2012: 138 threats/harassment (no bias) calls logged in CAD2013: 133 threats/harassment (no bias) calls logged in CAD2014: 156 threats/harassment (no bias) calls logged in CAD2015: 150 threats/harassment (no bias) calls logged in CAD2016: 117 threats/harassment (no bias) calls logged in CAD2017: 153 threats/harassment (no bias) calls logged in CAD2018: 158 threats/harassment (no bias) calls logged in CAD2019: 203 threats/harassment (no bias) calls logged in CAD2020: 170 threats/harassment (no bias) calls logged in CAD2021: 141 threats/harassment (no bias) calls logged in CAD2022: 146 threats/harassment (no bias) calls logged in CAD2023: 207 threats/harassment (no bias) calls logged in CAD2024: 210 threats/harassment (no bias) calls logged in CAD2025: 216 threats/harassment (no bias) calls logged in CAD2026: 177 threats/harassment (no bias) calls logged in CAD2009n=3682011n=1012013n=1332015n=1502017n=1532019n=2032021n=1412023n=2072025n=2162026n=177
threats/harassment (no bias) calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodThreats/harassment (no bias) calls logged in CAD
2009368
2010170
2011101
2012138
2013133
2014156
2015150
2016117
2017153
2018158
2019203
2020170
2021141
2022146
2023207
2024210
2025216
2026177
Threats/Harassment Calls Are at Their Highest in YearsSeattle Police logged 216 threats/harassment calls in 2025, the most calls in any full year on record.

Threats/Harassment: 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: 5.7%2009 · Report taken, no arrest: 67.4%2009 · Resolved on scene: 17.7%2009 · Unable to locate: 4.6%2009 · Other (unfounded / cancelled): 4.6%2010 · Arrest / citation: 3.5%2010 · Report taken, no arrest: 61.8%2010 · Resolved on scene: 7.6%2010 · Unable to locate: 2.9%2010 · Other (unfounded / cancelled): 24.1%2011 · Arrest / citation: 3.0%2011 · Report taken, no arrest: 50.5%2011 · Resolved on scene: 5.0%2011 · Other (unfounded / cancelled): 41.6%2012 · Arrest / citation: 1.4%2012 · Report taken, no arrest: 42.8%2012 · Resolved on scene: 8.7%2012 · Unable to locate: 2.2%2012 · Other (unfounded / cancelled): 44.9%2013 · Arrest / citation: 1.5%2013 · Report taken, no arrest: 45.9%2013 · Resolved on scene: 6.0%2013 · Unable to locate: 3.8%2013 · Other (unfounded / cancelled): 42.9%2014 · Arrest / citation: 1.3%2014 · Report taken, no arrest: 55.1%2014 · Resolved on scene: 5.8%2014 · Unable to locate: 1.9%2014 · Other (unfounded / cancelled): 35.9%2015 · Report taken, no arrest: 50.7%2015 · Resolved on scene: 8.0%2015 · Unable to locate: 2.7%2015 · Other (unfounded / cancelled): 38.7%2016 · Arrest / citation: 1.7%2016 · Report taken, no arrest: 41.9%2016 · Resolved on scene: 6.0%2016 · Unable to locate: 5.1%2016 · Other (unfounded / cancelled): 45.3%2017 · Arrest / citation: 3.3%2017 · Report taken, no arrest: 49.0%2017 · Resolved on scene: 3.3%2017 · Unable to locate: 1.3%2017 · Other (unfounded / cancelled): 43.1%2018 · Arrest / citation: 1.9%2018 · Report taken, no arrest: 41.8%2018 · Resolved on scene: 5.1%2018 · Unable to locate: 3.8%2018 · Other (unfounded / cancelled): 47.5%2019 · Arrest / citation: 0.5%2019 · Report taken, no arrest: 47.3%2019 · Resolved on scene: 4.4%2019 · Unable to locate: 5.9%2019 · Other (unfounded / cancelled): 41.9%2020 · Arrest / citation: 0.6%2020 · Report taken, no arrest: 49.4%2020 · Resolved on scene: 4.1%2020 · Unable to locate: 5.3%2020 · Other (unfounded / cancelled): 40.6%2021 · Report taken, no arrest: 39.7%2021 · Resolved on scene: 6.4%2021 · Unable to locate: 11.3%2021 · Other (unfounded / cancelled): 42.6%2022 · Arrest / citation: 3.4%2022 · Report taken, no arrest: 43.2%2022 · Resolved on scene: 8.2%2022 · Unable to locate: 11.6%2022 · Other (unfounded / cancelled): 33.6%2023 · Arrest / citation: 2.4%2023 · Report taken, no arrest: 44.4%2023 · Resolved on scene: 6.3%2023 · Unable to locate: 9.7%2023 · Other (unfounded / cancelled): 37.2%2024 · Arrest / citation: 1.9%2024 · Report taken, no arrest: 42.9%2024 · Resolved on scene: 7.6%2024 · Unable to locate: 15.2%2024 · Other (unfounded / cancelled): 32.4%2025 · Arrest / citation: 3.7%2025 · Report taken, no arrest: 34.7%2025 · Resolved on scene: 10.6%2025 · Unable to locate: 24.1%2025 · Other (unfounded / cancelled): 26.9%2026 · Arrest / citation: 2.3%2026 · Report taken, no arrest: 40.1%2026 · Resolved on scene: 7.9%2026 · Unable to locate: 25.4%2026 · Other (unfounded / cancelled): 24.3%2009n=3682011n=1012013n=1332015n=1502017n=1532019n=2032021n=1412023n=2072025n=2162026n=177
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)
20093685.7%67.4%17.7%4.6%4.6%
20101703.5%61.8%7.6%2.9%24.1%
20111013.0%50.5%5.0%—41.6%
20121381.4%42.8%8.7%2.2%44.9%
20131331.5%45.9%6.0%3.8%42.9%
20141561.3%55.1%5.8%1.9%35.9%
2015150—50.7%8.0%2.7%38.7%
20161171.7%41.9%6.0%5.1%45.3%
20171533.3%49.0%3.3%1.3%43.1%
20181581.9%41.8%5.1%3.8%47.5%
20192030.5%47.3%4.4%5.9%41.9%
20201700.6%49.4%4.1%5.3%40.6%
2021141—39.7%6.4%11.3%42.6%
20221463.4%43.2%8.2%11.6%33.6%
20232072.4%44.4%6.3%9.7%37.2%
20242101.9%42.9%7.6%15.2%32.4%
20252163.7%34.7%10.6%24.1%26.9%
20261772.3%40.1%7.9%25.4%24.3%
25% of Threats/Harassment Calls End “Unable to Locate,” Up From 5%Report-taken outcomes moved from 42% of calls in 2016 to 40% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Threats/Harassment: 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 18% of threats/harassment 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 min100 min200 min2009: 37.8 min2010: 27.3 min2011: 26.8 min2012: 59.0 min2013: 45.2 min2014: 41.7 min2015: 58.2 min2016: 65.5 min2017: 51.7 min2018: 87.1 min2019: 64.6 min2020: 70.1 min2021: 86.4 min2022: 88.9 min2023: 87.2 min2024: 90.5 min2025: 117.1 min2026: 121.8 min2009: 51.0 min2010: 39.8 min2011: 35.4 min2012: 62.4 min2013: 50.6 min2014: 50.9 min2015: 67.0 min2016: 63.4 min2017: 57.7 min2018: 104.9 min2019: 74.2 min2020: 74.6 min2021: 93.1 min2022: 97.0 min2023: 93.5 min2024: 92.7 min2025: 147.6 min2026: 135.7 min2009n=3012011n=682013n=1012015n=1082017n=1092019n=1632021n=1332023n=1842025n=2042026n=168
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
200930137.8 min51.0 min
201010827.3 min39.8 min
20116826.8 min35.4 min
201211059.0 min62.4 min
201310145.2 min50.6 min
201412041.7 min50.9 min
201510858.2 min67.0 min
20169465.5 min63.4 min
201710951.7 min57.7 min
201812487.1 min104.9 min
201916364.6 min74.2 min
202015570.1 min74.6 min
202113386.4 min93.1 min
202212388.9 min97.0 min
202318487.2 min93.5 min
202418990.5 min92.7 min
2025204117.1 min147.6 min
2026168121.8 min135.7 min
The Average Call Waits 136 Minutes for an Officer to ArriveAs calls rose 85% between 2016 and 2025, average response time has more than doubled in the past 10 years, from 63 minutes in 2016 to 136 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.

Threats/Harassment: 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 18% of threats/harassment 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: 6.6%2009 · 0–5 min: 7.6%2009 · 5–30 min: 40.5%2009 · 30–60 min: 19.9%2009 · 1–4 hr: 22.9%2009 · 4–8 hr: 2.3%2010 · No recorded response: 20.4%2010 · 0–5 min: 10.2%2010 · 5–30 min: 42.6%2010 · 30–60 min: 12.0%2010 · 1–4 hr: 13.9%2010 · 4–8 hr: 0.9%2011 · No recorded response: 32.4%2011 · 0–5 min: 13.2%2011 · 5–30 min: 23.5%2011 · 30–60 min: 16.2%2011 · 1–4 hr: 14.7%2012 · No recorded response: 28.2%2012 · 0–5 min: 10.9%2012 · 5–30 min: 20.9%2012 · 30–60 min: 10.0%2012 · 1–4 hr: 28.2%2012 · 4–8 hr: 1.8%2013 · No recorded response: 36.6%2013 · 0–5 min: 9.9%2013 · 5–30 min: 25.7%2013 · 30–60 min: 11.9%2013 · 1–4 hr: 14.8%2013 · 4–8 hr: 1.0%2014 · No recorded response: 29.2%2014 · 0–5 min: 7.5%2014 · 5–30 min: 31.7%2014 · 30–60 min: 12.5%2014 · 1–4 hr: 18.3%2014 · 4–8 hr: 0.8%2015 · No recorded response: 24.1%2015 · 0–5 min: 12.0%2015 · 5–30 min: 26.9%2015 · 30–60 min: 9.3%2015 · 1–4 hr: 24.1%2015 · 4–8 hr: 2.8%2015 · Over 8 hr: 0.9%2016 · No recorded response: 30.9%2016 · 0–5 min: 12.8%2016 · 5–30 min: 27.7%2016 · 30–60 min: 10.6%2016 · 1–4 hr: 13.8%2016 · 4–8 hr: 2.1%2016 · Over 8 hr: 2.1%2017 · No recorded response: 38.5%2017 · 0–5 min: 9.2%2017 · 5–30 min: 22.9%2017 · 30–60 min: 7.3%2017 · 1–4 hr: 20.2%2017 · 4–8 hr: 1.8%2018 · No recorded response: 38.7%2018 · 0–5 min: 2.4%2018 · 5–30 min: 19.4%2018 · 30–60 min: 14.5%2018 · 1–4 hr: 13.7%2018 · 4–8 hr: 9.7%2018 · Over 8 hr: 1.6%2019 · No recorded response: 36.8%2019 · 0–5 min: 9.8%2019 · 5–30 min: 16.6%2019 · 30–60 min: 8.0%2019 · 1–4 hr: 24.5%2019 · 4–8 hr: 4.3%2020 · No recorded response: 25.2%2020 · 0–5 min: 12.9%2020 · 5–30 min: 23.2%2020 · 30–60 min: 7.1%2020 · 1–4 hr: 27.1%2020 · 4–8 hr: 4.5%2021 · No recorded response: 34.6%2021 · 0–5 min: 6.8%2021 · 5–30 min: 21.8%2021 · 30–60 min: 9.0%2021 · 1–4 hr: 21.1%2021 · 4–8 hr: 5.3%2021 · Over 8 hr: 1.5%2022 · No recorded response: 21.1%2022 · 0–5 min: 8.9%2022 · 5–30 min: 30.1%2022 · 30–60 min: 13.8%2022 · 1–4 hr: 17.9%2022 · 4–8 hr: 4.9%2022 · Over 8 hr: 3.2%2023 · No recorded response: 27.2%2023 · 0–5 min: 13.6%2023 · 5–30 min: 30.4%2023 · 30–60 min: 7.1%2023 · 1–4 hr: 14.7%2023 · 4–8 hr: 3.3%2023 · Over 8 hr: 3.8%2024 · No recorded response: 26.5%2024 · 0–5 min: 14.8%2024 · 5–30 min: 24.3%2024 · 30–60 min: 9.5%2024 · 1–4 hr: 16.4%2024 · 4–8 hr: 5.3%2024 · Over 8 hr: 3.2%2025 · No recorded response: 20.6%2025 · 0–5 min: 11.3%2025 · 5–30 min: 27.4%2025 · 30–60 min: 8.3%2025 · 1–4 hr: 16.7%2025 · 4–8 hr: 7.8%2025 · Over 8 hr: 7.8%2026 · No recorded response: 17.9%2026 · 0–5 min: 10.7%2026 · 5–30 min: 28.0%2026 · 30–60 min: 6.5%2026 · 1–4 hr: 25.6%2026 · 4–8 hr: 6.0%2026 · Over 8 hr: 5.4%2009n=3012011n=682013n=1012015n=1082017n=1092019n=1632021n=1332023n=1842025n=2042026n=168
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
20093016.6%7.6%40.5%19.9%22.9%2.3%—
201010820.4%10.2%42.6%12.0%13.9%0.9%—
20116832.4%13.2%23.5%16.2%14.7%——
201211028.2%10.9%20.9%10.0%28.2%1.8%—
201310136.6%9.9%25.7%11.9%14.8%1.0%—
201412029.2%7.5%31.7%12.5%18.3%0.8%—
201510824.1%12.0%26.9%9.3%24.1%2.8%0.9%
20169430.9%12.8%27.7%10.6%13.8%2.1%2.1%
201710938.5%9.2%22.9%7.3%20.2%1.8%—
201812438.7%2.4%19.4%14.5%13.7%9.7%1.6%
201916336.8%9.8%16.6%8.0%24.5%4.3%—
202015525.2%12.9%23.2%7.1%27.1%4.5%—
202113334.6%6.8%21.8%9.0%21.1%5.3%1.5%
202212321.1%8.9%30.1%13.8%17.9%4.9%3.2%
202318427.2%13.6%30.4%7.1%14.7%3.3%3.8%
202418926.5%14.8%24.3%9.5%16.4%5.3%3.2%
202520420.6%11.3%27.4%8.3%16.7%7.8%7.8%
202616817.9%10.7%28.0%6.5%25.6%6.0%5.4%
The Average Call Waits 122 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 122 minutes in 2026, about 1.9 times what it was in 2016. 37% of calls took more than an hour to get a response in 2026, compared with 18% 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.