EDORA
Skip to content

EDORA Learn β€” Pipelines

Pre-Adjudication Supervision (Release Conditions & Monitoring)

Pipeline 03E

Transparency note: small release cohorts and mid-year policy shifts (e.g., revised response grids or monitoring rules) may create volatility; series breaks are annotated and small-n cells are pooled across months/quarters.

Overview

Many youth are released while petitions and hearings move forward. Jurisdictions set tailored conditionsβ€”attendance, curfew, school engagement, or program participationβ€”and may assign community-based alternatives to detention (ATDs), such as evening reporting or electronic monitoring. This page outlines how pre-adjudication supervision is structured, what is measurable, and how it connects to detention, diversion, and adjudication stages.

What We Track

Eligibility & Decision Logic

  • Release vs. hold criteria documented (policy grid/statute)
  • Detention risk instrument score & version recorded
  • Overrides logged with rationale & approver

Conditions & Contact Standards

  • Required check-ins (frequency & modality)
  • Curfew and school attendance conditions set
  • Program sessions (start date, cadence) scheduled

ATDs & Monitoring

  • ATD assignment (evening/day reporting, shelter/respite, EM)
  • Utilization vs. capacity tracked (enrolled Γ· slots)
  • Monitoring parameters configured (curfew windows, alerts)

Compliance & Responses

  • On-time check-ins & attendance rates tracked
  • Missed contacts and technical vs. new-law violations coded
  • Graduated responses applied short of revocation/readmission

Timeliness

  • Days from release β†’ next hearing; continuances & reasons
  • Time to case resolution (diversion completion, dismissal/decline, adjudication)

Simple Flow

  1. Release decision documented with conditions & any ATD
    • Record tool score/version and any overrides with rationale
  2. Orientation to expectations; schedule contacts & program starts
    • Provide plain-language terms; confirm contact modality & language
  3. Monitoring of contacts, attendance, compliance; record missed events
    • Log curfew, check-ins, service milestones; note barriers & supports
  4. Graduated responses for noncompliance; consider condition modifications
    • Apply response grid; document proportionality & outcomes
  5. Case resolution (diversion completion, dismissal/decline, adjudication) & transition
    • Handoff to next stage (court, services, or closure) with audit trail
Schema source: pretrial-supervision

Fields

FieldTypeRequiredCodesetDescription
pipeline_place_iduuidβœ…β€”Unique 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_idstringβœ…β€”Salted/hashed or state UID. No plaintext PII.
staff_idstringβ€”Supervising officer/case manager.
occurred_datetimedatetimeβœ…β€”Timestamp when the supervision episode was opened/authorized.
jurisdiction_codestringβœ…β€”County/parish/circuit or standardized local code.
location_site_idstringβ€”Office/site identifier.
actor_role_codeenum
roles.yml#actor_role(7)
  • Intake_Officer
  • Prosecutor
  • Defender
  • Probation_Officer
  • Case_Manager
  • Facility_Staff
  • Coach_Reentry
Role primarily responsible for this place.
legal_case_idstringβ€”Docket/case identifier.
source_systemstringβœ…β€”Origin system name.
source_filestringβ€”Source batch/file id if flatfile.
extract_run_idstringβ€”ETL run id for lineage.
series_break_flagbooleanβ€”Comparability 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.
risk_tool_nameenum
instruments.yml#risk_tool_name(2)
  • YLS_CMI
  • SAVRY
Detention risk instrument used at decision (e.g., RAI variant, YLS/CMI).
risk_tool_versionstringβ€”Version string/number of the instrument.
risk_total_scorenumberβ€”Score recorded at release decision.
risk_cutpoint_set_keyenum
cutpoint_sets.yml#set_key(2)
  • default_vendor_set
  • local_policy_set_YYYYMMDD
Named threshold set used to interpret the score.
release_decision_datetimedatetimeβ€”When the release with conditions was ordered.
override_flagbooleanβ€”Decision or conditions deviated from guidance.
override_reason_codeenum
overrides.yml#reason(4)
  • safety_exception
  • capacity_constraint
  • policy_exception
  • supervisor_override
