Every mental health court runs on the same weekly rhythm: the team meets in staffing, reviews each participant on the docket, and agrees on what the judge will say from the bench. That conversation is only as good as the information in front of the team. When the coordinator spends the two days before staffing chasing attendance from three providers and rebuilding a spreadsheet, the team ends up discussing incomplete facts.
This guide answers one question for coordinators and treatment providers: what should a mental health court staffing report contain, and how do you produce it without starting from scratch every week? It ends with a checklist you can use to test any mental health court software you are evaluating.
Why the staffing report matters more than the hearing
By the time a participant stands in front of the judge, most decisions have been made in staffing. The judge, coordinator, prosecutor, defense counsel, treatment providers, and supervision staff each bring a piece of the picture. A good staffing report puts those pieces on one page per participant, in the same order every week, so the team can spend its time on judgment instead of on reconciling numbers.
Two principles keep the report useful. First, it should describe what happened since the last review, not repeat the whole case history. Second, it should separate facts (a session was attended, a payment was made) from provider observations, so nobody mistakes one for the other.
The eight things a staffing report should show
1. Who the participant is and where they are in the program
Name, case number, the court and judge, defense attorney, referral source, and the current court phase. Phase is the context for everything else: missing a session means something different in Phase I than in the final phase. If phase lives only in a coordinator's memory or a free-text note, the team cannot filter or count it.
2. Attendance since the last review
For each program the participant is enrolled in, show sessions scheduled, attended, absent, and not yet marked. That last category matters. A blank attendance cell is not an absence; it is a missing record. Reports that treat unmarked as absent are unfair to participants and misleading for the team, so ask the provider to close out the roster before staffing.
3. Provider progress in the provider's own words
Treatment providers usually supply a short progress note: engagement, participation, and anything the team needs to know. Keep it short, keep it attributed to the provider, and include only what your consents allow the team to see. Your court's policies and the participant's releases decide what is shared; the software only holds and presents what staff enter.
4. Test results, if your court orders testing
If the court orders testing, the team needs the results since the last review, with dates. Record them on the participant's profile rather than in a separate log so they sit next to attendance and phase. Be clear about scope: recording results is different from scheduling randomized tests or receiving lab results electronically, and the report should show exactly what was recorded.
5. Other conditions and milestones
Community service hours, classes, employment or education goals, and any other conditions the court has set. Many courts track these with locally defined milestones. Whatever you track, record it in structured fields so you can report on it, not as a paragraph that has to be reread every week.
6. Fees and balance
If participants pay program fees, a one-line balance and the last payment date help the team avoid surprises at graduation. Keep fees factual and separate from treatment progress.
7. What changed since last time
A short "since last staffing" line: a phase change, a new enrollment, a missed appointment, a document received. This is often the most useful line on the page and the hardest to produce by hand.
8. The team's last decision
Record what the team decided at the previous staffing (for example, an incentive, a response, or a change in requirements) so this week's conversation starts where last week's ended. The decision belongs to the team and the judge; the record just keeps it in one place.
A pre-staffing checklist
Use this checklist the day before staffing, or use it to score software during a demo. Mark each line "yes," "partial," or "no."
| Before staffing, can you… | What "yes" looks like |
|---|---|
| List everyone on this week's docket with their current phase? | Phase is a structured field you can filter and report on |
| Show attendance since the last review for every enrollment? | Attended, absent, and unmarked counted separately per program |
| Find rosters that still have unmarked sessions? | A report or view that surfaces unmarked sessions before the meeting |
| Include provider progress without retyping it? | Session notes and progress comments pulled into the report |
| Show test results recorded since the last review? | Results on the participant profile, dated |
| Show conditions and milestones? | Custom fields or progress fields, not free text |
| Show balance and last payment? | Fee balance and transaction history on the same record |
| Produce the same report next week in minutes? | A saved report definition you re-run, with PDF output and history |
How to cut report prep from days to minutes
- Agree on one template. Pick the eight sections above (or your court's version) and stop accepting provider updates in different formats.
- Put every enrollment on one participant record. When treatment, classes, and community service are separate enrollments on the same profile, attendance rolls up without copy and paste.
- Close rosters before the deadline. Ask providers to mark attendance by a set time before staffing, and use reminders so unmarked sessions get attention early.
- Save the report, don't rebuild it. A saved report definition that you re-run each week is the difference between a two-day scramble and a ten-minute check.
- Keep a history. Save each finalized report as a PDF with a history, so "what did the team see in March?" has an answer.
What software should not do
Staffing is a human process. Software should not score participants, recommend sanctions, or decide whether someone moves to the next phase. Be wary of any product that promises to. The useful job is narrower: put accurate, current, consistently formatted information in front of the team so its time goes to the decisions only it can make.
Where COPS fits
COPS (Court Ordered Program Supervisor) is web-based practice management software for mental health court programs and the providers who serve them. Each participant record carries case information (court, judge, attorney, referral source), court phase, DSM-coded profile fields, multiple program enrollments with their own schedules and three-state attendance, session notes, progress fields and comments, test results when the drug-testing module is enabled, documents, and fees. Monthly reports move from draft to final PDF with a history, court/attorney reports pull case details from the record, and saved custom reports re-run each week. COPS also includes automated alerts and reminders, so unmarked sessions get attention before staffing.
See how it maps to treatment court workflows on our mental health court software page, compare the wider COPS software platform, or read the drug court software buyer's checklist if your court runs both dockets.