COPS is juvenile justice program software for community-based education, counseling, and intervention providers. Staff organize youth referrals, program enrollments, session attendance, notes, and progress documents on one participant record. The focus is delivery of community services and provider reporting, not detention operations, judicial decisions, or a replacement for a court case management system.
A youth referral can involve several services and several adults, but each service still needs a clear enrollment and attendance record. Start by defining the program requirements, the staff responsible for reviewing progress, and which information may be shared. COPS connects the operational records; your organization retains responsibility for consent, safeguarding, and decisions about disclosure. The same records support juvenile treatment and counseling programs, whether sessions are delivered in groups or one-on-one.
A youth is referred to several community services with different schedules.
Create separate enrollments for education, counseling, and other community programs on the same client profile. Each enrollment has its own schedule and attendance. Staff can use custom fields for referral identifiers and locally defined milestones, rather than treating every scheduled activity as a completed requirement. Review the relationship between your referral paperwork and these fields during the demo.
Attendance records need context before a progress update is issued.
Use recurring or one-off scheduling, staff assignments, and session notes to connect an activity with the people who delivered it. Mark attendance as attended, absent, or unmarked and review incomplete rosters before preparing a summary. An absence is an operational fact to review with staff; the software does not decide what response is appropriate for a young person.
Referral documents and provider updates are scattered across folders.
Store program documents with the participant record and use merge-tag templates for provider letters. Generated-document history helps staff identify which version was produced and when. Bring an anonymized referral and sample update so the demo can distinguish required data from unnecessary sensitive detail, especially where family information appears alongside the youth record.
Managers cannot see which program records still need a staff review.
Custom fields, progress comments, attendance exports, and saved custom reports provide a practical starting point for staff review. Choose milestone definitions that reflect your actual service delivery and verify the report output with a sample caseload. These are configurable operational records, not validated youth risk assessments or automated recommendations about placement, sanctions, or release.
Compare your options
Compare program administration workflows.
Provider workflow
Separate spreadsheets
Other practice software
COPS
A youth is referred to several community services with different schedules.
Reconcile source files and record ownership manually
Check support for your specific provider workflow
Create separate enrollments for education, counseling, and other community programs on the same client profile.
Attendance records need context before a progress update is issued.
Reconcile source files and record ownership manually
Check support for your specific provider workflow
Use recurring or one-off scheduling, staff assignments, and session notes to connect an activity with the people who delivered it.
Referral documents and provider updates are scattered across folders.
Reconcile source files and record ownership manually
Check support for your specific provider workflow
Store program documents with the participant record and use merge-tag templates for provider letters.
Managers cannot see which program records still need a staff review.
Reconcile source files and record ownership manually
Check support for your specific provider workflow
Custom fields, progress comments, attendance exports, and saved custom reports provide a practical starting point for staff review.
Data security
COPS production runs on dedicated AWS infrastructure with KMS encryption at rest for the database and document storage, TLS encryption in transit, and a full audit log of staff activity. COPS is a HIPAA-track platform: HIPAA-capable infrastructure is in place, and production HIPAA service requires executed Business Associate Agreements and HIPAA configuration before any protected health information is stored. Tell us about your compliance requirements during your demo.
Questions and answers
Frequently asked questions
Is COPS a juvenile detention management system?
No. This page describes community program administration: participant records, enrollments, schedules, attendance, documents, and reporting. It does not claim detention bed management, custody tracking, incident response, or judicial case management. If those functions are essential, identify them separately rather than assuming that a community provider platform includes them.
Can one youth attend several programs?
Yes. A client can have multiple program enrollments with separate schedules and attendance. This helps providers distinguish a counseling appointment from an education session. Your staff should decide how completed sessions relate to referral requirements and review the record before issuing any completion statement.
Does the portal provide guardian or family access?
The documented portal is a client portal for documents, profile updates, and payments. Dedicated guardian accounts, delegated consent, and family access workflows are not established by this page. Bring your requirements to the demo and confirm the appropriate access model before creating accounts or uploading youth information.
Can we prepare updates for a referring agency?
Document templates, monthly reports, and court/attorney reports support provider reporting from client data. Show the team your required headings and an anonymized example. Your organization must determine the lawful recipients, the information to include, and any approval process; generating a document does not authorize disclosure.
What should a juvenile program bring to the demo?
Bring an anonymized intake packet, a weekly schedule, milestone definitions, and one progress update. Explain who enters attendance and who reviews the final document. Do not send real youth records for a demonstration; synthetic examples can show whether the enrollment-to-report workflow fits your program.
See your juvenile justice program workflow in COPS.
COPS also serves drug courts, mental health courts, batterer intervention programs, private probation, parenting classes, and DUI schools — see all court-ordered program software.