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

Prowler

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

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

Swipe sideways to see the full chart →
010,00020,0002009: 4,688 prowler calls logged in CAD2010: 10,159 prowler calls logged in CAD2011: 6,535 prowler calls logged in CAD2012: 6,272 prowler calls logged in CAD2013: 7,719 prowler calls logged in CAD2014: 7,076 prowler calls logged in CAD2015: 9,361 prowler calls logged in CAD2016: 12,212 prowler calls logged in CAD2017: 14,974 prowler calls logged in CAD2018: 14,450 prowler calls logged in CAD2019: 14,608 prowler calls logged in CAD2020: 13,664 prowler calls logged in CAD2021: 14,071 prowler calls logged in CAD2022: 14,936 prowler calls logged in CAD2023: 13,544 prowler calls logged in CAD2024: 14,300 prowler calls logged in CAD2025: 12,351 prowler calls logged in CAD2026: 8,000 prowler calls logged in CAD2009n=4,6882011n=6,5352013n=7,7192015n=9,3612017n=14,9742019n=14,6082021n=14,0712023n=13,5442025n=12,3512026n=8,000
prowler calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodProwler calls logged in CAD
20094,688
201010,159
20116,535
20126,272
20137,719
20147,076
20159,361
201612,212
201714,974
201814,450
201914,608
202013,664
202114,071
202214,936
202313,544
202414,300
202512,351
20268,000
Prowler Calls Are Down 18% From Their 2017 PeakSeattle Police logged 14,974 prowler calls in 2017 and 12,351 in 2025, the most recent full year.

