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

Human Trafficking

Human Trafficking calls over time: volume, outcomes, and response speed

Human Trafficking: 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 (66% of the total). Excluded: Nothing.

Swipe sideways to see the full chart →
025502011: 12 human trafficking calls logged in CAD2012: 15 human trafficking calls logged in CAD2013: 20 human trafficking calls logged in CAD2014: 21 human trafficking calls logged in CAD2015: 18 human trafficking calls logged in CAD2016: 22 human trafficking calls logged in CAD2017: 19 human trafficking calls logged in CAD2018: 11 human trafficking calls logged in CAD2019: 40 human trafficking calls logged in CAD2020: 21 human trafficking calls logged in CAD2021: 10 human trafficking calls logged in CAD2022: 20 human trafficking calls logged in CAD2023: 11 human trafficking calls logged in CAD2024: 6 human trafficking calls logged in CAD2025: 6 human trafficking calls logged in CAD2026: 4 human trafficking calls logged in CAD2011n=122013n=202015n=182017n=192019n=402021n=102023n=112025n=62026n=4
human trafficking calls logged in CAD
View as table
Call volume — same numbers as the chart above
PeriodHuman trafficking calls logged in CAD
201112
201215
201320
201421
201518
201622
201719
201811
201940
202021
202110
202220
202311
20246
20256
20264
Human Trafficking Calls Average About 17 a YearSeattle Police logged 256 human trafficking calls between 2011 and 2026, with a high of 40 in 2019.

Human Trafficking: 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%2011 · Arrest / citation: 8.3%2011 · Report taken, no arrest: 83.3%2011 · Unable to locate: 8.3%2012 · Report taken, no arrest: 100.0%2013 · Report taken, no arrest: 90.0%2013 · Unable to locate: 10.0%2014 · Report taken, no arrest: 90.5%2014 · Resolved on scene: 9.5%2015 · Arrest / citation: 11.1%2015 · Report taken, no arrest: 88.9%2016 · Arrest / citation: 9.1%2016 · Report taken, no arrest: 81.8%2016 · Resolved on scene: 4.5%2016 · Unable to locate: 4.5%2017 · Report taken, no arrest: 94.7%2017 · Other (unfounded / cancelled): 5.3%2018 · Arrest / citation: 9.1%2018 · Report taken, no arrest: 81.8%2018 · Unable to locate: 9.1%2019 · Arrest / citation: 2.5%2019 · Report taken, no arrest: 87.5%2019 · Resolved on scene: 5.0%2019 · Unable to locate: 5.0%2020 · Arrest / citation: 9.5%2020 · Report taken, no arrest: 81.0%2020 · Resolved on scene: 4.8%2020 · Unable to locate: 4.8%2021 · Report taken, no arrest: 80.0%2021 · Unable to locate: 20.0%2022 · Arrest / citation: 10.0%2022 · Report taken, no arrest: 65.0%2022 · Resolved on scene: 20.0%2022 · Unable to locate: 5.0%2023 · Arrest / citation: 9.1%2023 · Report taken, no arrest: 45.5%2023 · Resolved on scene: 18.2%2023 · Unable to locate: 27.3%2024 · Arrest / citation: 16.7%2024 · Report taken, no arrest: 66.7%2024 · Unable to locate: 16.7%2025 · Arrest / citation: 16.7%2025 · Report taken, no arrest: 83.3%2026 · Report taken, no arrest: 100.0%2011n=122013n=202015n=182017n=192019n=402021n=102023n=112025n=62026n=4
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 arrestUnable to locateResolved on sceneOther (unfounded / cancelled)
2011128.3%83.3%8.3%——
201215—100.0%———
201320—90.0%10.0%——
201421—90.5%—9.5%—
20151811.1%88.9%———
2016229.1%81.8%4.5%4.5%—
201719—94.7%——5.3%
2018119.1%81.8%9.1%——
2019402.5%87.5%5.0%5.0%—
2020219.5%81.0%4.8%4.8%—
202110—80.0%20.0%——
20222010.0%65.0%5.0%20.0%—
2023119.1%45.5%27.3%18.2%—
2024616.7%66.7%16.7%——
2025616.7%83.3%———
20264—100.0%———
6% of Human Trafficking Calls End “Unable to Locate”Across 2011 to 2026, report-taken outcomes were 84% of calls. “Unable to locate” means officers could not find the incident or the person who called.

