How to Write a Mobilisation Plan That Wins Marks

Under the Procurement Act 2023, award criteria (s.23) test the comparative quality of what you are offering, separately from the pass/fail conditions of participation (s.22) that check your insurance, financial standing and certificates. Mobilisation almost always sits in the scored quality section, and it is scored for one reason: it is a proxy for delivery risk. The buyer cannot watch you run the service before they award it, so they read your transition plan as the best available evidence of whether you will actually turn up and perform.

This is where a credible plan quietly beats a cheaper bid. On a most-advantageous-tender evaluation, price is only one axis. If your mobilisation answer scores a 4 and a rival's scores a 2, that quality gap can outweigh a lower headline price once the weightings are applied. A vague transition promise reads as delivery risk, and delivery risk is exactly what a public buyer is trying to price out of the decision.

The evaluators are also thinking about their own exposure. A failed contract start means a service interruption, an internal post-mortem, and sometimes a challenge from the incumbent. A mobilisation plan that shows you understand their risk, not just yours, signals that you will be a safe pair of hands. That is worth marks in a way generic reassurance never is.

The spine of any mobilisation plan is a dated timeline running from contract award to the go-live date - the day the service is fully operational. Do not write it as vague phases. Anchor it to the actual dates in the ITT: the anticipated award date, the standstill period (8 working days for above-threshold contracts), and the contract start date the buyer has published. Work backwards from go-live and show what happens in each week.

Structure the timeline around the milestones that actually determine whether you start on time:

• ·Week 0-1: contract award confirmed, standstill cleared, mobilisation manager appointed, kick-off meeting with the buyer scheduled, and (where relevant) TUPE consultation opened with the outgoing provider.
• ·Weeks 1-3: due diligence on transferring staff and assets, systems provisioning, DBS or security clearances started (these have long lead times - flag them early), and any premises or access arrangements confirmed.
• ·Weeks 3-6: staff transferred or recruited, training and induction delivered, IT and reporting systems tested against the contract's KPI requirements, and a service readiness review with the buyer.
• ·Final week: go-live rehearsal or soft launch where the contract allows it, sign-off against a readiness checklist, and confirmation that day-1 cover is in place.
• ·Day 1 onwards: hypercare or enhanced-support period, with a named contact and a defined date when the service moves to business-as-usual.

A timeline that lists every task as equally important tells the evaluator nothing about where the real danger sits. Name the two or three items that, if they slip, delay everything else - usually clearances, TUPE consultation, or system integration - and show what you do to protect them.

This is the difference between a plan that looks organised and one that reads as experienced. Evaluators reward a bidder who has spotted the genuine bottlenecks and built slack around them over one who has drawn a tidy but generic chart where nothing is prioritised.

Where a milestone depends on the buyer or the outgoing provider doing something - handing over data, giving site access, releasing employee liability information - say so, and give the date you need it by. Showing the dependencies you do not control, and how you will chase them, tells the evaluator you have run a real mobilisation before and know where they stall.

If the contract involves taking over a service currently delivered by someone else - a cleaning contract, an FM contract, a care service, a bus route - there is a strong chance TUPE applies and the existing staff transfer to you on their current terms. This is the single most under-handled part of most SME mobilisation plans, and evaluators know it, because a botched staff transfer is the classic reason a contract start goes wrong.

A scoring answer shows you understand the mechanics: you will request the employee liability information from the outgoing provider, run the required information and consultation process with the affected staff and their representatives, and honour the transferring terms and conditions. It also shows you have priced and planned for the practical realities - due diligence on the transferring workforce, harmonising them into your systems, and covering any gaps if some staff choose not to transfer.

Do not overclaim certainty you cannot have. You will rarely have full workforce data at bid stage. The mature move is to state your assumptions, note where you have flagged information gaps to the buyer, and show your contingency if the reality differs. That reads as experience, not evasion. For the full mechanics of a transfer - the timeline, the consultation duties, the liability information you are entitled to, and the traps SMEs fall into - see our dedicated TUPE guide and cross-reference it in your bid rather than repeating it all inline.

