Juvenile diversion keeps young people out of formal court processing in exchange for completing a set of community requirements: an education class, counseling sessions, restorative activities, community service, or a combination. The referring agency sets the requirements. Community providers deliver the services and report back. Most of the software marketed as "juvenile justice software" is built for the agency side: detention, intake decisions, and court case management. Community providers have a different job and need different tools.
This guide is for nonprofit and private providers who deliver diversion services. It answers one question: what should you ask before choosing juvenile diversion program software? Use the questions in a demo, then score each product with the checklist at the end.
First, be clear about whose system it is
A provider's system holds the provider's record of service delivery: who was referred, what they were enrolled in, what they attended, and what the provider reported. It is not the referring agency's case management system and it does not make decisions about a young person. Keeping that line clear protects youth, keeps your data collection proportionate, and makes vendor conversations faster, because you can rule out tools built for detention or court operations.
Questions about referrals and intake
- Can we record the referral source and the referral's identifiers on the youth's record? Look for structured fields for the referring agency, case or referral number, and the requirements listed in the referral, plus a place to store the referral document itself.
- Can we add our own intake fields? Every diversion program asks slightly different questions. Custom fields let you capture what your program actually needs without forcing a vendor's model on you.
- Can we avoid collecting what we don't need? Ask whether optional fields can be hidden or left out. Data minimization matters more with youth records than almost anywhere else.
Questions about enrollments and attendance
- Can one young person be enrolled in several programs at once? A diversion agreement might require an education class, four counseling sessions, and community service. Each should be its own enrollment with its own schedule and attendance, all on one profile.
- Does attendance have three states? Attended, absent, and not yet marked. A two-state system turns "nobody marked it" into "absent," which can make a young person look non-compliant when the real gap is paperwork.
- Can facilitators mark a whole group at once? Bulk roster marking saves time for group sessions.
- Are staff assigned to sessions? Knowing who delivered a session matters when a referring agency asks a question months later.
- Can we keep session notes with the session? Notes tied to a specific class or appointment are easier to review than a single running notes field.
Questions about milestones and completion
- How do we define milestones? Diversion requirements are local. Look for progress fields or custom fields you define, rather than a vendor's fixed scoring model.
- Does the product make recommendations about youth? For most community providers the right answer is no. Be cautious with tools that score young people or suggest outcomes; your staff and the referring agency make those decisions.
- Can we see who is close to completion? A saved report that lists remaining sessions or hours per participant helps staff plan the last weeks of an agreement.
Questions about reporting back
- Can we generate provider letters from templates? Progress and completion letters built from merge-tag templates pull names, dates, and attendance from the record, so staff are not retyping them.
- Is there a history of what we sent? A generated-document history answers "which letter went to the agency, and when?"
- Can we export attendance? CSV, Excel, or PDF exports are useful when an agency asks for a summary in its own format.
- Who decides what gets shared? Your organization does. Software can produce a document; it does not authorize disclosure. Confirm the lawful recipients and the content of each update before you send it.
Questions about families, access, and security
- Who can log in, and to what? Ask exactly what a client portal provides and whether separate guardian or family accounts exist. Do not assume guardian access is included; confirm the access model before creating any accounts for youth or families.
- Are staff permissions role-based, and is there an audit log? Youth records deserve a clear record of who viewed or changed what.
- Where is data hosted and is it encrypted? Ask about encryption at rest and in transit, and who at the vendor can access your data.
A quick scorecard
| Need | What "meets" looks like |
|---|---|
| Referral record | Referral source, identifiers, requirements, and the referral document on the youth's profile |
| Proportionate intake | Custom fields you choose; nothing collected by default that you don't need |
| Multiple services | Separate enrollments with their own schedules and attendance on one profile |
| Attendance | Three-state, bulk roster marking, staff assignment, session notes |
| Milestones | Fields you define; no automated scoring of youth |
| Reporting back | Template letters, document history, attendance exports |
| Access and security | Clear portal scope, role-based access, audit log, encryption |
Run the demo with a synthetic case
Never send real youth records to a vendor for a demo. Instead, create one synthetic referral with three requirements, enroll the made-up participant in each, mark a few weeks of attendance including one absence and one unmarked session, and produce a progress letter. If the product cannot do that cleanly in a trial, it will not get easier with a full caseload.
Where COPS fits
COPS (Court Ordered Program Supervisor) is web-based program administration software for community providers, including juvenile diversion and intervention programs. Staff record referral source and case details, add custom intake fields, and enroll a young person in several programs, each with its own schedule, staff assignments, three-state attendance, and session notes. Progress fields and comments track the milestones your program defines. Merge-tag templates generate provider letters with a full document history, and attendance exports to CSV, Excel, or PDF. COPS runs on AWS with encryption at rest and in transit, role-scoped access, and a full staff audit log. It is not a detention or court case management system.
See how it fits community youth programs on our juvenile justice software page, or explore the full COPS software platform. If your diversion agreements include parenting education for families, the parenting class software guide covers that side.