Use native selection rules to reduce clicks without losing control of the response.
What an ARR actually does
Alarm and Response Regulations bundle vehicle selections into reusable buttons. They make selecting a response easier; you still need to check the available selection and dispatch it. A saved rule does not create missing resources, train personnel or guarantee that the complete response is available.
TKB recommendation: start with a small set of rules for the incidents you encounter most often. Build an understandable system before importing a huge list. A hundred buttons with unexplained abbreviations may be slower to use than ten well-labelled ones.
Create and organise a rule
The official creation guide describes a name, colour, column, category, station restriction, hotkey and vehicle quantities. It also documents an option to reset the previous selection. Menu placement varies between layouts; find Alarm and Response Regulations in the profile or main menu and create a rule there.
Use a naming convention you understand at a glance. A mission-specific name is useful for an exact recipe; a capability name is useful for a small reusable addition. For example, distinguish a complete first response from an extra command or transport component. This is a design convention, not a requirement imposed by the game.
Understand reset and composition
A rule that clears the previous selection can remove vehicles chosen manually or through another rule. That behaviour is useful for a complete replacement response but confusing for an add-on button. Test a rule on a mission before relying on it, and inspect selected vehicles after combining buttons.
TKB recommendation: maintain a small test checklist. Check an ordinary mission, a variant with additional requirements, a case where the closest vehicle is busy and a case with an active station restriction. Read any shortfall message rather than repeatedly clicking in the hope that a missing vehicle will appear.
Balance updates and responsiveness
The native setting to update all visible ARRs after a selection change trades extra updating work for more current button states. Official help explains that switching it off can slightly improve loading while leaving other buttons stale until clicked. Choose according to your device and the size of your rule list.
Keep seasonal or rarely used categories out of the way when they are not needed. Revisit imported rules after vehicle additions and mission changes. A rule authored for another national version may use different resources; similar names do not prove UK compatibility.
A reliable dispatch loop
- Read the mission name, variant and current missing requirements.
- Choose the relevant ARR and inspect what it selected.
- Resolve shortages, conditional transport needs and unusually long travel times.
- Dispatch, then revisit incidents that report a change or missing capability.
- Review recurring selection failures and improve the relevant rule rather than adding unrelated buttons.
Protect your configuration
Keep a record or export where the game offers one before deleting a large group of rules. Official help says deleted ARRs cannot simply be restored. Use native ARRs as an aid to active play; this guide does not recommend unattended dispatch tools or claim that third-party automation is approved.
Sources and further reading
Latest editorial change: Added an answer-first summary, action checklist and related planning/reference link. Detailed source dates remain independent.
Official sources establish game rules; practical build orders and planning examples are TKB recommendations. Follow the UK game’s current requirement panel where a later update differs.