EDORA Learn — Pipelines
Restorative Justice & Victim Engagement (Accountability Paths)
Pipeline 04E
Transparency note: participation is voluntary and often small-n; we pool across quarters and mark series breaks when eligibility or facilitation models change.
Overview
Restorative justice (RJ) processes—such as victim–offender conferencing, community conferences, or circles—provide structured opportunities for accountability and repair. Programs can occur pre-petition (as diversion) or post-adjudication (as a condition). This page outlines where RJ fits in the pipeline, what is measurable, and how victim services interact with restitution and agreement monitoring.
What We Track
Eligibility & Referral
- Offense types included / excluded (statutory and local policy)
- Referral point recorded
- Intake
- Prosecutor
- Court (pre/post-adjudication)
- Screening criteria applied (risk, readiness, voluntariness)
Preparation & Consent
- Informed participation documented (youth & victim)
- Facilitator assigned; conflict check completed
- Safety planning steps recorded (location, supports, de-escalation)
Conference & Outcomes
- Conference occurred (Y/N); date & duration
- Agreement terms captured
- Apology / letter
- Service / repair activities
- Restitution (amount, plan)
- Target timelines & responsible parties set
Restitution & Services
- Payment plan or in-kind repair defined; schedule recorded
- Connections to victim services (advocacy, counseling) made
Completion & Follow-up
- Proportion completed on time; partial completions noted
- Returns to formal processing tracked (reason codes)
- Short re-referral window (6–12 months) monitored
Typical Flow
- Referral to RJ program based on eligibility & consent
- Confirm voluntariness and readiness; assign facilitator
- Preparation meetings with participants
- Set ground rules; develop safety plan; schedule conference
- Conference facilitated; draft written agreement
- Specify timelines, responsibilities, and supports
- Implementation of agreement terms (restitution, service, repair)
- Monitor progress; address barriers; adjust plan with consent
- Closure upon completion or return to formal processing if not completed
- Record outcomes; set short follow-up to check for new referrals
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 or facilitator associated to this RJ event. | |
occurred_datetime | datetime | ✅ | — | Timestamp this RJ event (referral/prep/conference/agreement/closure) was recorded. |
jurisdiction_code | string | ✅ | — | County/parish/circuit or standardized local code. |
legal_case_id | string | — | Case/docket identifier. | |
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 (policy/vendor change). | |
rj_event_action_code | enum | ✅ | rj_event_actions.yml#action(7)
| referral, screening, preparation, conference, agreement_update, completion, return_to_formal |
referral_point_code | enum | referral_points.yml#point(4)
| intake, prosecutor, court_pre_adjudication, court_post_adjudication | |
offense_eligibility_code | enum | rj_offense_eligibility.yml#eligibility(3)
| included, excluded, discretionary | |
screening_criteria_codes | array<string> | rj_screening_criteria.yml#criterion(6)
| Criteria applied (risk, readiness, voluntariness, etc.); semicolon-delimited. | |
screening_result_code | enum | rj_screening_results.yml#result(3)
| eligible, ineligible, pending | |
youth_consent_status_code | enum | consent_status.yml#status(5)
| Consent status for youth participation. | |
victim_consent_status_code | enum | consent_status.yml#status(5)
| Consent status for victim participation. | |
consent_datetime | datetime | — | Timestamp consent statuses were captured. | |
facilitator_id | string | — | Facilitator person/provider identifier. | |
facilitator_conflict_check_code | enum | conflict_check.yml#status(3)
| passed, conflict_found, pending | |
safety_plan_element_codes | array<string> | safety_plan_elements.yml#element(6)
| Location, supports, de-escalation steps; semicolon-delimited. | |
conference_occurred_flag | boolean | — | Conference occurred. | |
conference_datetime | datetime | — | When the conference took place. | |
conference_duration_minutes | integer | — | Duration of the conference in minutes. | |
agreement_term_codes | array<string> | rj_agreement_terms.yml#term(6)
| Terms included (apology_letter, service_repair, restitution, etc.); semicolon-delimited. | |
target_due_date | date | — | Date by which terms should be completed. | |
responsible_party_role_code | enum | roles.yml#actor_role(7)
| Role primarily responsible for carrying out terms. | |
restitution_amount_ordered | number | — | Restitution amount specified (monetary units local). | |
restitution_plan_type_code | enum | restitution_plan_types.yml#type(4)
| payment_plan, in_kind_repair, mixed, none | |
payment_frequency_unit_code | enum | payment_frequency_units.yml#unit(4)
| weekly, biweekly, monthly, one_time | |
victim_service_type_codes | array<string> | victim_service_types.yml#type(6)
| Advocacy, counseling, safety planning; semicolon-delimited. | |
interim_support_code | enum | interim_supports.yml#support(3)
| Bridge supports if language/availability mismatches (reuse shared codeset). | |
completion_status_code | enum | rj_completion_statuses.yml#status(4)
| completed_on_time, completed_late, partial, not_completed | |
completion_datetime | datetime | — | When completion/closure was recorded. | |
return_to_formal_processing_flag | boolean | — | Returned to formal processing. | |
return_reason_code | enum | rj_return_reasons.yml#reason(5)
| Reason for return (noncompliance, new_offense, withdrawal, other). | |
follow_up_review_datetime | datetime | — | Short re-referral window review (e.g., 6–12 months). | |
Download CSVwhat_we_track.csv |
Data & Methods
Denominators depend on the referral point (e.g., eligible referrals for diversion; adjudicated cases for post-disposition RJ). Completion is measured as agreement-fulfilled within a defined window (e.g., 90/180 days). Restitution tracking includes amount ordered, amount paid, and proportion paid by target date. Where programs shift models or eligibility, we mark series breaks. Small-n suppression follows Suppression & Small-n, and consistency checks draw on Metadata & Documentation.