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

Public Gatherings

Public Gatherings calls over time: volume, outcomes, and response speed

Public Gatherings: 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 (47% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
03006002009: 10 public gatherings calls logged in CAD2010: 6 public gatherings calls logged in CAD2011: 20 public gatherings calls logged in CAD2012: 8 public gatherings calls logged in CAD2013: 15 public gatherings calls logged in CAD2014: 163 public gatherings calls logged in CAD2015: 226 public gatherings calls logged in CAD2016: 174 public gatherings calls logged in CAD2017: 282 public gatherings calls logged in CAD2018: 223 public gatherings calls logged in CAD2019: 280 public gatherings calls logged in CAD2020: 553 public gatherings calls logged in CAD2021: 306 public gatherings calls logged in CAD2022: 137 public gatherings calls logged in CAD2023: 191 public gatherings calls logged in CAD2024: 123 public gatherings calls logged in CAD2025: 170 public gatherings calls logged in CAD2026: 167 public gatherings calls logged in CAD2009n=102011n=202013n=152015n=2262017n=2822019n=2802021n=3062023n=1912025n=1702026n=167
public gatherings calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodPublic gatherings calls logged in CAD
200910
20106
201120
20128
201315
2014163
2015226
2016174
2017282
2018223
2019280
2020553
2021306
2022137
2023191
2024123
2025170
2026167
Calls for Public Gatherings Are Down 69% From Their 2020 PeakSeattle Police logged 553 public gatherings calls in 2020 and 170 in 2025, the most recent full year.

Public Gatherings: 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 · Resolved on scene: 80.0%2009 · Unable to locate: 10.0%2009 · Other (unfounded / cancelled): 10.0%2010 · Resolved on scene: 16.7%2010 · Other (unfounded / cancelled): 83.4%2011 · Resolved on scene: 5.0%2011 · Unable to locate: 10.0%2011 · Other (unfounded / cancelled): 85.0%2012 · Resolved on scene: 37.5%2012 · Other (unfounded / cancelled): 62.5%2013 · Resolved on scene: 20.0%2013 · Other (unfounded / cancelled): 80.0%2014 · Report taken, no arrest: 6.1%2014 · Resolved on scene: 77.9%2014 · Unable to locate: 3.7%2014 · Other (unfounded / cancelled): 12.3%2015 · Arrest / citation: 0.4%2015 · Report taken, no arrest: 4.9%2015 · Resolved on scene: 79.6%2015 · Unable to locate: 8.4%2015 · Other (unfounded / cancelled): 6.6%2016 · Report taken, no arrest: 3.4%2016 · Resolved on scene: 83.3%2016 · Unable to locate: 2.3%2016 · Other (unfounded / cancelled): 10.9%2017 · Arrest / citation: 1.4%2017 · Report taken, no arrest: 5.3%2017 · Resolved on scene: 84.4%2017 · Unable to locate: 4.6%2017 · Other (unfounded / cancelled): 4.3%2018 · Arrest / citation: 1.3%2018 · Report taken, no arrest: 4.5%2018 · Resolved on scene: 80.7%2018 · Unable to locate: 5.4%2018 · Other (unfounded / cancelled): 8.1%2019 · Arrest / citation: 0.7%2019 · Report taken, no arrest: 3.9%2019 · Resolved on scene: 78.6%2019 · Unable to locate: 7.9%2019 · Other (unfounded / cancelled): 8.9%2020 · Arrest / citation: 8.1%2020 · Report taken, no arrest: 7.4%2020 · Resolved on scene: 73.6%2020 · Unable to locate: 5.2%2020 · Other (unfounded / cancelled): 5.6%2021 · Arrest / citation: 1.0%2021 · Report taken, no arrest: 4.6%2021 · Resolved on scene: 75.8%2021 · Unable to locate: 13.4%2021 · Other (unfounded / cancelled): 5.2%2022 · Arrest / citation: 0.7%2022 · Report taken, no arrest: 5.1%2022 · Resolved on scene: 73.0%2022 · Unable to locate: 18.2%2022 · Other (unfounded / cancelled): 2.9%2023 · Arrest / citation: 0.5%2023 · Report taken, no arrest: 4.7%2023 · Resolved on scene: 72.8%2023 · Unable to locate: 20.4%2023 · Other (unfounded / cancelled): 1.6%2024 · Arrest / citation: 1.6%2024 · Report taken, no arrest: 1.6%2024 · Resolved on scene: 70.7%2024 · Unable to locate: 20.3%2024 · Other (unfounded / cancelled): 5.7%2025 · Arrest / citation: 1.2%2025 · Report taken, no arrest: 5.9%2025 · Resolved on scene: 64.1%2025 · Unable to locate: 22.9%2025 · Other (unfounded / cancelled): 5.9%2026 · Arrest / citation: 1.2%2026 · Report taken, no arrest: 4.8%2026 · Resolved on scene: 68.9%2026 · Unable to locate: 21.6%2026 · Other (unfounded / cancelled): 3.6%2009n=102011n=202013n=152015n=2262017n=2822019n=2802021n=3062023n=1912025n=1702026n=167
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
PeriodEventsResolved on sceneUnable to locateOther (unfounded / cancelled)Report taken, no arrestArrest / citation
20091080.0%10.0%10.0%——
2010616.7%—83.4%——
2011205.0%10.0%85.0%——
2012837.5%—62.5%——
20131520.0%—80.0%——
201416377.9%3.7%12.3%6.1%—
201522679.6%8.4%6.6%4.9%0.4%
201617483.3%2.3%10.9%3.4%—
201728284.4%4.6%4.3%5.3%1.4%
201822380.7%5.4%8.1%4.5%1.3%
201928078.6%7.9%8.9%3.9%0.7%
202055373.6%5.2%5.6%7.4%8.1%
202130675.8%13.4%5.2%4.6%1.0%
202213773.0%18.2%2.9%5.1%0.7%
202319172.8%20.4%1.6%4.7%0.5%
202412370.7%20.3%5.7%1.6%1.6%
202517064.1%22.9%5.9%5.9%1.2%
202616768.9%21.6%3.6%4.8%1.2%
22% of Calls for Public Gatherings End “Unable to Locate,” Up From 2%Report-taken outcomes moved from 3% of calls in 2016 to 5% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Public Gatherings: 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 47% of public gatherings 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 min60 min120 min2009: 2.7 min2010: 10.8 min2011: 14.0 min2013: 3.0 min2014: 64.9 min2015: 30.9 min2016: 17.4 min2017: 21.0 min2018: 33.8 min2019: 21.2 min2020: 50.0 min2021: 54.5 min2022: 66.9 min2023: 88.4 min2024: 63.1 min2025: 75.6 min2026: 104.2 min2009: 7.0 min2010: 16.8 min2011: 3.5 min2013: 9.6 min2014: 74.6 min2015: 37.4 min2016: 25.9 min2017: 25.5 min2018: 39.3 min2019: 27.2 min2020: 58.3 min2021: 59.5 min2022: 80.1 min2023: 84.3 min2024: 49.5 min2025: 74.7 min2026: 104.0 min2009n=32011n=52013n=62015n=1192017n=1392019n=1322021n=1772023n=1172025n=1072026n=104
Average response timeAverage dispatch delay
Small sample: Only a small share of public gatherings events are called in. The year with the fewest had only 2, 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
200932.7 min7.0 min
2010210.8 min16.8 min
2011514.0 min3.5 min
20120——
201363.0 min9.6 min
20147064.9 min74.6 min
201511930.9 min37.4 min
20168217.4 min25.9 min
201713921.0 min25.5 min
201810133.8 min39.3 min
201913221.2 min27.2 min
202031050.0 min58.3 min
202117754.5 min59.5 min
20228466.9 min80.1 min
202311788.4 min84.3 min
20247463.1 min49.5 min
202510775.6 min74.7 min
2026104104.2 min104.0 min
The Average Call Waits 104 Minutes for an Officer to ArriveAverage response time has grown about 4-fold in the past 10 years, from 26 minutes in 2016 to 104 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.

Public Gatherings: 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 47% of public gatherings 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: 33.3%2009 · 0–5 min: 33.3%2009 · 5–30 min: 33.3%2010 · 5–30 min: 100.0%2011 · No recorded response: 60.0%2011 · 0–5 min: 20.0%2011 · 5–30 min: 20.0%2013 · 0–5 min: 33.3%2013 · 5–30 min: 66.7%2014 · No recorded response: 10.0%2014 · 0–5 min: 24.3%2014 · 5–30 min: 44.3%2014 · 30–60 min: 10.0%2014 · 1–4 hr: 8.6%2014 · 4–8 hr: 1.4%2014 · Over 8 hr: 1.4%2015 · No recorded response: 11.8%2015 · 0–5 min: 17.6%2015 · 5–30 min: 46.2%2015 · 30–60 min: 10.9%2015 · 1–4 hr: 11.8%2015 · 4–8 hr: 0.8%2015 · Over 8 hr: 0.8%2016 · No recorded response: 6.1%2016 · 0–5 min: 24.4%2016 · 5–30 min: 51.2%2016 · 30–60 min: 9.8%2016 · 1–4 hr: 7.3%2016 · 4–8 hr: 1.2%2017 · No recorded response: 6.5%2017 · 0–5 min: 36.7%2017 · 5–30 min: 41.0%2017 · 30–60 min: 5.8%2017 · 1–4 hr: 7.9%2017 · 4–8 hr: 2.2%2018 · No recorded response: 10.9%2018 · 0–5 min: 31.7%2018 · 5–30 min: 29.7%2018 · 30–60 min: 12.9%2018 · 1–4 hr: 10.9%2018 · 4–8 hr: 4.0%2019 · No recorded response: 10.6%2019 · 0–5 min: 30.3%2019 · 5–30 min: 34.9%2019 · 30–60 min: 12.1%2019 · 1–4 hr: 11.4%2019 · 4–8 hr: 0.8%2020 · No recorded response: 4.2%2020 · 0–5 min: 31.0%2020 · 5–30 min: 26.8%2020 · 30–60 min: 14.2%2020 · 1–4 hr: 18.4%2020 · 4–8 hr: 4.8%2020 · Over 8 hr: 0.7%2021 · No recorded response: 13.6%2021 · 0–5 min: 16.4%2021 · 5–30 min: 33.3%2021 · 30–60 min: 13.6%2021 · 1–4 hr: 16.9%2021 · 4–8 hr: 4.5%2021 · Over 8 hr: 1.7%2022 · No recorded response: 13.1%2022 · 0–5 min: 19.1%2022 · 5–30 min: 25.0%2022 · 30–60 min: 11.9%2022 · 1–4 hr: 23.8%2022 · 4–8 hr: 4.8%2022 · Over 8 hr: 2.4%2023 · No recorded response: 17.9%2023 · 0–5 min: 12.8%2023 · 5–30 min: 34.2%2023 · 30–60 min: 12.8%2023 · 1–4 hr: 14.5%2023 · 4–8 hr: 4.3%2023 · Over 8 hr: 3.4%2024 · No recorded response: 13.5%2024 · 0–5 min: 14.9%2024 · 5–30 min: 36.5%2024 · 30–60 min: 14.9%2024 · 1–4 hr: 17.6%2024 · 4–8 hr: 2.7%2025 · No recorded response: 16.8%2025 · 0–5 min: 17.8%2025 · 5–30 min: 25.2%2025 · 30–60 min: 12.2%2025 · 1–4 hr: 20.6%2025 · 4–8 hr: 6.5%2025 · Over 8 hr: 0.9%2026 · No recorded response: 12.5%2026 · 0–5 min: 17.3%2026 · 5–30 min: 19.2%2026 · 30–60 min: 14.4%2026 · 1–4 hr: 26.0%2026 · 4–8 hr: 6.7%2026 · Over 8 hr: 3.9%2009n=32011n=52013n=62015n=1192017n=1392019n=1322021n=1772023n=1172025n=1072026n=104
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of public gatherings events are called in. The year with the fewest had only 2, 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
2009333.3%33.3%33.3%————
20102——100.0%————
2011560.0%20.0%20.0%————
20120———————
20136—33.3%66.7%————
20147010.0%24.3%44.3%10.0%8.6%1.4%1.4%
201511911.8%17.6%46.2%10.9%11.8%0.8%0.8%
2016826.1%24.4%51.2%9.8%7.3%1.2%—
20171396.5%36.7%41.0%5.8%7.9%2.2%—
201810110.9%31.7%29.7%12.9%10.9%4.0%—
201913210.6%30.3%34.9%12.1%11.4%0.8%—
20203104.2%31.0%26.8%14.2%18.4%4.8%0.7%
202117713.6%16.4%33.3%13.6%16.9%4.5%1.7%
20228413.1%19.1%25.0%11.9%23.8%4.8%2.4%
202311717.9%12.8%34.2%12.8%14.5%4.3%3.4%
20247413.5%14.9%36.5%14.9%17.6%2.7%—
202510716.8%17.8%25.2%12.2%20.6%6.5%0.9%
202610412.5%17.3%19.2%14.4%26.0%6.7%3.9%
The Average Call Waits 104 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 104 minutes in 2026, more than double what it was in 2016. 37% of calls took more than an hour to get a response in 2026, compared with 9% 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.