Tender mobilisation plans: what to include

What is a tender mobilisation plan?

It explains how you will prepare to deliver a contract after award. Contract mobilisation covers the activities, people, timescales and checks needed before the service starts.

Your team may know how to get everything ready, but tender evaluators need that knowledge on the page. A credible tender response helps them assess your approach against the evaluation criteria. It should show that you understand the work, dependencies and risks in the procurement process.

Start with the buyer’s requirements, then build a clear sequence covering responsibilities, resources, contingency arrangements and evidence of readiness.

Key takeaways

Every critical task needs an owner, a deadline and a completion check. If it depends on information or action from someone else, make that dependency visible too.

What your mobilisation plan should include

Start with the full tender question, specification, contract dates and evaluation criteria. A question headed “mobilisation” may also assess staffing, communication and business continuity.

Give each requirement a clear home in your answer. A detailed timetable won’t recover marks for a missing part of the question.

People, responsibilities and resources

Name the mobilisation lead and identify who handles operations, HR, systems, finance and client communication. Set out project management ownership and oversight, including which roles must be in place by contract award. Where appointments are pending, describe the role and appointment timetable honestly.

Show available capacity alongside responsibilities. Explain your resource allocation and how it supports credible service delivery. Your operations director might be excellent, but they still have existing contracts to manage.

Include equipment, subcontractors and supply chain commitments where relevant. For a security contract, confirm licensed staff and role coverage. Check that mobilisation costs agree with your pricing schedule. Temporary cover, training and system setup don’t become free because they’re in a different document.

Governance and readiness measures

Governance means how decisions are made, progress is checked and problems are escalated. Explain how risks are escalated, including who meets, what they review and who can approve changes.

Set measurable readiness checks, such as authorised system access, completed induction or confirmed site coverage. Explain what happens if a check fails.

What I would be looking for is a clear decision route: who identifies the problem, who resolves it and when the buyer hears about it.

How to structure the mobilisation timeline

Follow the buyer’s requested format first. If they prescribe a template, use it.

Otherwise, organise the mobilisation plan around sensible stages. Treat the table below as a starting point for your own timeline, and adjust the stages to fit the contract.

Stage	Main activities	Completion evidence
Pre-award preparation	Review requirements, capacity and outstanding questions	Assumptions and dependencies recorded
Contract award	Confirm responsibilities, access and reporting arrangements	Agreed mobilisation schedule
Workforce preparation	Address transfer arrangements, recruitment and training	Staffing and competence checks
Operational setup	Prepare systems, equipment and supplier arrangements	Tested access, confirmed availability and updated asset register
Readiness review	Check outstanding risks and service coverage	Recorded readiness decision
Early delivery	Monitor key performance indicators and resolve transition issues	Transition plan reviewed, with handover into business as usual

Use project management controls to assign each activity a responsible owner and realistic dates. Separate permitted pre-award preparation from commitments requiring a signed contract or buyer approval.

Show dependencies in the Gantt chart

A Gantt chart displays activities against time. You can build one in Excel, provided it remains readable in the submitted format.

Show which tasks can run together and which depend on earlier work. System testing, for example, may depend on access permissions and usable data.

Identify the critical path, the linked tasks whose delay would delay readiness.

Explain the effect on existing services

An impact schedule records how transition activities affect current operations. That could include training cover, restricted site access or a planned system change.

Explain the continuity arrangements alongside the timing. A tidy chart doesn’t tell the evaluator how customers remain supported.

How to handle TUPE and missing employee information

TUPE, the Transfer of Undertakings (Protection of Employment) regulations, protects employees’ rights when they transfer to a new employer. Acas guidance on TUPE transfers explains the process.

Whether it applies needs proper assessment. Don’t assume every change of supplier triggers a transfer.

Plan the workforce transition

Where TUPE applies, show who will obtain and check employee information, and when they’ll inform and consult, prepare payroll and arrange induction during contract mobilisation.

Use confirmed employee information for workforce planning and recruitment. Explain how you’ll address vacancies, absence and competence gaps without making unsupported promises about transferring employees.

For a security contract, check which roles require Security Industry Authority licences and relevant vetting. For other services, identify the contract’s actual training, safeguarding or qualification requirements.

Make missing data a managed dependency

The government’s Sourcing Playbook says full and accurate TUPE information should be shared with bidders during tendering.

If information is incomplete, raise a formal clarification through the procurement portal. A clarification is a question asking the buyer to resolve an uncertainty in the tender documents.