Prowler: 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: 7.0%2009 · Report taken, no arrest: 29.4%2009 · Resolved on scene: 58.8%2009 · Unable to locate: 3.8%2009 · Other (unfounded / cancelled): 1.1%2010 · Arrest / citation: 5.6%2010 · Report taken, no arrest: 28.8%2010 · Resolved on scene: 61.5%2010 · Unable to locate: 3.4%2010 · Other (unfounded / cancelled): 0.6%2011 · Arrest / citation: 4.9%2011 · Report taken, no arrest: 14.4%2011 · Resolved on scene: 76.1%2011 · Unable to locate: 3.7%2011 · Other (unfounded / cancelled): 0.8%2012 · Arrest / citation: 4.3%2012 · Report taken, no arrest: 14.0%2012 · Resolved on scene: 75.7%2012 · Unable to locate: 4.9%2012 · Other (unfounded / cancelled): 1.0%2013 · Arrest / citation: 5.0%2013 · Report taken, no arrest: 13.3%2013 · Resolved on scene: 75.6%2013 · Unable to locate: 5.2%2013 · Other (unfounded / cancelled): 0.9%2014 · Arrest / citation: 4.2%2014 · Report taken, no arrest: 18.8%2014 · Resolved on scene: 68.5%2014 · Unable to locate: 7.2%2014 · Other (unfounded / cancelled): 1.4%2015 · Arrest / citation: 4.6%2015 · Report taken, no arrest: 26.1%2015 · Resolved on scene: 60.2%2015 · Unable to locate: 7.4%2015 · Other (unfounded / cancelled): 1.7%2016 · Arrest / citation: 4.2%2016 · Report taken, no arrest: 21.3%2016 · Resolved on scene: 65.1%2016 · Unable to locate: 7.5%2016 · Other (unfounded / cancelled): 1.9%2017 · Arrest / citation: 4.4%2017 · Report taken, no arrest: 21.7%2017 · Resolved on scene: 64.5%2017 · Unable to locate: 6.9%2017 · Other (unfounded / cancelled): 2.6%2018 · Arrest / citation: 4.5%2018 · Report taken, no arrest: 23.3%2018 · Resolved on scene: 61.4%2018 · Unable to locate: 7.5%2018 · Other (unfounded / cancelled): 3.3%2019 · Arrest / citation: 4.9%2019 · Report taken, no arrest: 27.0%2019 · Resolved on scene: 54.7%2019 · Unable to locate: 9.9%2019 · Other (unfounded / cancelled): 3.6%2020 · Arrest / citation: 3.2%2020 · Report taken, no arrest: 24.3%2020 · Resolved on scene: 56.1%2020 · Unable to locate: 11.5%2020 · Other (unfounded / cancelled): 5.0%2021 · Arrest / citation: 1.5%2021 · Report taken, no arrest: 19.0%2021 · Resolved on scene: 61.6%2021 · Unable to locate: 12.4%2021 · Other (unfounded / cancelled): 5.6%2022 · Arrest / citation: 1.6%2022 · Report taken, no arrest: 18.4%2022 · Resolved on scene: 61.6%2022 · Unable to locate: 14.3%2022 · Other (unfounded / cancelled): 4.0%2023 · Arrest / citation: 1.8%2023 · Report taken, no arrest: 19.3%2023 · Resolved on scene: 56.8%2023 · Unable to locate: 17.2%2023 · Other (unfounded / cancelled): 4.8%2024 · Arrest / citation: 2.4%2024 · Report taken, no arrest: 16.9%2024 · Resolved on scene: 58.8%2024 · Unable to locate: 18.4%2024 · Other (unfounded / cancelled): 3.5%2025 · Arrest / citation: 3.8%2025 · Report taken, no arrest: 19.9%2025 · Resolved on scene: 53.6%2025 · Unable to locate: 19.0%2025 · Other (unfounded / cancelled): 3.8%2026 · Arrest / citation: 4.5%2026 · Report taken, no arrest: 24.5%2026 · Resolved on scene: 48.3%2026 · Unable to locate: 19.0%2026 · Other (unfounded / cancelled): 3.6%2009n=4,6882011n=6,5352013n=7,7192015n=9,3612017n=14,9742019n=14,6082021n=14,0712023n=13,5442025n=12,3512026n=8,000
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)
20094,6887.0%29.4%58.8%3.8%1.1%
201010,1595.6%28.8%61.5%3.4%0.6%
20116,5354.9%14.4%76.1%3.7%0.8%
20126,2724.3%14.0%75.7%4.9%1.0%
20137,7195.0%13.3%75.6%5.2%0.9%
20147,0764.2%18.8%68.5%7.2%1.4%
20159,3614.6%26.1%60.2%7.4%1.7%
201612,2124.2%21.3%65.1%7.5%1.9%
201714,9744.4%21.7%64.5%6.9%2.6%
201814,4504.5%23.3%61.4%7.5%3.3%
201914,6084.9%27.0%54.7%9.9%3.6%
202013,6643.2%24.3%56.1%11.5%5.0%
202114,0711.5%19.0%61.6%12.4%5.6%
202214,9361.6%18.4%61.6%14.3%4.0%
202313,5441.8%19.3%56.8%17.2%4.8%
202414,3002.4%16.9%58.8%18.4%3.5%
202512,3513.8%19.9%53.6%19.0%3.8%
20268,0004.5%24.5%48.3%19.0%3.6%
19% of Prowler Calls End “Unable to Locate,” Up From 8%Report-taken outcomes moved from 21% of calls in 2016 to 24% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Prowler: 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 26% of prowler 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: 19.1 min2010: 14.3 min2011: 14.5 min2012: 18.3 min2013: 20.8 min2014: 23.8 min2015: 33.5 min2016: 26.7 min2017: 27.8 min2018: 33.4 min2019: 33.3 min2020: 28.9 min2021: 41.4 min2022: 50.0 min2023: 58.6 min2024: 83.8 min2025: 72.5 min2026: 60.4 min2009: 24.4 min2010: 19.6 min2011: 19.9 min2012: 23.9 min2013: 26.5 min2014: 30.0 min2015: 40.1 min2016: 34.3 min2017: 35.0 min2018: 40.8 min2019: 40.9 min2020: 37.1 min2021: 51.2 min2022: 58.6 min2023: 70.7 min2024: 93.2 min2025: 84.8 min2026: 70.5 min2009n=2,2262011n=3,6442013n=5,1372015n=6,5232017n=10,0882019n=11,2802021n=12,3072023n=11,4192025n=10,4222026n=6,655
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
20092,22619.1 min24.4 min
20104,41814.3 min19.6 min
20113,64414.5 min19.9 min
20124,02518.3 min23.9 min
20135,13720.8 min26.5 min
20145,19823.8 min30.0 min
20156,52333.5 min40.1 min
20168,30226.7 min34.3 min
201710,08827.8 min35.0 min
201810,60533.4 min40.8 min
201911,28033.3 min40.9 min
202011,37528.9 min37.1 min
202112,30741.4 min51.2 min
202212,14950.0 min58.6 min
202311,41958.6 min70.7 min
202411,08683.8 min93.2 min
202510,42272.5 min84.8 min
20266,65560.4 min70.5 min
The Average Call Waits 70 Minutes for an Officer to ArriveAverage response time has more than doubled in the past 10 years, from 34 minutes in 2016 to 70 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.

