Crossover Youth & Dual-Status Coordination (Justice–Child Welfare)

Pipeline 13

Transparency note: dual-status counts are often small and linkage quality varies by jurisdiction; small-n results are pooled across quarters and series breaks are annotated when matching rules or MOUs change.

Overview

Crossover or dual-status youth are involved with both the youth justice and child welfare systems. Coordination focuses on consistent case planning, stable placements, and uninterrupted schooling and healthcare while court processes continue. This page outlines how dual involvement is identified, how lead-agency models operate, and which indicators support transparent measurement across agencies.

What We Track

Identification & Confirmation

Dual-status flags at intake/petition (active child welfare case, prior custody episodes)
Confirmation workflow completed (match rules, steward approval, timestamped audit trail)

Lead-Agency Models

Lead designated: justice or child welfare (with rationale recorded)
Team composition documented (PO, CW worker, education liaison, BH clinician, counsel)
Joint case planning cadence (weekly/biweekly/monthly) & decision authority defined

Placement & Stability

Number of placement moves; days in OOH care (rate per 100 youth-days)
Reentries to shelter/respite; step-down attempts and reasons for failure
Kinship/family-based settings availability & use; proximity to home/school

Education & Health Continuity

School re-enrollment ≤ 10 days after move; credit transfer posting verified
IEP/504 services continuous (service minutes & meeting schedules tracked)
BH linkage pre/post transition (plan, meds reconciliation, first-appointment kept)

Timeliness, Safety, & Permanency

Time to initial joint meeting from identification (target window set)
Incident rates per 100 youth-days (AWOL, restraints, ER visits), with context notes
Permanency plan milestones (reunification, guardianship, adoption) & court review intervals

Typical Flow

Flag & confirm dual-status at intake/petition
- Apply match rules; contact child welfare point; record confirmation and timestamp
Assign lead agency & convene joint meeting
- Create unified plan covering placement, education, health, visitation, court obligations
- Define decision authority and escalation paths
Coordinate services & responsibilities
- School enrollment, treatment linkages, family contact plan; set timelines and owners
Review & adjust after events and at set intervals
- Moves, violations, hearings trigger plan updates; record overrides with rationale
Step-down & handoff toward permanency or reentry supports
- Transmit records; define 30/90/180-day follow-ups; close when permanency achieved

Fields

