Mobilisation
The transition period between contract award and full service delivery; includes TUPE consultation, team onboarding, and system setup.
Definition
Mobilisation is the transition period between contract award and full service delivery. It includes TUPE consultation (where staff transfer), team onboarding, system setup, knowledge transfer from the incumbent supplier, security clearances, customer communication, and any necessary procurement of equipment or subcontracts. Mobilisation periods typically run 30-180 days depending on contract complexity; major outsourcing transitions can run 6-12 months. The mobilisation plan is usually a substantial section of the Method Statement and a scored element of the bid.
How it works in practice
Strong mobilisation plans address five workstreams in parallel. First, people: TUPE consultation if staff transfer, recruitment for any new roles, security vetting, induction and training. Second, systems: IT setup, integration with the buyer's environment, data migration, single-sign-on, ongoing operational tooling. Third, knowledge: handover from the incumbent including documentation, shadow operations, escalation playbooks, key contact relationships. Fourth, governance: KPI reporting structure, contract management cadence, change control mechanism, dispute resolution path. Fifth, customer experience: communication to end users, transition messaging, complaint handling during transition. The mobilisation timeline should be milestone-based with go/no-go gates: at gate 1 (typically 30 days in) all staff transferred and onboarded; at gate 2 (60 days) all systems live; at gate 3 (90 days) full service delivery against KPIs. The plan should include risk management for each workstream: what could go wrong, what the mitigation is, who owns the risk. Buyer involvement during mobilisation is substantial: a strong mobilisation plan defines the buyer dependencies explicitly. Mobilisation overspend or delays are common: many post-award disputes originate in the mobilisation period from unrealistic timelines or unclear scope. Treat the mobilisation plan as a contract-binding document; deviation can trigger formal contract management responses.
Common questions
How long should the mobilisation period be?
Depends on contract complexity. Routine services: 30-60 days. Mid-complexity contracts (FM, IT support): 60-120 days. Major outsourcing: 6-12 months. The buyer will state the expected mobilisation in the ITT; bidders should respond with a credible plan that fits the published timeline or, if it does not, propose a longer mobilisation with explicit justification.
What goes wrong in mobilisation?
Common failures include underestimating TUPE complexity (especially pension liabilities), underestimating IT integration effort, weak knowledge transfer from incumbent (leading to operational gaps post-go-live), unclear buyer dependencies (mobilisation stalls waiting on buyer decisions), and aggressive timelines that leave no slack for unexpected issues. Most can be mitigated with disciplined milestone-based planning and explicit dependency management.
Is mobilisation paid for separately or included in the contract price?
Depends on the contract. Some buyers pay mobilisation as a fixed-price discrete phase; others include it in the ongoing service price. The bid should price mobilisation transparently regardless of the commercial structure so the buyer can see the cost being absorbed. Hiding mobilisation cost in ongoing service rates often surfaces as a dispute when actual mobilisation cost exceeds estimates.