Youth Transport & Transfer (Between Facilities and Courts)

Pipeline 08C

Transparency note: transport records are sometimes incomplete when multiple agencies are involved. Missing data on duration or custody chain are flagged in metadata and excluded from time-based averages.

Overview

Youth transport events connect the physical flow of cases to their administrative flow. Each movement—court hearing, placement admission, or inter-facility transfer—requires a verified custody chain, authorization record, and timely data entry. Reliable transport data ensure accountability, safety, and continuity of case information. This page describes measurable features of youth transport and transfer operations.

What We Track

Custody Chain

Sending/receiving officer or facility identified (names, IDs)
Pickup & delivery timestamps recorded (time zone noted)
Property & medications documented (inventory, counts, signatures)

Scheduling

Coordination with court calendars, detention staff, transport units
Cancellations & delays logged (who/why/when)

Duration & Delays

Total in-transit time (depart → arrive)
Late departure/arrival flags with reason codes
- Weather
- Staffing
- Route conflict / traffic
- Vehicle issue

Safety & Compliance

Incident reports: restraints, medical events, missed meals/rest breaks
Vehicle standards adhered to (seat restraints, temperature, capacity)

Data Integrity

Custody, case, and location records match at arrival (youth ID, case #, facility code)
Digital handoff success rate (e-file receipt, API sync status)

Typical Flow

Authorization received from court or facility; custody form generated
- Include destination, purpose, time window, and special conditions
Pickup logged with youth ID, officer ID, and departure timestamp; record synced
- Verify property/meds inventory; obtain signatures
Transit with GPS/route logging where available; incidents noted
- Record rest/meal breaks; capture any delays with reason codes
Arrival confirmed with receiving staff; custody & property transfer verified
- Complete receiving checklist; update youth location and status
Data upload completed; custody chain closed; central database updated
- Confirm digital handoff success (receipt ID/API acknowledgment)

Fields

Field	Type	Required	Codeset	Description
pipeline_place_id	uuid	✅	—	Unique identifier for this transport/transfer record.
pipeline_stage_id	enum	✅	stages.yml#stage_key(8) intake detention adjudication disposition supervision commitment_and_placement reentry closure	One of the eight canonical stages.
pipeline_place_key	enum	✅	pipeline_places.yml#place_key(45) intake pre_petition_diversion_and_deflection diversion youth_assessment_tools prosecutorial_screening status_offenses adjudication case_planning family_engagement case_timeliness language_access restorative_justice detention_screening community_atds electronic_monitoring court_appearance_and_fta initial_hearing pretrial_supervision probation intensive_supervision …and 25 more	Canonical key for this place (maps to route/slug).
youth_id	string	✅	—	Salted/hashed or state UID. No plaintext PII.
staff_id	string		—	Scheduling/coordinating staff person (ID only).
occurred_datetime	datetime	✅	—	Authorization or order timestamp for this transport.
jurisdiction_code	string	✅	—	County/parish/circuit or standardized local code.
legal_case_id	string		—	Case/docket identifier if the move is court-directed.
source_system	string	✅	—	Origin system name.
source_file	string		—	Source batch/file id if flatfile.
extract_run_id	string		—	ETL run id for lineage.
series_break_flag	boolean		—	Comparability break applies to this row.
series_break_reason	enum		series_breaks.yml#reason(4) definition_change vendor_change coverage_change policy_change	Reason for break (policy/process/tool change).
sending_facility_id	string		—	Sending facility/provider identifier.
receiving_facility_id	string		—	Receiving facility/provider identifier or court location.
transport_officer_staff_id	string		—	Primary transport officer ID.
escort_staff_ids	array<string>		—	Additional escort staff IDs; semicolon-delimited.
custody_form_generated_flag	boolean		—	Custody form generated prior to pickup.
custody_release_signature_flag	boolean		—	Releasing signature captured at pickup.
custody_acceptance_signature_flag	boolean		—	Acceptance signature captured at delivery.
property_inventory_document_id	string		—	Document/ref id for property/medications inventory.
medications_transferred_count	integer		—	Number of distinct medication items transferred.
medications_discrepancy_flag	boolean		—	Any discrepancy between send and receive counts.
transfer_status_code	enum	✅	transfer_statuses.yml#status(4) scheduled cancelled in_transit completed	scheduled, cancelled, in_transit, completed.
scheduled_pickup_datetime	datetime		—	Scheduled pickup datetime.
scheduled_delivery_datetime	datetime		—	Scheduled delivery datetime.
cancellation_reason_code	enum		transport_cancellation_reasons.yml#reason(8) court_calendar_change provider_capacity youth_health_screen_fail staffing weather vehicle_issue paperwork_issue other	Reason for cancellation if status = cancelled.
depart_datetime	datetime		—	Actual pickup/departure timestamp.
depart_timezone	string		—	IANA timezone string at departure (e.g., America/Chicago).
arrive_datetime	datetime		—	Actual delivery/arrival timestamp.
arrive_timezone	string		—	IANA timezone string at arrival.
total_in_transit_minutes	integer		—	Total minutes between depart and arrive (structural store).
late_departure_flag	boolean		—	Departure later than scheduled.
late_arrival_flag	boolean		—	Arrival later than scheduled.
delay_reason_codes	array<string>		transport_delay_reasons.yml#reason(9) weather staffing route_conflict traffic vehicle_issue paperwork court_calendar safety_event other	weather, staffing, route_conflict, traffic, vehicle_issue, paperwork, court_calendar, safety_event, other; semicolon-delimited.
incident_type_codes	array<string>		transport_incident_types.yml#type(7) restraint medical_event missed_meal missed_rest_break equipment_failure behavior_alert other	Incident categories (restraint, medical_event, missed_meal, missed_rest_break, equipment_failure); semicolon-delimited.
rest_breaks_count	integer		—	Number of rest breaks recorded.
meal_breaks_count	integer		—	Number of meal breaks recorded.
vehicle_id	string		—	Vehicle identifier used for transport.
vehicle_standard_adhered_flag	boolean		—	Vehicle standards adhered to (seat restraints, temp, capacity).
noncompliance_codes	array<string>		vehicle_noncompliance.yml#code(6) seat_restraint_not_used temperature_out_of_range capacity_exceeded maintenance_issue documentation_missing other	Which standards were not met; semicolon-delimited.
seat_restraint_used_flag	boolean		—	Seat restraints used per policy.
temperature_within_range_flag	boolean		—	Temperature maintained per standard.
capacity_not_exceeded_flag	boolean		—	Vehicle capacity not exceeded.
gps_logging_flag	boolean		—	GPS/route logging enabled.
route_log_id	string		—	Reference id for stored route/GPS log if captured.
custody_match_flag	boolean		—	Custody record (youth ID) matches at arrival.
case_match_flag	boolean		—	Case number/order matches at arrival.
location_match_flag	boolean		—	Location/facility codes match receiving records.
digital_handoff_status_code	enum		digital_handoff_statuses.yml#status(4) efile_received api_synced partial failed	efile_received, api_synced, partial, failed.
digital_handoff_receipt_id	string		—	Receipt or acknowledgment id from receiving system/API.
Download CSVwhat_we_track.csv

Data & Methods

Transport metrics use trip-level records. The primary indicators are average trip duration, percent of delayed trips, and verified custody chain completion rate. When agencies upgrade fleet tracking or custody software, we mark series breaks. Data fields include origin/destination, timestamps, staff IDs, and incident codes. Suppression and reconciliation rules follow Data Quality & Validation and Series Breaks & Definition Changes. For cross-agency handoffs, interoperability guidance from Data Interoperability & Architecture applies. Confidential incident reporting adheres to Data Privacy & Disclosure Control.

EDORA • Learn