Records management system

A records management system, or RMS, is software an agency uses to create, store, manage, and retrieve reports and related records. In law enforcement, it can hold incident information used for investigations and crime reporting. An RMS is an internal records system; it is not automatically a public database.

What an RMS helps the agency do

A report can contain structured information, such as dates and offense categories, alongside a narrative describing what was reported or observed. Related records may add later information about people, property, or investigative developments. Managing these connections helps staff retrieve a case without treating every new detail as a separate event.

The Bureau of Justice Assistance defines an RMS in terms of computerized incident reports and other data, and notes that it may compile information for national crime reporting or connect with CAD. Those are possible functions, not a promise that every agency uses the same software or integration. BJA's RMS entry.

The FBI's 2025.0 National Incident-Based Reporting System manual describes incident information collected on paper or through electronic systems connected to an agency's RMS. It also explains that material changes can require updates to submitted crime data. A record's presence in an RMS therefore does not make its first version permanent. FBI manual, incident collection and report modifications.

Example

Hypothetical example: A resident reports a stolen bicycle using the department's approved reporting process. The agency creates case R-871 in its RMS, recording the reported theft date, report date, bicycle description, and narrative. A week later, the resident provides the serial number, which is added in a supplemental record connected to the case.

The supplement adds information; it is not necessarily a second theft. A data export with one row per document could contain two rows, while a case-level export still contains one case. Knowing what the export counts prevents an inflated incident total.

If no unit was dispatched, the report may have no corresponding CAD event. If a dispatch did occur, its CAD number may be linked to the case rather than identical to the case number.

Common confusion

RMS and CAD serve different purposes. CAD supports the coordination of calls and units. RMS supports reports and related records. A single software package may connect both functions, but that does not make the underlying record types interchangeable.

An RMS entry is not a conviction. It can document an allegation, an officer's observations, or an investigative status. Court findings belong to a different process.

An RMS export is not the full system. A public file may contain selected approved records and fields. Narratives, identifying information, attachments, and later supplements may be omitted. The export's scope must be established from its documentation.

Reading changes and identifiers

Check whether the displayed date is the event date, report date, or last update. A report entered today can concern an event from last month, and a revised offense category can change a historical total.

Also identify the stable case identifier and how supplements or multiple offenses are represented. Do not assume every row is a unique case. Where the agency supplies revised files, preserve the release date when describing your result so readers know which version supported the count.

The useful question is not simply whether data came from an RMS. It is which records were selected, which fields were released, and how the agency transformed those records into the published dataset.

Related terms

• Computer-aided dispatch
• Incident report
• Supplemental report
• Case number

Sources

• Bureau of Justice Assistance — Glossary of Terms, RMS and CAD entries. Supports core system functions; legacy program counts are not used.
• FBI — NIBRS User Manual, version 2025.0, June 23, 2025, sections 2 and 3.4. Describes incident collection through RMS and material report updates.