Station Placement and Coverage

MissionChief coverage is determined by operational travel, destination cycles, access routes and mission demand—not by aesthetically even circles on a map. A station is well placed when it reduces the real time and capability cost of serving its intended area while preserving reserve elsewhere.

Current evidence baseline: 28 July 2026.

Placement decision loop

Map current mission and destination pressure
                 ↓
Identify the route or access bottleneck
                 ↓
Choose candidate station / base / extension sites
                 ↓
Test practical travel and reserve coverage
                 ↓
Commission vehicles and personnel together
                 ↓
Observe the changed mission geography

Seven placement questions

Before building or moving the operational plan, answer:

Demand: Which verified mission families will this site serve?
Route: Which roads, bridges, tunnels, coastlines or rail corridors control travel?
Destination: Where will patients, prisoners or recovery assets go afterwards?
Access: Does the service need launch, runway, railway, off-road or towing access?
Reserve: What remains when the local fleet dispatches?
Specialists: Are trained crews and logistics chains near the vehicles?
Recovery: Where will resources return after the mission completes?

A site that passes only the first question is not operationally validated.

Minimum placement record

Document every proposed site using this table.

Field	Record
Intended mission families	Fire, patient, Police, public order, coastal, railway, airport, etc.
Primary response area	Towns, districts, corridor, coast, airport or remote region
Main route constraints	Bridges, congestion, one-way roads, water crossings, tunnels or rural roads
Destinations	Hospitals, custody, towing/return area or launch base
Required specialists	Command, aerial, HART, dogs, foam, Road Rail, ARFF, towing, etc.
Personnel plan	Commissioning and replacement cohorts
Protected reserve	Capability deliberately retained outside a normal dispatch
Reinforcement source	Neighbouring cluster or alliance contingency
Failure condition	The measurable problem that would justify duplication or relocation

Response clusters

A response cluster is a group of nearby stations that can support ordinary demand and reinforce one another without relying on the whole account.

Recommended cluster components

routine Fire, Police and Ambulance response;
one protected command route;
access to common rescue-support capability;
realistic hospital and custody destinations;
documented specialist reinforcement;
personnel depth that does not borrow one cohort across several vehicles.

Cluster boundary test

The cluster boundary should be based on route time and response independence, not a fixed radius.

Test:

one routine Fire mission;
one patient or Police mission;
protected reserve in the same cluster;
reinforcement from the next cluster;
destination and return time;
one local specialist requirement.

If the next cluster always supplies the basic response, the boundary or station distribution is probably too weak.

Frontline station placement

Fire

Prioritise:

routine mission density;
road access to urban and rural areas;
reinforcement routes;
water and specialist travel;
reserve after multi-appliance dispatch.

Avoid placing every frontline appliance at the specialist hub. Specialist dispatch should not empty ordinary Fire cover.

Police

Prioritise:

incident density;
custody and prisoner-transport routes;
public-order/event geography;
motorway and roads-policing corridors;
armed, dog and air-support reinforcement.

A nearby station can still be operationally distant when prisoner transport or congestion removes vehicles for long periods.

Ambulance

Prioritise:

patient density;
hospital routes and return time;
critical-care and HART geography;
major-incident corridors;
protected transport reserve.

Size and position the network from the complete patient cycle rather than first-arrival distance alone.

Specialist hubs

A specialist hub is useful when several rare capabilities share geography, personnel or support infrastructure. It becomes dangerous when it creates one regional failure point.

Suitable hub functions

command and incident control;
technical rescue and HazMat;
containers and carriers;
HART and mass-casualty support;
public-order transport and supervision;
railway access and investigation;
airfield operations;
Bomb Disposal command/heavy equipment;
Coastguard specialist and towing systems.

Hub safeguards

retain frontline capacity outside the hub;
train replacement cohorts;
distribute at least one hard-blocking capability to a relief zone when demand justifies it;
document which carriers or towing vehicles serve which specialists;
test one major hub incident plus ordinary regional demand.

Relief bases

A relief base protects the network when the primary specialist base is committed.

Recommended uses:

airport ARFF and operations relief;
railway Road Rail/BA/Foam reinforcement;
regional command and mass-casualty reserve;
second coastal towing or vessel route;
remote Mountain/SAR response;
duplicate Bomb Disposal land or marine chain;
Recovery/HGV corridor backup.

A relief base does not need to duplicate every specialist. It should remove the measured single point of failure.

Destination-led placement

Hospitals

Account for:

patient specialisation where published;
transport probability;
long hospital journeys;
vehicle return time;
several simultaneous patient missions.

Do not place Ambulance stations solely around spawn geography while ignoring destinations.

Custody

Account for:

prisoner maxima;
Detention Van and other verified capacity;
transport and return time;
public-order/event surges;
routine patrol cover during custody movements.

Recovery

Account for:

car versus truck asset class;
road corridors and incident clearance;
towing and return time;
HGV extension geography;
emergency services that remain committed during recovery.

Access-led placement

Coastal and Lifeboat

Test:

road access to beaches, harbours, cliffs and marinas;
vessel class and navigable coverage;
Lifeboat 4x4 and trailer pairing;
hovercraft/transporter and mud-decontamination logistics;
aircraft coverage and patient handoff.

Straight-line proximity to water does not prove usable launch access.

Mountain and SAR

Test:

actual off-road approach routes;
custom spawn areas;
command and dog-support travel;
helicopter/HART overlays;
remote patient extraction and return time.

Railway

Test:

railway hubs and corridor direction;
station, crossing, freight and tunnel POIs;
Road Rail access from both sides where relevant;
EIU, BA, Foam and command placement;
Railway Police personnel and HART support.

Airfield

Test:

runway POIs;
primary and relief ARFF bases;
operations, command, foam, water and HazMat access;
HART, Police and hospital geography;
regional reserve outside Code C/F incidents.

Urban placement model

Characteristics

high mission density;
shorter station spacing;
traffic and destination congestion;
greater specialist concurrency;
opportunity to share some reserve.

Recommended pattern

several independently useful clusters;
routine stations around demand and destinations;
specialist hubs with relief capability;
command and HART distributed across the city;
motorway/rail/airport corridors treated separately;
patient and custody throughput measured explicitly.

Rural placement model

Characteristics

lower density but longer travel;
weaker neighbouring reinforcement;
remote patient and custody destinations;
earlier geographic pressure for water, air, off-road and command capability.

Recommended pattern

stronger local frontline reserve;
stations aligned with actual roads and bridges;
regional specialist bases rather than one distant central hub;
air and off-road support where they produce measurable value;
alliance assistance as contingency rather than basic coverage.

Coastal and waterway placement model

separate shore response, inland water, coastal vessels and ocean rescue;
pair trailers with compatible tow vehicles;
distribute Flood Rescue and pumping by river/canal/coast corridors;
preserve launch and return time;
keep Fire, Ambulance and Police handoff capability within reach.

Multi-region account model

Create independently dispatchable regions connected by strategic reinforcement.

Each region should define:

routine response floor;
primary command route;
hard-blocking specialists;
patient/custody/recovery destinations;
reinforcement direction;
alliance contingency;
recovery condition.

Do not treat a specialist as regional reserve when every region depends on the same single vehicle or crew.

Candidate comparison

Compare candidate sites without inventing a weighted score.

Criterion	Candidate A	Candidate B	Candidate C
Routine route coverage
Specialist mission access
Destination cycle
Reinforcement routes
Protected reserve
Personnel/training alignment
Towing/launch/carrier logistics
Major-incident resilience
Recovery positioning

Reject a candidate that fails a hard operational criterion even if it looks favourable elsewhere.

Placement anti-patterns

Anti-pattern	Failure	Correction
Even visual spacing	Stations ignore roads, bridges and destinations	Use real route and mission geography
One giant specialist hub	One incident removes regional capability	Add relief or distribute hard blockers
Station near mission but far from hospital/custody	First arrival improves while full cycle worsens	Model destination and return time
Trailer away from tow vehicle	Specialist exists but cannot dispatch	Pair the logistics chain
Trained staff stored elsewhere	Vehicle appears ready but cannot crew locally	Align cohorts with intended stations
Every rare unit centralised	Distant regions depend on long travel	Duplicate by measured travel or concurrency
Building before response chain	New missions appear without capability	Commission vehicles/personnel first
Alliance assumed as local coverage	Support is unavailable during overlap	Maintain local core reserve

Placement audit workflow

Export or list recent mission pressure by region.
Identify recurring long travel and unavailable-resource messages.
Map hospitals, custody, road corridors, launch points, railway and airport POIs.
Define routine response clusters.
Identify the current hard specialist single points of failure.
Compare candidate sites using the placement record.
Test representative incidents in Fleet Planner.
Preserve protected reserve outside the new site’s intended dispatch.
Activate one controlled expansion.
Observe the changed mission geography before repeating.

Station Placement and Coverage

Placement decision loop

Seven placement questions

Minimum placement record

Response clusters

Recommended cluster components

Cluster boundary test

Frontline station placement

Fire

Police

Ambulance

Specialist hubs

Suitable hub functions

Hub safeguards

Relief bases

Destination-led placement

Hospitals

Custody

Recovery

Access-led placement

Coastal and Lifeboat

Mountain and SAR

Railway

Airfield

Urban placement model

Characteristics

Recommended pattern

Rural placement model

Characteristics

Recommended pattern

Coastal and waterway placement model

Multi-region account model

Candidate comparison

Placement anti-patterns

Placement audit workflow

Placement readiness checklist

Related planning