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

Child (Abandoned, Abused, or Neglected)

Child (Abandoned, Abused, or Neglected) calls over time: volume, outcomes, and response speed

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

Swipe sideways to see the full chart →
06001,2002009: 610 child (abandoned, abused, or neglected) calls logged in CAD2010: 1,071 child (abandoned, abused, or neglected) calls logged in CAD2011: 1,045 child (abandoned, abused, or neglected) calls logged in CAD2012: 941 child (abandoned, abused, or neglected) calls logged in CAD2013: 981 child (abandoned, abused, or neglected) calls logged in CAD2014: 904 child (abandoned, abused, or neglected) calls logged in CAD2015: 944 child (abandoned, abused, or neglected) calls logged in CAD2016: 868 child (abandoned, abused, or neglected) calls logged in CAD2017: 833 child (abandoned, abused, or neglected) calls logged in CAD2018: 763 child (abandoned, abused, or neglected) calls logged in CAD2019: 649 child (abandoned, abused, or neglected) calls logged in CAD2020: 360 child (abandoned, abused, or neglected) calls logged in CAD2021: 348 child (abandoned, abused, or neglected) calls logged in CAD2022: 437 child (abandoned, abused, or neglected) calls logged in CAD2023: 473 child (abandoned, abused, or neglected) calls logged in CAD2024: 474 child (abandoned, abused, or neglected) calls logged in CAD2025: 485 child (abandoned, abused, or neglected) calls logged in CAD2026: 376 child (abandoned, abused, or neglected) calls logged in CAD2009n=6102011n=1,0452013n=9812015n=9442017n=8332019n=6492021n=3482023n=4732025n=4852026n=376
child (abandoned, abused, or neglected) calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodChild (abandoned, abused, or neglected) calls logged in CAD
2009610
20101,071
20111,045
2012941
2013981
2014904
2015944
2016868
2017833
2018763
2019649
2020360
2021348
2022437
2023473
2024474
2025485
2026376
Child Calls Are Down 55% From Their 2010 PeakSeattle Police logged 1,071 child calls in 2010 and 485 in 2025, the most recent full year.

