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

Premise Checks

Premise Checks calls over time: volume, outcomes, and response speed

Premise Checks: 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 (99% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
030,00060,0002009: 20,985 premise checks calls logged in CAD2010: 47,191 premise checks calls logged in CAD2011: 50,202 premise checks calls logged in CAD2012: 48,077 premise checks calls logged in CAD2013: 41,353 premise checks calls logged in CAD2014: 26,422 premise checks calls logged in CAD2015: 36,236 premise checks calls logged in CAD2016: 41,780 premise checks calls logged in CAD2017: 46,692 premise checks calls logged in CAD2018: 43,648 premise checks calls logged in CAD2019: 44,645 premise checks calls logged in CAD2020: 24,790 premise checks calls logged in CAD2021: 17,050 premise checks calls logged in CAD2022: 19,365 premise checks calls logged in CAD2023: 21,281 premise checks calls logged in CAD2024: 16,437 premise checks calls logged in CAD2025: 18,922 premise checks calls logged in CAD2026: 12,696 premise checks calls logged in CAD2009n=20,9852011n=50,2022013n=41,3532015n=36,2362017n=46,6922019n=44,6452021n=17,0502023n=21,2812025n=18,9222026n=12,696
premise checks calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodPremise checks calls logged in CAD
200920,985
201047,191
201150,202
201248,077
201341,353
201426,422
201536,236
201641,780
201746,692
201843,648
201944,645
202024,790
202117,050
202219,365
202321,281
202416,437
202518,922
202612,696
Calls for Premise Checks Are Down 62% From Their 2011 PeakSeattle Police logged 50,202 premise checks calls in 2011 and 18,922 in 2025, the most recent full year.

Premise Checks: 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: 0.1%2009 · Report taken, no arrest: 0.6%2009 · Resolved on scene: 94.6%2009 · Unable to locate: 0.5%2009 · Other (unfounded / cancelled): 4.1%2010 · Report taken, no arrest: 0.8%2010 · Resolved on scene: 97.0%2010 · Unable to locate: 0.5%2010 · Other (unfounded / cancelled): 1.7%2011 · Report taken, no arrest: 1.1%2011 · Resolved on scene: 97.3%2011 · Unable to locate: 0.5%2011 · Other (unfounded / cancelled): 1.1%2012 · Report taken, no arrest: 0.5%2012 · Resolved on scene: 98.5%2012 · Unable to locate: 0.2%2012 · Other (unfounded / cancelled): 0.8%2013 · Report taken, no arrest: 1.1%2013 · Resolved on scene: 98.4%2013 · Unable to locate: 0.2%2013 · Other (unfounded / cancelled): 0.3%2014 · Report taken, no arrest: 1.7%2014 · Resolved on scene: 97.3%2014 · Unable to locate: 0.7%2014 · Other (unfounded / cancelled): 0.3%2015 · Arrest / citation: 0.1%2015 · Report taken, no arrest: 1.3%2015 · Resolved on scene: 97.3%2015 · Unable to locate: 1.1%2015 · Other (unfounded / cancelled): 0.2%2016 · Arrest / citation: 0.1%2016 · Report taken, no arrest: 1.7%2016 · Resolved on scene: 96.5%2016 · Unable to locate: 1.4%2016 · Other (unfounded / cancelled): 0.3%2017 · Arrest / citation: 0.1%2017 · Report taken, no arrest: 2.4%2017 · Resolved on scene: 95.9%2017 · Unable to locate: 1.4%2017 · Other (unfounded / cancelled): 0.2%2018 · Report taken, no arrest: 1.9%2018 · Resolved on scene: 95.9%2018 · Unable to locate: 1.9%2018 · Other (unfounded / cancelled): 0.2%2019 · Report taken, no arrest: 1.4%2019 · Resolved on scene: 96.4%2019 · Unable to locate: 1.9%2019 · Other (unfounded / cancelled): 0.3%2020 · Report taken, no arrest: 3.9%2020 · Resolved on scene: 94.1%2020 · Unable to locate: 1.6%2020 · Other (unfounded / cancelled): 0.4%2021 · Report taken, no arrest: 0.3%2021 · Resolved on scene: 97.2%2021 · Unable to locate: 1.9%2021 · Other (unfounded / cancelled): 0.5%2022 · Report taken, no arrest: 1.3%2022 · Resolved on scene: 95.7%2022 · Unable to locate: 2.5%2022 · Other (unfounded / cancelled): 0.4%2023 · Report taken, no arrest: 0.5%2023 · Resolved on scene: 96.3%2023 · Unable to locate: 2.7%2023 · Other (unfounded / cancelled): 0.4%2024 · Arrest / citation: 0.1%2024 · Report taken, no arrest: 0.3%2024 · Resolved on scene: 95.8%2024 · Unable to locate: 3.4%2024 · Other (unfounded / cancelled): 0.5%2025 · Arrest / citation: 0.1%2025 · Report taken, no arrest: 0.3%2025 · Resolved on scene: 95.3%2025 · Unable to locate: 3.5%2025 · Other (unfounded / cancelled): 0.8%2026 · Report taken, no arrest: 0.4%2026 · Resolved on scene: 94.1%2026 · Unable to locate: 4.4%2026 · Other (unfounded / cancelled): 1.2%2009n=20,9852011n=50,2022013n=41,3532015n=36,2362017n=46,6922019n=44,6452021n=17,0502023n=21,2812025n=18,9222026n=12,696
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)
200920,9850.1%0.6%94.6%0.5%4.1%
201047,191—0.8%97.0%0.5%1.7%
201150,202—1.1%97.3%0.5%1.1%
201248,077—0.5%98.5%0.2%0.8%
201341,353—1.1%98.4%0.2%0.3%
201426,422—1.7%97.3%0.7%0.3%
201536,2360.1%1.3%97.3%1.1%0.2%
201641,7800.1%1.7%96.5%1.4%0.3%
201746,6920.1%2.4%95.9%1.4%0.2%
201843,648—1.9%95.9%1.9%0.2%
201944,645—1.4%96.4%1.9%0.3%
202024,790—3.9%94.1%1.6%0.4%
202117,050—0.3%97.2%1.9%0.5%
202219,365—1.3%95.7%2.5%0.4%
202321,281—0.5%96.3%2.7%0.4%
202416,4370.1%0.3%95.8%3.4%0.5%
202518,9220.1%0.3%95.3%3.5%0.8%
202612,696—0.4%94.1%4.4%1.2%
4% of Calls for Premise Checks End “Unable to Locate,” Up From 1%Report-taken outcomes moved from 2% of calls in 2016 to 0% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Premise Checks: 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 99% of premise checks 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 premise checks 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 min500 min1,000 min2009: 21.8 min2010: 36.4 min2011: 22.8 min2012: 45.6 min2013: 37.8 min2014: 76.1 min2015: 109.9 min2016: 64.5 min2017: 75.1 min2018: 69.9 min2019: 52.8 min2020: 47.1 min2021: 79.9 min2022: 71.6 min2023: 110.1 min2024: 155.9 min2025: 425.4 min2026: 758.1 min2009: 27.9 min2010: 51.2 min2011: 28.6 min2012: 53.3 min2013: 39.2 min2014: 87.4 min2015: 138.0 min2016: 76.8 min2017: 77.3 min2018: 84.0 min2019: 61.0 min2020: 49.0 min2021: 104.2 min2022: 80.6 min2023: 125.3 min2024: 174.6 min2025: 399.4 min2026: 438.1 min2009n=2902011n=3292013n=2702015n=1972017n=2642019n=2652021n=1622023n=2902025n=1,0702026n=1,277
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
200929021.8 min27.9 min
201027836.4 min51.2 min
201132922.8 min28.6 min
201240945.6 min53.3 min
201327037.8 min39.2 min
201420076.1 min87.4 min
2015197109.9 min138.0 min
201625664.5 min76.8 min
201726475.1 min77.3 min
201830069.9 min84.0 min
201926552.8 min61.0 min
202019547.1 min49.0 min
202116279.9 min104.2 min
202219571.6 min80.6 min
2023290110.1 min125.3 min
2024309155.9 min174.6 min
20251,070425.4 min399.4 min
20261,277758.1 min438.1 min
The Average Call Waits 438 Minutes for an Officer to ArriveDespite a 55% drop in calls between 2016 and 2025, average response time has grown about 6-fold in the past 10 years, from 77 minutes in 2016 to 438 in 2026, driven largely by dispatch delays. This counts only the 1% of premise checks 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.

