The Court, Legal, and RMS Case Management surfaces handle the outside-the-walls part of the inmate’s journey — charges, hearings, holds, dispositions — plus the broader RMS (Records Management System) case load and the underlying Arrests & Citations log.
What it does
- Tracks each open charge with its court, prosecutor, defense counsel, next hearing, and current status.
- Captures holds (detainers, warrants, court orders) so the release surface can warn before a premature release.
- Provides RMS Case Management for non-incarcerated case work (post-release supervision, victim services) so the same system covers both sides of the records line.
- Records arrests and citations into the same ledger that feeds NIBRS reporting and the Operations Threat Assessment queue.
How it works
Court & Legal is read- and write-heavy; charges are edited by booking staff, holds by court liaisons, dispositions by clerks. RMS Case Management shares the same case row but adds non-incarcerated workflows. Arrests & Citations is the upstream log that feeds the rest.
Data captured
- Charges with statute code, severity, court, status, disposition
- Hearings with court, time, type, outcome
- Holds with origin agency, expiration, contact
- Arrests and citations with officer, time, location, statute
Compliance & retention
Charges, holds, and dispositions are NIBRS-reportable. Retention follows court-records rules and the facility’s records schedule. Threat Assessment cases that pivot on a court event are linked to the case id and inherit the longer retention window.
We’ve been struggling to get our NIBRS submissions accurate ever since we migrated to a new platform last year — does your system handle the mapping of local charge codes to NIBRS offense codes automatically, or does that require manual configuration on our end? That’s been our biggest headache. Really glad to see court holds and hearing schedules integrated in the same module instead of juggling spreadsheets.
We’ve been struggling with keeping our RMS data properly linked to active holds when cases get continued multiple times — does your system automatically flag those discrepancies or does it require manual reconciliation on the booking side? That’s been our biggest headache during NIBRS transition.
We’ve been struggling with syncing our RMS arrest records directly to court hearing schedules without double-entry — does your system handle that integration out of the box or does it require custom mapping? Our current workflow is a nightmare when charges get amended last minute before arraignment.
We switched to a unified system about two years ago and the difference in how quickly our staff can pull up hearing schedules tied directly to an inmate’s charge history has been night and day. The NIBRS compliance piece alone saved us a serious headache during our last state audit. Curious whether your system handles consecutive vs. concurrent sentencing holds differently in the case view or if that’s a manual flag.
We’ve been wrestling with getting our NIBRS submissions clean ever since the state mandate kicked in, so seeing court holds and arrest records tied directly into the same system is something we’d seriously consider. Does this handle multi-count charges where each count ties back to a separate RMS incident number, or does it flatten everything under one case? That’s been our biggest headache with the legacy setup.
We’ve been struggling to keep our court holds and arrest records in sync between our old RMS and the jail side — constantly chasing down discrepancies before hearings. Does your system handle automatic updates when a charge gets amended in court, or does someone still have to manually reconcile on the detention end?