CAD and RMS: how dispatch and records systems work together

Reference article · 5 min read

Most police and fire agencies run two systems at the center of operations. Computer aided dispatch handles the live event: a call comes in, a call taker enters it, the system recommends and assigns units, and it tracks status and times until the call clears. Records management holds what the event becomes afterward: an incident report, a case, an arrest, property in evidence, and the data the agency owes to its state repository. The same event passes through both, which is why the boundary belongs in the solicitation rather than in implementation.

Agencies buy these systems in several combinations: one vendor's suite, two products joined by an interface, or a shared regional dispatch system feeding several agency record systems. What matters more than the vendor count is knowing which system is authoritative for which information, what moves between them, and who is responsible when the movement stops.

What computer aided dispatch is responsible for

CAD is an operational system, measured by uptime and by whether a dispatcher can work it under load.

Call entry and location validation. What is happening and where, checked against a geofile of street segments, address ranges, and common place names.
Unit recommendation and assignment. Response plans define how many units of what type go to each call type, often informed by automatic vehicle location.
Status and timing. Dispatched, en route, on scene, cleared. These timestamps are the source for response time reporting, so their definitions matter.
Field access. Mobile data computers let units update status, read call notes, and run queries without voice traffic.
Short operational history. CAD holds enough history for the shift and recent activity. It is not the agency's long term record.

What records management is responsible for

RMS is a system of record, measured by completeness, accuracy, and retention.

Incident and case reports. Narrative, offenses, persons, vehicles, property, supplements, review and approval, and case status.
Master indexes. One record per person, vehicle, location, and business, linked to every event where it appears. The matching rules determine whether the index is usable.
Property and evidence. Intake, barcodes, chain of custody, storage location, disposition, and purge eligibility.
State and federal reporting. Most agencies submit incident based crime data to a state repository that forwards to the FBI's national collection. Crash, arrest disposition, and use of force reporting run on separate state schedules. Formats and requirements change, so confirm current specifications with the state program.
Retention and disclosure. Retention schedules, redaction, and public records production apply to records content differently than to dispatch logs.

The handoff, and what crosses it

Every agency needs a written answer to one question: when a call for service becomes an incident report, which system issues the number, and which fields carry over untouched.

Typically CAD pushes to RMS at or near call closure, sending the call number, call type, validated location, times, responding units and personnel, disposition, and the event log. RMS owns everything added afterward. The reverse direction matters as much: records data sent back to dispatch gives call takers and responding units premise history, caution flags, prior contacts at an address, and associated persons.

Other interfaces sit around this pair and should be scoped at the same time:

The state message switch and national law enforcement networks, reached from both dispatch and mobile
Field based reporting on the mobile computer, writing into RMS
Electronic citation, crash reporting, jail, prosecutor, court, evidence, and laboratory systems
Dispatch to dispatch sharing with neighboring centers, and call and location delivery from a next generation 911 system
Analytics and data warehouse feeds

Many of these exchanges are defined using the National Information Exchange Model, and industry associations publish functional standards for both systems. Ask which specification and version a product implements rather than accepting a general claim of compliance.

Where these integrations break

Code tables drift. Call types and offense codes are different vocabularies, and disposition codes are not clearance codes. Someone has to own the mapping and revisit it after every upgrade on either side.
Identifiers do not line up. Unit numbers, personnel identifiers, and person matching rules differ between systems, producing duplicate master records.
Addresses disagree. The dispatch geofile and the records address validation often come from different sources. Designate one authoritative address source and feed both.
Time is inconsistent. Clock synchronization, time zone handling, and daylight saving change response time math.
Upgrades are uncoordinated. An interface that works can stop working when either product releases a new version.

What to ask and what to put in the contract

Ask vendors which interfaces to the other product run in production today at agencies of similar size, what each one transfers in both directions, whether it is real time or batch, what happens to queued records when the receiving system is unavailable, and what the agency pays when either side upgrades.

Require in the contract:

The interface specification, field mapping, and data dictionary as named deliverables, not documentation promised later.
A responsibility matrix signed by both vendors when two are involved, naming who diagnoses and who fixes.
Advance notice of breaking changes and a commitment to keep existing interfaces working across the vendor's own releases.
Acceptance testing with realistic volumes and edge cases, including a receiving system outage and the catch up afterward.
Export of agency data in a documented, non proprietary format on demand and at termination.
Security terms reflecting the criminal justice information requirements that apply, confirmed with your state CJIS systems agency.

HQT builds and integrates public safety software for state and local government agencies.

Frequently asked questions

Do CAD and RMS have to come from the same vendor?

No. Agencies run both models successfully: a single vendor's suite, or separate dispatch and records products joined by an interface. A suite removes one vendor boundary but ties the two upgrade schedules together, while separate products let each be replaced on its own timeline if the interface is documented and owned. The deciding factors are usually the quality of each product for its own users and how clearly the contract assigns responsibility for the connection between them.

What data should transfer from CAD to RMS?

At a minimum the call number, call type, validated location, the dispatch and clearance timestamps, the units and personnel who responded, the disposition, and the dispatch event log. Records then owns everything added afterward, including narrative, offenses, persons, property, and case status. Decide in advance which transferred fields a report writer may edit and which must stay exactly as dispatch recorded them, because response time reporting depends on the answer.

Which system submits incident based crime data to the state?

Records management does. The submission is built from offense, person, property, and arrest data that live in the records system, not from the call for service. Agencies report to a state repository that forwards data to the FBI's national collection, and validation rules and file formats vary by state and change over time. Confirm current requirements with your state reporting program before relying on a vendor's general compliance claim.

Who is responsible when the interface between dispatch and records stops working?

Whoever the contract names. Without a written responsibility matrix, agencies with two vendors often end up relaying messages between them while reports pile up. Require a named interface owner, a joint escalation path, documented specifications, and advance notice of changes that break compatibility.

Should the incident number be issued by CAD or by RMS?

Either can work. What matters is that one system issues the number and the other stores it as a cross reference, so a call and its report can always be matched. Write the rule down, including how numbers are assigned for reports written without a call for service and for a single call that produces several reports.