Prowler: 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 26% of prowler 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: 4.2%2009 · 0–5 min: 22.5%2009 · 5–30 min: 51.8%2009 · 30–60 min: 12.5%2009 · 1–4 hr: 8.7%2009 · 4–8 hr: 0.3%2009 · Over 8 hr: 0.0%2010 · No recorded response: 3.8%2010 · 0–5 min: 24.5%2010 · 5–30 min: 55.3%2010 · 30–60 min: 9.7%2010 · 1–4 hr: 6.5%2010 · 4–8 hr: 0.2%2011 · No recorded response: 4.5%2011 · 0–5 min: 25.2%2011 · 5–30 min: 52.9%2011 · 30–60 min: 10.4%2011 · 1–4 hr: 6.8%2011 · 4–8 hr: 0.2%2012 · No recorded response: 4.5%2012 · 0–5 min: 22.6%2012 · 5–30 min: 52.1%2012 · 30–60 min: 11.6%2012 · 1–4 hr: 8.8%2012 · 4–8 hr: 0.5%2012 · Over 8 hr: 0.0%2013 · No recorded response: 5.1%2013 · 0–5 min: 20.9%2013 · 5–30 min: 50.9%2013 · 30–60 min: 12.3%2013 · 1–4 hr: 10.4%2013 · 4–8 hr: 0.5%2013 · Over 8 hr: 0.1%2014 · No recorded response: 4.9%2014 · 0–5 min: 18.0%2014 · 5–30 min: 51.3%2014 · 30–60 min: 13.2%2014 · 1–4 hr: 11.8%2014 · 4–8 hr: 0.8%2014 · Over 8 hr: 0.1%2015 · No recorded response: 5.2%2015 · 0–5 min: 16.7%2015 · 5–30 min: 46.6%2015 · 30–60 min: 13.3%2015 · 1–4 hr: 16.3%2015 · 4–8 hr: 1.5%2015 · Over 8 hr: 0.2%2016 · No recorded response: 5.1%2016 · 0–5 min: 16.5%2016 · 5–30 min: 50.1%2016 · 30–60 min: 12.9%2016 · 1–4 hr: 14.2%2016 · 4–8 hr: 1.1%2016 · Over 8 hr: 0.1%2017 · No recorded response: 5.8%2017 · 0–5 min: 15.3%2017 · 5–30 min: 49.5%2017 · 30–60 min: 13.4%2017 · 1–4 hr: 14.6%2017 · 4–8 hr: 1.2%2017 · Over 8 hr: 0.1%2018 · No recorded response: 6.9%2018 · 0–5 min: 13.8%2018 · 5–30 min: 46.5%2018 · 30–60 min: 13.9%2018 · 1–4 hr: 17.1%2018 · 4–8 hr: 1.6%2018 · Over 8 hr: 0.2%2019 · No recorded response: 7.5%2019 · 0–5 min: 13.9%2019 · 5–30 min: 45.9%2019 · 30–60 min: 14.0%2019 · 1–4 hr: 16.8%2019 · 4–8 hr: 1.7%2019 · Over 8 hr: 0.1%2020 · No recorded response: 8.8%2020 · 0–5 min: 13.9%2020 · 5–30 min: 48.3%2020 · 30–60 min: 12.4%2020 · 1–4 hr: 15.0%2020 · 4–8 hr: 1.4%2020 · Over 8 hr: 0.2%2021 · No recorded response: 10.5%2021 · 0–5 min: 8.9%2021 · 5–30 min: 43.6%2021 · 30–60 min: 14.2%2021 · 1–4 hr: 19.9%2021 · 4–8 hr: 2.5%2021 · Over 8 hr: 0.4%2022 · No recorded response: 10.4%2022 · 0–5 min: 8.9%2022 · 5–30 min: 40.0%2022 · 30–60 min: 14.1%2022 · 1–4 hr: 22.8%2022 · 4–8 hr: 3.3%2022 · Over 8 hr: 0.5%2023 · No recorded response: 11.0%2023 · 0–5 min: 7.6%2023 · 5–30 min: 39.5%2023 · 30–60 min: 13.9%2023 · 1–4 hr: 22.1%2023 · 4–8 hr: 4.7%2023 · Over 8 hr: 1.2%2024 · No recorded response: 10.6%2024 · 0–5 min: 5.8%2024 · 5–30 min: 32.3%2024 · 30–60 min: 14.4%2024 · 1–4 hr: 27.4%2024 · 4–8 hr: 7.3%2024 · Over 8 hr: 2.1%2025 · No recorded response: 8.4%2025 · 0–5 min: 5.3%2025 · 5–30 min: 35.4%2025 · 30–60 min: 15.7%2025 · 1–4 hr: 27.6%2025 · 4–8 hr: 5.8%2025 · Over 8 hr: 1.7%2026 · No recorded response: 7.6%2026 · 0–5 min: 6.5%2026 · 5–30 min: 39.8%2026 · 30–60 min: 16.2%2026 · 1–4 hr: 24.0%2026 · 4–8 hr: 4.8%2026 · Over 8 hr: 1.1%2009n=2,2262011n=3,6442013n=5,1372015n=6,5232017n=10,0882019n=11,2802021n=12,3072023n=11,4192025n=10,4222026n=6,655
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
20092,2264.2%22.5%51.8%12.5%8.7%0.3%0.0%
20104,4183.8%24.5%55.3%9.7%6.5%0.2%—
20113,6444.5%25.2%52.9%10.4%6.8%0.2%—
20124,0254.5%22.6%52.1%11.6%8.8%0.5%0.0%
20135,1375.1%20.9%50.9%12.3%10.4%0.5%0.1%
20145,1984.9%18.0%51.3%13.2%11.8%0.8%0.1%
20156,5235.2%16.7%46.6%13.3%16.3%1.5%0.2%
20168,3025.1%16.5%50.1%12.9%14.2%1.1%0.1%
201710,0885.8%15.3%49.5%13.4%14.6%1.2%0.1%
201810,6056.9%13.8%46.5%13.9%17.1%1.6%0.2%
201911,2807.5%13.9%45.9%14.0%16.8%1.7%0.1%
202011,3758.8%13.9%48.3%12.4%15.0%1.4%0.2%
202112,30710.5%8.9%43.6%14.2%19.9%2.5%0.4%
202212,14910.4%8.9%40.0%14.1%22.8%3.3%0.5%
202311,41911.0%7.6%39.5%13.9%22.1%4.7%1.2%
202411,08610.6%5.8%32.3%14.4%27.4%7.3%2.1%
202510,4228.4%5.3%35.4%15.7%27.6%5.8%1.7%
20266,6557.6%6.5%39.8%16.2%24.0%4.8%1.1%
The Average Call Waits 60 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 60 minutes in 2026, more than double what it was in 2016. 30% of calls took more than an hour to get a response in 2026, compared with 15% 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.