EDORA Learn — Pipelines
Probation Supervision (Core Case Management)
Pipeline 05
Transparency note: supervision caseloads and definitions of “active contact” vary by jurisdiction. We standardize across datasets and mark series breaks when contact standards or supervision levels change.Overview
Probation supervision is the most common outcome following adjudication, combining monitoring, service coordination, and behavior change supports. Officers manage caseloads by risk level and use structured contacts, incentives, and graduated responses to support progress. This page outlines measurable components of supervision across programs and time.
What We Track
Caseload Structure
- Youth per officer by supervision level (min/med/high/ISP)
- Weighted caseloads by risk & needs complexity (scoring rubric noted)
Contact Standards
- Required vs. achieved contacts/month by modality
- Field
- Office
- Virtual (phone/video/SMS check-ins)
- Missed contacts, reschedules, and time-to-makeup
Service Integration
- Referrals to:
- Education (enrollment, credit recovery, IEP/504)
- Behavioral health (assessment, treatment, meds)
- Mentoring / prosocial programs
- Time to engagement (referral → first appointment) & closure rates
Compliance & Incentives
- Monthly count per youth of positive responses (praise notes, privileges, earned passes)
- Monthly count per youth of negative responses (verbal warning → sanction grid)
- Distribution of incentives vs. sanctions (proportionality)
Equity & Performance
- Caseloads & contact rates by race/ethnicity, geography, and supervision level
- Successful completions & early terminations by subgroup (rate ratios)
Typical Flow
- Assignment of youth to supervision level & officer (post-disposition or step-down)
- Open case; confirm risk/needs scores and any special conditions
- Case plan created; services initiated; contact schedule set
- SMART goals, roles, review dates; schedule field/office/virtual cadence
- Monitoring of attendance, compliance, and service participation via structured contacts
- Log achieved vs. required contacts; track time to engagement and barriers
- Graduated responses for violations or progress; incentives documented
- Apply response grid; prefer positive reinforcement; record overrides & rationale
- Review outcomes at scheduled intervals; consider step-down or early termination
- Update plan/supervision level; prepare closure & community handoffs when goals met
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 | — | Staff primary actor for this supervision episode. | |
occurred_datetime | datetime | ✅ | — | Timestamp when the probation episode was opened/authorized. |
jurisdiction_code | string | ✅ | — | County/parish/circuit or standardized local code. |
location_site_id | string | — | Supervising office/site identifier. | |
actor_role_code | enum | roles.yml#actor_role(7)
| Role primarily responsible for this place. | |
legal_case_id | string | — | Docket/case identifier if already created. | |
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. | |
supervision_level_code | enum | ✅ | supervision_levels.yml#level(4)
| Supervision intensity (policy-defined levels). |
conditions_imposed_codes | array<string> | order_conditions.yml#condition(6)
| Conditions imposed at start (e.g., curfew, school_attendance); semicolon-delimited. | |
contact_channel_codes | array<string> | contact_channels.yml#channel(4)
| Allowed/required contact modalities (in_person, phone, sms, portal); semicolon-delimited. | |
meeting_frequency_code | enum | meeting_frequencies.yml#frequency⚠️ using meeting_frequencies.yml#freq(5)
| Policy frequency bucket for case contacts. | |
contact_cadence_per_week | number | — | Required case contacts per week. | |
curfew_start_time | time | — | Daily curfew start (local time), if ordered. | |
curfew_end_time | time | — | Daily curfew end (local time), if ordered. | |
contacts_scheduled_count | integer | — | Number of scheduled case contacts in the episode window. | |
contacts_completed_count | integer | — | Number of completed case contacts. | |
missed_contact_count | integer | — | Missed contacts in the episode window. | |
compliance_status_code | enum | compliance_statuses.yml#status(4)
| Current compliance status at last review (compliant, partial, noncompliant). | |
response_action_codes | array<string> | graduated_responses.yml#action(5)
| Responses applied (contact_attempt, step_up, incentive, violation_report); semicolon-delimited. | |
service_referral_codes | array<string> | service_referrals.yml#service(6)
| Services referred/linked during episode; semicolon-delimited. | |
provider_id | string | — | Lead provider organization identifier, if assigned. | |
last_review_datetime | datetime | — | Timestamp of the most recent compliance/review meeting. | |
completion_status_code | enum | completion_statuses.yml#status(3)
| Episode closed as completed, neutral_exit, or unsuccessful. | |
completion_datetime | datetime | — | Episode end timestamp. | |
unsuccessful_reason_code | enum | failure_reasons.yml#reason(3)
| If unsuccessful, reason (new_offense, noncompliance, withdrawal). | |
routed_to_next_node_code | enum | next_routes.yml#route(3)
| Where the case moved next (case_review, modification, revocation, closure). | |
Download CSVwhat_we_track.csv |
Data & Methods
Supervision indicators use supervision-based denominators. Contacts are event-level records with timestamps, modality, and outcome fields. Completion metrics follow Program Completion & Early Termination. Equity analyses use rate ratios and control for supervision level following Cross-Jurisdiction Comparability. Data validation and exposure adjustments follow Data Quality & Validation and Denominators & Exposure Time. Changes in contact standards or definitions are annotated as series breaks and reflected in metadata.