Juvenile justice & diversion
Records restricted by default. Young people seen in full.
Diversion providers carry a double obligation: protect each young person's record, and document participation reliably enough for a court to depend on. BridgeCase gives diversion and community-accountability programs restricted records with tight role-based access, dependable attendance and requirement tracking, and reporting that answers referral sources without exposing anyone's story.
What gets in the way
The most sensitive records in youth services, on the least protective tools.
A young person's diversion referral deserves better handling than a shared spreadsheet — and the stakes of getting documentation wrong are higher here than anywhere else in youth work.
Referral records one forwarded link from overexposure
A diversion roster in a shared spreadsheet has no access boundaries. Anyone with the link sees every name, every referral source, every note — and no one can say who looked.
Attendance documentation a court will rely on
When a status hearing asks whether a young person met their program requirements, the answer has to come from complete, dated records — not a coordinator's memory of who showed up in March.
Reporting that overexposes by default
Emailing a full case file when the referral source only needs enrollment status and completion is an overexposure problem disguised as being helpful. The report should carry exactly what the agreement requires — nothing more.
The rest of the work lives somewhere else
Diversion done well includes mentoring, family support, and school and job goals. When those live in separate tools, staff see requirements instead of the whole young person.
How the work runs
How diversion providers run the work.
Restricted referral intake
Log referrals from courts, probation, schools, or community boards with restriction applied at intake — visible only to assigned staff from the first record.
Attendance & program requirements
Session attendance, service hours, and milestone completion tracked against each young person's specific requirements, with dates and staff attribution.
Mentoring within diversion
Mentor screening, matching decisions made by your staff, and session logs connected to the same restricted record — not a separate system.
Family support & referrals
Household needs identified at intake, closed-loop referrals to community services, and follow-through visible to the assigned team.
Education & employment goals
School engagement, credentials, internships, and job placements recorded as strengths-based outcomes — the progress that outlasts the referral.
Privacy-protecting reporting
Completion and outcome reporting for courts, counties, and funders built from aggregate counts — never from forwarded case files.
The modules you'll use
The modules diversion teams rely on.
The recommended starting point is restricted intake and requirement tracking — then connect mentoring and family support to the same record.
Security & Governance
Record-level restriction, role-based access, and audit history — the foundation everything else sits on.
Programs, Intake & Enrollment
Referral intake, program requirements, cohort scheduling, and completion tracking.
Participant & Household 360
One longitudinal record per young person, so assigned staff see the whole picture — within their permissions.
Mentoring
Screening, matching, and session tracking for mentoring delivered inside diversion programs.
Family Resources & Referrals
Closed-loop referrals connecting families to community services beyond the program requirement.
Outcomes & Reporting
De-identified reporting for referral sources, counties, and funders.
Built for your requirements
Built for the obligations diversion providers actually carry.
- Record-level restriction with role-based access and least-privilege defaults — assignment, not org membership, grants visibility
- Audit history covering views, changes, and exports of restricted records, including administrator access
- Configurable statuses and terminology, so the system speaks your program's strengths-based language
- Referral-source reporting limited to defined fields — enrollment, attendance against requirements, completion
- Data ownership with export and retention workflows that follow your policies at program completion
- Security documentation shared during evaluation, so your agency can validate against its own requirements
- Designed to run alongside county and court systems of record, not to replace them
- Accessibility as a requirement, not an afterthought — the platform targets WCAG conformance
Evidence and reporting
Answer the court. Protect the record.
Because attendance, mentoring, and family support all record into one restricted system, providers can report completion and outcomes with confidence — in aggregate for counties and funders, and field-by-field for referral sources, exactly as agreements define.
- Referrals received and enrolled, by referral source, program, and month
- Completion rates by cohort, requirement type, and program length
- Attendance and service hours logged against individual program requirements
- Mentoring matches made and session consistency across enrolled young people
- Education and employment outcomes at exit, reported in aggregate
- Family referrals initiated and completed, by service category
Frequently asked questions
How granular is record restriction?
Restriction operates at the record level. A young person's diversion record is visible only to the staff assigned to it — not to everyone in your organization, and not to staff running your other programs unless explicitly granted. Supervisory visibility is configurable, and every access, including an administrator's, is written to the audit history.
How do we report to courts and referral sources without overexposing young people?
Referral-source reporting is limited to defined fields — typically enrollment status, attendance against requirements, and completion — matched to what your agreements actually require. Case notes, family circumstances, and mentoring details stay inside the restricted record. Reporting to counties and funders is aggregate and de-identified.
What happens to a young person's record when they complete the program?
That follows your policy, not ours. Retention obligations for diversion records vary by state and by county contract, so implementation maps your requirements to the platform's workflows: tighten restriction further at completion, retain for a defined reporting window, export, or delete on schedule. Your organization owns its data throughout.
Can BridgeCase work alongside the county's case-management system?
Yes, and it should. Courts and probation departments keep their own official systems of record; BridgeCase manages the provider's side — intake, attendance, mentoring, family support, and reporting. Data leaves the platform only through the exports and reports your agreements define.
Is BridgeCase CJIS-certified or HIPAA-certified?
We don't make certification claims, and we'd encourage skepticism toward vendors in this space who do so loosely. What we do: share our security documentation — architecture, access control, restriction model, and audit capabilities — during evaluation, so your agency and its county partners can validate the platform against their own requirements before any record is entered.
See what one connected system could look like for your organization.
We will tailor the conversation to your programs, users, reporting needs, and current tools.
No youth or family data is required to request a demo.