Field	Type	Required	Codeset	Description
pipeline_place_id	uuid	✅	—	Unique identifier for this dual-status coordination record.
pipeline_stage_id	enum	✅	stages.yml#stage_key(8) intake detention adjudication disposition supervision commitment_and_placement reentry closure	One of the canonical stages; currently mapped to reentry_aftercare.
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		—	Coordinating staff (ID only).
occurred_datetime	datetime	✅	—	Anchor timestamp for this coordination event (e.g., confirmation, joint meeting, update).
jurisdiction_code	string	✅	—	County/parish/circuit or standardized local code.
legal_case_id	string		—	Court case/docket identifier when relevant.
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).
dual_status_flag	boolean	✅	—	True if youth is identified/confirmed as dual-status.
dual_status_identified_datetime	datetime	✅	—	Timestamp when dual-status was first flagged.
cw_active_case_flag	boolean		—	Active child welfare case at identification.
prior_custody_episode_count	integer		—	Count of prior CW custody episodes (if known).
confirmation_workflow_status_code	enum	✅	confirmation_statuses.yml#status(9) initiated acknowledged reschedule_requested need_help no_response matched_pending_steward confirmed not_confirmed revoked	initiated, matched_pending_steward, confirmed, not_confirmed, revoked.
confirmation_match_method_code	enum		matching_methods.yml#method(3) deterministic probabilistic clerical_review	deterministic, probabilistic, clerical_review.
confirmation_match_score	number		—	Probabilistic score if method = probabilistic.
steward_approval_staff_id	string		—	Data steward who approved the confirmation.
confirmation_audit_log_id	string		—	Reference to audit trail for confirmation workflow.
lead_agency_type_code	enum	✅	lead_agency_types.yml#agency(7) probation justice school behavioral_health child_welfare reentry_team other	Designated lead (justice/probation or child_welfare).
lead_rationale_category_code	enum		lead_rationale_categories.yml#category(5) custody_jurisdiction service_need_primary court_order capacity other	custody_jurisdiction, service_need_primary, court_order, capacity, other.
team_roles	array<string>		meeting_participation_roles.yml#role(11) youth caregiver coordinator provider school_rep probation_officer therapist education_liaison behavioral_health_partner workforce_partner reentry_coordinator	Team composition (PO, CW worker, education liaison, BH clinician, counsel); semicolon-delimited.
team_role_statuses	array<string>		❌ missing in _index.yml	Attendance outcomes aligned to team_roles order; semicolon-delimited.
decision_authority_model_code	enum		decision_authority_models.yml#model(4) joint lead_consult split_domain court_directed	joint, lead_consult, split_domain, court_directed.
first_joint_meeting_datetime	datetime		—	Timestamp of first joint planning meeting after identification.
meeting_cadence_interval_code	enum		review_intervals.yml#interval(3) review_7d review_14d review_30d	Planned cadence (weekly, biweekly, monthly).
elapsed_hours_identification_to_first_meeting	integer		—	Hours from dual_status_identified_datetime to first_joint_meeting_datetime.
current_placement_setting_code	enum		cw_placement_setting_types.yml#type(8) kinship foster_home group_home shelter residential_treatment independent_living transitional_living other	kinship, foster_home, group_home, shelter, residential_treatment, independent_living, other.
placement_provider_id	string		—	Current CW placement provider/site.
placement_move_count	integer		—	Number of placement moves since identification (structural count).
days_in_ooh_care	integer		—	Days in out-of-home care during active dual-status period.
step_down_attempted_flag	boolean		—	True if a less restrictive placement was attempted.
step_down_failure_reason_codes	array<string>		step_down_failure_reasons.yml#reason(7) family_unavailable provider_capacity youth_preference safety_concern school_placement_issue treatment_needs other	Reasons step-down failed; semicolon-delimited.
kinship_available_flag	boolean		—	Kinship/family-based setting available.
kinship_used_flag	boolean		—	Kinship/family-based setting used.
proximity_home_miles	number		—	Approx. miles from placement to home.
proximity_school_miles	number		—	Approx. miles from placement to school.
school_reenroll_date	date		—	Date of re-enrollment after a move.
re_enrollment_within_10d_flag	boolean		—	True if re-enrollment occurred within 10 days of move.
credit_posting_verified_flag	boolean		—	Transcript/credit posting verified at receiving school.
iep504_continuity_status_code	enum		service_continuity_statuses.yml#status(3) continuous gap_detected not_applicable	continuous, gap_detected, not_applicable.
service_minutes_scheduled	integer		—	Weekly minutes scheduled for IEP/504 services.
service_minutes_delivered	integer		—	Minutes delivered within the first 30 days post-move.
bh_linkage_pre_transition_flag	boolean		—	Behavioral health linkage set before placement change.
meds_reconciliation_completed_flag	boolean		—	Medication reconciliation completed at transition.
first_bh_appointment_date	date		—	First BH appointment kept after move.
incident_type_codes	array<string>		incident_types.yml#type(7) awol restraint er_visit police_contact injury property_damage other	Incident categories (awol, restraint, er_visit, police_contact, injury, other); semicolon-delimited.
incident_count	integer		—	Count of incidents logged during the period covered by this row.
court_review_interval_code	enum		court_review_intervals.yml#interval(4) 30d 60d 90d statutory_other	Court review interval cadence.
permanency_goal_type_code	enum		permanency_goal_types.yml#type(5) reunification guardianship adoption appla other	reunification, guardianship, adoption, appla, other.
permanency_milestone_status_code	enum		permanency_milestone_statuses.yml#status(4) on_track delayed achieved changed	on_track, delayed, achieved, changed.
permanency_goal_set_date	date		—	Date permanency goal was set/updated.
permanency_achieved_date	date		—	Date permanency achieved (if applicable).
dual_status_closed_date	date		—	Date dual-status coordination was closed.
dual_status_outcome_code	enum		dual_status_outcomes.yml#outcome(5) reunified stepped_down transferred_jurisdiction aged_out other	reunified, stepped_down, transferred_jurisdiction, aged_out, other.
Download CSVwhat_we_track.csv

Data & Methods

Dual-status identification uses deterministic or probabilistic linkage between justice and child welfare systems with required match fields (name/DOB, agency IDs). Coverage and match confidence are documented in metadata. Stability is summarized via placement-move counts and days-in-care; incidents use exposure-adjusted rates per 100 youth-days. Education continuity follows event-to-event metrics (move→enrollment, request→credit-posting). When MOUs, matching rules, or program definitions change, we mark series breaks. Confidentiality and access controls follow Data Governance & Ethical Integration and Data Privacy & Disclosure Control. Linkage practices are described in Data Linkage & Integration and technical standards in Data Interoperability & Architecture.

EDORA • Learn