Child: 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: 1.3%2009 · Report taken, no arrest: 60.8%2009 · Resolved on scene: 26.6%2009 · Unable to locate: 8.5%2009 · Other (unfounded / cancelled): 2.8%2010 · Arrest / citation: 1.8%2010 · Report taken, no arrest: 65.0%2010 · Resolved on scene: 22.0%2010 · Unable to locate: 8.0%2010 · Other (unfounded / cancelled): 3.1%2011 · Arrest / citation: 1.7%2011 · Report taken, no arrest: 64.1%2011 · Resolved on scene: 23.2%2011 · Unable to locate: 8.4%2011 · Other (unfounded / cancelled): 2.6%2012 · Arrest / citation: 1.4%2012 · Report taken, no arrest: 62.7%2012 · Resolved on scene: 24.8%2012 · Unable to locate: 8.0%2012 · Other (unfounded / cancelled): 3.1%2013 · Arrest / citation: 0.7%2013 · Report taken, no arrest: 61.2%2013 · Resolved on scene: 26.3%2013 · Unable to locate: 8.0%2013 · Other (unfounded / cancelled): 3.9%2014 · Arrest / citation: 1.2%2014 · Report taken, no arrest: 61.1%2014 · Resolved on scene: 24.2%2014 · Unable to locate: 9.6%2014 · Other (unfounded / cancelled): 3.9%2015 · Arrest / citation: 1.3%2015 · Report taken, no arrest: 64.3%2015 · Resolved on scene: 19.7%2015 · Unable to locate: 10.2%2015 · Other (unfounded / cancelled): 4.6%2016 · Arrest / citation: 0.9%2016 · Report taken, no arrest: 63.8%2016 · Resolved on scene: 20.2%2016 · Unable to locate: 10.0%2016 · Other (unfounded / cancelled): 5.1%2017 · Arrest / citation: 1.2%2017 · Report taken, no arrest: 67.2%2017 · Resolved on scene: 17.6%2017 · Unable to locate: 8.5%2017 · Other (unfounded / cancelled): 5.4%2018 · Arrest / citation: 1.3%2018 · Report taken, no arrest: 65.9%2018 · Resolved on scene: 17.6%2018 · Unable to locate: 8.8%2018 · Other (unfounded / cancelled): 6.4%2019 · Arrest / citation: 0.9%2019 · Report taken, no arrest: 65.9%2019 · Resolved on scene: 16.8%2019 · Unable to locate: 11.1%2019 · Other (unfounded / cancelled): 5.2%2020 · Arrest / citation: 1.1%2020 · Report taken, no arrest: 71.4%2020 · Resolved on scene: 13.1%2020 · Unable to locate: 9.2%2020 · Other (unfounded / cancelled): 5.3%2021 · Arrest / citation: 2.3%2021 · Report taken, no arrest: 72.1%2021 · Resolved on scene: 14.9%2021 · Unable to locate: 7.8%2021 · Other (unfounded / cancelled): 2.8%2022 · Arrest / citation: 4.3%2022 · Report taken, no arrest: 62.0%2022 · Resolved on scene: 16.0%2022 · Unable to locate: 14.0%2022 · Other (unfounded / cancelled): 3.7%2023 · Arrest / citation: 3.8%2023 · Report taken, no arrest: 57.9%2023 · Resolved on scene: 16.1%2023 · Unable to locate: 15.6%2023 · Other (unfounded / cancelled): 6.5%2024 · Arrest / citation: 3.8%2024 · Report taken, no arrest: 62.2%2024 · Resolved on scene: 12.4%2024 · Unable to locate: 16.5%2024 · Other (unfounded / cancelled): 5.1%2025 · Arrest / citation: 3.9%2025 · Report taken, no arrest: 54.8%2025 · Resolved on scene: 15.5%2025 · Unable to locate: 18.4%2025 · Other (unfounded / cancelled): 7.4%2026 · Arrest / citation: 4.0%2026 · Report taken, no arrest: 51.1%2026 · Resolved on scene: 16.8%2026 · Unable to locate: 22.1%2026 · Other (unfounded / cancelled): 6.1%2009n=6102011n=1,0452013n=9812015n=9442017n=8332019n=6492021n=3482023n=4732025n=4852026n=376
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)
20096101.3%60.8%26.6%8.5%2.8%
20101,0711.8%65.0%22.0%8.0%3.1%
20111,0451.7%64.1%23.2%8.4%2.6%
20129411.4%62.7%24.8%8.0%3.1%
20139810.7%61.2%26.3%8.0%3.9%
20149041.2%61.1%24.2%9.6%3.9%
20159441.3%64.3%19.7%10.2%4.6%
20168680.9%63.8%20.2%10.0%5.1%
20178331.2%67.2%17.6%8.5%5.4%
20187631.3%65.9%17.6%8.8%6.4%
20196490.9%65.9%16.8%11.1%5.2%
20203601.1%71.4%13.1%9.2%5.3%
20213482.3%72.1%14.9%7.8%2.8%
20224374.3%62.0%16.0%14.0%3.7%
20234733.8%57.9%16.1%15.6%6.5%
20244743.8%62.2%12.4%16.5%5.1%
20254853.9%54.8%15.5%18.4%7.4%
20263764.0%51.1%16.8%22.1%6.1%
22% of Child Calls End “Unable to Locate,” Up From 10%Report-taken outcomes moved from 64% of calls in 2016 to 51% in 2026. “Unable to locate” means officers could not find the incident or the person who called.