Record the missing information, permitted assumptions, owner, deadline and dependencies in the mobilisation plan. Explain how receiving it will trigger a review of staffing, costs and timing.

Don’t hide uncertainty inside “subject to TUPE”. That leaves the evaluator wondering how much of your plan is still undecided. Use the tender’s permitted approach to assumptions and qualifications.

How to plan systems, assets and statutory compliance

Workforce readiness is only part of mobilisation. Access, equipment, records and compliance can hold up delivery even when every shift is covered.

Test systems before relying on them

Identify required system access, data transfers, integrations, reporting and user training. Explain who authorises access to operational reporting systems and who checks the setup works.

In facilities management, a computer-aided facilities management system, or CAFM system, may hold asset records, work orders and maintenance schedules.

If integration is required, include data checks and user testing. A successful import doesn’t prove that the right job reaches the right engineer. Limit access to authorised users and plan secure handling of employee and client information.

Reconcile assets and inspection responsibilities

An incomplete asset register can affect maintenance planning and compliance checks. State how you will validate records, identify gaps and escalate missing information.

Where statutory inspections fall during mobilisation, clarify responsibility across the outgoing provider, buyer and incoming supplier.

Check inspection dates, available certificates, competent resources and access arrangements. Record outstanding details against the asset register, with an owner and a deadline for resolution.

Any proposed contingency must remain within applicable duties and contract requirements. Make unresolved health and safety issues visible at the readiness review, so the mobilisation plan supports statutory compliance.

How to evidence your approach, including as the incumbent

Your plan explains what you’ll do, and your evidence is what convinces the evaluator you can do it, so keep the two clearly separated.

Put proof beside the commitment

Choose a comparable contract and explain the mobilisation challenge, your actions and the verified service delivery result. Include dates, scale and your organisation’s actual role.

Useful proof might include an approved handover record, recruitment completion data, an asset register you hold and can share, or early-service performance reports.

Avoid making the evaluator search through an appendix for evidence behind your strongest claim. An independent red review can test whether that connection is clear to someone outside your delivery team.

Use incumbent knowledge without assuming credit

An incumbent provider is the existing supplier. You may already know the sites, people and systems, but the evaluator still needs a contract-specific plan.

As the incumbent provider, show what remains in place, what changes and what needs revalidation. Address revised requirements, expiring approvals and capacity for additional work.

Previous scores can help identify weak explanations. A tender feedback review can turn those comments into practical improvements before another deadline arrives.

Common mistakes that cost mobilisation marks

Where I most often see bidders lose marks is the gap between a reassuring statement and a commitment the buyer can hold you to.

“We will work closely with the client” tells me little. A stronger response identifies the meetings, participants, decisions, reporting and escalation arrangements.

Other avoidable problems include dates that conflict with the contract, owners who haven’t confirmed capacity, unreadable Gantt charts and readiness checks without measurable key performance indicators.

Reusing an old plan can carry over the wrong staffing assumptions, systems, approval routes or an outdated asset register. Borrow the structure, then check every detail.

Be careful with contingency promises, because unverified staffing or cover puts the whole plan at risk. A contingency plan stating “Additional staff will be available” needs a credible source, competence checks and an activation process.

Finally, don’t describe readiness approval as permission to miss the service start date. Explain the risk management controls, warning signs and escalation routes for handling issues within the contract’s requirements.

Before you submit: the mobilisation checklist

Ask someone outside the writing team to test your mobilisation plan against the question. Your delivery team will naturally fill in gaps because they know the work, and the evaluator won’t have that background.

• Have you answered every mobilisation requirement and scored sub-question?
• Do dates match the contract and the rest of your response?
• Have workforce planning and each responsible person’s capacity been confirmed?
• Are buyer, incumbent and subcontractor dependencies visible?
• Have you recorded missing information and raised necessary clarifications?
• Does your risk management identify warning signs, controls, owners and escalation routes?
• Are readiness checks measurable and supported by evidence, including an asset register where asset data is required?
• Can the evaluator read the schedule without zooming in repeatedly?

Make the plan credible before making it polished

A strong contract mobilisation answer makes delivery easy to understand, believe and assess. Keep the sequence realistic, responsibilities clear and evidence close to the commitments.

Your team keeps control of the bid. Bidsmithery™ can help you identify gaps in your bid writing before submission through an evaluator-led bid review.

If the tender response looks convincing internally, check whether its written commitments reflect the service delivery your team can provide. That’s a useful place to start with a second pair of eyes.

Frequently asked questions