The pursuit crossed the city line. Now the next dispatch center can see it.
Every agency’s vehicle locations are walled inside its own CAD. When a pursuit crosses from one city into the next, the receiving dispatch center is listening to a radio patch, not watching a map. LVTRAQ pushes the pursuing unit’s position to the neighbouring agency the moment the unit crosses — read-only, time-boxed, and revoked when the pursuit ends.
A supplemental situational-awareness aid. It never replaces voice radio.
Neighbouring CADs. One radio patch. No shared map.
In a dense metro grid, neighbouring police departments each run their own dispatch center on their own computer-aided dispatch system. Each one can see its own units. None of them can see the others’.
A pursuit that starts in one city can cross two more in four minutes. The agencies it enters hear the broadcast; they do not see the unit. Officers setting up ahead of it are working from a voice description of a position that is already out of date.
Mutual-aid interoperability is the documented weak point of the category, and it has stayed that way because the fix has to sit between CADs, not inside one of them. That is the only thing LVTRAQ does.
- Sold toDispatch centers and the joint-powers authorities that run them. Never to individual officers.
- Reads fromThe pursuing unit's own device. Nothing from CAD, nothing from records.
- SharesOne pursuit, with the agencies it crosses into, for as long as it is active.
Three steps, all of them logged.
- 01Step
Track
The pursuing unit's device reports its position once a second. Each fix carries the time it was taken and the time it arrived. The difference is displayed, never hidden.
- 02Step
Cross
Every fix is tested against agency boundary polygons. The moment a unit enters a neighbouring jurisdiction, that agency's dispatch console receives a live, read-only share of the pursuit — automatically, and on the record. The likely next jurisdiction is shown too, and labelled as a prediction.
- 03Step
Acknowledge
A dispatcher at the receiving agency acknowledges the handoff under their own login. The share ends when the pursuit ends, or when the originating agency revokes it. Every grant, acknowledgement and revocation is logged with who and when.
A neighbouring agency sees exactly one thing: the pursuits currently shared with it. Tenant isolation is enforced by row-level security in the database itself, not by application code.
A stale position is never shown as a live one.
Every unit carries the age of its last confirmed fix, on every screen, at all times. The state is spelled out in a word, so it reads correctly without colour, on a dim monitor, and in a screenshot pulled for an after-action review.
At 100 mph a vehicle covers about 147 feet every second. A rendered position is behind reality by the age shown beside it. That is why the age is shown, and why the rule is confirm by radio before any tactical decision.
- Fresh0 – 3 sPosition reflects the last few seconds.
- Aging3 – 8 sUpdate cadence has slipped. Watch it.
- Stale8 – 20 sDo not treat this position as current.
- Lost> 20 sNo reliable position. Radio only.
- No fix—Never received a fix. Shown as an em dash — never a position, never a zero.
No criminal justice information. There is nowhere to put it.
LVTRAQ stores positions, unit callsigns, timestamps and agency names. It has no field for a name, a date of birth, a driver’s licence, a plate, a VIN or a warrant, and it does not read from CAD. That is a database decision, made once and enforced by the schema itself, so the system stays outside CJIS scope by construction rather than by policy.
A callsign is a rotating radio designator broadcast in the clear all day. It identifies a unit, not a person, which is why the track is a record of a pursuit and not a record of an officer.
This is an engineering position, not legal advice. Before deployment it is reviewed with the agency’s own terminal agency coordinator.
- Names — suspect, driver, owner, victim, witness
- Dates of birth
- Driver's licence numbers
- Licence plates and VINs
- Vehicle make, model or colour
- Warrants, NCIC or CLETS returns, criminal history
- Booking, arrest or charge data
- Officer names or badge numbers on the pursuit record
- Radio traffic, audio or video
- Any CAD integration
Positions · unit callsigns · timestamps · agency names · a free-text pursuit note
What LVTRAQ does not do.
- Voice radio
- It does not replace voice radio, and it does not change the broadcasts your pursuit policy requires. Direction, vehicle description, occupant count and justification are not GPS data.
- Units, not suspects
- It tracks pursuing units. It does not track, tag or identify a suspect vehicle.
- Not a CAD
- It is not a dispatch system and does not read from one. It sits beside CAD, between agencies.
- Boundaries
- Jurisdiction boundaries are as good as the GIS your agency provides. Approximate boundaries are labelled approximate on the map.
- Delay
- Positions can be delayed by the network, the device or the sky. The age of every fix is shown so a delay is visible, not hidden.
Built to be shown to a dispatch supervisor in twenty minutes.
LVTRAQ is provisioned to agencies, not to individuals. If you run or support a communications center, ask for a briefing: the handoff, the age-of-fix rule and the data boundary, demonstrated on simulated units, with your questions answered by the people who built it.
LVTRAQ is a supplemental situational-awareness aid. It never replaces voice radio. Positions shown may be delayed — confirm status by radio before any tactical decision.
Include your agency, your role and the neighbouring agencies you most often hand pursuits to. Briefings are scheduled by reply.
Or open the demo console nowSimulated units, no login. The scripted pursuit crosses two city lines in the first minute.