Child: 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 30% of child 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: 24.3 min2010: 18.9 min2011: 16.6 min2012: 21.2 min2013: 24.7 min2014: 23.4 min2015: 31.4 min2016: 29.6 min2017: 28.6 min2018: 36.5 min2019: 38.2 min2020: 41.3 min2021: 50.9 min2022: 52.8 min2023: 48.9 min2024: 91.8 min2025: 79.5 min2026: 72.4 min2009: 34.2 min2010: 28.3 min2011: 25.6 min2012: 32.6 min2013: 36.1 min2014: 35.1 min2015: 42.0 min2016: 42.1 min2017: 41.2 min2018: 49.1 min2019: 51.4 min2020: 56.3 min2021: 67.2 min2022: 68.1 min2023: 68.2 min2024: 103.1 min2025: 100.1 min2026: 92.5 min2009n=3902011n=6642013n=7082015n=6962017n=5872019n=4712021n=2622023n=3332025n=3692026n=302
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
200939024.3 min34.2 min
201065418.9 min28.3 min
201166416.6 min25.6 min
201261521.2 min32.6 min
201370824.7 min36.1 min
201468723.4 min35.1 min
201569631.4 min42.0 min
201666329.6 min42.1 min
201758728.6 min41.2 min
201857836.5 min49.1 min
201947138.2 min51.4 min
202023141.3 min56.3 min
202126250.9 min67.2 min
202233752.8 min68.1 min
202333348.9 min68.2 min
202430991.8 min103.1 min
202536979.5 min100.1 min
202630272.4 min92.5 min
The Average Call Waits 92 Minutes for an Officer to ArriveDespite a 44% drop in calls between 2016 and 2025, average response time has more than doubled in the past 10 years, from 42 minutes in 2016 to 92 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.

