Getting Started

Use this section to move from an empty or early account into a sustainable multi-service network without activating mission pressure faster than the fleet, personnel and geography can absorb it.

Start with the operating loop

Build routine Fire, Police or Ambulance capability in a practical response area.
Complete the missions already generated before adding another generator.
Record recurring shortages: quantity, journey time, personnel, training, transport or infrastructure.
Correct the narrowest measured bottleneck.
Protect a useful routine reserve.
Test two representative incidents together.
Expand one controlled step.
Observe the changed mission mix before repeating.

Open Cross-Service Account Progression · Open Account Readiness Planner

First command route

Decision	Use this guide or tool
Understand mission requirement types	Missions and Dispatching
Choose a first or next location	Station Placement and Coverage
Decide whether the first expansion is safe	First Expansion
Review a service fleet and training chain	Emergency Services
Search a specific UK mission	Mission Lookup
Test inventory and protected reserve	Account Readiness Planner
Compare candidate resources	Resource Comparison
Understand buildings and extensions	Buildings and Extensions
Use alliance support safely	Alliance Operations

Foundation readiness

A foundation network should be able to:

dispatch its common local incidents;
leave some useful routine cover after a normal response;
provide correctly staffed and trained units rather than owned-but-unusable vehicles;
handle basic patient or prisoner movements where those services are active;
recover vehicles and personnel to useful geography;
explain which shortages require local correction and which are temporary alliance contingencies.

Do not count a future purchase, untrained vehicle, unavailable crew or unverified substitution as current capability.

Account archetypes

Dense urban

Prioritise short route times, high concurrency, hospital/custody throughput and distributed routine cover. Specialist hubs can work well, but only when ordinary demand remains protected.

Rural

Prioritise road topology, bridge and mountain access, relief locations and travel-time resilience. A resource that exists but cannot reach its mission family promptly is not effective coverage.

Coastal

Separate road response from launch, vessel, trailer, towing and air-rescue chains. Place resources around real access points rather than visual coastline spacing.

Alliance-supported

Alliance support can defer an expensive specialist capability, but should remain a named contingency with known travel time and donor reserve. It must not hide persistent local routine deficits.

First-session checklist

Choose a compact operating area with usable road access.
Build one coherent routine service before scattering stations.
Learn the distinction between guaranteed, alternative, conditional and probabilistic requirements.
Keep personnel and training attached to vehicle decisions.
Check likely hospitals, custody destinations and cross-service partners.
Record mission pressure before purchasing another specialist.
Use the readiness planner with blank fields left unknown rather than guessed.
Expand only after the current network returns to a stable operating state.

Common early mistakes

adding buildings because credits are available rather than because capability is ready;
treating vehicle ownership as proof of trained staffing;
using alliance assistance as permanent routine cover;
placing stations by equal map circles instead of routes and destinations;
activating an extension before its personnel, vehicles and partner services are commissioned;
filling unknown prices, capacities or unlock rules with assumed values;
expanding again before patient, custody or recovery cycles have returned resources to service.

Next step

Continue to First Expansion, then use Cross-Service Account Progression as the long-term roadmap.