Sample CCSA field report

What a Certified Child Safety Advocate actually files

This is an illustrative example — not a real report — of what a CCSA submits through the platform after observing potential trafficking. Reports stick to observed facts, use a structured indicator checklist, and are routed by admin-configured rules to the appropriate law-enforcement partner. The CCSA's identity is attached for accountability; the subjects observed are anonymous-by-default.

Field report · CCSA-2026-#####Status: routed
Report type
Suspected trafficking
When did it occur?
2026-05-09 · 18:42 local time
Location
Truck stop, I-40 exit 234, Nashville TN
lat 36.1627 · lng −86.7816 · captured with consent at submission
Indicators observed
  • Subject appears underage
  • Subject is fearful or coached
  • Adult speaks for the subject
  • Subject lacks ID / personal items
  • Vehicle / room with multiple beds
Narrative

Observed an adult male shepherding two female minors (approx. 12-14) through a truck stop. Minors avoided eye contact and adult answered all questions for them. Minors did not leave the adult's side; one appeared to be coached when the cashier asked her name. Vehicle plate noted privately: TN-7XK432, white Ford F-150 pickup. Phone tag visible on the dashboard listing "615-555-0179". I withdrew to a safe distance and submitted this report.

Routing decision
Routed to [Partner: TBD by AF leadership] via rule v1 · Default — suspected trafficking
Acknowledgment receipt pending
Force-multiplier signals (auto-extracted)
  • VEHICLE_PLATE · TN7XK432
  • VEHICLE_DESCRIPTOR · white ford
  • PHONE_NUMBER · 6155550179
Cross-case predator-pattern recognition checks these against all other reports. If the same plate appears in 2+ reports, a pattern surfaces at /admin/patterns for analyst review.
Hotspot evaluation
Geofence 36.16:-86.78 · 1 of 3 distinct CCSAs required to flag · 30-day rolling window

What does NOT go in a CCSA report

What happens after the CCSA hits Submit

  1. The report is persisted with hash-chained audit entry — FIELD_REPORT_SUBMITTED
  2. Signal extraction runs on the narrative: vehicle plates, descriptors, aliases, phone numbers
  3. Missing-children database cross-reference fires for relevant report types
  4. Hotspot evaluation runs against the reporter's geofence
  5. Routing engine matches the report against admin-configured partner rules
  6. If a rule matches, the report is dispatched to that law-enforcement partner with an acknowledgment-receipt channel where supported
  7. If the report contains a hotspot signal or matches the missing-children DB, those events surface in the dispatcher console

See also: About · FAQ · Apply to become a CCSA