Child: 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 30% of child 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.9%2009 · 0–5 min: 12.1%2009 · 5–30 min: 54.6%2009 · 30–60 min: 13.8%2009 · 1–4 hr: 13.9%2009 · 4–8 hr: 0.3%2009 · Over 8 hr: 0.5%2010 · No recorded response: 5.5%2010 · 0–5 min: 15.3%2010 · 5–30 min: 58.1%2010 · 30–60 min: 9.5%2010 · 1–4 hr: 11.0%2010 · 4–8 hr: 0.5%2010 · Over 8 hr: 0.1%2011 · No recorded response: 4.4%2011 · 0–5 min: 18.5%2011 · 5–30 min: 55.3%2011 · 30–60 min: 11.1%2011 · 1–4 hr: 10.2%2011 · 4–8 hr: 0.3%2011 · Over 8 hr: 0.1%2012 · No recorded response: 5.7%2012 · 0–5 min: 15.3%2012 · 5–30 min: 51.4%2012 · 30–60 min: 13.0%2012 · 1–4 hr: 13.7%2012 · 4–8 hr: 1.0%2013 · No recorded response: 3.8%2013 · 0–5 min: 12.7%2013 · 5–30 min: 52.8%2013 · 30–60 min: 12.8%2013 · 1–4 hr: 16.8%2013 · 4–8 hr: 0.8%2013 · Over 8 hr: 0.1%2014 · No recorded response: 4.8%2014 · 0–5 min: 12.4%2014 · 5–30 min: 54.0%2014 · 30–60 min: 14.3%2014 · 1–4 hr: 13.1%2014 · 4–8 hr: 1.5%2015 · No recorded response: 5.0%2015 · 0–5 min: 13.2%2015 · 5–30 min: 50.1%2015 · 30–60 min: 11.5%2015 · 1–4 hr: 18.1%2015 · 4–8 hr: 1.6%2015 · Over 8 hr: 0.4%2016 · No recorded response: 6.0%2016 · 0–5 min: 14.0%2016 · 5–30 min: 48.0%2016 · 30–60 min: 13.6%2016 · 1–4 hr: 16.3%2016 · 4–8 hr: 2.0%2016 · Over 8 hr: 0.1%2017 · No recorded response: 6.0%2017 · 0–5 min: 12.3%2017 · 5–30 min: 50.9%2017 · 30–60 min: 11.2%2017 · 1–4 hr: 17.7%2017 · 4–8 hr: 1.9%2018 · No recorded response: 7.4%2018 · 0–5 min: 12.6%2018 · 5–30 min: 46.7%2018 · 30–60 min: 11.1%2018 · 1–4 hr: 19.4%2018 · 4–8 hr: 2.2%2018 · Over 8 hr: 0.5%2019 · No recorded response: 6.2%2019 · 0–5 min: 14.7%2019 · 5–30 min: 42.5%2019 · 30–60 min: 11.9%2019 · 1–4 hr: 21.7%2019 · 4–8 hr: 2.8%2019 · Over 8 hr: 0.4%2020 · No recorded response: 8.2%2020 · 0–5 min: 10.4%2020 · 5–30 min: 44.6%2020 · 30–60 min: 10.0%2020 · 1–4 hr: 23.4%2020 · 4–8 hr: 2.6%2020 · Over 8 hr: 0.9%2021 · No recorded response: 3.8%2021 · 0–5 min: 7.6%2021 · 5–30 min: 43.9%2021 · 30–60 min: 14.5%2021 · 1–4 hr: 24.8%2021 · 4–8 hr: 4.2%2021 · Over 8 hr: 1.1%2022 · No recorded response: 7.1%2022 · 0–5 min: 10.4%2022 · 5–30 min: 46.0%2022 · 30–60 min: 10.4%2022 · 1–4 hr: 19.3%2022 · 4–8 hr: 4.8%2022 · Over 8 hr: 2.1%2023 · No recorded response: 9.6%2023 · 0–5 min: 11.7%2023 · 5–30 min: 47.8%2023 · 30–60 min: 10.5%2023 · 1–4 hr: 14.4%2023 · 4–8 hr: 4.2%2023 · Over 8 hr: 1.8%2024 · No recorded response: 13.3%2024 · 0–5 min: 9.1%2024 · 5–30 min: 41.4%2024 · 30–60 min: 10.7%2024 · 1–4 hr: 15.9%2024 · 4–8 hr: 4.8%2024 · Over 8 hr: 4.8%2025 · No recorded response: 10.3%2025 · 0–5 min: 11.1%2025 · 5–30 min: 37.1%2025 · 30–60 min: 11.1%2025 · 1–4 hr: 19.5%2025 · 4–8 hr: 7.6%2025 · Over 8 hr: 3.2%2026 · No recorded response: 9.6%2026 · 0–5 min: 13.2%2026 · 5–30 min: 43.0%2026 · 30–60 min: 7.3%2026 · 1–4 hr: 15.9%2026 · 4–8 hr: 8.0%2026 · Over 8 hr: 3.0%2009n=3902011n=6642013n=7082015n=6962017n=5872019n=4712021n=2622023n=3332025n=3692026n=302
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
20093904.9%12.1%54.6%13.8%13.9%0.3%0.5%
20106545.5%15.3%58.1%9.5%11.0%0.5%0.1%
20116644.4%18.5%55.3%11.1%10.2%0.3%0.1%
20126155.7%15.3%51.4%13.0%13.7%1.0%—
20137083.8%12.7%52.8%12.8%16.8%0.8%0.1%
20146874.8%12.4%54.0%14.3%13.1%1.5%—
20156965.0%13.2%50.1%11.5%18.1%1.6%0.4%
20166636.0%14.0%48.0%13.6%16.3%2.0%0.1%
20175876.0%12.3%50.9%11.2%17.7%1.9%—
20185787.4%12.6%46.7%11.1%19.4%2.2%0.5%
20194716.2%14.7%42.5%11.9%21.7%2.8%0.4%
20202318.2%10.4%44.6%10.0%23.4%2.6%0.9%
20212623.8%7.6%43.9%14.5%24.8%4.2%1.1%
20223377.1%10.4%46.0%10.4%19.3%4.8%2.1%
20233339.6%11.7%47.8%10.5%14.4%4.2%1.8%
202430913.3%9.1%41.4%10.7%15.9%4.8%4.8%
202536910.3%11.1%37.1%11.1%19.5%7.6%3.2%
20263029.6%13.2%43.0%7.3%15.9%8.0%3.0%
The Average Call Waits 72 Minutes Before an Officer Is AssignedThe average wait before an officer is assigned reached 72 minutes in 2026, more than double what it was in 2016. 27% 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.