EDORA
Skip to content

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

  1. Referral generated by probation/diversion/court based on need & eligibility
    • Send referral packet; note capacity status (open/waitlist)
  2. Program intake conducted by provider; plan created; start date recorded
    • Confirm service goals & expected dosage; align with court/probation plan
  3. Service delivery tracked via attendance & progress reports to supervising agency
    • Log barriers (transport, schedule); apply supports as needed
  4. Completion or discharge documented with reason codes (completed / withdrew / terminated)
    • Capture dosage delivered; note unmet need or transfer if applicable
  5. Follow-up outcomes at 90/180 days where available
    • Education, employment, and re-referral/recidivism indicators
Schema source: community-programs

Fields

FieldTypeRequiredCodesetDescription
pipeline_place_iduuidUnique identifier for this pipeline place row.
pipeline_stage_idenum
stages.yml#stage_key(8)
  • intake
  • detention
  • adjudication
  • disposition
  • supervision
  • commitment_and_placement
  • reentry
  • closure
One of the 8 canonical stages.
pipeline_place_keyenum
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_idstringSalted/hashed or state UID. No plaintext PII.
staff_idstringSupervising officer or referring staff, if applicable.
occurred_datetimedatetimeTimestamp the program referral was authorized or the episode opened.
jurisdiction_codestringCounty/parish/circuit or standardized local code.
legal_case_idstringCase/docket identifier, if applicable.
source_systemstringOrigin system name.
source_filestringSource batch/file id if flatfile.
extract_run_idstringETL run id for lineage.
series_break_flagbooleanComparability break applies to this row.
series_break_reasonenum
series_breaks.yml#reason(4)
  • definition_change
  • vendor_change
  • coverage_change
  • policy_change
Reason for break when flagged.
program_episode_idstringLocal program episode identifier (if system provides one).
provider_idstringProvider organization delivering the service.
service_type_codeenum
service_types.yml#type(9)
  • cognitive_skills
  • mentoring
  • family_therapy
  • individual_therapy
  • substance_use_treatment
  • education_support
  • vocational/employment
  • prosocial_activities
  • restitution_support
Program category (education, employment_readiness, counseling, restorative, family_support, etc.).
program_milestone_codesarray<string
program_milestones.yml#milestone(6)
  • orientation_completed
  • first_session_completed
  • midpoint_review_completed
  • service_hours_50pct
  • service_hours_100pct
  • restitution_completed
Optional labeled milestones reached; semicolon-delimited.
referral_datetimedatetimeWhen referral was sent to provider.
capacity_status_codeenum
capacity_constraints.yml#status⚠️ using capacity_constraints.yml#constraint(6)
  • court_congestion
  • judge_unavailable
  • courtroom_unavailable
  • staffing_shortage
  • technology_failure
  • other
Provider capacity response at referral (open, waitlist, closed) if tracked.
waitlist_flagbooleanYouth placed on waitlist at referral.
waitlist_reason_codeenum
waitlist_reasons.yml#reason⚠️ using waitlist_reasons.yml#level(6)
  • minimal
  • standard
  • enhanced
  • intensive
  • electronic_monitoring
  • custody
Reason for waitlist when known.
program_intake_datetimedatetimeProvider’s intake/orientation timestamp.
planned_start_datedateProvider’s planned service start date.
start_datetimedatetimeActual start timestamp of services.
planned_sessions_countintegerCount of sessions planned for this episode.
planned_dosage_amountnumberPlanned dosage amount (e.g., hours).
dosage_unit_codeenum
dosage_units.yml#unit(4)
  • sessions_per_week
  • hours_per_week
  • total_hours
  • total_weeks
Unit for dosage amounts (hours, days, credits, etc.).
reporting_cadence_codeenum
meeting_frequencies.yml#frequency⚠️ using meeting_frequencies.yml#freq(5)
  • weekly
  • biweekly
  • monthly
  • quarterly
  • ad_hoc
Expected reporting cadence from provider (weekly, biweekly, monthly).
sessions_scheduled_countintegerSessions scheduled during the episode window.
sessions_attended_countintegerSessions attended during the episode window.
sessions_missed_countintegerSessions missed during the episode window.
dosage_delivered_amountnumberDelivered dosage amount corresponding to dosage_unit_code.
attendance_status_codeenum
attendance_status.yml#status(7)
  • scheduled
  • attended
  • excused_absence
  • declined
  • no_show
  • outreach_only
  • cancelled
Overall attendance disposition (e.g., regular, sporadic, unknown).
transport_support_flagbooleanTransport assistance provided during episode.
travel_time_minutesintegerTypical one-way travel time to program, if recorded.
completion_status_codeenum
completion_statuses.yml#status(3)
  • successful
  • neutral_exit
  • failure
completed, neutral_exit, or unsuccessful.
non_completion_reason_codeenum
non_completion_reasons.yml#reason(4)
  • access_barrier
  • refusal
  • scheduling_conflict
  • moved
If not completed, reason recorded by provider/agency.
completion_datetimedatetimeTimestamp when episode ended/closed.
dosage_at_completion_amountnumberDosage delivered at closure (same unit as dosage_unit_code).
last_provider_report_datetimedatetimeMost recent report received from provider.
reporting_timeliness_flagbooleanTrue if latest provider report met expected cadence.
missing_data_flagbooleanTrue if required elements (attendance, completion) were missing in last report.
followup_90d_due_datedateDue date for 90-day follow-up capture.
followup_90d_collected_flagbooleanWhether 90-day follow-up data were collected.
followup_180d_due_datedateDue date for 180-day follow-up capture.
followup_180d_collected_flagbooleanWhether 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.

Related