First Expansion

The first expansion should remove a measured constraint or add a fully commissionable capability. It should not merely increase the number of mission generators.

Recommendation boundary

No universal credit reserve, station count or service order is asserted. The safe decision depends on current mission pressure, route geography, trained personnel, transport capacity, alliance assumptions and the exact capability being activated.

Five expansion gates

Gate	Question	Pass condition
Evidence	What recurring problem will this expansion solve?	A specific quantity, geography, training, throughput or infrastructure deficit is documented
Routine reserve	Can current common missions still dispatch afterwards?	Useful existing cover remains after the new commitment
Personnel	Can the new vehicles or roles operate immediately?	Commissioning and replacement cohorts are available or scheduled before activation
Geography	Will the capability reach the intended demand?	The proposed location improves real routes, access points or destinations
Cross-service and throughput	Are partner services and post-incident cycles ready?	Patients, prisoners, recovery, command and other hard dependencies can complete

A failed gate does not always mean “never expand”. It means the missing condition should be corrected or explicitly accepted as a temporary risk.

Decision sequence

1. Search the recurring mission or missing capability in Mission Lookup.
2. Review the relevant service guide.
3. Add representative missions to the Account Readiness Planner.
4. Enter only correctly staffed and dispatchable resources.
5. Protect routine and specialist reserve.
6. Review exact gaps, unresolved unknowns and non-exact advisory fields separately.
7. Compare expansion candidates in Resource Comparison.
8. Check the proposed location in Station Placement.
9. Activate one controlled change.
10. Observe the resulting mission mix and recovery cycle before expanding again.

Expand the current service or add another service?

Expand the current service when

• routine incidents regularly consume all local cover;
• the shortage is clearly quantity or journey time;
• a second response cluster would reduce repeated travel delays;
• current personnel and training can support the additional units;
• adding another service would introduce unsupported cross-service demand.

Add another service when

• current missions repeatedly require that service or capability;
• the complete building, vehicle, personnel and training chain can be commissioned;
• its destinations and partner services are ready;
• alliance support is too slow or unreliable for the recurring demand;
• the existing routine network remains protected after the investment.

Specialist-extension gate

Before activating a specialist extension, confirm:

• the extension’s mission family is understood;
• required vehicles, trailers, containers or aircraft are available;
• towing, carrier or launch chains are complete;
• exact personnel roles and verified training contracts are covered;
• command and cross-service dependencies are independent;
• two representative incidents can be handled without silently reusing one unit;
• a recovery plan restores useful cover afterwards.

Financial discipline without invented thresholds

The guide does not publish a universal “minimum credits before expansion” figure. Use a capability budget instead:

1. construction or extension cost where directly verified;
2. required vehicle and equipment purchases where verified;
3. training lead time and temporary staffing loss;
4. destination or supporting-infrastructure work;
5. reserve for corrective purchases after the mission mix changes;
6. operating risk if an unknown value remains unresolved.

An expansion is not affordable merely because the initial building can be purchased.

Urban and rural differences

Urban

• concurrency and destination queues often dominate;
• several smaller response clusters may outperform one central fleet;
• traffic and river crossings can create sharp route boundaries;
• specialist duplication should follow measured overlap.

Rural

• travel time and route topology dominate earlier;
• relief locations and correctly placed off-road capability matter;
• one specialist hub may need wider reserve and alliance contingency;
• hospitals, custody, coast, mountain and railway access can be distant.

Alliance assumptions

Record alliance support as one of:

• routine local — not recommended for a capability the account generates frequently;
• planned regional contingency — named providers, typical travel time and donor reserve are known;
• exceptional escalation — used for rare major incidents rather than ordinary progression.

Do not count “someone in the alliance probably has it” as a passed readiness gate.

Expansion completion checklist

• The measured deficit is documented.
• The complete capability chain is identified.
• Costs and unknowns are separated.
• Vehicles are staffed and trained.
• Routine reserve remains useful.
• Geography and destinations are practical.
• Cross-service dependencies are ready.
• Concurrent reference incidents pass or have explicit contingency.
• Recovery-to-readiness has been considered.
• Only one major generator change will be observed at a time.