Human Trafficking: 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 66% of human trafficking 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 human trafficking 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 min125 min250 min2011: 34.0 min2012: 189.4 min2013: 31.1 min2014: 8.0 min2015: 38.0 min2016: 62.2 min2017: 14.9 min2018: 67.3 min2019: 128.9 min2020: 48.6 min2021: 58.6 min2022: 91.1 min2023: 92.7 min2024: 114.5 min2025: 75.0 min2026: 49.0 min2011: 35.9 min2012: 191.1 min2013: 56.4 min2014: 16.1 min2015: 45.5 min2016: 71.5 min2017: 32.6 min2018: 17.3 min2019: 160.5 min2020: 62.0 min2021: 73.6 min2022: 104.0 min2023: 113.5 min2024: 137.9 min2025: 80.1 min2026: 51.5 min2011n=12013n=42015n=32017n=62019n=102021n=92023n=92025n=52026n=3
Average response timeAverage dispatch delay
Small sample: Only a small share of human trafficking events are called in. The year with the fewest had only 1, 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
2011134.0 min35.9 min
20121189.4 min191.1 min
2013431.1 min56.4 min
201428.0 min16.1 min
2015338.0 min45.5 min
2016562.2 min71.5 min
2017614.9 min32.6 min
2018567.3 min17.3 min
201910128.9 min160.5 min
2020948.6 min62.0 min
2021958.6 min73.6 min
20221191.1 min104.0 min
2023992.7 min113.5 min
20244114.5 min137.9 min
2025575.0 min80.1 min
2026349.0 min51.5 min
49% of Called-In Human Trafficking Calls Get a Response Within 30 Minutes9% were answered in under 5 minutes, across all years on record. This counts only the 34% of human trafficking 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.

Human Trafficking: 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 66% of human trafficking events, because they have no wait. Because most human trafficking 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%2011 · 30–60 min: 100.0%2012 · 1–4 hr: 100.0%2013 · 5–30 min: 75.0%2013 · 1–4 hr: 25.0%2014 · 0–5 min: 50.0%2014 · 30–60 min: 50.0%2015 · 5–30 min: 66.7%2015 · 1–4 hr: 33.3%2016 · 5–30 min: 60.0%2016 · 30–60 min: 20.0%2016 · 4–8 hr: 20.0%2017 · 0–5 min: 16.7%2017 · 5–30 min: 50.0%2017 · 1–4 hr: 33.3%2018 · No recorded response: 40.0%2018 · 0–5 min: 40.0%2018 · 30–60 min: 20.0%2019 · No recorded response: 10.0%2019 · 5–30 min: 40.0%2019 · 1–4 hr: 30.0%2019 · 4–8 hr: 10.0%2019 · Over 8 hr: 10.0%2020 · 5–30 min: 44.4%2020 · 30–60 min: 11.1%2020 · 1–4 hr: 44.4%2021 · No recorded response: 11.1%2021 · 5–30 min: 22.2%2021 · 30–60 min: 22.2%2021 · 1–4 hr: 44.4%2022 · No recorded response: 9.1%2022 · 0–5 min: 9.1%2022 · 5–30 min: 54.5%2022 · 1–4 hr: 18.2%2022 · Over 8 hr: 9.1%2023 · No recorded response: 11.1%2023 · 0–5 min: 11.1%2023 · 5–30 min: 33.3%2023 · 1–4 hr: 22.2%2023 · 4–8 hr: 22.2%2024 · 5–30 min: 50.0%2024 · 1–4 hr: 25.0%2024 · 4–8 hr: 25.0%2025 · 5–30 min: 60.0%2025 · 1–4 hr: 20.0%2025 · 4–8 hr: 20.0%2026 · 0–5 min: 66.7%2026 · 1–4 hr: 33.3%2011n=12013n=42015n=32017n=62019n=102021n=92023n=92025n=52026n=3
No recorded response0–5 min5–30 min30–60 min1–4 hr4–8 hrOver 8 hr
Small sample: Only a small share of human trafficking events are called in. The year with the fewest had only 1, 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 events30–60 min1–4 hr5–30 min0–5 min4–8 hrNo recorded responseOver 8 hr
20111100.0%——————
20121—100.0%—————
20134—25.0%75.0%————
2014250.0%——50.0%———
20153—33.3%66.7%————
2016520.0%—60.0%—20.0%——
20176—33.3%50.0%16.7%———
2018520.0%——40.0%—40.0%—
201910—30.0%40.0%—10.0%10.0%10.0%
2020911.1%44.4%44.4%————
2021922.2%44.4%22.2%——11.1%—
202211—18.2%54.5%9.1%—9.1%9.1%
20239—22.2%33.3%11.1%22.2%11.1%—
20244—25.0%50.0%—25.0%——
20255—20.0%60.0%—20.0%——
20263—33.3%—66.7%———
36% of Called-In Human Trafficking Calls Wait Over an Hour for a ResponseAcross 2011 to 2026, 36% of called-in events took more than an hour to get a response.
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. 2011 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.