How to write a tender mobilisation plan
A tender mobilisation plan should show how the service will be ready to start, who is responsible and what must happen first. Work backwards from the required start date, identify the activities that depend on the buyer or another supplier, and define how readiness will be checked. Use dates and resources your delivery team can support. The plan, narrative and price must describe the same transition into service.
Before you start
Who this helps
- A supplier preparing a contract-start or transition response
- A team coordinating recruitment, systems, sites and customer handover
- A reviewer checking whether a mobilisation timetable is credible
Points to check
- A date in a schedule does not prove the dependency can be met.
- Staff transfer issues may need assessment even if the pack is unclear.
- The plan needs to cover service continuity and post-start support.
Establish the starting conditions
Confirm the intended award and service-start dates, the scope at go-live and any phased rollout. Identify what already exists and what must be created, recruited, transferred, configured or approved. Read the buyer’s handover obligations and information available about the incumbent service.
List uncertainties that could change the plan or price. Raise material questions through the official clarification process. Do not assume site access, accurate data or cooperation from another supplier simply because the plan requires it.
Break the transition into workstreams
Use workstreams that fit the contract, such as people, sites and assets, systems and data, suppliers, service procedures and communications. For each activity, record the owner, duration, dependency and evidence of completion.
For example, a systems activity might be “configure user roles after the buyer approves the access matrix, then test with nominated users”. This explains more than a bar labelled “IT setup”, because it shows the decision and test needed before the activity is complete.
Build the schedule from dependencies
Work backwards from service readiness and identify the activities that would delay the start if they slipped. Show which tasks can run in parallel and where buyer approval or external lead times control the sequence.
Put a named role against each activity and check the people in those roles have time alongside their existing work. A tight timetable needs a convincing explanation of how work overlaps and who is set aside to do it. Do not put every task in the final week or treat all activities as independent.
- Activity and accountable role
- Start, finish and predecessor
- Required buyer or third-party input
- Completion evidence and escalation point
Deal with staffing and TUPE early
Where staff may transfer, involve suitably qualified HR or legal advisers to assess TUPE and the available employee information. Acas guidance highlights planning, employee communication and due diligence before a transfer. These can affect the timetable, employment costs and how you deliver the service.
Do not assume TUPE does not apply just because the tender pack says nothing about it. Check recruitment, vetting, training and induction requirements for the workforce you actually plan to use. Only let approved people see sensitive employee information.
Define readiness and continuity checks
Specify what must be true before the service begins and who accepts it. Depending on the contract, this could include trained staff, working access, tested equipment, approved procedures, completed site checks and functioning reporting. Use the buyer’s required acceptance process.
Explain how service continuity will be protected if a critical dependency is late. A contingency should name the trigger, decision owner and workable response. “We will resolve delays quickly” does not explain what happens if a site is inaccessible or a required system cannot pass testing.
Include the period after go-live
Show how the team will support the service straight after go-live, track issues and move into routine management. Say where you will add extra oversight or support, and how you will decide that mobilisation is complete.
Check the plan against the quality narrative, staffing model and price. Delivery owners should approve the dates and method; finance should confirm the resources are funded. A useful final test is to ask each workstream owner to explain the next dependency and the evidence that will prove readiness. Bidgen can help turn that checked plan into a clear tender response.
Common questions
01Does a mobilisation plan have to be a Gantt chart?
Use the format and attachment rules in the tender. A Gantt chart can show timing and dependencies, but it may need a short narrative explaining ownership, readiness and contingency. A clear table can be sufficient where permitted.
02What if the buyer’s start date seems unrealistic?
Identify the dependency or lead time that makes it unrealistic, test alternatives with delivery colleagues and raise a clarification question in good time. Do not submit a schedule you cannot support just to match the requested date.
03Should we include buyer responsibilities?
Yes, where the documents set them out or a clarification confirms them. Show the inputs and decision dates you need from the buyer accurately, without inventing obligations or relying on assumptions nobody has approved.
04Who should approve the plan?
The people responsible for delivering each workstream and the person authorised to approve the commercial position. They should confirm the resources, dates, dependencies and commitments before your business approves the final response.