Mobilisation plans are consistently the section where UK public sector bidders leave marks on the table. When a buyer allocates 15% of the total quality score to the tender mobilisation methodology, they are not merely checking a box. They are actively testing your operational maturity, your understanding of their specific contract, and your ability to handle the inevitable friction of transitioning a service.
A weak mobilisation plan does more than lose marks in its own section. It undermines the credibility of your entire bid. If you cannot articulate a believable, detailed plan for the first 90 days, evaluators will doubt your ability to deliver the service for the next five years. Conversely, a robust, contract-specific delivery narrative turns your bid into a scoring asset. It proves you have managed complex transitions before and provides the evaluator with the reassurance they need to award you the contract.
This guide breaks down exactly what evaluators are looking for in a mobilisation plan tender response, section by section, and provides the structures and strategies needed to turn a generic 60/100 answer into a winning 85/100 delivery narrative.
What this guide covers
- The true weight and purpose of mobilisation questions in quality evaluations.
- How to structure a credible, phased mobilisation timeline.
- Writing a contract-specific risk register that proves operational experience.
- Managing TUPE and incumbent handover seamlessly.
- Sector-specific compliance nuances across Facilities Management, IT Services, and Construction.
- A detailed worked example of a winning mobilisation response.
- Common mistakes that cost bidders marks, and how to fix them.
- Frequently asked questions about mobilisation planning.
The weight of mobilisation in quality evaluations
In UK public sector procurement, particularly under the Public Contracts Regulations 2015 (PCR 2015) and the Procurement Act 2023 (PA 2023), the mobilisation question is rarely an afterthought. Evaluators routinely assign between 10% and 20% of the total quality score to the implementation plan tender question. On a major multi-year framework or call-off contract, this section alone can dictate the outcome of the bid.
However, the importance of the mobilisation plan extends beyond its standalone weighting. Evaluators read this section to gauge your overall operational credibility. A weak, generic plan undermines the persuasive power of your methodology, quality assurance, and social value responses. The evaluator's underlying thought process is simple: if this bidder cannot articulate a credible, detailed plan for the first 90 days, can they genuinely be trusted to run the contract for its full term?
Conversely, a strong mobilisation plan does the exact opposite. It signals that you have managed complex transitions before, that you understand the buyer's specific constraints, and that you possess the maturity to handle the messy reality of contract commencement. That perception of competence carries into how the rest of the bid is evaluated.
Most bidders fail to score top marks not because their plans are inherently flawed, but because they are entirely generic. Evaluators are exhausted by reading the same boilerplate risk registers, the same vague commitments to "robust planning," and the same undated timelines copied from previous submissions. To move from a middle-tier score to an upper-quartile score, your narrative must prove that you understand the specific mechanics of this particular contract.
Structuring a credible timeline
A high-scoring mobilisation timeline is specific, dated, and accountable. Evaluators are not testing whether your plan is the fastest possible transition; they are testing whether it is the most plausible one. A 12-week mobilisation plan with clear dependencies, named owners, and built-in contingency buffers will always outscore a 4-week plan built entirely on optimism.
The timeline should be broken down into distinct phases, anchoring every activity to the contract award date (Day 0).
Phase 0: Pre-award preparation
The most compelling mobilisation plans begin before the formal contract is even awarded. Detailing your pre-award activities demonstrates a highly proactive posture. This phase should include tentative resource mapping, drafting the necessary TUPE Employee Liability Information (ELI) request templates, alerting key supply chain partners, and protecting the diaries of your core mobilisation team.
Most bidders skip this phase entirely because the contract is not yet won. Including it shows the evaluator that you take mobilisation seriously enough to invest time and planning before you are officially paid to do so. It signals deep professionalism.
Phase 1: Contract award and the first seven days
The first week sets the tone for the entire transition, and evaluators scrutinise this phase heavily. Your narrative must outline immediate, concrete actions. This includes scheduling the formal kick-off meeting with the buyer (and providing a proposed agenda), establishing the governance structure, issuing the formal TUPE ELI request to the incumbent, and commencing weekly progress reporting.
If your Day 1 actions are vague or rely on generic "kick-off" language, the evaluator immediately stops trusting the rest of the plan.
Phase 2: Resourcing, recruitment, and systems
This phase forms the operational backbone of the mobilisation period. It covers TUPE consultation, gap recruitment, training rollout, IT and systems integration, supplier onboarding, and the distribution of uniforms and PPE.
Every single activity in this phase must have a named owner and a specific target completion date. Evaluators often mark this phase directly against the buyer's own stated timeline. If the buyer has specified a six-week mobilisation window, your Phase 2 must align perfectly with that constraint while demonstrating exactly how you will manage parallel workstreams to meet the deadline.
Phase 3: Go-live readiness
Treat the go-live date as a discrete, highly orchestrated event rather than merely the end date on a Gantt chart. Detail the final operational checklists that must be completed before go-live. Outline the physical on-site presence of your Mobilisation Lead and senior management team on Day 1. Specify the communication protocols for the first 24 hours, and clearly define the pre-agreed escalation routes if any element of the service is not fully ready.
A common trap is treating go-live as a date rather than an event. Evaluators want to know exactly what happens on Day 1 to ensure service continuity.
Phase 4: Post-go-live stabilisation
Mobilisation does not magically end on Day 1. Evaluators reward bidders who recognise the critical need for post-go-live stabilisation. Include formal 30-day, 60-day, and 90-day review milestones. Detail exactly when formal KPI reporting will commence and how you will manage the smooth handover from the dedicated mobilisation team to the steady-state operational management team.
Including this stabilisation phase reliably adds marks, as it proves you understand that a contract is only truly mobilised when it is genuinely operational and stable.
Evidencing risk awareness
The risk register is the section where most bidders lose the easiest marks. A generic table listing "supply chain delays," "staff turnover," and "weather" with mitigations like "close monitoring" or "robust planning" will not impress an evaluator. Evaluators have read that exact version a thousand times, and it consistently scores in the low 60s.
A high-scoring risk register is populated with risks that the evaluator actually recognises from their own painful experiences with previous contracts going wrong. Your mitigations must describe verifiable actions rather than abstract feelings. "Robust planning" cannot be verified. "Mobilisation Lead conducts daily stand-up meetings with workstream owners from Day 1 to Day 14, with mandatory escalation to the Operations Director for any task marked red for 48 hours" can be verified.
A credible, contract-specific risk register should address:
- Incumbent TUPE information arriving late or incomplete: This is a near-universal risk in service contracts. The mitigation should specify issuing the information request on Day 1 with a strict 14-day response deadline. If not received, the mitigation must include formal escalation to the buyer's commercial team and the activation of a parallel resource plan based on the original tender pack assumptions.
- TUPE-transferring staff failing right-to-work or vetting checks: A critical risk, especially in secure environments. The mitigation should include a pre-go-live verification window and pre-booked contingency agency cover at a specified percentage of headcount.
- Specialist licences lapsing during the consultation period: For example, SIA licences for security, CSCS cards for FM trades, or food hygiene certificates for catering. The mitigation should detail a Day 1 licence audit and pre-approved funding for immediate renewals to prevent any break in service.
- Buyer-side delays: Risks such as delays in providing data, building access, IT credentials, or security passes. The mitigation should outline a weekly RAG (Red, Amber, Green) report submitted to the buyer with explicit action owners and a written escalation route directly into the procurement team.
If your risk register includes specific, actionable versions of these risks, you are immediately ahead of the vast majority of the field.
Managing TUPE and incumbent handover
For any service contract involving an incumbent supplier (which covers almost every facilities management, cleaning, security, or IT support contract you will bid for), the handling of TUPE is the single most heavily scrutinised element of the mobilisation plan. Mishandling the TUPE narrative is a fast track to a failing score. Get it right and you reassure the evaluator. Get it wrong and the rest of the bid is fighting an uphill battle.
Evaluators are looking for a clear, legally compliant sequence with highly realistic dates.
You must specify that the formal request for Employee Liability Information (ELI) will be issued within 24 hours of contract award, asking the buyer to obtain this from the incumbent under TUPE Regulation 11. You need to detail the ELI review window, typically 21 days before transfer, naming the specific legal or HR oversight responsible for analysing the data and managing clarification questions.
The consultation process must be explicitly outlined, noting that it will commence at least 30 days before transfer where reasonably practicable. You must reference the "measures" letter, the formal communication of any changes the new employer plans to make to working conditions, such as aligning pay dates, changing pension providers, or altering reporting lines. Bidders who fail to mention measures demonstrate a lack of practical TUPE experience.
Finally, your Day 1 continuity plan must reassure the evaluator that transferring staff will experience a seamless transition. This means detailing how payroll will be processed without interruption, how terms and conditions will be transferred, how new line management will be introduced, and how uniforms and ID badges will be provided on or before Day 1.
The ultimate test of your TUPE narrative is empathy: would a transferring employee feel reassured reading your plan? Write to that audience, and you will score highly.
Sector-specific compliance and nuance
Most generic "how to write a mobilisation plan" advice is sector-agnostic. The reality is that the same generic plan will score differently depending on what the specific buyer is actually worried about. Your narrative must pivot to address the unique compliance and operational hurdles of the industry.
| Sector | Buyer's Primary Concern | Marks-Winning Detail |
|---|---|---|
| Facilities Management | Statutory compliance continuity (asbestos, fire, water hygiene) | Compliance handover sequence and CAFM data migration plan |
| IT Services | Data security, uptime, and user disruption | Rollback contingency plan and parallel running phase |
| Construction / Minor Works | CDM compliance, supply chain readiness, out-of-hours response | Day 1 emergency call-handling worked example |
Facilities Management
In hard and soft FM contracts, buyers are primarily concerned with the continuity of statutory compliance. Your mobilisation plan must explicitly detail how you will take over the asbestos register, verify that fire risk assessments are current, and manage water hygiene records. You must also address the handover of the CAFM (Computer-Aided Facility Management) system and ensure that planned preventative maintenance (PPM) schedules are transferred without any missed jobs. The marks-winning detail here is the statutory compliance handover sequence, showing exactly how you deal with the inevitable gaps in the incumbent's records.
IT Services
For IT and managed services contracts, the focus shifts entirely to data security, system uptime, and minimising user disruption. The mobilisation narrative must cover data migration protocols, API integration testing, and parallel running phases. Buyers will look for highly detailed contingency plans for rollback scenarios if the cutover fails. Furthermore, you must provide clear communication strategies for end-users to minimise helpdesk spikes during the transition period.
Construction
In construction, repair, maintenance, and minor works frameworks, buyers prioritise site safety, supply chain readiness, and strict adherence to CDM (Construction (Design and Management) Regulations). Your plan must demonstrate exactly how you will establish site welfare facilities, onboard and vet sub-contractors, and ensure that out-of-hours response capabilities are fully live from Day 1. Providing a worked example of how a first-call emergency repair would be handled during Week 1 adds significant credibility to your response.
Worked example
Below is a comparison of a typical generic response versus a high-scoring, specific response to a standard mobilisation question. This is an illustrative example, built to reflect the kind of FM contract commonly awarded through CCS frameworks such as RM6232 (Total Facilities Management). The question is: "Describe how you will mobilise this contract within the eight-week period required, including how you will manage TUPE and mitigate key risks."
The generic approach (Scores 50-60%)
"Following contract award, our experienced mobilisation team will work closely with the Authority to ensure a smooth and seamless transition. We have a proven track record of mobilising contracts of this size and complexity, and we will follow our standard mobilisation methodology to deliver an on-time go-live within the 8-week period. TUPE will be managed in accordance with all relevant regulations, and we will consult with affected employees in line with statutory requirements. Risks will be identified and managed through our risk management framework, with mitigations put in place to ensure successful delivery. We will provide regular progress updates to the Authority throughout the mobilisation period."
Why it fails: This response contains no dates, no names, no specifics, no recognisable risks, no actual TUPE process, no past evidence, and no Day 1 detail. Every single clause could be copy-pasted from any other bid. An evaluator reads this in 15 seconds and immediately forgets it.
The credible delivery narrative (Scores 85%+)
"Our 8-week mobilisation will be led by Sarah Jenkins (Mobilisation Lead, 12 years’ experience, including the successful transition of the £4m DWP regional contract in 2024), with our Operations Director as the senior accountable owner.
Phase 1 (Award + Days 1-7): We will issue the formal TUPE ELI request within 24 hours of award. The kick-off meeting with the Authority will occur by Day 5 to agree on the CAFM data migration schedule and establish the weekly RAG reporting format.
Phase 2 (Weeks 2-6): We anticipate 45 colleagues will transfer. ELI will be reviewed by our HR Business Partner in Days 8-21. Formal consultation commences on Day 22 at the regional office. A 'measures' letter will be issued on Day 25 to address the alignment of payroll dates. Day-1 readiness (right-to-work, vetting, and uniform sizing) will be audited in Week 6. We have pre-booked agency contingency at 10% of headcount to mitigate any late vetting failures.
Phase 3 (Go-Live & Stabilisation): Sarah Jenkins will be on-site for the first 48 hours to oversee the transition. We will conduct formal 30, 60, and 90-day stabilisation reviews, with steady-state KPI reporting commencing at the 30-day mark.
Top Risk Mitigation: If ELI is received late or incomplete from the incumbent, we will activate a parallel resource plan based on the tender pack assumptions and formally escalate to the Authority's commercial team by Day 14 to prevent delays to the consultation window."
Why it wins: Nothing about the underlying capability of the bidder has changed. Everything about how it is evidenced has changed. The specificity is what moves the score. It includes named accountability, dated timelines, a real TUPE process, and a highly specific risk mitigation.
Common mistakes
- Failing to name the team.
The mistake: Relying on vague phrases like "our senior management team" or "our dedicated mobilisation unit." What to do instead: Name your Mobilisation Lead and key workstream owners. Even if you use placeholders pending recruitment, providing a role profile, years of experience, and an accountability matrix (RACI) proves you have a structured approach.
- Treating go-live as the end of the plan.
The mistake: Ending the timeline abruptly on the contract start date. What to do instead: Extend your timeline to include 30, 60, and 90-day post-go-live reviews. Evaluators want to see exactly how you transition from mobilisation to business-as-usual.
- Writing a generic risk register.
The mistake: Listing generic risks like "weather" or "delays" with mitigations like "robust planning." What to do instead: Populate your risk register with contract-specific threats. Address incumbent non-cooperation, vetting delays, and data migration failures, providing verifiable, actionable mitigations for each.
- Glossing over TUPE measures.
The mistake: Stating "we will comply with TUPE regulations" without detailing the process. What to do instead: Explicitly mention the consultation process and the issuance of a "measures" letter. Detail exactly how you will handle the practicalities of Day 1 for transferring staff, including payroll and uniforms.
- Ignoring buyer dependencies.
The mistake: Assuming the buyer will perfectly execute their side of the transition without prompting. What to do instead: Clearly state what you need from the buyer and when you need it (e.g., building access, IT credentials, incumbent data). Show how you will escalate issues if the buyer fails to meet these dependencies.
- Submitting an undated timeline.
The mistake: Providing a list of tasks without attaching them to specific timeframes. What to do instead: Use relative dates (e.g., "Award + 14 days" or "Week 3") for every single milestone. An undated list of tasks is merely a checklist, not a mobilisation plan.
Frequently asked questions
How much detail should I include if the word count is strictly limited?
Prioritise the timeline, the named accountability structure, and the contract-specific risk mitigations. If space is tight, use a Gantt chart or a RACI matrix to convey complex scheduling and ownership information efficiently. This saves your precious word count for the detailed TUPE narrative and specific risk management strategies.
What if we do not have a dedicated, full-time mobilisation team?
You do not need a permanent, standalone mobilisation department to score well, especially as an SME. You simply need to identify who within your operational or project management team will act as the Mobilisation Lead for the transition period, and clearly articulate how their normal duties will be backfilled to give them the necessary capacity to focus on the mobilisation.
How do we handle incumbent suppliers who refuse to share information?
Your risk register must explicitly address this scenario, as it is incredibly common. State that you will issue information requests immediately upon award, set clear deadlines, and define a formal escalation path to the buyer's procurement team if the incumbent obstructs the process. Crucially, outline your parallel contingency plan for resourcing the contract without the incumbent's data.
Should we include pricing for mobilisation?
Only if the pricing schedule explicitly asks for it, or if the buyer allows a separate mobilisation fee. In most UK public sector tenders, mobilisation costs are expected to be amortised across the life of the contract or absorbed as an overhead. Always check the ITT instructions before detailing costs in the quality response.
How do we demonstrate past mobilisation experience if we are bidding for a contract larger than anything we have delivered before?
Focus on the transferable elements of your track record rather than trying to match the contract scale exactly. Evaluators are looking for evidence that you have managed the key risks, such as TUPE, system integration, and supply chain onboarding, not that you have delivered an identical contract. Quantify what you have done: number of sites, number of transferring staff, the mobilisation timeline achieved, and any specific challenges overcome. A well-evidenced smaller contract is far more persuasive than a vague claim about a larger one.
