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.
| Period | Public gatherings calls logged in CAD |
|---|---|
| 2009 | 10 |
| 2010 | 6 |
| 2011 | 20 |
| 2012 | 8 |
| 2013 | 15 |
| 2014 | 163 |
| 2015 | 226 |
| 2016 | 174 |
| 2017 | 282 |
| 2018 | 223 |
| 2019 | 280 |
| 2020 | 553 |
| 2021 | 306 |
| 2022 | 137 |
| 2023 | 191 |
| 2024 | 123 |
| 2025 | 170 |
| 2026 | 167 |
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.
| Period | Events | Resolved on scene | Unable to locate | Other (unfounded / cancelled) | Report taken, no arrest | Arrest / citation |
|---|---|---|---|---|---|---|
| 2009 | 10 | 80.0% | 10.0% | 10.0% | — | — |
| 2010 | 6 | 16.7% | — | 83.4% | — | — |
| 2011 | 20 | 5.0% | 10.0% | 85.0% | — | — |
| 2012 | 8 | 37.5% | — | 62.5% | — | — |
| 2013 | 15 | 20.0% | — | 80.0% | — | — |
| 2014 | 163 | 77.9% | 3.7% | 12.3% | 6.1% | — |
| 2015 | 226 | 79.6% | 8.4% | 6.6% | 4.9% | 0.4% |
| 2016 | 174 | 83.3% | 2.3% | 10.9% | 3.4% | — |
| 2017 | 282 | 84.4% | 4.6% | 4.3% | 5.3% | 1.4% |
| 2018 | 223 | 80.7% | 5.4% | 8.1% | 4.5% | 1.3% |
| 2019 | 280 | 78.6% | 7.9% | 8.9% | 3.9% | 0.7% |
| 2020 | 553 | 73.6% | 5.2% | 5.6% | 7.4% | 8.1% |
| 2021 | 306 | 75.8% | 13.4% | 5.2% | 4.6% | 1.0% |
| 2022 | 137 | 73.0% | 18.2% | 2.9% | 5.1% | 0.7% |
| 2023 | 191 | 72.8% | 20.4% | 1.6% | 4.7% | 0.5% |
| 2024 | 123 | 70.7% | 20.3% | 5.7% | 1.6% | 1.6% |
| 2025 | 170 | 64.1% | 22.9% | 5.9% | 5.9% | 1.2% |
| 2026 | 167 | 68.9% | 21.6% | 3.6% | 4.8% | 1.2% |
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| 2009 | 3 | 2.7 min | 7.0 min |
| 2010 | 2 | 10.8 min | 16.8 min |
| 2011 | 5 | 14.0 min | 3.5 min |
| 2012 | 0 | — | — |
| 2013 | 6 | 3.0 min | 9.6 min |
| 2014 | 70 | 64.9 min | 74.6 min |
| 2015 | 119 | 30.9 min | 37.4 min |
| 2016 | 82 | 17.4 min | 25.9 min |
| 2017 | 139 | 21.0 min | 25.5 min |
| 2018 | 101 | 33.8 min | 39.3 min |
| 2019 | 132 | 21.2 min | 27.2 min |
| 2020 | 310 | 50.0 min | 58.3 min |
| 2021 | 177 | 54.5 min | 59.5 min |
| 2022 | 84 | 66.9 min | 80.1 min |
| 2023 | 117 | 88.4 min | 84.3 min |
| 2024 | 74 | 63.1 min | 49.5 min |
| 2025 | 107 | 75.6 min | 74.7 min |
| 2026 | 104 | 104.2 min | 104.0 min |
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| 2009 | 0 | — | — |
| 2010 | 0 | — | — |
| 2011 | 0 | — | — |
| 2012 | 0 | — | — |
| 2013 | 0 | — | — |
| 2014 | 2 | 2.7 min | 6.2 min |
| 2015 | 2 | 1.5 min | 12.2 min |
| 2016 | 2 | 1.1 min | 6.5 min |
| 2017 | 4 | 0.7 min | 4.9 min |
| 2018 | 0 | — | — |
| 2019 | 4 | 7.6 min | 18.9 min |
| 2020 | 2 | 0.8 min | 3.4 min |
| 2021 | 2 | 2.2 min | 7.0 min |
| 2022 | 6 | 1.5 min | 11.5 min |
| 2023 | 9 | 1.7 min | 13.2 min |
| 2024 | 2 | 3.2 min | 11.3 min |
| 2025 | 6 | 1.8 min | 6.0 min |
| 2026 | 1 | 1.2 min | 6.5 min |
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| 2009 | 0 | — | — |
| 2010 | 0 | — | — |
| 2011 | 0 | — | — |
| 2012 | 0 | — | — |
| 2013 | 1 | 5.7 min | 11.6 min |
| 2014 | 8 | 6.3 min | 12.7 min |
| 2015 | 33 | 12.8 min | 21.1 min |
| 2016 | 21 | 11.9 min | 20.4 min |
| 2017 | 24 | 10.7 min | 15.5 min |
| 2018 | 15 | 29.9 min | 40.9 min |
| 2019 | 22 | 13.4 min | 27.5 min |
| 2020 | 25 | 22.9 min | 34.9 min |
| 2021 | 33 | 39.6 min | 61.4 min |
| 2022 | 13 | 68.9 min | 81.2 min |
| 2023 | 19 | 26.5 min | 29.0 min |
| 2024 | 9 | 54.5 min | 54.6 min |
| 2025 | 27 | 40.1 min | 45.5 min |
| 2026 | 11 | 42.9 min | 43.3 min |
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| 2009 | 3 | 2.7 min | 7.0 min |
| 2010 | 2 | 10.8 min | 16.8 min |
| 2011 | 5 | 14.0 min | 3.5 min |
| 2012 | 0 | — | — |
| 2013 | 5 | 2.5 min | 9.2 min |
| 2014 | 54 | 77.2 min | 89.2 min |
| 2015 | 82 | 39.6 min | 45.8 min |
| 2016 | 57 | 20.5 min | 29.0 min |
| 2017 | 93 | 23.2 min | 28.6 min |
| 2018 | 64 | 32.6 min | 38.5 min |
| 2019 | 72 | 21.5 min | 26.8 min |
| 2020 | 263 | 53.8 min | 61.7 min |
| 2021 | 133 | 61.2 min | 62.5 min |
| 2022 | 53 | 56.7 min | 58.8 min |
| 2023 | 85 | 103.4 min | 92.5 min |
| 2024 | 53 | 67.5 min | 43.8 min |
| 2025 | 61 | 96.8 min | 91.4 min |
| 2026 | 69 | 138.7 min | 139.7 min |
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.
| Period | Called-in events | No recorded response | 0–5 min | 5–30 min | 30–60 min | 1–4 hr | 4–8 hr | Over 8 hr |
|---|---|---|---|---|---|---|---|---|
| 2009 | 3 | 33.3% | 33.3% | 33.3% | — | — | — | — |
| 2010 | 2 | — | — | 100.0% | — | — | — | — |
| 2011 | 5 | 60.0% | 20.0% | 20.0% | — | — | — | — |
| 2012 | 0 | — | — | — | — | — | — | — |
| 2013 | 6 | — | 33.3% | 66.7% | — | — | — | — |
| 2014 | 70 | 10.0% | 24.3% | 44.3% | 10.0% | 8.6% | 1.4% | 1.4% |
| 2015 | 119 | 11.8% | 17.6% | 46.2% | 10.9% | 11.8% | 0.8% | 0.8% |
| 2016 | 82 | 6.1% | 24.4% | 51.2% | 9.8% | 7.3% | 1.2% | — |
| 2017 | 139 | 6.5% | 36.7% | 41.0% | 5.8% | 7.9% | 2.2% | — |
| 2018 | 101 | 10.9% | 31.7% | 29.7% | 12.9% | 10.9% | 4.0% | — |
| 2019 | 132 | 10.6% | 30.3% | 34.9% | 12.1% | 11.4% | 0.8% | — |
| 2020 | 310 | 4.2% | 31.0% | 26.8% | 14.2% | 18.4% | 4.8% | 0.7% |
| 2021 | 177 | 13.6% | 16.4% | 33.3% | 13.6% | 16.9% | 4.5% | 1.7% |
| 2022 | 84 | 13.1% | 19.1% | 25.0% | 11.9% | 23.8% | 4.8% | 2.4% |
| 2023 | 117 | 17.9% | 12.8% | 34.2% | 12.8% | 14.5% | 4.3% | 3.4% |
| 2024 | 74 | 13.5% | 14.9% | 36.5% | 14.9% | 17.6% | 2.7% | — |
| 2025 | 107 | 16.8% | 17.8% | 25.2% | 12.2% | 20.6% | 6.5% | 0.9% |
| 2026 | 104 | 12.5% | 17.3% | 19.2% | 14.4% | 26.0% | 6.7% | 3.9% |
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.
| Period | Called-in events | 0–5 min | 5–30 min | No recorded response | 30–60 min |
|---|---|---|---|---|---|
| 2009 | 0 | — | — | — | — |
| 2010 | 0 | — | — | — | — |
| 2011 | 0 | — | — | — | — |
| 2012 | 0 | — | — | — | — |
| 2013 | 0 | — | — | — | — |
| 2014 | 2 | 50.0% | 50.0% | — | — |
| 2015 | 2 | 50.0% | 50.0% | — | — |
| 2016 | 2 | — | 50.0% | 50.0% | — |
| 2017 | 4 | 50.0% | 50.0% | — | — |
| 2018 | 0 | — | — | — | — |
| 2019 | 4 | 25.0% | 25.0% | 25.0% | 25.0% |
| 2020 | 2 | 100.0% | — | — | — |
| 2021 | 2 | 50.0% | 50.0% | — | — |
| 2022 | 6 | 50.0% | 33.3% | — | 16.7% |
| 2023 | 9 | 11.1% | 88.9% | — | — |
| 2024 | 2 | — | 100.0% | — | — |
| 2025 | 6 | 33.3% | 33.3% | 33.3% | — |
| 2026 | 1 | — | 100.0% | — | — |
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.
| Period | Called-in events | 5–30 min | No recorded response | 0–5 min | 30–60 min | 1–4 hr | 4–8 hr |
|---|---|---|---|---|---|---|---|
| 2009 | 0 | — | — | — | — | — | — |
| 2010 | 0 | — | — | — | — | — | — |
| 2011 | 0 | — | — | — | — | — | — |
| 2012 | 0 | — | — | — | — | — | — |
| 2013 | 1 | 100.0% | — | — | — | — | — |
| 2014 | 8 | 75.0% | 12.5% | 12.5% | — | — | — |
| 2015 | 33 | 60.6% | 6.1% | 12.1% | 15.2% | 6.1% | — |
| 2016 | 21 | 61.9% | 9.5% | 14.3% | 9.5% | 4.8% | — |
| 2017 | 24 | 70.8% | 4.2% | 12.5% | 8.3% | 4.2% | — |
| 2018 | 15 | 33.3% | 6.7% | 13.3% | 20.0% | 26.7% | — |
| 2019 | 22 | 59.1% | 9.1% | 9.1% | 4.5% | 18.2% | — |
| 2020 | 25 | 48.0% | — | 16.0% | 16.0% | 20.0% | — |
| 2021 | 33 | 42.4% | 6.1% | 3.0% | 18.2% | 24.2% | 6.1% |
| 2022 | 13 | 23.1% | 7.7% | 7.7% | 15.4% | 38.5% | 7.7% |
| 2023 | 19 | 42.1% | 36.8% | 5.3% | 10.5% | 5.3% | — |
| 2024 | 9 | 33.3% | 44.4% | — | 11.1% | 11.1% | — |
| 2025 | 27 | 44.5% | 11.1% | 3.7% | 14.8% | 25.9% | — |
| 2026 | 11 | 54.5% | 18.2% | — | 9.1% | 18.2% | — |
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.
| Period | Called-in events | No recorded response | 0–5 min | 5–30 min | 30–60 min | 1–4 hr | 4–8 hr | Over 8 hr |
|---|---|---|---|---|---|---|---|---|
| 2009 | 3 | 33.3% | 33.3% | 33.3% | — | — | — | — |
| 2010 | 2 | — | — | 100.0% | — | — | — | — |
| 2011 | 5 | 60.0% | 20.0% | 20.0% | — | — | — | — |
| 2012 | 0 | — | — | — | — | — | — | — |
| 2013 | 5 | — | 40.0% | 60.0% | — | — | — | — |
| 2014 | 54 | 11.1% | 27.8% | 37.0% | 13.0% | 7.4% | 1.9% | 1.9% |
| 2015 | 82 | 13.4% | 18.3% | 41.5% | 9.8% | 14.6% | 1.2% | 1.2% |
| 2016 | 57 | 3.5% | 26.3% | 49.1% | 10.5% | 8.8% | 1.8% | — |
| 2017 | 93 | 8.6% | 34.4% | 38.7% | 6.5% | 9.7% | 2.1% | — |
| 2018 | 64 | 15.6% | 25.0% | 34.4% | 14.1% | 6.2% | 4.7% | — |
| 2019 | 72 | 15.3% | 27.8% | 33.3% | 12.5% | 11.1% | — | — |
| 2020 | 263 | 4.9% | 31.2% | 26.2% | 13.3% | 18.2% | 5.3% | 0.8% |
| 2021 | 133 | 15.8% | 17.3% | 31.6% | 12.8% | 15.8% | 4.5% | 2.3% |
| 2022 | 53 | 18.9% | 18.9% | 30.2% | 13.2% | 15.1% | 1.9% | 1.9% |
| 2023 | 85 | 16.5% | 14.1% | 28.2% | 15.3% | 16.5% | 5.9% | 3.5% |
| 2024 | 53 | 11.3% | 17.0% | 35.9% | 17.0% | 17.0% | 1.9% | — |
| 2025 | 61 | 21.3% | 19.7% | 18.0% | 14.8% | 16.4% | 8.2% | 1.6% |
| 2026 | 69 | 15.9% | 13.0% | 11.6% | 18.8% | 26.1% | 8.7% | 5.8% |
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.
| Period | Public gatherings calls logged in CAD |
|---|---|
| Sep 2025 | 17 |
| Oct 2025 | 15 |
| Nov 2025 | 12 |
| Dec 2025 | 11 |
| Jan 2026 | 33 |
| Feb 2026 | 14 |
| Mar 2026 | 12 |
| Apr 2026 | 10 |
| May 2026 | 12 |
| Jun 2026 | 31 |
| Jul 2026 | 34 |
| Aug 2026 | 19 |
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.
| Period | Events | Resolved on scene | Unable to locate | Other (unfounded / cancelled) | Report taken, no arrest | Arrest / citation |
|---|---|---|---|---|---|---|
| Sep 2025 | 17 | 70.6% | 17.6% | 11.8% | — | — |
| Oct 2025 | 15 | 80.0% | 13.3% | 6.7% | — | — |
| Nov 2025 | 12 | 41.7% | 58.3% | — | — | — |
| Dec 2025 | 11 | 54.5% | 18.2% | — | 27.3% | — |
| Jan 2026 | 33 | 69.7% | 21.2% | 9.1% | — | — |
| Feb 2026 | 14 | 64.3% | 21.4% | — | 14.3% | — |
| Mar 2026 | 12 | 75.0% | 25.0% | — | — | — |
| Apr 2026 | 10 | 40.0% | 30.0% | 10.0% | — | 20.0% |
| May 2026 | 12 | 58.3% | 25.0% | — | 16.7% | — |
| Jun 2026 | 31 | 74.2% | 16.1% | 3.2% | 6.5% | — |
| Jul 2026 | 34 | 76.5% | 14.7% | 2.9% | 5.9% | — |
| Aug 2026 | 19 | 68.4% | 31.6% | — | — | — |
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| Sep 2025 | 9 | 70.7 min | 30.6 min |
| Oct 2025 | 6 | 72.4 min | 86.3 min |
| Nov 2025 | 9 | 135.8 min | 145.6 min |
| Dec 2025 | 8 | 26.3 min | 35.5 min |
| Jan 2026 | 15 | 35.3 min | 43.1 min |
| Feb 2026 | 4 | 68.5 min | 71.9 min |
| Mar 2026 | 10 | 58.6 min | 60.4 min |
| Apr 2026 | 5 | 56.3 min | 70.1 min |
| May 2026 | 9 | 104.1 min | 118.7 min |
| Jun 2026 | 18 | 106.6 min | 151.1 min |
| Jul 2026 | 27 | 79.3 min | 84.8 min |
| Aug 2026 | 14 | 250.6 min | 220.9 min |
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| Sep 2025 | 1 | 2.5 min | 5.0 min |
| Oct 2025 | 0 | — | — |
| Nov 2025 | 0 | — | — |
| Dec 2025 | 0 | — | — |
| Jan 2026 | 0 | — | — |
| Feb 2026 | 0 | — | — |
| Mar 2026 | 1 | 1.2 min | 6.5 min |
| Apr 2026 | 0 | — | — |
| May 2026 | 0 | — | — |
| Jun 2026 | 0 | — | — |
| Jul 2026 | 0 | — | — |
| Aug 2026 | 0 | — | — |
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| Sep 2025 | 1 | 119.3 min | 119.3 min |
| Oct 2025 | 2 | 8.2 min | 19.2 min |
| Nov 2025 | 1 | 90.8 min | 96.5 min |
| Dec 2025 | 1 | 3.0 min | 9.9 min |
| Jan 2026 | 4 | 29.8 min | 15.9 min |
| Feb 2026 | 1 | 132.1 min | 145.8 min |
| Mar 2026 | 0 | — | — |
| Apr 2026 | 0 | — | — |
| May 2026 | 2 | 16.3 min | 26.3 min |
| Jun 2026 | 3 | 38.1 min | 14.2 min |
| Jul 2026 | 0 | — | — |
| Aug 2026 | 1 | 74.1 min | 115.3 min |
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| Sep 2025 | 6 | 85.5 min | 22.1 min |
| Oct 2025 | 4 | 104.6 min | 131.1 min |
| Nov 2025 | 8 | 141.5 min | 152.6 min |
| Dec 2025 | 6 | 32.4 min | 42.6 min |
| Jan 2026 | 11 | 37.3 min | 50.5 min |
| Feb 2026 | 2 | 70.3 min | 70.3 min |
| Mar 2026 | 6 | 81.2 min | 83.3 min |
| Apr 2026 | 4 | 64.2 min | 85.2 min |
| May 2026 | 7 | 129.2 min | 149.5 min |
| Jun 2026 | 9 | 164.8 min | 251.2 min |
| Jul 2026 | 17 | 107.0 min | 122.3 min |
| Aug 2026 | 11 | 309.1 min | 285.2 min |
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.
| Period | Called-in events | No recorded response | 0–5 min | 5–30 min | 30–60 min | 1–4 hr | 4–8 hr | Over 8 hr |
|---|---|---|---|---|---|---|---|---|
| Sep 2025 | 9 | 22.2% | 33.3% | 22.2% | 11.1% | 11.1% | — | — |
| Oct 2025 | 6 | 16.7% | 16.7% | 33.3% | 16.7% | — | 16.7% | — |
| Nov 2025 | 9 | 11.1% | — | 11.1% | 11.1% | 44.4% | 22.2% | — |
| Dec 2025 | 8 | 12.5% | — | 50.0% | 25.0% | 12.5% | — | — |
| Jan 2026 | 15 | 6.7% | 26.7% | 40.0% | 6.7% | 20.0% | — | — |
| Feb 2026 | 4 | — | 25.0% | — | 25.0% | 50.0% | — | — |
| Mar 2026 | 10 | — | 30.0% | 10.0% | 30.0% | 30.0% | — | — |
| Apr 2026 | 5 | 20.0% | — | 40.0% | 20.0% | 20.0% | — | — |
| May 2026 | 9 | 11.1% | — | 22.2% | 44.4% | — | 11.1% | 11.1% |
| Jun 2026 | 18 | 16.7% | 11.1% | 16.7% | 5.6% | 27.8% | 16.7% | 5.6% |
| Jul 2026 | 27 | 11.1% | 22.2% | 18.5% | 11.1% | 29.6% | 3.7% | 3.7% |
| Aug 2026 | 14 | 21.4% | 7.1% | 7.1% | 7.1% | 35.7% | 14.3% | 7.1% |
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.
| Period | Called-in events | 0–5 min | 5–30 min |
|---|---|---|---|
| Sep 2025 | 1 | 100.0% | — |
| Oct 2025 | 0 | — | — |
| Nov 2025 | 0 | — | — |
| Dec 2025 | 0 | — | — |
| Jan 2026 | 0 | — | — |
| Feb 2026 | 0 | — | — |
| Mar 2026 | 1 | — | 100.0% |
| Apr 2026 | 0 | — | — |
| May 2026 | 0 | — | — |
| Jun 2026 | 0 | — | — |
| Jul 2026 | 0 | — | — |
| Aug 2026 | 0 | — | — |
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.
| Period | Called-in events | 1–4 hr | 5–30 min | 30–60 min | No recorded response |
|---|---|---|---|---|---|
| Sep 2025 | 1 | 100.0% | — | — | — |
| Oct 2025 | 2 | — | 50.0% | 50.0% | — |
| Nov 2025 | 1 | 100.0% | — | — | — |
| Dec 2025 | 1 | — | 100.0% | — | — |
| Jan 2026 | 4 | — | 75.0% | — | 25.0% |
| Feb 2026 | 1 | 100.0% | — | — | — |
| Mar 2026 | 0 | — | — | — | — |
| Apr 2026 | 0 | — | — | — | — |
| May 2026 | 2 | — | 50.0% | 50.0% | — |
| Jun 2026 | 3 | — | 66.7% | — | 33.3% |
| Jul 2026 | 0 | — | — | — | — |
| Aug 2026 | 1 | 100.0% | — | — | — |
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.
| Period | Called-in events | No recorded response | 0–5 min | 5–30 min | 30–60 min | 4–8 hr | 1–4 hr | Over 8 hr |
|---|---|---|---|---|---|---|---|---|
| Sep 2025 | 6 | 33.3% | 16.7% | 33.3% | 16.7% | — | — | — |
| Oct 2025 | 4 | 25.0% | 25.0% | 25.0% | — | 25.0% | — | — |
| Nov 2025 | 8 | 12.5% | — | 12.5% | 12.5% | 25.0% | 37.5% | — |
| Dec 2025 | 6 | 16.7% | — | 33.3% | 33.3% | — | 16.7% | — |
| Jan 2026 | 11 | — | 36.4% | 27.3% | 9.1% | — | 27.3% | — |
| Feb 2026 | 2 | — | — | — | 50.0% | — | 50.0% | — |
| Mar 2026 | 6 | — | 16.7% | — | 50.0% | — | 33.3% | — |
| Apr 2026 | 4 | 25.0% | — | 25.0% | 25.0% | — | 25.0% | — |
| May 2026 | 7 | 14.3% | — | 14.3% | 42.9% | 14.3% | — | 14.3% |
| Jun 2026 | 9 | 22.2% | 11.1% | — | 11.1% | 22.2% | 22.2% | 11.1% |
| Jul 2026 | 17 | 17.6% | 11.8% | 11.8% | 17.6% | 5.9% | 29.4% | 5.9% |
| Aug 2026 | 11 | 27.3% | — | 9.1% | — | 18.2% | 36.4% | 9.1% |
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.
| Period | Public gatherings calls logged in CAD |
|---|---|
| Week of Jun 15 | 10 |
| Week of Jun 22 | 15 |
| Week of Jun 29 | 7 |
| Week of Jul 6 | 13 |
| Week of Jul 13 | 8 |
| Week of Jul 20 | 4 |
| Week of Jul 27 | 10 |
| Week of Aug 3 | 3 |
| Week of Aug 10 | 3 |
| Week of Aug 17 | 4 |
| Week of Aug 24 | 3 |
| Week of Aug 31 | 1 |
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.
| Period | Events | Report taken, no arrest | Resolved on scene | Unable to locate | Other (unfounded / cancelled) |
|---|---|---|---|---|---|
| Week of Jun 15 | 10 | 10.0% | 90.0% | — | — |
| Week of Jun 22 | 15 | 6.7% | 66.7% | 20.0% | 6.7% |
| Week of Jun 29 | 7 | — | 71.4% | 28.6% | — |
| Week of Jul 6 | 13 | — | 84.6% | 15.4% | — |
| Week of Jul 13 | 8 | 12.5% | 50.0% | 25.0% | 12.5% |
| Week of Jul 20 | 4 | 25.0% | 75.0% | — | — |
| Week of Jul 27 | 10 | — | 70.0% | 30.0% | — |
| Week of Aug 3 | 3 | — | 66.7% | 33.3% | — |
| Week of Aug 10 | 3 | — | 66.7% | 33.3% | — |
| Week of Aug 17 | 4 | — | 75.0% | 25.0% | — |
| Week of Aug 24 | 3 | — | 100.0% | — | — |
| Week of Aug 31 | 1 | — | 100.0% | — | — |
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| Week of Jun 15 | 6 | 48.4 min | 220.7 min |
| Week of Jun 22 | 9 | 112.1 min | 95.4 min |
| Week of Jun 29 | 5 | 153.8 min | 68.0 min |
| Week of Jul 6 | 10 | 89.9 min | 33.5 min |
| Week of Jul 13 | 7 | 39.0 min | 57.5 min |
| Week of Jul 20 | 3 | 70.9 min | 303.8 min |
| Week of Jul 27 | 7 | 136.2 min | 127.2 min |
| Week of Aug 3 | 3 | 281.9 min | 284.7 min |
| Week of Aug 10 | 3 | 607.3 min | 602.1 min |
| Week of Aug 17 | 2 | 63.5 min | 63.6 min |
| Week of Aug 24 | 2 | 121.6 min | 125.3 min |
| Week of Aug 31 | 1 | 665.6 min | — |
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.
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| Week of Jun 15 | 2 | 3.5 min | 14.2 min |
| Week of Jun 22 | 1 | 107.3 min | — |
| Week of Jun 29 | 0 | — | — |
| Week of Jul 6 | 0 | — | — |
| Week of Jul 13 | 0 | — | — |
| Week of Jul 20 | 0 | — | — |
| Week of Jul 27 | 0 | — | — |
| Week of Aug 3 | 1 | 74.1 min | 115.3 min |
| Week of Aug 10 | 0 | — | — |
| Week of Aug 17 | 0 | — | — |
| Week of Aug 24 | 0 | — | — |
| Week of Aug 31 | 0 | — | — |
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.
| Period | Called-in events | Average dispatch delay | Average response time |
|---|---|---|---|
| Week of Jun 15 | 2 | 69.4 min | 575.5 min |
| Week of Jun 22 | 5 | 166.5 min | 144.2 min |
| Week of Jun 29 | 2 | 303.5 min | 110.1 min |
| Week of Jul 6 | 4 | 185.2 min | 55.1 min |
| Week of Jul 13 | 6 | 45.2 min | 66.7 min |
| Week of Jul 20 | 3 | 70.9 min | 303.8 min |
| Week of Jul 27 | 6 | 158.8 min | 152.5 min |
| Week of Aug 3 | 2 | 385.8 min | 454.1 min |
| Week of Aug 10 | 3 | 607.3 min | 602.1 min |
| Week of Aug 17 | 1 | 94.0 min | 94.1 min |
| Week of Aug 24 | 2 | 121.6 min | 125.3 min |
| Week of Aug 31 | 1 | 665.6 min | — |
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.
| Period | Called-in events | 5–30 min | 1–4 hr | 4–8 hr | Over 8 hr | No recorded response | 0–5 min | 30–60 min |
|---|---|---|---|---|---|---|---|---|
| Week of Jun 15 | 6 | 33.3% | 33.3% | 16.7% | 16.7% | — | — | — |
| Week of Jun 22 | 9 | 11.1% | 33.3% | 11.1% | — | 22.2% | 22.2% | — |
| Week of Jun 29 | 5 | 20.0% | 60.0% | — | — | 20.0% | — | — |
| Week of Jul 6 | 10 | 20.0% | 20.0% | — | — | 20.0% | 40.0% | — |
| Week of Jul 13 | 7 | 14.3% | 28.6% | — | — | — | 28.6% | 28.6% |
| Week of Jul 20 | 3 | 33.3% | — | — | 33.3% | 33.3% | — | — |
| Week of Jul 27 | 7 | 14.3% | 14.3% | 28.6% | — | 14.3% | 14.3% | 14.3% |
| Week of Aug 3 | 3 | — | 33.3% | 33.3% | — | 33.3% | — | — |
| Week of Aug 10 | 3 | — | 33.3% | — | 33.3% | 33.3% | — | — |
| Week of Aug 17 | 2 | — | 50.0% | — | — | — | — | 50.0% |
| Week of Aug 24 | 2 | — | 100.0% | — | — | — | — | — |
| Week of Aug 31 | 1 | — | — | — | — | 100.0% | — | — |
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.
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.
| Period | Called-in events | 5–30 min | No recorded response | 1–4 hr |
|---|---|---|---|---|
| Week of Jun 15 | 2 | 100.0% | — | — |
| Week of Jun 22 | 1 | — | 100.0% | — |
| Week of Jun 29 | 0 | — | — | — |
| Week of Jul 6 | 0 | — | — | — |
| Week of Jul 13 | 0 | — | — | — |
| Week of Jul 20 | 0 | — | — | — |
| Week of Jul 27 | 0 | — | — | — |
| Week of Aug 3 | 1 | — | — | 100.0% |
| Week of Aug 10 | 0 | — | — | — |
| Week of Aug 17 | 0 | — | — | — |
| Week of Aug 24 | 0 | — | — | — |
| Week of Aug 31 | 0 | — | — | — |
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.
| Period | Called-in events | 4–8 hr | Over 8 hr | No recorded response | 0–5 min | 1–4 hr | 5–30 min | 30–60 min |
|---|---|---|---|---|---|---|---|---|
| Week of Jun 15 | 2 | 50.0% | 50.0% | — | — | — | — | — |
| Week of Jun 22 | 5 | 20.0% | — | 20.0% | 20.0% | 40.0% | — | — |
| Week of Jun 29 | 2 | — | — | 50.0% | — | 50.0% | — | — |
| Week of Jul 6 | 4 | — | — | 50.0% | 25.0% | 25.0% | — | — |
| Week of Jul 13 | 6 | — | — | — | 16.7% | 33.3% | 16.7% | 33.3% |
| Week of Jul 20 | 3 | — | 33.3% | 33.3% | — | — | 33.3% | — |
| Week of Jul 27 | 6 | 33.3% | — | 16.7% | — | 16.7% | 16.7% | 16.7% |
| Week of Aug 3 | 2 | 50.0% | — | 50.0% | — | — | — | — |
| Week of Aug 10 | 3 | — | 33.3% | 33.3% | — | 33.3% | — | — |
| Week of Aug 17 | 1 | — | — | — | — | 100.0% | — | — |
| Week of Aug 24 | 2 | — | — | — | — | 100.0% | — | — |
| Week of Aug 31 | 1 | — | — | 100.0% | — | — | — | — |
“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.
“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. “n=” under each month is the number of events logged that month 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.
“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. “n=” under each week is the number of events logged that week 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.