EDORA Learn — Pipelines
Community Programs & Service Networks (Non-Custodial Supports)
Pipeline 05A
Transparency note: community programs vary widely in data systems and reporting cadence. Participation rates and completion outcomes may reflect partial submissions from providers.
Overview
Community-based programs form the connective tissue between supervision and opportunity. These programs—contracted or directly operated—provide non-custodial services including counseling, education, job readiness, mentoring, and restorative activities. They are central to reducing recidivism risk and supporting stability without confinement. This page explains how such programs are structured, tracked, and evaluated across jurisdictions.
What We Track
Program Categories
- Education & tutoring (credit recovery, GED, IEP/504 supports)
- Employment readiness (work readiness, apprenticeships, placement)
- Counseling (individual, group, family; MH/SUD linkages)
- Restorative / community service (service hours, RJ projects)
- Family-based supports (parent coaching, concrete needs, mentoring)
Referral Criteria
- Eligibility definitions & risk/needs thresholds (tool-aligned)
- Program capacity at intake (slots, waitlist, priority rules)
Participation & Dosage
- Enrollment counts with referral → start date lag
- Sessions attended and dosage delivered vs. planned
- Completion rate per episode (completed / neutral / unsuccessful)
Equity & Access
- Referral distribution by geography & demographics (rate ratios)
- Travel distance & time-to-engagement; wait times by subgroup
Provider Reporting
- Timeliness of reports (weekly/monthly cadence; missing-data flags)
- Required data: attendance, completion status, short follow-up outcomes
- Quality audits (outlier checks, consistency with orders/plan)
Typical Flow
- Referral generated by probation/diversion/court based on need & eligibility- Send referral packet; note capacity status (open/waitlist)
 
- Program intake conducted by provider; plan created; start date recorded- Confirm service goals & expected dosage; align with court/probation plan
 
- Service delivery tracked via attendance & progress reports to supervising agency- Log barriers (transport, schedule); apply supports as needed
 
- Completion or discharge documented with reason codes (completed / withdrew / terminated)- Capture dosage delivered; note unmet need or transfer if applicable
 
- Follow-up outcomes at 90/180 days where available- Education, employment, and re-referral/recidivism indicators
 
Fields
| Field | Type | Required | Codeset | Description | 
|---|---|---|---|---|
| pipeline_place_id | uuid | ✅ | — | Unique identifier for this pipeline place row. | 
| pipeline_stage_id | enum | ✅ | stages.yml#stage_key(8)
 | One of the 8 canonical stages. | 
| 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 | — | Supervising officer or referring staff, if applicable. | |
| occurred_datetime | datetime | ✅ | — | Timestamp the program referral was authorized or the episode opened. | 
| jurisdiction_code | string | ✅ | — | County/parish/circuit or standardized local code. | 
| legal_case_id | string | — | Case/docket identifier, if applicable. | |
| 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 when flagged. | |
| program_episode_id | string | — | Local program episode identifier (if system provides one). | |
| provider_id | string | — | Provider organization delivering the service. | |
| service_type_code | enum | ✅ | service_types.yml#type(9)
 | Program category (education, employment_readiness, counseling, restorative, family_support, etc.). | 
| program_milestone_codes | array<string | program_milestones.yml#milestone(6)
 | Optional labeled milestones reached; semicolon-delimited. | |
| referral_datetime | datetime | ✅ | — | When referral was sent to provider. | 
| capacity_status_code | enum | capacity_constraints.yml#status⚠️ using capacity_constraints.yml#constraint(6)
 | Provider capacity response at referral (open, waitlist, closed) if tracked. | |
| waitlist_flag | boolean | — | Youth placed on waitlist at referral. | |
| waitlist_reason_code | enum | waitlist_reasons.yml#reason⚠️ using waitlist_reasons.yml#level(6)
 | Reason for waitlist when known. | |
| program_intake_datetime | datetime | — | Provider’s intake/orientation timestamp. | |
| planned_start_date | date | — | Provider’s planned service start date. | |
| start_datetime | datetime | — | Actual start timestamp of services. | |
| planned_sessions_count | integer | — | Count of sessions planned for this episode. | |
| planned_dosage_amount | number | — | Planned dosage amount (e.g., hours). | |
| dosage_unit_code | enum | dosage_units.yml#unit(4)
 | Unit for dosage amounts (hours, days, credits, etc.). | |
| reporting_cadence_code | enum | meeting_frequencies.yml#frequency⚠️ using meeting_frequencies.yml#freq(5)
 | Expected reporting cadence from provider (weekly, biweekly, monthly). | |
| sessions_scheduled_count | integer | — | Sessions scheduled during the episode window. | |
| sessions_attended_count | integer | — | Sessions attended during the episode window. | |
| sessions_missed_count | integer | — | Sessions missed during the episode window. | |
| dosage_delivered_amount | number | — | Delivered dosage amount corresponding to dosage_unit_code. | |
| attendance_status_code | enum | attendance_status.yml#status(7)
 | Overall attendance disposition (e.g., regular, sporadic, unknown). | |
| transport_support_flag | boolean | — | Transport assistance provided during episode. | |
| travel_time_minutes | integer | — | Typical one-way travel time to program, if recorded. | |
| completion_status_code | enum | completion_statuses.yml#status(3)
 | completed, neutral_exit, or unsuccessful. | |
| non_completion_reason_code | enum | non_completion_reasons.yml#reason(4)
 | If not completed, reason recorded by provider/agency. | |
| completion_datetime | datetime | — | Timestamp when episode ended/closed. | |
| dosage_at_completion_amount | number | — | Dosage delivered at closure (same unit as dosage_unit_code). | |
| last_provider_report_datetime | datetime | — | Most recent report received from provider. | |
| reporting_timeliness_flag | boolean | — | True if latest provider report met expected cadence. | |
| missing_data_flag | boolean | — | True if required elements (attendance, completion) were missing in last report. | |
| followup_90d_due_date | date | — | Due date for 90-day follow-up capture. | |
| followup_90d_collected_flag | boolean | — | Whether 90-day follow-up data were collected. | |
| followup_180d_due_date | date | — | Due date for 180-day follow-up capture. | |
| followup_180d_collected_flag | boolean | — | Whether 180-day follow-up data were collected. | |
| Download CSVwhat_we_track.csv | ||||
Data & Methods
Community program data come from provider management systems or uploads to centralized case management tools. Standard elements include demographic identifiers, referral source, session counts, and exit reasons. Missing or delayed reports are noted in metadata per Data Quality & Validation. When program definitions or service models change, we mark series breaks following Series Breaks & Definition Changes. Denominators are youth referred, with participation rates calculated as enrolled ÷ referred. Small-n rules follow Suppression & Small-n.