FiveM UK Control Room RP: Dispatch, CAD, Call Grading and Running Police Comms Properly

FiveM UK Control Room RP: Dispatch, CAD, Call Grading and Running Police Comms Properly

Eight officers on duty. A shoplifter walks out of the Co-op with a meal deal and an attitude, someone shouts it over the radio, and within ninety seconds every unit on the server is blue-lighting to the same high street. Two arrive nose to nose. A third puts a wheel into a bollard and spends the rest of the shift explaining it. Meanwhile there is a domestic in progress two streets away that nobody has picked up, because nobody knows it exists, because the only trace of it is a line someone typed in general chat eleven minutes ago.

That is a policing server without a control room. Fixing it does not need a new map, a new script pack or another recruitment push. It needs one person in a chair with a list. This post covers FiveM UK police dispatch RP end to end: taking the 999 call, grading it, keeping an incident log worth reading, running a radio channel eight people can share, making checks mean something, spreading four cars across six jobs, and training the next operator so you are not the only one who can do it.

What a control room operator actually does on a British policing server

There is a habit on a lot of servers of treating dispatch as the seat you get put in when you have no car, no rank and no friends. That habit is why nobody wants it, and why the servers that fix it pull ahead so fast.

An operator is not a human notification popup. The job is four things at once. You turn a panicking member of the public into usable information. You decide how fast anyone needs to get there. You keep a record an officer can join halfway through and be useful from. And you hold the map in your head: who is where, who is committed, who is free, and what breaks if the next job lands before the last one clears.

Done properly, it is the only role on the server with a view of the whole shift. Everyone else has a windscreen. You have the board.

Taking the call: the first thirty seconds decide everything

New operators want to hear the story. The caller wants to tell you the story. Both of you are wrong for about half a minute, because a story you cannot send anyone to is just audio.

Run the questions in this order and do not let the caller reorder them for you:

  1. Where are you, and where is it happening? Those are sometimes two different places and you need both.
  2. What is happening right now, in one line, rather than what happened at Christmas.
  3. Is anyone injured, and does anyone need an ambulance?
  4. Are the offenders still there, and which way did they go?
  5. Descriptions: how many, what are they wearing, what are they carrying.
  6. Vehicles: index, make, colour, direction of travel.
  7. Your name and a number we can call you back on.

Location is the one people fumble. A frightened caller says "outside the shop", "near the roundabout", "the big block of flats", then gets annoyed that you do not already know. Work it the way call handlers do: what can you see, is there a street sign, what shop are you next to, what number is on the nearest door, what junction did you pass. On a GTA V map that means landmarks your officers actually recognise, so build a cheat sheet of them and pin it. Then keep the caller on while a unit is running, because the picture keeps changing and you are the only one receiving it.

Two bits of British texture worth stealing. 999 is for emergencies and 101 is for everything else, so give your server a non-emergency line and watch the grading improve on its own. And the silent solution, where a caller who cannot speak presses 55, is a superb roleplay hook that costs nothing.

Call grading: immediate, priority and scheduled

Grading is the thing that turns dispatch from admin into a game. UK forces sort calls into response categories, and the shorthand most people recognise is roughly this:

Grade every job out loud on the radio when you send it. "Immediate" and "priority" mean different driving, different tactics and different consequences for turning up late. The moment officers know a shoplifter is a priority and not an immediate, the great high street pile-up stops happening on its own. You did not ban anything. You just gave the word a meaning.

The incident log is the spine of the shift

The CAD, the command and control system, the incident log: whatever you call it, it is the one artefact that survives the shift. Every job gets a log number and every log number gets an audit trail. UK style numbering works nicely, something like "log 47 of the first", and it is short enough to say on the radio.

A log entry that is worth writing has the time and grade, the location, one line of what is happening, the units assigned and their status, and then a running list of updates with timestamps. Add the caller's details, any warning markers, and the outcome when it closes.

The test for whether your log is any good: an officer joins the server mid-incident, reads the log, and knows what to do without asking a single question. If they have to ask "what's going on at that address", the log failed. Write updates as they happen rather than reconstructing them later, because a log written afterwards is a story and a log written live is evidence. Your custody team, your CID and anyone doing a court scene later will be reading it, and they can tell the difference immediately.

Radio discipline: callsigns, phonetics and the difference between talking and transmitting

A radio channel is a queue, not a conversation. Everything you say lands in eight people's ears at once, so the only question that matters before you key up is whether all eight of them need it. Talking is what you do with the officer next to you. Transmitting is a broadcast, and it costs everyone else their turn.

The habits that fix a channel in one shift:

Voice tooling makes or breaks this. Most servers land on pma-voice or SaltyChat with a proper radio resource so channels, static and range behave, and it is worth wiring a control room seat properly into your QBCore police job setup so the operator has full radio and system access without needing a patrol car assigned to them.

Running PNC checks so they take time and mean something

A check that returns instantly and perfectly is not roleplay, it is a search bar. The British version has friction in it, and the friction is the point.

An operator running a vehicle should read the index back in phonetics, confirm what is being asked, then take a beat before answering. Come back with the registered keeper, the make and colour, the insurance and MOT position, and any markers. A marker is where the drama lives: interest in the vehicle, previous for violence, do not approach alone. That one line changes how the officer walks up to the driver's door.

A person check works the same way. Full name, date of birth, spelt phonetically, and then wanted status, bail conditions, warning signals, previous convictions in general terms. An address history check is slower still, and it should be, because you are pulling records rather than pinging a database.

Two rules keep this honest. Make officers give you something before they get something, so no fishing for a name they have not established. And build in a real possibility of no trace, a partial match, or a delay because the system is slow. A control room that always has the answer removes every reason to investigate.

Four cars, six jobs: deployment, escalation and calling in the specialists

This is the resource game, and it is genuinely fun once you stop apologising for it. You have four units. There are six live jobs. Something is going to wait, and choosing what waits is your whole job.

Work it like this. Immediates get bodies first, and a job with a threat to life takes a unit off a lower job without a debate. Never commit your last free unit unless you have already decided who is coming off something else. Keep an eye on the ones who have been at the same address for forty minutes, because a unit that has quietly gone off the air is a unit you do not have. And say "no" out loud when three officers self-assign to the same call, because two of them are needed somewhere else and only you can see where.

Escalation is where the limits of the role matter. A control room requests specialist resources; it does not authorise them. Firearms are a good example: you can call for an armed response vehicle and pass on the intelligence that justifies it, but the authority to deploy comes from an authorising officer, not from you. The same logic covers a pursuit, where a control room inspector or force incident manager decides whether it runs or gets called off, and calling it off is a real power you should use when the driving stops being proportionate. Dog units and air support are requests too, and air support in particular should be allowed to say no because the aircraft is on another job or grounded by weather. A resource that always comes when called stops feeling like a resource.

Multi-agency comms are the other half. Ambulance and fire do not sit on your police channel in real life, they sit in their own control rooms and you ring them. Recreate that with a separate channel and a short structured handover: what has happened, exactly where, how many casualties, and what hazards their crews are walking into. If you want the wider picture of how the British emergency services fit together on a server, that inter-agency handshake is the joint everything else hangs off.

What you need to run dispatch, and how to train the next operator

The tooling ladder is short. At the top, communities run a full computer aided dispatch web app such as SnailyCAD alongside in-game resources, which gives you live unit statuses, a proper incident log and an MDT that officers can read from the car. In the middle sit the in-game options, the various dispatch and MDT systems that push alerts, blips and unit states straight into the game so your operator and your officers are looking at the same picture.

At the bottom, and this is the honest one, you can run an excellent control room with a Discord server and a spreadsheet. One text channel for incoming calls, one for the incident log, one voice channel as the radio. A sheet with columns for log number, time, grade, location, summary, units and status. That is it. Every good control room culture I have seen started on something roughly this ugly, and the servers that bought the expensive CAD first usually still could not grade a call.

Training an operator takes about three shifts. First shift they only listen, with the log open, writing down every callsign and where each unit is. Second shift they run the log while you talk, so they learn what an update looks like without the pressure of the microphone. Third shift they take the radio and you sit behind them, saying nothing unless it is going badly. Give them a one-page card with the question order, the grades and the five radio phrases, and let them keep it.

Which brings us back to the Co-op. The meal deal thief is still a priority call, and one unit is enough, and now everyone knows that because somebody said so on the radio. If you have a member who colour-codes their spreadsheets, remembers everyone's callsign and gets a small thrill from a tidy audit trail, you have found your operator. Every server has one. Ask them before they get bored and go and play a paramedic.

Related posts

FiveM UK Custody and Booking RP: PACE, Cell Time and Processing a Suspect Properly
Guide
FiveM UK Custody and Booking RP: PACE, Cell Time and Processing a Suspect Properly
FiveM UK Public Order Policing: Protests, Football Days and Crowd Control RP
Guide
FiveM UK Public Order Policing: Protests, Football Days and Crowd Control RP
Building a UK Police FiveM Server: British Ranks, ANPR, Response Codes and Pursuit Tactics
Guide
Building a UK Police FiveM Server: British Ranks, ANPR, Response Codes and Pursuit Tactics
Published · Sep 02, 2026 Read more posts →