Rationale for override (policy/safety/capacity/etc.).
check_in_modality_codesarray<string>
contact_channels.yml#channel(4)
  • sms
  • voice
  • mail
  • portal
Allowed/required contact modalities (sms, voice, portal, in_person); semicolon-delimited in CSV.
check_in_cadence_per_weeknumberβ€”Required check-ins per week.
curfew_start_timetimeβ€”Daily curfew start (local time), if ordered.
curfew_end_timetimeβ€”Daily curfew end (local time), if ordered.
school_attendance_required_flagbooleanβ€”School attendance condition ordered.
program_start_datetimedatetimeβ€”Start date/time for any required program/services.
program_session_cadence_per_weeknumberβ€”Planned sessions/contacts per week (services/classes).
atd_assigned_flagbooleanβ€”True if an ATD was assigned under these conditions.
atd_type_codeenum
atd_types.yml#type(5)
  • evening_reporting
  • day_reporting
  • electronic_monitoring
  • shelter_respite
  • community_supervision
If assigned: evening_reporting, day_reporting, shelter_respite, electronic_monitoring, community_supervision.
atd_program_idstringβ€”Program identifier if specific program assigned.
monitoring_alert_grace_minutesintegerβ€”Configured grace period for alert/curfew windows at start of episode.
check_ins_scheduled_countintegerβ€”Number of scheduled check-ins in the episode window.
check_ins_completed_countintegerβ€”Number of completed check-ins.
missed_contact_countintegerβ€”Missed check-ins/contacts during the episode.
violation_event_count_new_lawintegerβ€”New-law violations during the episode.
violation_event_count_technicalintegerβ€”Technical violations (missed curfew, missed check-ins, etc.).
response_action_codesarray<string>
graduated_responses.yml#action(5)
  • contact_attempt
  • home_visit
  • step_up
  • violation_report
  • program_review
Graduated responses applied (contact_attempt, step_up, violation_report, etc.); semicolon-delimited in CSV.
next_hearing_datetimedatetimeβ€”Next scheduled hearing.
continuance_countintegerβ€”Number of continuances during the supervision window.
continuance_reason_codesarray<string>
continuance_reasons.yml#reason(13)
  • witness_unavailable
  • discovery_pending
  • counsel_conflict
  • court_calendar
  • youth_health
  • other_good_cause
  • counsel_request
  • discovery_delay
  • court_congestion
  • participant_availability
  • interpreter_needed
  • weather_emergency
  • other
Reasons for continuance(s); semicolon-delimited.
completion_status_codeenum
completion_statuses.yml#status(3)
  • successful
  • neutral_exit
  • failure
Episode closed as completed, neutral_exit, or failure/unsuccessful.
completion_datetimedatetimeβ€”Episode end timestamp.
unsuccessful_reason_codeenum
failure_reasons.yml#reason(3)
  • new_offense
  • withdrawal
  • noncompliance
If failure/unsuccessful, reason (new_offense, noncompliance, withdrawal).
case_resolution_codeenum
case_resolutions.yml#resolution(3)
  • diversion_completed
  • dismissal_decline
  • adjudication
Downstream resolution reached (diversion_completed, dismissal_decline, adjudication).
routed_to_next_node_codeenum
next_routes.yml#route(3)
  • prosecutorial_screening
  • petition
  • other
Where the case moved next (petition, adjudication, other).
Download CSVwhat_we_track.csv

Data & Methods

Indicators use release-based denominators and time-at-risk adjustments through adjudication or closure. Compliance is measured as the proportion of expected contacts met; violations are categorized per Technical Violations vs. New Offenses. When eligibility rules or ATD models change, we mark series breaks. For exposure and timeliness conventions, see Denominators & Exposure Time and Time Series & Seasonality. Equity checks compare entry and response rates by race/ethnicity and geography following Cross-Jurisdiction Comparability.

Related