Reentry case management software should do six things on one participant record: hold several concurrent service enrollments, record attended/absent/unmarked sessions with who delivered each one, track the milestones your program defines, store referral and partner details, generate partner updates from the record, and control who can see the data. COPS covers those for community reentry providers.
Community reentry programs coordinate education, counseling, employment readiness, support groups, and partner referrals on different schedules. The records behind that work answer the questions partners and supervisors ask every week: What is this person enrolled in? What was delivered? What is outstanding? This guide turns those questions into a feature checklist you can take to a demo.
Can one participant hold several services at once?
Yes, and that is the first feature to test. Each service needs its own enrollment, schedule, and attendance, all visible on one profile.
The problem
Generic tools treat a participant as one "case" with one calendar. When education, counseling, and a job workshop run in parallel, staff either duplicate records or lose which sessions belong to which service.
How COPS solves it
- Multi-program enrollments per participant, each with its own schedule.
- One client profile that shows every enrollment and its attendance.
- Custom fields for referral identifiers and locally defined milestones.
- Reports by one service across participants, or all services for one participant.
How should software separate referrals, starts, and completions?
Record each as a distinct fact. A referral is not a start, and an enrollment is not a completion. Status, attendance, and progress fields should make that obvious in reports.
The problem
When those stages blur, partner updates overstate what was delivered.
How COPS solves it
- Enrollment status plus three-state attendance (attended, absent, unmarked).
- Progress fields and comments for milestones your program defines.
- Document history so you can show what was generated and when.
How does reentry case management software help with parolee or probationer supervision?
It does not replace the supervising officer. It keeps the provider's side of the record: enrollments, attendance, notes, fees if any, and the letters or monthly updates the referral source asked for.
The problem
Providers get asked for status updates on short notice and rebuild them from email and spreadsheets.
How COPS solves it
- Case information fields for court, judge, attorney, and referral source, plus probation officer links.
- Automated alerts and reminders so absences and unmarked sessions get follow-up.
- Monthly reports with draft, finalize, PDF, and history.
- Merge-tag document templates for progress letters.
COPS records what happened. Supervising agencies make supervision decisions.
What should a partner or funder update include?
For a clear date range: services enrolled, sessions attended out of sessions scheduled, unmarked sessions still being checked, milestones reached, and a short staff note. Generate it from the record, review it, then save what you sent.
The problem
Hand-written updates vary by staff member, and programs often cannot show which version went to which partner.
How COPS solves it
- Monthly report workflow with history.
- Document templates with merge tags.
- Attendance exports when a partner wants its own format.
If a funder specifies an exact submission format, bring that specification to the demo and ask to see it produced.
What should you ask about risk scores and outcome claims?
Ask whether any score is a validated instrument, whether the product makes recommendations or only organizes records, and where outcome data comes from. Be skeptical of recidivism predictions built from attendance alone.
The problem
Marketing sometimes promises decision-making the software cannot honestly deliver.
How COPS solves it
- COPS tracks operational milestones you define. It does not predict recidivism, automate eligibility, or make release decisions.
- Progress comments and session notes keep context next to attendance.
How should reentry records be protected?
Encrypt at rest and in transit, use role-based staff access with an audit log, and require multi-factor login for any participant portal. Your organization still decides consent and disclosure.
- COPS runs on AWS with encryption at rest (AWS KMS) and in transit (TLS).
- Role-scoped staff access and a full staff audit log.
- Optional client portal with MFA for documents, profile updates, and payments.
Reentry case management software checklist
| Need | Ask the vendor |
|---|---|
| Several services | Can one participant hold multiple enrollments, each with its own schedule and attendance? |
| Referrals vs delivery | How are referrals, starts, and completions represented in reports? |
| Staff handoffs | Is the facilitator recorded on each session? |
| Follow-up | Are there automated alerts and reminders for absences and unmarked sessions? |
| Partner updates | Can you reproduce our monthly update from the record and keep history? |
| Claims | What exactly do any risk or outcome features do? |
| Security | Encryption at rest and in transit, role-based access, audit log, MFA portal? |
| Fees | If we charge fees: schedules, balances, online pay, receipts? If not, can fee UI stay out of the way? |
Where COPS fits
COPS (Court Ordered Program Supervisor) is web-based practice management for community providers. For reentry, it keeps case details, multi-program enrollments, attendance, staff assignments, session notes, progress fields, documents, and monthly reports on one record. See the reentry program software page. Related: homeless services software buyer's guide, how housing providers track court-ordered attendance, substance use program software vs. an EHR, housing and homeless services software, and the COPS platform overview.