Private probation providers and community supervision programs run on records. Who supervises this person, what the court ordered, whether they checked in, what they still owe, and what the court was told last month. When those answers are spread across a legacy database, a fee spreadsheet, and paper sign-in sheets, every court report means hunting through all three.
This guide is for owners, office managers, and supervisors shopping for probation case management software. It gives you twelve questions to put to any vendor, what a good answer sounds like, and a short trial plan so you can judge fit with your own workflow rather than a scripted demo.
First, define the job
"Probation software" covers very different products. Some are built for state agencies and include risk instruments, warrants, and integrations with statewide court systems. Others are built for private and contracted providers who need to manage a caseload, collect supervision fees, and report to the referring court. Decide which job you are hiring software for before you compare features. A product that is excellent at one is often awkward at the other.
Whatever you choose, the software records and organizes. Officers and courts still make supervision decisions.
Caseload and case information
1. Can each client carry an assigned officer, and can I see a caseload by officer?
Look for an officer field tied to a staff directory, not a free-text name, and a way to list everyone assigned to a given officer. Ask how reassignment is recorded so a handoff does not lose history.
2. Where do court, judge, attorney, and referral source live?
These should be structured fields on the client record, because they drive court reports and referral tracking. If they live in notes, you will retype them into every letter.
3. Can one client be enrolled in several requirements at once?
Supervision often runs alongside classes, counseling, or community service. Ask the vendor to enroll a test client in two programs and show attendance for each without creating a duplicate client.
Conditions, check-ins, and attendance
4. How are conditions recorded?
Many offices track conditions such as community service hours, curfew notes, or treatment referrals in configurable fields. Ask whether you can add your own fields and report on them. Keep in mind that a recorded field is documentation. It is not automatic proof that a condition was met.
5. How do clients check in, and what evidence is kept?
Options range from staff marking a calendar to self check-in at an office kiosk. Ask what is captured: a signature, a timestamp, the staff member, a note. Check whether attendance has three states (attended, absent, not yet marked). A two-state system turns "nobody marked it" into "absent".
6. What happens after a missed check-in?
Be precise here. Ask whether the system sends automated alerts and reminders, what triggers them, and who receives them. COPS includes automated alerts and reminders, and its attendance reports also show absences and unmarked sessions so staff can follow up. Ask for a demo of the alerts with your own schedule.
Fees and payments
7. Can you model our fee schedule?
Supervision fees, program fees, and one-time charges should post to a balance with a transaction history. Ask the vendor to set up one of your real fee schedules during the demo.
8. Can clients pay online, and how do payments reconcile?
Ask which payment methods are available to staff and which to clients themselves, whether receipts are printable, and whether payment reports match your deposits. Self-service card payments through a client portal can take a large share of routine payment calls off the front desk.
Court reporting
9. Can you reproduce the report our court reads today?
Bring a de-identified copy of your monthly or progress report and ask the vendor to build it. Good signs are template-based documents that pull case details from the record, a draft-then-finalize step, PDF output, and a history of every report sent.
10. Can I save a custom report and re-run it each month?
Every office has a question the standard reports do not answer. Saved custom reports with run history keep you from rebuilding filters each month.
Security and setup
11. Where is the data, and who can see it?
Ask about hosting, encryption at rest and in transit, role-based staff permissions, a full audit log of staff activity, and multi-factor login for any client portal. Then check the answers against your contracts and your state's rules.
12. How long until we are running, and who does the setup?
Web-based software removes installation. Ask who configures fields, fee schedules, and report templates, and how existing records will be migrated. If you have years of history, ask how the migration is reconciled. Counts of clients, attendance, and payments before and after are a reasonable expectation.
Scorecard
| Area | "Meets" looks like |
|---|---|
| Caseload | Officer assignment from a staff directory, caseload lists, reassignment history |
| Case information | Structured court, judge, attorney, referral source |
| Conditions | Custom fields you can report on; multiple enrollments per client |
| Check-ins | Three-state attendance, kiosk or self check-in with signature and timestamp |
| Fees | Fee schedules, balances, online payment, receipts, reconciling reports |
| Court reports | Your real report reproduced; PDF history; saved custom reports |
| Security | Encryption, role-based access, audit log, portal MFA |
| Setup | Web-based; clear migration and reconciliation plan |
A one-week trial plan
- Day 1: enter your fee schedule and one officer's caseload of de-identified test clients.
- Days 2–3: record check-ins for a week, including one absence and one unmarked session, and see how each shows up in reports.
- Day 4: take a test payment and print a receipt.
- Day 5: produce your monthly court report and compare it line by line with the one you send today.
Where COPS fits
COPS (Court Ordered Program Supervisor) is web-based software for private probation offices and other court-ordered program providers. Each client can carry a probation profile with an assigned officer from the officer directory, along with court, judge, attorney, and referral source, several program enrollments, three-state attendance, kiosk check-in with signature capture, fees and balances, and documents. Teams run 11 built-in report types and saved custom reports, produce monthly reports as PDFs with history, and let clients pay by card through a portal with multi-factor login. COPS runs on AWS with encryption at rest and in transit and a full staff audit log. It supports administrative caseload tracking. It is not a jail management system and does not replace an officer's judgment.
See the workflow in detail on our private probation software page, or compare the whole COPS platform. If your clients also attend treatment court, the drug court software checklist covers that side.