Skip to content
menu_bookDocumentation menu

Admin Settings

Unit Status Codes

The 10-codes your units press and the colours dispatch reads. This is the setting with the widest blast radius in the dashboard: it drives the status buttons, the unit cards, the map blips and the assignment logic all at once.

Two kinds of status

Base statuses — required for every community. These are the ones the CAD itself reacts to: available, unavailable, busy, en route and on scene. The system sets them for you at the right moments — attaching to a call sets en route, arriving or starting a traffic stop sets on scene — and the assignment screens use them to decide who counts as free.

You can rename them and recolour them. You cannot delete them, and that is on purpose: half the CAD's automatic behaviour is keyed to them existing.

info

In Station Mode SAFR gets two more: Returning to station and Transporting to hospital (by default 10-19 and 10-76). They are added when you turn Station Mode on, and the same rule applies: change the code, label and colour, not the behaviour. See Stations & Apparatus.

Custom statuses are yours. 10-99 Officer Needs Help, a meal break, a code for court — whatever your community says on the radio.

The fields

Each status has a code (10-8), a description (Available) and a colour.

The code is what players see on the button. The description is the tooltip and the readable label. The colour is what dispatch actually reads — on a busy unit list nobody parses codes, they scan colours, so keep the palette meaningful: one colour family for free, one for busy, one for something wrong.

Getting it right

Match the radio. If your community says 10-8 for available, the button should say 10-8. A status set that disagrees with what people say out loud gets ignored, and then the unit list stops reflecting reality.

Fewer is better. Every extra code is another button on a sidebar and another colour to learn. Statuses nobody presses are worse than absent, because a unit list where half the codes are stale tells a dispatcher nothing.

Live everywhere

Changes reach every client immediately — no refresh, no restart. Renaming a status changes it under people who are on duty right now, so a rename in the middle of a busy shift is a rename everyone notices.