Intensive Supervision & Graduated Responses (High-Need Youth)

Pipeline 05B

Transparency note: small-n cohorts and midyear updates to response grids can affect comparability; we pool across quarters and document version changes in metadata.

Overview

Intensive supervision programs (ISP) serve youth with higher assessed risk or complex needs through increased contact frequency, structured service plans, and quick feedback on compliance. Graduated response systems—balancing incentives and sanctions—ensure that responses remain proportional and data-driven. This page details observable elements in ISP design, delivery, and evaluation.

What We Track

Eligibility & Caseload

Assignment criteria documented (risk tier, criminogenic needs, court order)
Average caseload per officer recorded; weighted caseload noted for complexity
Supervision levels defined with entry/exit thresholds

Contact Standards

Minimum vs. actual contacts per week/month by modality
- Field
- Office
- Virtual (phone/video/SMS)
Ratio of contacts to identified needs (are we matching intensity to risk?)

Graduated Responses

Formalized grid linking violations & incentives to scaled consequences
Response timeliness (hours/days from event → action) tracked
Overrides documented with rationale & approver; proportionality checks

Service Dosage

Frequency & duration of interventions vs. case-plan expectations (delivered ÷ planned)
Wait times and capacity constraints logged for high-intensity services

Performance & Step-Down

Time in track until step-down eligibility; criteria met/not met
Completion/early termination criteria and reasons for extensions
Reentry outcomes at 90/180 days where available (school, employment, petitions)

Typical Flow

Referral from probation or court to intensive supervision
- Confirm eligibility thresholds and special conditions
Initial plan with enhanced contacts & service requirements
- Set weekly contact cadence; define high-intensity services and start dates
Weekly monitoring of contacts, engagement, and behavioral compliance
- Track achieved vs. required; log barriers and supports added
Graduated responses applied proportionally for incentives or violations
- Record timeliness and any overrides to the grid
Step-down review after sustained compliance or program completion
- Evaluate criteria; authorize step-down or continue with adjustments

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) intake detention adjudication disposition supervision commitment_and_placement reentry closure	One of the 8 canonical stages.
pipeline_place_key	enum	✅	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_id	string	✅	—	Salted/hashed or state UID. No plaintext PII.
staff_id	string		—	Supervising officer / primary case manager.
occurred_datetime	datetime	✅	—	Episode open/authorization timestamp.
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) definition_change vendor_change coverage_change policy_change	Reason for break when flagged.
eligibility_criteria_code	enum		eligibility_criteria.yml#criterion(5) risk_tier criminogenic_need court_order administrative other	Assignment basis (risk_tier, criminogenic_need, court_order, other).
supervision_level_code	enum	✅	supervision_levels.yml#level(4) minimal standard enhanced intensive	Intensive track level at episode start.
weighted_caseload_index	number		—	Officer’s weighted caseload index at episode start (unitless scalar).
officer_avg_caseload_count	integer		—	Officer average caseload count (unweighted) at episode start.
required_contacts_per_week	number		—	Required total contacts per week per policy.
required_contact_channel_codes	array<string>		contact_channels.yml#channel(4) sms voice mail portal	Modalities required (in_person, phone, sms, video); semicolon-delimited.
contacts_field_count	integer		—	Field contacts completed during episode.
contacts_office_count	integer		—	Office contacts completed during episode.
contacts_virtual_count	integer		—	Virtual (phone/video/SMS) contacts completed during episode.
contacts_total_count	integer		—	Total completed contacts during episode.
planned_high_intensity_service_codes	array<string>		high_intensity_services.yml#service(6) multisystemic_therapy functional_family_therapy day_reporting electronic_monitoring_plus cognitive_behavioral_group other_service	Required high-intensity services (e.g., MST, FFT, day_reporting); semicolon-delimited.
planned_dosage_amount	number		—	Planned cumulative dosage for high-intensity services.
dosage_unit_code	enum		dosage_units.yml#unit(4) sessions_per_week hours_per_week total_hours total_weeks	Unit for dosage amounts (hours, days, sessions, credits).
delivered_dosage_amount	number		—	Delivered cumulative dosage aligned to dosage_unit_code.
service_waitlist_flag	boolean		—	One or more high-intensity services waitlisted.
capacity_status_code	enum		capacity_constraints.yml#status⚠️ using capacity_constraints.yml#constraint(6) court_congestion judge_unavailable courtroom_unavailable staffing_shortage technology_failure other	Capacity condition for key service at referral (open, waitlist, closed).
response_grid_key	enum		response_grids.yml#grid(2) standard_grid_v1 enhanced_grid_v1	Policy grid identifier used for proportionality.
violations_count	integer		—	Count of recorded violations during episode.
incentives_count	integer		—	Count of recorded incentives during episode.
responses_applied_count	integer		—	Total graduated responses applied (any type).
last_event_datetime	datetime		—	Timestamp of last qualifying violation/incentive event.
last_response_applied_datetime	datetime		—	Timestamp of last response applied to that event.
override_flag	boolean		—	A policy override to the grid occurred during episode.
override_reason_code	enum		overrides.yml#reason(4) safety_exception capacity_constraint policy_exception supervisor_override	Rationale for override (clinical_judgment, safety_exception, etc.).
override_approver_staff_id	string		—	Approver staff identifier for override.
step_down_eligibility_date	date		—	Date the youth first met eligibility criteria to step down.
step_decision_code	enum		step_decisions.yml#decision(7) approved_step_down continue_current continue_intensive step_up transfer release_to_aftercare administrative_closure	approved_step_down, continue_intensive, step_up, administrative_closure.
step_decision_datetime	datetime		—	Timestamp of step decision.
extension_reason_code	enum		extension_reasons.yml#reason(6) criteria_not_met ongoing_treatment safety_concern pending_hearings staffing_capacity other	Reason for extending intensive supervision when criteria not met.
completion_status_code	enum		completion_statuses.yml#status(3) successful neutral_exit failure	completed, neutral_exit, or unsuccessful.
unsuccessful_reason_code	enum		failure_reasons.yml#reason(3) new_offense withdrawal noncompliance	If unsuccessful, primary reason.
completion_datetime	datetime		—	Episode end timestamp.
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

ISP metrics use supervision-based denominators. Contact compliance is measured as completed ÷ expected contacts per month; dosage completion as completed service hours ÷ planned hours. Graduated response fidelity is monitored through audit logs comparing applied vs. expected tiers. Series breaks are annotated when response grids or contact policies change. Equity analyses use rate ratios by race, gender, and geography following Cross-Jurisdiction Comparability. For small-n cells, suppression rules from Suppression & Small-n apply. Exposure adjustment conventions follow Denominators & Exposure Time, and data validation standards align with Data Quality & Validation.

EDORA • Learn