Dispatch that keeps up with
your shift.
A live call queue, unit statuses, incident reports, BOLOs, warrants and a searchable citizen and vehicle database — for police, fire, EMS, dispatch, civilian and government roleplay on any platform your community runs on.
Included free Every part of CAD is free on every plan. Nothing here is an add-on, and nothing is capped by what you pay.
The dispatch board
The numbers first, then the calls worst-first, then who is free to send. Everything a dispatcher checks in the first three seconds of a shift is above the fold.
Active calls 4
-
#218 High In Progress 2 assignedStructure fire · Northgate Industrial ParkFire & Rescue · Engine 4, Ladder 2
-
#221 High Open UnassignedInjured person · Riverside Walk, near the bandstandEmergency Medical
-
#224 Medium In Progress 1 assignedTraffic stop · 5th & MainPolice · Unit 12
-
#225 Low Open 1 assignedNoise complaint · Cedar CourtPolice · Unit 7
Units on duty 6
- Unit 7 Police Available
- Unit 12 Police On Scene
- Engine 4 Fire & Rescue On Scene
- Medic 3 Emergency Medical Available
Worst first, always
The queue is ordered by priority and then by how long a call has been waiting — never by whichever was opened last. A call nobody has taken is marked, and counted at the top of the page.
Your words, not ours
Unit statuses and call priorities are yours to name. A server that says "10-8" and one that says "Available" both work, and neither has to explain itself to the other.
Four separate permissions
View, take a unit on duty, dispatch, and configure are four different things. A trainee can watch the board, a unit can set their own status, and only dispatch can open, assign and close calls.
Nothing to undo by accident
Closing a call cannot be reversed, so it says so before it happens, and names what stops and what does not. Ending a record asks for a reason, and keeps the record in full either way.
Look somebody up mid-call
In-character people, the vehicles registered to them, and every record that names them — searchable, and linked properly rather than matched on a name that might be somebody else's.
| Name | DOB / age | Linked member | Status |
|---|---|---|---|
| Jordan Vale | 12 March 1994 | Cascade RP · verified | Active |
| Marcy Vale | mid-40s | Not linked | Active |
Jordan Vale Active
Registered vehicles
- TRB‑4417 Blue saloon Registered
- KLN‑0092 Grey pickup · previous owner on file Transferred
Timeline
- WarrantServed — failure to appear3 Mar
- CitationSpeeding — 52 in a 3028 Feb
- VehicleKLN‑0092 transferred from M. Vale14 Feb
The paperwork, and where it lives
BOLOs, warrants, enforcement records and incident reports — all free, all searchable, and none of them deleted when they end.
BOLOs 2 active
- Vehicle TRB‑4417 Blue saloon — failed to stop Active
- Person Unidentified male Northgate — grey hooded jacket Active
Warrants
- Jordan Vale Failure to appear Served
- Ellis Brant Criminal damage Outstanding
Enforcement records
| Type | Subject | Detail | Status |
|---|---|---|---|
| Citation | Jordan Vale | Speeding — 52 in a 30 | Filed |
| Warning | Ellis Brant | Parking obstruction | Filed |
| Arrest | Unidentified male | Released without charge | Voided |
Incident report #61 Filed on call #218
Attended a working structure fire at Northgate Industrial Park with Engine 4 and Ladder 2. Two occupants were accounted for on arrival and handed to Medic 3. Scene handed to the fire investigator at 21:40.
Frozen when filed — the call details, assigned units and history are captured with it.
Who it is for
Any public-safety RP
Police, fire, EMS, dispatch, civilian and government roleplay. Five wording profiles ship with it — a general one, and ones tuned for ER:LC, FiveM/GTA, Roblox RP and military roleplay — and a profile only changes wording and defaults, never how anything works.
Small servers most of all
You do not need a separate CAD service, a second bot or a spreadsheet. A server with one department and four people on shift gets the same board a large one does.
Servers already using the bot
CAD departments are the rank groups you have already configured, so who is eligible for which department is a question you have already answered. There is no second structure to keep in step.
Setting it up
The dashboard walks this in order, and tells you which steps you have done.
-
Choose how CAD should be worded
Pick a profile, or stay on the general one. It sets your starting unit statuses, call priorities and the word you use for a department — all editable afterwards.
-
Pick which departments run CAD
Choose from the rank groups your server already has. If you have not set any up yet, that is the one thing to do first.
-
Turn CAD on
One switch on the Features page. It is off until you turn it on, so nothing appears in your server before you are ready.
-
Decide who may use it
Grant the four CAD permissions to the Discord roles you already use. They are separate on purpose — dispatch is not the same job as being a unit.
-
Start dispatching
Members open the board with
/cadin your server. Go on duty, open a call, assign a unit.
The optional game-server link
If your community runs an ER:LC private server and has its own API access from the game, CAD can read who is in game and show it beside your units. It is read-only — it never writes anything back, never issues a command, and creates no records.
It is off until somebody adds a key, and we have not yet verified it against a live server, so treat it as untested rather than as something to plan around. Everything above works without it, and CAD is not built around any one game.
What CAD does not do yet
There is no live push — the board refreshes when you ask it to, or on a timer you switch on. A call's priority cannot be changed after it is opened. A unit is assigned to a call one at a time. History is kept for a fair recent window rather than forever.
These are on the roadmap rather than in the product, and none of them is a paid upgrade today.
The rest of the platform
Ready to run dispatch properly?
CAD is free on every plan. Pick a server and set it up in a few minutes.
Get Started — Pick a Server