EDORA Learn β Pipelines
Reentry & Aftercare (Pipeline Overview)
Pipeline 09
Transparency note: small release cohorts can create volatile month-to-month rates; where applicable, we pool across quarters and mark any series breaks tied to policy or definition changes.
Overview
Reentry links residential care to community life. Planning typically begins 30β90 days pre-release and aligns supervision conditions, education re-enrollment, behavioral health care, and family supports. A well-documented handoff reduces gaps in services, mitigates early violations, and improves stability in the first 90β180 days. This page summarizes common steps, roles, and observable data elements for cross-jurisdiction comparisons.
What We Track
Pre-release Planning
- Reentry plan created with target release date
- Named reentry coordinator (contact recorded)
- Youth & caregiver participation documented (meeting dates, signatures)
- Housing & school placement identified pre-release
Handoffs (Warm)
- Education packet: credits, IEP/504, receiving school contact & start date
- Health packet: medication list, treatment plan, immunizations, consent forms
- Provider referrals with appointment dates and confirmation (attended/No Show)
Supervision (Dosage)
- Initial contact β€ 7 days post-release (date/time captured)
- Caseload ratios & contact frequency by supervision level (required vs. achieved)
- Graduated responses to violations (grid adherence; overrides recorded)
Services & Supports
- Evidence-aligned programming (e.g., MST/FFT) initiated (referral β first session lag)
- Employment supports & mentoring engaged; transportation assistance provided as needed
Early Outcomes
- School enrollment & attendance within first 30 days; credit accrual observed monthly
- Program engagement (attendance, dosage delivered) and supports used (transport, mentoring)
- Technical violations, new petitions, and 90/180-day stability indicators tracked
Typical Flow
- Begin reentry planning with MDT and target release date
- Confirm coordinator; schedule family-inclusive meetings; map housing/school options
- Confirm placements & appointments; document consents
- Secure school placement/enrollment plan; set BH/primary care visits with dates
- Day of release: transmit records; complete initial community contact β€ 7 days
- Align expectations, incentives, and communication preferences (language/modality)
- First 90 days: increase contact frequency; stabilize services; apply graduated responses
- Track attendance & engagement; troubleshoot barriers (transport, tech, scheduling)
- 90β180 days: taper intensity as risks decline; reassess; close or step-down
- Document outcomes; complete warm handoffs; set optional 6β12 mo. check-ins
Fields
Field | Type | Required | Codeset | Description |
---|---|---|---|---|
pipeline_place_id | uuid | β | β | Unique identifier for this reentry/aftercare transition record. |
pipeline_stage_id | enum | β | stages.yml#stage_key(8)
| One of the canonical stages; here = reentry_aftercare. |
pipeline_place_key | enum | β | pipeline_places.yml#place_key(45)
| Canonical key for this place (maps to route/slug). |
youth_id | string | β | β | Salted/hashed or state UID. No plaintext PII. |
staff_id | string | β | Reentry coordinator or supervising officer (ID only). | |
occurred_datetime | datetime | β | β | Anchor timestamp for this transition event (e.g., plan finalization or community handoff). |
jurisdiction_code | string | β | β | County/parish/circuit or standardized local code. |
legal_case_id | string | β | Case/docket identifier if tied to court-ordered aftercare. | |
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)
| Reason for break (policy/process/tool change). | |
plan_initiated_date | date | β | Date reentry plan was first opened (target 30β90 days pre-release). | |
plan_finalized_date | date | β | Date reentry plan was finalized prior to release. | |
target_release_date | date | β | Projected release date at time of planning. | |
actual_release_date | date | β | Actual date youth returned to community supervision. | |
reentry_coordinator_staff_id | string | β | Assigned reentry coordinator (ID only). | |
supervision_level_code | enum | supervision_levels.yml#level(4)
| Initial community supervision level at release. | |
contact_frequency_required_per_month | integer | β | Required contact count per month set at handoff. | |
contact_frequency_plan_window_code | enum | review_intervals.yml#interval(3)
| Interval unit for contact cadence (e.g., monthly/weekly). | |
initial_contact_datetime | datetime | β | First community contact attempt/meeting timestamp (β€ 7 days target). | |
education_enrollment_status_code | enum | education_status.yml#status(6)
| Enrollment status within first 10 days post-release. | |
health_handoff_status_code | enum | digital_handoff_statuses.yml#status(4)
| Status of health/behavioral-health handoff (efile/API receipt). | |
provider_referral_types | array<string> | service_types.yml#type(9)
| Services referred at release (e.g., MST/FFT, mentoring, CTE); semicolon-delimited. | |
provider_first_appointment_date | date | β | First kept appointment date for any referred community service. | |
followup_window_code | enum | followup_windows.yml#window(4)
| Early follow-up window anchored to release (e.g., 30/90/180 days). | |
compliance_status_code | enum | compliance_statuses.yml#status(4)
| Compliance snapshot within the chosen follow-up window. | |
response_outcome_code | enum | response_outcomes.yml#outcome(4)
| Most serious graduated response applied within early window, if any. | |
warm_handoff_status_code | enum | digital_handoff_statuses.yml#status(4)
| Overall data handoff success (education/health packet receipt). | |
caregiver_participation_status_code | enum | caregiver_participation_statuses.yml#status(6)
| Participation status for caregiver in pre-release planning. | |
housing_placement_type_code | enum | housing_placement_types.yml#type(8)
| Housing placement identified pre-release. | |
meeting_participation_roles | array<string> | meeting_participation_roles.yml#role(11)
| Roles represented in the documented planning meeting; semicolon-delimited. | |
consent_type_codes | array<string> | consent_types.yml#typeβ οΈ using consent_types.yml#Type(5)
| Types of consent forms collected. | |
consent_status_code | enum | consent_statuses.yml#statusβ οΈ using consent_statuses.yml#Status(4)
| Overall consent status at release (all signed/pending/etc). | |
appointment_outcome_code | enum | appointment_outcomes.yml#outcome(5)
| Outcome of first scheduled provider or service appointment. | |
support_service_type_codes | array<string> | support_services.yml#type(7)
| Types of early supports provided (transportation, mentoring, etc); semicolon-delimited. | |
communication_modality_code | enum | communication_modalities.yml#modality(9)
| Agreed primary communication channel for supervision contacts. | |
preferred_language_code | enum | β missing in _index.yml | Preferred spoken/written language for youth/family communication. | |
barrier_type_codes | array<string> | barrier_types.yml#type(8)
| Barriers encountered during early aftercare follow-up; semicolon-delimited. | |
Download CSVwhat_we_track.csv |
Data & Methods
Measures use episode-based denominators (youth released from placement) with fixed windows (e.g., 30/90/180 days). Time-to-contact is measured in days from release; appointment completion is binary with date stamps. When tools or policies change (e.g., new graduated response grids), we mark series breaks and avoid direct pre/post rate comparisons. For small cohorts, we report pooled quarterly aggregates and provide rate ratios with uncertainty notes. See Methods pages on denominators & exposure time, series breaks, and attrition & censoring.