Premise Checks: 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 99% of premise checks events, because they have no wait. Because most premise checks 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: 22.4%2009 · 0–5 min: 24.8%2009 · 5–30 min: 33.8%2009 · 30–60 min: 9.7%2009 · 1–4 hr: 8.6%2009 · 4–8 hr: 0.3%2009 · Over 8 hr: 0.3%2010 · No recorded response: 22.3%2010 · 0–5 min: 27.3%2010 · 5–30 min: 30.2%2010 · 30–60 min: 6.1%2010 · 1–4 hr: 10.4%2010 · 4–8 hr: 2.2%2010 · Over 8 hr: 1.4%2011 · No recorded response: 15.5%2011 · 0–5 min: 49.2%2011 · 5–30 min: 21.0%2011 · 30–60 min: 6.1%2011 · 1–4 hr: 6.4%2011 · 4–8 hr: 1.2%2011 · Over 8 hr: 0.6%2012 · No recorded response: 14.2%2012 · 0–5 min: 56.0%2012 · 5–30 min: 15.6%2012 · 30–60 min: 4.4%2012 · 1–4 hr: 6.1%2012 · 4–8 hr: 2.2%2012 · Over 8 hr: 1.5%2013 · No recorded response: 15.6%2013 · 0–5 min: 47.4%2013 · 5–30 min: 17.4%2013 · 30–60 min: 8.9%2013 · 1–4 hr: 7.4%2013 · 4–8 hr: 2.2%2013 · Over 8 hr: 1.1%2014 · No recorded response: 16.0%2014 · 0–5 min: 24.0%2014 · 5–30 min: 31.5%2014 · 30–60 min: 9.5%2014 · 1–4 hr: 14.0%2014 · 4–8 hr: 2.5%2014 · Over 8 hr: 2.5%2015 · No recorded response: 14.7%2015 · 0–5 min: 23.9%2015 · 5–30 min: 23.4%2015 · 30–60 min: 9.1%2015 · 1–4 hr: 19.8%2015 · 4–8 hr: 6.1%2015 · Over 8 hr: 3.0%2016 · No recorded response: 16.8%2016 · 0–5 min: 23.1%2016 · 5–30 min: 28.1%2016 · 30–60 min: 12.1%2016 · 1–4 hr: 13.3%2016 · 4–8 hr: 4.3%2016 · Over 8 hr: 2.3%2017 · No recorded response: 16.7%2017 · 0–5 min: 20.1%2017 · 5–30 min: 33.3%2017 · 30–60 min: 9.5%2017 · 1–4 hr: 12.9%2017 · 4–8 hr: 5.3%2017 · Over 8 hr: 2.3%2018 · No recorded response: 23.3%2018 · 0–5 min: 11.7%2018 · 5–30 min: 32.7%2018 · 30–60 min: 9.0%2018 · 1–4 hr: 16.7%2018 · 4–8 hr: 3.3%2018 · Over 8 hr: 3.3%2019 · No recorded response: 21.9%2019 · 0–5 min: 22.6%2019 · 5–30 min: 28.3%2019 · 30–60 min: 11.3%2019 · 1–4 hr: 12.1%2019 · 4–8 hr: 2.3%2019 · Over 8 hr: 1.5%2020 · No recorded response: 28.2%2020 · 0–5 min: 11.3%2020 · 5–30 min: 31.8%2020 · 30–60 min: 11.8%2020 · 1–4 hr: 14.4%2020 · 4–8 hr: 2.0%2020 · Over 8 hr: 0.5%2021 · No recorded response: 20.4%2021 · 0–5 min: 13.6%2021 · 5–30 min: 32.1%2021 · 30–60 min: 14.2%2021 · 1–4 hr: 13.6%2021 · 4–8 hr: 3.7%2021 · Over 8 hr: 2.5%2022 · No recorded response: 22.6%2022 · 0–5 min: 10.8%2022 · 5–30 min: 30.8%2022 · 30–60 min: 8.7%2022 · 1–4 hr: 20.0%2022 · 4–8 hr: 4.6%2022 · Over 8 hr: 2.6%2023 · No recorded response: 30.0%2023 · 0–5 min: 8.6%2023 · 5–30 min: 22.4%2023 · 30–60 min: 9.7%2023 · 1–4 hr: 18.6%2023 · 4–8 hr: 6.2%2023 · Over 8 hr: 4.5%2024 · No recorded response: 15.2%2024 · 0–5 min: 7.1%2024 · 5–30 min: 20.1%2024 · 30–60 min: 11.3%2024 · 1–4 hr: 26.9%2024 · 4–8 hr: 10.4%2024 · Over 8 hr: 9.1%2025 · No recorded response: 18.8%2025 · 0–5 min: 2.6%2025 · 5–30 min: 14.9%2025 · 30–60 min: 8.3%2025 · 1–4 hr: 16.6%2025 · 4–8 hr: 16.7%2025 · Over 8 hr: 22.1%2026 · No recorded response: 12.7%2026 · 0–5 min: 2.2%2026 · 5–30 min: 34.6%2026 · 30–60 min: 9.9%2026 · 1–4 hr: 11.1%2026 · 4–8 hr: 4.4%2026 · Over 8 hr: 25.1%2009n=2902011n=3292013n=2702015n=1972017n=2642019n=2652021n=1622023n=2902025n=1,0702026n=1,277
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
200929022.4%24.8%33.8%9.7%8.6%0.3%0.3%
201027822.3%27.3%30.2%6.1%10.4%2.2%1.4%
201132915.5%49.2%21.0%6.1%6.4%1.2%0.6%
201240914.2%56.0%15.6%4.4%6.1%2.2%1.5%
201327015.6%47.4%17.4%8.9%7.4%2.2%1.1%
201420016.0%24.0%31.5%9.5%14.0%2.5%2.5%
201519714.7%23.9%23.4%9.1%19.8%6.1%3.0%
201625616.8%23.1%28.1%12.1%13.3%4.3%2.3%
201726416.7%20.1%33.3%9.5%12.9%5.3%2.3%
201830023.3%11.7%32.7%9.0%16.7%3.3%3.3%
201926521.9%22.6%28.3%11.3%12.1%2.3%1.5%
202019528.2%11.3%31.8%11.8%14.4%2.0%0.5%
202116220.4%13.6%32.1%14.2%13.6%3.7%2.5%
202219522.6%10.8%30.8%8.7%20.0%4.6%2.6%
202329030.0%8.6%22.4%9.7%18.6%6.2%4.5%
202430915.2%7.1%20.1%11.3%26.9%10.4%9.1%
20251,07018.8%2.6%14.9%8.3%16.6%16.7%22.1%
20261,27712.7%2.2%34.6%9.9%11.1%4.4%25.1%
The Average Call Waits 758 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 758 minutes in 2026, more than double what it was in 2016. 41% of calls took more than an hour to get a response in 2026, compared with 20% in 2016. This counts only the 1% of premise checks 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.