DevelopmentPulseRMS · Records Management

From dispatch tone
to case close.

PulseRMS is an active development initiative — a records management system designed to live natively inside CommandCORE. The screens below are concept mockups of what we are prototyping. PulseRMS is not yet for sale and is not part of the Early Access Program.

R&D
Stage
Concept
Mockups only
Not sold
No pilots · No EAP
2026+
Possible future
Active Development · Not Yet Available
PulseRMS is not being sold or offered under the Early Access Program.

PulseSafety is actively developing a Records Management System designed to live natively inside CommandCORE. The screens on this page are concept mockups drawn from internal prototypes — they are not a shipping product, not available for pilot, and not included in any procurement or Early Access package. We are not yet CJIS certified or SOC 2 compliant, though we are actively pursuing both.

What we’re building

Five concept surfaces,
one records story.

The sketches below show where PulseRMS development is heading. The goal: an RMS that feels native to CommandCORE from the first incident number through the final NIBRS submission — not a third-party bolt-on.

Surface 01

Incident Reports

Structured record-keeping from the moment an incident number is assigned. Officers fill narrative, add persons and vehicles, attach property, and walk through a review checklist — all in one workflow.

  • Tabbed layout: Details, Narrative, Persons, Vehicles, Property, Timeline, Review
  • Auto-populated from CAD dispatch data — no re-keying addresses or timestamps
  • Environmental conditions captured with the record, not in a separate form
  • Supervisor review queue built directly into the record workflow
Incident: IR-2026-000001closedDispatch
Print Report
Occurred: Mar 10, 2026, 9:30 AMReported: Mar 10, 2026, 9:35 AMLocation: 3847 Elm Street, Springfield, TX
DetailsNarrativePersonsVehiclesPropertyTimelineReview
Record Info Edit
Record #
IR-2026-000001
Type
Assault
Source
Dispatch
Call Type
Assault
Call Nature
Assault – Bodily Injury
Disposition
Report Taken
Priority
2
Beat
Beat 3
Case: 2026-0003OpenMisdemeanor
Submit for Review
DetailsOffensesNarrativePersonsVehiclesPropertyDocumentsNIBRS
92
NIBRS Score
Not Ready · 1 error
Administrative
1 error
Offense
N/A
Victim
N/A
Offender
N/A
Property
N/A
Arrestee
N/A
ADM-001 · AdministrativeCase must have at least one offense.
Surface 02

Case Management

Investigations need more than a folder. Cases in PulseRMS link directly to incidents, track offenses against the UCR/NIBRS code set, and surface submission readiness before anything leaves the agency.

  • NIBRS validation scoring with per-segment error codes and one-click fix prompts
  • Case assignment: officer, detective, and reviewing supervisor in one view
  • Linked records panel — tie warrants, arrests, and related incidents to a case
  • eFile docs, property, and clearance info on tabbed sub-pages
Surface 03

Warrant Module

Search warrants, arrest warrants, and bench warrants — managed alongside the cases and persons they relate to. No more separate systems for warrant tracking.

  • Issued date, judge, court, NCIC number, bail, bond type in one record
  • Charges, subjects, and co-persons linked directly to the warrant
  • Full status history — issued, served, recalled, cancelled — with timestamps
  • One-click Serve / Recall / Cancel from the warrant header bar
WR-2026-000004SearchActive
ServeRecall
DetailsActivitiesCharges 1Persons 1Status History 1
Warrant Information
Warrant #
WR-2026-000004
Type
Search
Status
Active
Jurisdiction
Springfield PD
Issuing Court
District Court
Issuing Judge
Judge Michael Torres
Issued Date
Mar 19, 2026, 7:00 PM
Expiration
Extraditable
No
Nighttime Svc
No
Notes

Search warrant for 442 Oak Hill Dr — suspected stolen electronics from Oakwood subdivision burglary pattern.

Platform-Native

PulseRMS isn’t bolted on.
It’s built in.

Because PulseRMS lives inside CommandCORE, every record ties directly to the tools your officers, supervisors, and community staff already use — no middleware, no re-keying, no sync lag.

PulseCAD

Incident numbers and dispatch data flow directly into RMS — officers open a pre-populated report, not a blank form.

Internal Affairs

Use-of-force, complaint, and officer-involved incidents in RMS automatically surface to the IA queue for review.

Victim Services

Person records created during an incident are immediately available to victim advocates without re-entry.

PassOn / Shift Log

Key incidents and open cases appear in the shift hand-off briefing automatically — no separate PassOn entry needed.

Active Development

Help us shape PulseRMS

We’re in active development and talking to agencies every week about what an RMS should actually do. If you have opinions about incident reporting, NIBRS pain points, or case workflows — we want to hear them.