Cross-Service Account Progression

A strong MissionChief UK account expands mission generation only when the current network can absorb the additional vehicles, personnel, patients, prisoners, towing, command and travel-time pressure. Station count alone does not prove readiness.

Current evidence baseline: 28 July 2026.

The universal decision loop

Observe current mission pressure
              ↓
Identify the narrowest bottleneck
              ↓
Correct quantity, geography, training or infrastructure
              ↓
Test simultaneous demand with protected reserve
              ↓
Restore the network to Ready
              ↓
Activate one controlled expansion
              ↓
Observe the changed mission mix

Do not add several generators at once when one controlled activation can reveal the real constraint.

Open Mission Lookup · Open Concurrent Fleet Planner · Compare Resources

Eight universal expansion gates

Gate	Question	Recommended pass condition
Routine reserve	Can ordinary Fire, Police and Ambulance demand continue after a normal dispatch?	Useful staffed frontline capacity remains in each primary response cluster
Personnel	Are the required qualifications and mission personnel actually available?	Vehicles and trained cohorts can dispatch simultaneously without hidden sharing
Geography	Will the new resource reach the missions, destinations or access points it is intended to serve?	Real route coverage improves rather than only filling a visual map gap
Cross-service chain	Are partner services and handoffs ready?	No mission family depends on an uncommissioned Police, Ambulance, Fire, HART, SAR, maritime or railway capability
Command and support	Can independent command, welfare, mass-casualty and specialist-support rows be met?	Each published group has its own valid resource allocation
Throughput	Can patients, prisoners, recovery assets and returning vehicles complete the full cycle?	Transport and return time do not silently exhaust the fleet
Concurrency	Can two representative incidents operate together?	No vehicle, trailer, carrier, crew or specialist role is counted twice
Recovery	Can the network return to useful geography after the incidents clear?	The selected stress scenario can be run again with protected reserve

When one gate fails, correct it before expanding. A new building rarely fixes a personnel, destination or geographic bottleneck by itself.

State	Recommended meaning	Expansion posture
Ready	Current representative missions can dispatch while protected routine and specialist reserve remains	One controlled expansion may proceed
Watch	Reserve exists, but one capability or region is approaching its floor	Observe and correct before further specialist activation
Degraded	Current missions can finish, but a critical service, specialist or response zone has no independent reserve	Stop expansion and rebuild the depleted chain
Recovery	Incidents are clearing, but vehicles, crews, patients, prisoners or towing assets have not returned to useful positions	Do not treat completion as restored readiness
Unavailable	Another reference incident requires alliance assistance or leaves essential calls unsupported	Restore local core capacity before adding generators

Stage 1 — Tri-service foundation

Build the first operational network around routine Fire, Police and Ambulance demand.

Objectives

staffed frontline Fire capacity with useful reserve;
routine Police Cars with patrol and custody headroom;
Ambulances positioned for treatment, transport and hospital return;
practical station geography rather than equal visual spacing;
enough funds and personnel to recover from ordinary overlap.

Service	Foundation capability
Fire and Rescue	Frontline pumping, one useful reserve route and emerging Rescue Support/command awareness
Police	Routine patrol capacity, prisoner-handling awareness and protected local response
Ambulance	Treatment/transport capacity sized from patient cycle time rather than station count

Do not progress when

one routine incident empties the local Fire fleet;
Ambulances remain away at hospitals while new patients queue;
Police custody journeys remove every nearby unit;
the next station is selected only because the map looks empty;
personnel are assumed rather than assigned.

Open Fire progression · Open Police progression · Open Ambulance progression

Stage 2 — First specialist capability

Choose the first specialist from observed mission pressure rather than a universal purchase list.

Common first-pressure families

Pressure	Likely planning response	Evidence check
Repeated rescue-support delays	Commission Rescue Support or verified dual-capability response	Mission Lookup and Fire guide
Command groups appearing	Train and distribute the relevant Fire, Ambulance or service command route	Preserve independent alternative groups
Repeated aerial demand	Add the verified aerial capability within realistic travel time	Do not invent missing economics
Armed, roads or dog demand	Commission the relevant Police vehicle and education	Keep routine patrol reserve separate
HART demand	Build the full PRV/SRV/training/command chain	Do not buy uncrewed specialist vehicles
Coastal or mountain demand	Commission the complete access, towing, vessel or off-road system	Preserve exact resource classes

Specialist commissioning rule

Verified mission pressure
          ↓
Correct infrastructure
          ↓
Vehicle / trailer / vessel / equipment
          ↓
Qualified personnel
          ↓
Carrier / towing / launch path
          ↓
Geographic placement
          ↓
Replacement depth

Owning only one link in this chain does not create operational capability.

Stage 3 — Stable regional clusters

Move from individual stations to independently functional response clusters.

A response cluster should contain

routine Fire, Police and Ambulance capacity;
one protected local command route;
access to common technical-rescue and specialist support;
realistic hospital and custody destinations;
documented reinforcement routes from neighbouring clusters;
enough trained personnel to avoid implicit double assignment.

Cluster test

Select one representative Fire mission.
Add one patient or Police-heavy mission.
Dispatch the guaranteed requirements in Fleet Planner.
Allocate every alternative group independently.
Keep a documented local response floor outside the incidents.
Confirm patient, custody and return-time pressure.
Mark the cluster Ready only when the resources return to useful positions.

Stage 4 — Service specialisation

Expand into the service whose complete response chain is already closest to readiness.

Service progression matrix

