FiveM Police, EMS, MDT and Dispatch Scripts: The Honest 2026 Guide

A FiveM law enforcement setup is not one script, it is four layers that have to agree on the same data. The police job handles duty, arrests, cuffing, fines and loadouts. The EMS job handles revive, treatment, hospital and death state. The MDT (mobile data terminal) is the database UI for citizen lookups, reports, warrants, BOLOs and charges. Dispatch turns in-game events like shots fired or a stolen vehicle into alerts and blips for on-duty officers.

The hard part is not picking any single script, it is making all four read and write the same citizen, charge and evidence records. When the job, MDT and dispatch come from different authors they often store data differently, so a charge filed in the MDT does not appear in dispatch, or an arrest does not update the record. That mismatch is the number one reason police roleplay feels broken on a busy server, and it is why single-vendor stacks built on a shared data model behave more predictably than a pile of mixed free resources.

qb-policejob is the long-standing QBCore default and still maintained by the QBCore team. It covers duty toggle, cuffing, escorting, jailing, evidence basics and an armory, and almost every QBCore tutorial assumes it, so it is the safest free starting point if you run QBCore.

ox_police (the OX ecosystem police resource, sometimes shipped as police-em style modules) is the choice when your server is already built on ox_lib, ox_target and ox_inventory. It is lighter, more modern in code style and integrates cleanly with the rest of the OX stack, which matters for performance on high-population servers.

For ESX, esx_policejob remains the baseline, and there are mature framework-agnostic premium jobs that add a duty roster, rank-based loadouts, body-camera capture and a built-in evidence locker. Quasar Store's police job sits in this premium tier: it is built to share one data layer with Quasar's dispatch and evidence, so charges, arrests and alerts stay in sync instead of drifting apart, which is the failure mode that free mixed stacks hit under load.

ps-mdt by Project Sloth is the most widely deployed free MDT. Rebuilt with Svelte for QBCore and QBox through its lib abstraction, it gives officers citizen lookups, report writing, case and evidence management, warrants, BOLOs, vehicle and weapon lookups, camera and bodycam views and department management. If you run QBCore or QBox and want zero license cost, this is the default.

lb-tablet from LB Scripts is a premium tablet that bundles an MDT for both police and EMS and ships with ESX, QBCore and QBox support plus template files for custom frameworks. It is the pick when you want one polished tablet device that also covers civilian and EMS apps, not just a police terminal.

codem mMDT (AIO) is another strong premium all-in-one: asset upload via Fivemanage or Discord, per-profession permissions, boss grade systems, unit commands and Discord webhook audit trails. Choose it when you care about granular access control and audit logging across multiple departments.

ps-dispatch by Project Sloth is the free dispatch most QBCore servers start with. It is battle-tested on large communities, fires alerts for crimes like shots fired, melee, vehicle theft and store robberies, and pairs naturally with ps-mdt. If you already run the Project Sloth resources, this is the obvious match.

cd_dispatch (Codesign) is the popular premium option, with a cleaner alert UI, unit assignment and response tracking, and is widely supported as a dispatch backend by other resources. Codesign's newer 3D dispatch adds map-based call organisation and unit assignment for control-room style play.

Many premium MDTs and tablets, including lb-tablet and codem, can either provide their own dispatch layer or integrate with cd_dispatch, qs-dispatch, ps-dispatch and rcore_dispatch, so confirm the integration list before mixing. The cleanest result is still a dispatch that was written against the same job and MDT you are running, because event data and call records then match without a compatibility shim.

Small QBCore server, no budget: qb-policejob + ps-mdt + ps-dispatch is the proven free baseline. It works, it is documented everywhere, and you can launch on it the same day.

OX-based server: lean on ox_police with ox_lib, ox_target and ox_inventory, then add an MDT and dispatch that support the OX data layer. This is the most performance-friendly route for high population.

ESX or mixed-framework server: a framework-agnostic premium police job plus lb-tablet or codem gives you ESX, QBCore and QBox support from one vendor and avoids per-framework patching.

Server that wants police roleplay to be a headline feature: go single-vendor. A police job, MDT, evidence and dispatch from one author that share a data model removes the cross-resource desync that free mixed stacks suffer, which is exactly where Quasar Store's police and dispatch resources earn the top recommendation. The trade is license cost against far fewer compatibility bugs and a consistent UI across the whole LEO experience.