Generic mobilisation plans say "a dedicated team will manage the transition." Scoring ones name a mobilisation manager, say who they are, what they have mobilised before, and how much of their time is ring-fenced for this contract. Named accountability is one of the strongest credibility signals you can send, because it tells the evaluator there is a specific person whose job it is to make day one work.

Set out the mobilisation team as distinct from the business-as-usual delivery team, and show the handover point between them. Make clear who owns each workstream - TUPE and HR, systems and IT, training, health and safety, buyer liaison - and who the buyer's single point of contact is. A named contact with a direct line beats an anonymous "account management function" every time.

Be honest about capacity. If you are a small firm, do not pretend you have a standing mobilisation department. Show instead that you have protected the right people's time, named the external support you will draw on if needed, and that your plan is sized to your actual team. An evaluator would rather see a realistic small-team plan than an implausible one that collapses the moment it meets reality.

This is where you prove the service will actually function on day one. Set out how your reporting and management systems will be configured to produce the exact KPI and performance data the contract requires - not a generic mention of "our bespoke software," but the specific outputs the buyer has asked for and when they will first be available.

Cover the practical onboarding that determines whether the service runs: DBS or security clearances and their lead times, mandatory training and induction, uniforms or equipment, access passes and site inductions, insurance and any accreditations named as contract requirements. Buyers check these because they are the things that quietly derail a start. A supplier who has listed them, given each a lead time, and shown they fit inside the mobilisation window looks like a supplier who has done this before.

Where the contract needs integration with the buyer's own systems - a portal, a case management system, a payment or booking platform - name it and show you have planned the technical and data-protection work, including any data-sharing agreement and the processing arrangements. Vague answers here read as risk; specific ones read as readiness.

Every mobilisation carries risk, and pretending otherwise is a tell. A scoring plan carries a short, contract-specific risk register: the two or three things most likely to go wrong on this particular start, each with a likelihood, an impact, an owner, and a mitigation. Generic risks - "staff may be unavailable" - score little. Real ones - "clearances for the night shift may not complete before go-live" with a named fallback - score well because they show you understand this contract's actual failure points.

Contingency is what turns a risk register into reassurance. For each material risk, show your fallback: bank or agency cover if TUPE staff decline to transfer, a manual reporting workaround if system integration slips, a phased go-live if full readiness is at risk. The evaluator is asking a single question - if this goes wrong, does the service still start? - and your contingencies answer it.

Finally, connect mobilisation to the KPIs and SLAs the contract will be measured against. Show that your systems, staffing and reporting will be able to hit those measures from day one, or state clearly which measures have a defined ramp-up period and why. Demonstrating that you have read the performance framework and built your mobilisation to satisfy it, rather than treating go-live as the finish line, is exactly the kind of joined-up thinking that separates a top score from a middling one.

The fastest way to lose marks is a plan that could have been submitted for any contract. Evaluators read a lot of bids and they spot a recycled template instantly - the wrong service named in a stray sentence, generic risks, a timeline with no real dates, milestones that do not match this buyer's requirements. A template signals that you have not engaged with what they actually asked for, and it drags down the credibility of your whole submission.

Specificity is straightforward to build in if you work from the documents. Use the buyer's own contract start date and go-live date. Reference the specific KPIs, the named systems, the actual sites, the real workforce being transferred. Reflect the local context - the region, the service users, the particular constraints the ITT describes. Every place where you name something concrete from this procurement is a place where the evaluator sees a supplier who has genuinely planned for their contract.

The devolved dimension matters too. If you are bidding in Scotland, the regime is different - the Procurement Reform (Scotland) Act 2014 and its regulations, not the Procurement Act 2023, with tenders on Public Contracts Scotland - so mirror that framework and its terminology. In Wales, the Act applies alongside a Welsh policy overlay and the Sell2Wales portal, and community-benefit expectations run high. Getting the regime and the vocabulary right is a small thing that tells an evaluator you know their world.