Fire and Rescue Service
The Fire and Rescue Service is the broadest operational expansion route in MissionChief UK. A strong fire estate is not simply a large collection of appliances: it is a network with enough frontline capacity for routine demand, enough reserve to absorb simultaneous incidents, and specialist capability distributed where it can arrive in time.
Current evidence baseline: 27 July 2026. The guide links to the complete canonical mission catalogue and the 100%-resolved resource decision estate, but unpublished game values remain unknown.
Command doctrine
Section titled “Command doctrine”Use this order when expanding:
- Frontline capacity first — routine incidents should not consume every available pumping appliance.
- Geographic coverage second — a specialist that is always too far away is not operationally available.
- Personnel before hardware — buy or activate trained capability only when its crew can be sustained.
- Specialists in response to evidence — add capability because your mission mix requires it, not because a vehicle exists in the market.
- Resilience before another service — expansion is safer when the current fire network can survive overlapping calls without relying on the alliance for every reserve move.
Five expansion gates
Section titled “Five expansion gates”Treat a new station, extension or specialist purchase as ready only when all relevant gates are satisfied.
| Gate | Question | Pass condition |
|---|---|---|
| Frontline reserve | Can routine missions be dispatched without emptying the area? | At least one useful frontline appliance remains available across the local response cluster after a normal dispatch. |
| Geography | Will the new unit reach the incidents it is intended to cover? | Placement improves actual road response coverage rather than only filling a visual map gap. |
| Personnel | Can the vehicle be crewed today and after simultaneous dispatches? | The required trained personnel are assigned locally with operational reserve. |
| Evidence | Is the capability appearing in your current mission pressure? | Mission Lookup or recent dispatch history shows a repeated requirement, probability or prerequisite. |
| Recovery | Can the account absorb the purchase without stopping essential growth? | The purchase does not consume the funds needed for frontline replacement, staffing or the next planned station. |
Frontline pumping capacity
Section titled “Frontline pumping capacity”Frontline appliances create the operational base from which every specialist fleet works. The exact appliance chosen may provide additional capability, but the planning question remains the same: how many independent incidents can the network support before specialist availability collapses?
Recommended reserve model
Section titled “Recommended reserve model”Use response clusters rather than treating each station in isolation.
- Keep one reserve frontline appliance for every three to four appliances routinely committed at the same time.
- In a dense urban area, neighbouring stations may share that reserve when travel times are short.
- In rural or separated areas, keep the reserve physically closer to the demand because neighbouring coverage may be too slow.
- Do not count an appliance as reserve when its crew is normally borrowed by a specialist vehicle.
This is a planning ratio, not a MissionChief requirement.
Verified capability reference
Section titled “Verified capability reference”The table below uses the current canonical resource records. Missing purchase, staffing or building data remains intentionally absent.
| Resource | Evidence-backed function | Published operational detail | Planning use |
|---|---|---|---|
| Rescue Pump | Community-reported combined fire-engine and rescue-support capability | Community catalogue: 19,000 credits, 25 coins, maximum crew 9 | Potentially reduces duplicated frontline/rescue-support purchases, but verify the current market before treating the value as authoritative. |
| Water Ladder with CAFS | Verified firefighting, foam response and compressed-air foam capability | 17,300 credits, 10 coins, crew 2–9; requires a Fire Station with Fire Support | A verified route to combine frontline and foam capability where the Fire Support requirement fits the station plan. |
| Aerial Appliance Truck | Verified possible specialist requirement on current UK missions | Cost, staffing, training and station restrictions are not yet published in the canonical record | Add after aerial demand appears; do not invent a purchase threshold from the absence of data. |
| Fire Officer | Verified deployable incident-command capability | Distinct from personnel-role fields | Distribute command coverage rather than placing every officer at one central station. |
| Water Carrier | Verified bulk-water-supply capability | Guaranteed on current UK airfield incident pages represented in the source record | Useful for water-demand and airfield planning; place with travel-time coverage in mind. |
| HazMat Unit | Verified hazardous-materials response | Requires the HazMat course: 3 days at the Fire Academy | Train the crew before the vehicle becomes part of the dispatch plan. |
Open the complete Vehicle Catalogue · Review 100% field-resolution status
Specialist capability order
Section titled “Specialist capability order”There is no single compulsory purchase order for every account. The following sequence is a recommended risk order for a general-purpose fire network.
1. Rescue-support coverage
Section titled “1. Rescue-support coverage”Secure rescue-support capability without removing too much frontline pumping capacity. A dual-capability appliance may help where its evidence and current market details are acceptable, while a separate specialist unit may provide clearer availability in a larger network.
2. Command coverage
Section titled “2. Command coverage”Introduce Fire Officer capability when command requirements become regular enough that alliance borrowing or long-distance response delays incidents. Spread command units across response clusters as the account grows.
3. Aerial coverage
Section titled “3. Aerial coverage”Add aerial capability once the current mission mix produces verified aerial requirements or probabilities. A single central unit can cover an early compact network; a wider network usually benefits more from geographic duplication than from stacking multiple aerials at one station.
4. Water and foam capability
Section titled “4. Water and foam capability”Treat water supply and foam as different operational needs. The Water Ladder with CAFS is a verified foam-capable appliance with published cost, staffing and Fire Support compatibility. Water Carrier capability is separately verified for bulk-water demand. Review the mission rather than assuming one replaces the other.
5. HazMat and technical rescue
Section titled “5. HazMat and technical rescue”HazMat requires trained personnel, so the three-day course is part of the purchase decision. Technical Rescue Extensions are verified as countable mission-generation preconditions, while compatible buildings, price and construction details remain unpublished in the current canonical record. Activating mission generation before response capability is ready can create avoidable pressure.
Open specialist extension and container playbooks · Review Buildings & Extensions · Review Training & Personnel
Recommended fleet templates
Section titled “Recommended fleet templates”These templates describe capability slots, not mandatory game requirements. Adjust them for geography, mission generation, alliance support and the actual vehicles available to the account.
Foundation network
Section titled “Foundation network”Suitable for a compact early fire estate.
| Capability | Recommended position |
|---|---|
| Frontline pumping | 4–6 appliances across the local coverage area |
| Operational reserve | 1 frontline appliance not committed by a normal dispatch |
| Rescue support | 1 available capability when repeated mission demand appears |
| Command | Alliance-backed initially, then 1 local Fire Officer when delays become regular |
| Aerial | 1 centrally placed unit after verified demand appears |
| Foam, water and HazMat | Add only against demonstrated mission pressure and personnel readiness |
Developing network
Section titled “Developing network”Suitable when several incidents are commonly active together.
| Capability | Recommended position |
|---|---|
| Frontline pumping | 8–12 appliances across two or more response clusters |
| Operational reserve | At least 2 useful frontline appliances across the network |
| Rescue support | 1 per main operating cluster or enough dual-capability coverage to avoid a single point of failure |
| Command | 1–2 Fire Officers distributed geographically |
| Aerial | 1 per broad coverage zone where one unit no longer reaches demand reliably |
| Foam and water | At least one available capability of each type when the mission mix regularly calls for them |
| HazMat | One trained response group, with replacement personnel planned before duplication |
Established network
Section titled “Established network”Suitable for a wide account handling sustained concurrency.
| Capability | Recommended position |
|---|---|
| Frontline pumping | Size by measured concurrent demand, with reserve maintained in every major cluster |
| Command and aerial | Duplicate by travel-time zone rather than station count alone |
| Rescue support | No single unit should be the only response for the entire account |
| Water, foam and HazMat | Distributed according to mission geography and extension-driven generation |
| Containers and carriers | Planned as a logistics system: carrier availability must be assessed separately from container ownership |
| Personnel reserve | Trained crews available for simultaneous incidents, leave, reassignment and future vehicles |
Urban and rural planning
Section titled “Urban and rural planning”Urban or dense network
Section titled “Urban or dense network”- Shorter travel times allow neighbouring stations to share some reserve.
- Specialist duplication can follow incident concurrency rather than distance alone.
- Avoid over-centralising: traffic and simultaneous missions can still make a central specialist unavailable.
- Smaller response clusters should remain independently functional during large incidents.
Rural or dispersed network
Section titled “Rural or dispersed network”- Distance makes geographic duplication more important.
- Keep frontline reserve local rather than relying on a distant station.
- Water supply, technical rescue and specialist response may need forward placement before incident frequency alone appears to justify it.
- Use actual route times when comparing station sites.
Alliance-supported account
Section titled “Alliance-supported account”- Alliance support can cover rare specialists during early growth.
- Do not treat voluntary alliance response as guaranteed reserve.
- Build local capability when repeated borrowing delays completion or prevents independent play.
- Keep enough frontline capacity to contribute without leaving your own area empty.
Use the intelligence tools before buying
Section titled “Use the intelligence tools before buying”Mission Lookup
Section titled “Mission Lookup”Use Mission Lookup to inspect current requirements, alternatives, probabilities, patients, personnel and prerequisites. Search the missions actually appearing in your area rather than buying from a generic list.
Concurrent Fleet Planner
Section titled “Concurrent Fleet Planner”Use the Concurrent Fleet Planner to multiply guaranteed requirements across several incidents. This exposes whether the shortage is frontline volume, a specialist single point of failure, or trained personnel.
Resource Comparison
Section titled “Resource Comparison”Use Resource Comparison before choosing between apparently similar appliances. Compare verified capabilities and leave unknown fields unknown.
Command search
Section titled “Command search”Press Ctrl+K, ⌘K or / anywhere in the guide to search missions, resources, infrastructure and qualifications together.
Common expansion failures
Section titled “Common expansion failures”| Failure | Operational symptom | Correction |
|---|---|---|
| Buying specialists before pumps | Specialist vehicles remain available while routine missions wait for fire engines | Restore frontline and reserve capacity first |
| Activating extensions too early | New mission families appear before the response fleet or trained personnel are ready | Delay activation until the full capability chain is staffed |
| Centralising every specialist | Long travel times and one large incident remove capability from the whole account | Duplicate by response zone |
| Counting parked vehicles instead of staffed vehicles | The fleet looks complete but cannot dispatch concurrently | Audit trained personnel and crew assignment |
| Treating probability as guarantee | Too many units are permanently tied up covering occasional requirements | Use the mission probability and concurrency tools |
| Treating unknown as zero | Missing cost, crew or restriction data becomes an unsafe assumption | Keep the field unknown until a reproducible source is added |
Operational readiness checklist
Section titled “Operational readiness checklist”Before the next fire expansion, confirm:
- normal dispatches leave useful frontline reserve;
- the proposed station or specialist improves actual route coverage;
- required training is complete before operational activation;
- mission demand is verified through Mission Lookup or account history;
- extensions will not generate missions the fleet cannot support;
- specialist resources are not concentrated into one failure point;
- carriers, containers and crews are planned as separate resources;
- alliance assistance is treated as support, not guaranteed local capacity;
- unpublished values remain explicitly unknown;
- the purchase still leaves funds for staffing and the next essential frontline step.
Stage 37A continuation
Section titled “Stage 37A continuation”Batch 1 establishes the progression foundation. Batch 2 adds the specialist extension and container logistics playbooks. Later batches will cover training pipelines, airfield and railway coverage, wildfire and water-rescue planning, and mission-family pressure analysis from the complete canonical catalogue.