Programme	Activate when	Principal hidden bottlenecks
Fire specialists	Frontline and command reserve survives extension-driven incidents	Training, carrier/pod availability, water/foam distinction
Ambulance and HART	Routine transport remains resilient during specialist dispatch	Patient throughput, command, welfare, SORT/HART cohorts
Police and Public Safety	Patrol, supervision and custody remain available	Educated officer cohorts, prisoner capacity, specialist geography
Coastguard and Lifeboat	Shore, vessel, towing and trained crew chains are complete	Launch access, tow vehicles, vessel class, patient handoff
Mountain Rescue / SAR	Off-road, command, dog, aerial and personnel chains are ready	Alternative groups, remote travel, active-Drone semantics
Bomb Disposal	Crew/equipment and partner services are ready before HQ growth	Command/heavy/diver resources, active Drone, HART/Police/Coastguard
Airfield Operations	ARFF, operations, water/foam/HazMat and medical systems are complete	Training, independent command groups, mass-casualty pressure
Recovery / HGV	Towing outcomes can be cleared without inventing response rows	Asset class, corridor geography, towing-return time
Railway	Railway Police, rail access and cross-service specialists are commissioned	EIU, Road Rail, BA/Foam, personnel, command and tunnel geography

Open the completed service programme

Stage 5 — Cross-service integration

At this stage, expansion decisions should be based on shared dependencies rather than individual service pages.

Cross-service dependency matrix

Mission family	Primary systems	Frequent partner systems
Major urban Fire	Fire, command, technical rescue	Ambulance/HART, Police, mass casualty, welfare
Public order	Police personnel, supervision and transport	Ambulance, custody, dogs, mounted response
Airfield	ARFF, operations, foam, water and command	HART, mass casualty, Police, HazMat, hospitals
Railway	Railway Police, EIU, Road Rail and Fire support	HART, Ambulance command, SAR, dogs, HazMat
Flood / inland water	Flood Rescue, pumping and water access	Fire, Coastguard/Lifeboat, Police, HART
Maritime	Shore, vessel, towing and air rescue	Ambulance, Police, Fire, Bomb Disposal
Mountain / SAR	Off-road, search command, dogs and aerial search	HART, Fire, Police, Coastguard helicopter
Bomb Disposal	Crew/equipment, command and infrastructure	Fire, Police, HART, Coastguard/Lifeboat, Railway
Recovery	Car/truck towing outcome	Fire, Police, Ambulance, Roads Policing

Integration rule

Do not activate a mission family because the primary service alone is ready. Activate it when every hard partner dependency can operate with reserve.

Stage 6 — Major-incident resilience

Prepare the account for overlapping high-load missions rather than one record at a time.

Required operating layers

Incident response — every guaranteed, alternative, personnel and patient field can be supported.
Protected local reserve — routine missions still dispatch in exposed regions.
Strategic specialist reserve — command, aerial, welfare, mass-casualty, towing and access resources are not single points of failure.
Regional reinforcement — neighbouring clusters support the incident without emptying themselves.
Alliance contingency — exceptional peaks can request support without hiding permanent local gaps.
Recovery — the network returns to useful geography before more generators activate.

Reference stress test

Choose two incidents from different mission families, for example:

major Fire plus public order;
airfield plus railway;
flood plus remote search;
Bomb Disposal harbour plus ordinary urban demand;
patient-heavy major incident plus HGV recovery.

Use verified guaranteed rows, preserve every alternative group, and leave patient/transport conversion unknown unless published.

Stage 7 — Mature regional network

A mature account is not defined by a station total. It is a network that can:

operate several response clusters independently;
absorb specialist and major incidents without regional collapse;
sustain trained replacement cohorts;
maintain patient, custody, towing and launch throughput;
distribute rare resources by travel time;
use alliance support as contingency rather than routine dependency;
recover deterministically after large incidents;
add new game content through the evidence workflow without inventing values.

Mature operating cadence

Cadence	Review
Per expansion	Readiness gates, exact mission pressure and funding recovery
Weekly or periodic	Unmet requirements, long travel, patient/custody queues and specialist reuse
After major incident	Reserve erosion and recovery-to-readiness
After game update	Mission, vehicle, training and infrastructure evidence drift
Before new service family	Complete cross-service commissioning test

Account archetypes

Dense urban account

Shorter travel permits some shared reserve.
Hospital and custody throughput can dominate despite close stations.
Distribute rare specialists to avoid congestion and simultaneous-demand failures.
Use several smaller response clusters rather than one giant central fleet.

Rural or dispersed account

Local reserve matters more because neighbours may be distant.
Water, air, off-road, command and patient transport can require earlier geographic duplication.
Station placement should follow real road corridors and destinations.
Alliance support may cover rare peaks but should not replace local core response.

Coastal and waterway account

Shore response, launch points, vessel class and towing form the placement model.
Flood, Coastguard, Lifeboat, Fire and Ambulance capability overlap.
Preserve coastal and inland-water systems separately.
Include patients, prisoners and return-to-launch time.

Alliance-supported account

Build enough local routine capacity to contribute safely.
Record which rare capabilities are realistically available from allies.
Avoid several members relying on the same single alliance specialist.
Agree request, dispatch and release etiquette before major incidents.

Expansion stop conditions

Pause expansion when any of these is true:

the account is Degraded or in Recovery;
a new extension would generate missions without the complete response chain;
one trained cohort is counted across several vehicles;
patient or custody throughput is persistently growing;
a rare command, welfare, aerial, towing or access resource has no replacement;
the next station does not improve practical route coverage;
alliance support is the only solution for routine incidents;
missing evidence is being treated as zero or as an assumed game rule.

Recovery-to-readiness

After any high-load period:

list vehicles, aircraft, vessels, trailers, containers and crews still committed;
restore routine Fire, Police and Ambulance cover in exposed clusters;
restore command and hard-blocking specialists;
rebuild patient, custody, towing and destination throughput;
return rare resources to their intended geography;
restore trained replacement cohorts;
rerun the selected stress scenario;
correct recurring deficits before another expansion.