PulseSafety
See a Demo
ResearchPulseCAD · Research Preview

Computer-aided dispatch,
being drafted in public.

PulseCAD is an active research initiative — a planned CAD surface designed to live inside CommandCORE from day one. The screens below are concept mockups of what we are prototyping. PulseCAD is not for sale, not in the Early Access Program, and not available for pilot.

Share your CAD pain points What are we researching?
R&D
Stage
Concept
Mockups only
Not sold
No pilots · No EAP
2026+
Possible future
Active Research · Early Development
PulseCAD is not being sold or offered under the Early Access Program.

PulseSafety is researching and prototyping a Computer-Aided Dispatch surface that would plug into 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 EAP package.

What we’re building

Five concept surfaces,
one dispatch story.

The sketches below show where PulseCAD research is pointing. The goal: a CAD that feels native to CommandCORE from the first tone through the final report — not a third-party system stitched in at the edges.

Concept 01
Dispatcher Console

Single-pane command surface — pending queue, active incidents, available units, and an operator command line.

Concept 02
Incident Detail

Full narrative timeline, assigned units with status timestamps, beat, location, and alert annotations.

Concept 03
Mobile MDT

In-car consumer of the same record — accept, en route, on scene, clear, with one-tap status updates.

Concept 04
Live Map

Unit positions, active call pins, and beat overlays on a single geospatial canvas.

Concept 05
CommandCORE Link

Every event flows to RMS, PassOn, and Internal Affairs — one record of truth, no re-keying.

CONCEPT 01
Dispatcher Console

The single pane
dispatch runs from.

One console. Pending queue on the left, the active-incident grid front and center, and the unit roster on the right — with a command line across the top for dispatchers who live on the keyboard.

PulseCAD · DispatchPulseSafety Inc. New Call
Pending 2Active 11 Connected
> Type / for commands...? No incident
I2026-000001 · Traffic Accident
I2026-00038 · Dist
I2026-00055 · Noise
I2026-00039 · Susp
Pending2
I2026-00057P2
DUI
8400 N IH-35
Waiting 1462:21:58
I2026-00040P4
Traffic
11200 N Lamar Blvd
Waiting 1461:43:57
Active Incidents11
Create Incident
I2026-00033Critical
Shot
2500 E Riverside Dr
3 unitsOn Scene
I2026-00052High
Assault
9200 W Parmer Ln
2 unitsDispatched
I2026-00039Medium
Suspicious Activity
500 E 7th St
2 unitsDispatched
I2026-00055Medium
Noise
2800 Guadalupe St
1 unitsOn Scene
Units
Available (0)
No available units
Busy (2)
PulseSafety AdminDispatched
PulseSafety Admin
ADAM-1Dispatched
Max Little
One pane, three rails
Pending, active, and units each get their own column — the dispatcher’s eye never has to context-switch between tools.
Command-line first
A typed operator surface (/dispatch, /clear, /assign) for keyboard-driven dispatchers — buttons still there for everyone else.
Live elapsed timers
Pending waits and on-scene dwell times are rendered in real time, colored by severity.
Welfare alerts
A welfare-timer panel surfaces when a unit has been on-scene past the beat’s configured threshold.
CONCEPT 02
Incident Detail

Every action,
on one record.

The detail view collects the full life of an incident — narrative entries, unit status transitions, timeline stamps, and assigned personnel — so the dispatcher and the on-scene supervisor are always reading the same truth.

I2026-00038MediumOn Scene
Edit Update Status Clear
Dist
800 W 5th St
Austin, TX 78703
Beat
ADAM
Add Alert
Narrative
Initial Narrativecall
Feb 20, 05:25

Noise disturbance at construction site during quiet hours.

Unit ADAM-2unit
Feb 20, 05:37

On scene. Making contact with involved parties.

Unit ADAM-2unit
Feb 20, 05:29

En route.

Assigned Units2
Test EmployeeOn Scene
Dispatched05:27
En Route05:30
Arrived05:44
Timeline
CreatedFeb 20, 05:25
DispatchedFeb 20, 05:29
ArrivedFeb 20, 05:48
Full narrative stream
Call, system, and unit entries time-stamped in one column — the record that follows the incident into RMS.
Status timestamps
Dispatched, en route, arrived, cleared — captured per unit and rolled up on the incident timeline.
Officer safety alerts
Hazard flags stamped on the record and surfaced in the header so nobody misses them.
NCIC panel (planned)
Person, vehicle, and wanted-person returns rendered inline on the incident record.
CONCEPT 03
Mobile MDT

For the officer
in the car.

A rugged, thumb-safe companion to the dispatcher console. The same incident record, the same narrative stream — just sized for the MDT bolted to the dash.

08:42 5G
ADAM-2 · On Duty
Max Martinez
Available
2
My Calls
4:32
Unit Time
ADAM
Beat
My CallsView All
I2026-00033P1
Shots Fired
3400 Burleson Rd
AcceptNavigate
I2026-00038P3
Disturbance
800 W 5th St
AcceptNavigate
HomeMapSearchSettings
In-car, not in-app
MDT is built for rugged tablets and in-car laptops — big tap targets, high-contrast status pills, thumb-safe layout.
One-tap status
Accept, en route, on scene, clear — each a single button that updates the incident record instantly.
Offline-resilient
Status changes and narrative entries queue locally and reconcile when a signal returns.
Safety flags surface
Hazard flags on the location, subject, or vehicle are pulled to the top of the call card.
CONCEPT 04
Live Map

Every unit,
every call, one canvas.

A geospatial surface that sits alongside the console, not inside another vendor’s tab. Unit positions, pending calls, and beat boundaries all live on the same map.

BEAT · ADAM
I2026-00033
I2026-00052
I2026-00039
I2026-00055
ADAM-1
ADAM-2
BAKER-3
Live Map
Critical
High
Medium
3 Units · 4 Calls
Unit + call geolocation
Every dispatched unit and active call is plotted in real time on the shared canvas.
Beat + zone overlays
Geographic beat boundaries, reporting districts, and closed-patrol zones are draw-in layers — not separate apps.
Click-to-dispatch
Drag the nearest available unit onto a pending call to dispatch it; the console and MDT both update instantly.
Response routing
Route hints and ETAs for each assigned unit drawn directly on the map.
CONCEPT 05
CommandCORE Integration

Native to the platform,
not bolted on.

Because PulseCAD is being researched inside CommandCORE — not as a third-party product — every event it records flows straight into the modules your agency already uses.

RMS

PulseCAD incidents seed the PulseRMS report — officers don’t re-type narrative, location, or involved parties.

Policy & PassOn

Shift-change hand-offs and acknowledged policies automatically annotate in-progress incidents.

Internal Affairs

Use-of-force and complaint workflows ingest the CAD record as the baseline incident log.

Roster & Fleet

On-duty officers, assigned units, and vehicle check-outs populate the unit roster automatically.

COREConnect

Verified public alerts originate from the CAD incident record — one source, one truth, one timeline.

Research only · Not for sale

Have CAD problems
worth solving?

PulseCAD is in active research and is not being offered for purchase or Early Access. If your agency has dispatch pain points you’d like to see solved, we’d rather hear about them now than after we’ve built the wrong thing.

Share your CAD pain points See the CommandCORE platform