Writing & Scoring

How to write a winning mobilisation plan: transition with confidence

Mobilisation can be 15-25% of your score. Learn how to plan transitions that commissioners trust and evaluators score highly.

Why mobilisation makes or breaks tenders

Mobilisation planning is where many tenders are won or lost. It’s commonly worth 15-25% of quality scores — sometimes the single largest weighted section.

Why commissioners care so much:

  1. Failed mobilisation = service failure — disruption, complaints, risk
  2. It’s the immediate future — what happens first if they award to you
  3. It tests your competence — can you actually deliver what you promise?
  4. Risk management — what if things go wrong?

The pattern: Providers with “Good” service delivery but “Poor” mobilisation often lose to competitors with “Acceptable” delivery but “Excellent” mobilisation.

This guide shows you how to write mobilisation plans that score.


The mobilisation score framework

What evaluators assess

ElementTypical WeightWhat Excellent looks like
Timeline20%Specific, realistic, phased with clear milestones
Staffing25%Numbers, recruitment plan, training schedule, contingency
Systems15%Technology, processes, reporting, integration
Risk management20%Risks identified, mitigations specific, contingencies detailed
Governance15%Oversight, quality gates, reporting, escalation
Stakeholder management5%Communication, engagement, relationship building

The difference between scores

Poor (0-7/20) 0-7/20

“We will mobilise efficiently over 4 weeks. Staff will be recruited and trained. Systems will be ready. We have experience in mobilisation.”

Good (12-15/20) 12-15/20

“8-week mobilisation: Week 1-2 recruitment, Week 3-4 training, Week 5-6 shadowing, Week 7-8 go-live. 15 staff recruited, all DBS checked and trained.”

Excellent (18-20/20) 18-20/20

“12-week mobilisation with 5 phases: Preparation, Recruitment, Training, Transition, Stabilisation. 18 staff recruited (20% contingency), 156 hours training per person, systems live with data migration, 4 quality gates, 12 risks identified with mitigations, daily commissioner reporting week 1-2, weekly thereafter.”


The 6 components of mobilisation

1. Timeline and phases

What commissioners want:

  • Specific start and end dates
  • Clear phases with objectives
  • Realistic duration (not rushed, not excessive)
  • Milestones and quality gates
  • Link to contract start date
How to write it

Mobilisation timeline: [X] weeks from contract award ([date]) to full service delivery ([date]).

Phase 1: Preparation (Weeks 1-2)

  • Contract finalisation and kick-off meeting
  • Detailed service mapping with outgoing provider
  • Site/setting inspections
  • Systems setup and testing
  • Governance structure establishment

Phase 2: Recruitment (Weeks 2-5)

  • Job advertisements live
  • Interview and selection
  • DBS and reference checks
  • Pre-employment health assessments
  • Contract offers and acceptance

Phase 3: Training (Weeks 4-7)

  • Induction programme
  • Mandatory training (safeguarding, etc.)
  • Service-specific training
  • Shadowing existing provider (if applicable)
  • Competency assessments

Phase 4: Transition (Weeks 8-10)

  • Gradual handover from existing provider
  • Parallel running (if applicable)
  • Service user/family introductions
  • Systems go-live
  • Quality monitoring intensified

Phase 5: Stabilisation (Weeks 11-12)

  • Full service responsibility
  • Performance monitoring
  • Issue resolution
  • Continuous improvement begins

Milestones:

  • Week 2: Recruitment plan confirmed
  • Week 4: All staff contracts signed
  • Week 6: Training complete
  • Week 8: Systems live
  • Week 10: Transition complete
  • Week 12: Mobilisation complete, business as usual

The rule: Specifics, dates, numbers. Not “we’ll recruit staff” but “we’ll recruit 12 care workers by [date].“


2. Staffing and recruitment

What commissioners want:

  • How many staff of which types
  • Recruitment sources and timeline
  • Contingency if recruitment shortfall
  • Training schedule and content
  • When staff are “live”
How to write it

Staffing requirements: [X] FTE required: [breakdown by role].

Recruitment plan:

  • Week 1: Advertisements live ([channels: job boards, local partnerships, social media])
  • Week 2-3: Applications reviewed, shortlisting
  • Week 3-4: Interviews, offers
  • Week 4-5: DBS checks, references, health checks
  • Week 5-6: Contracts signed, start dates confirmed

Contingency recruitment: We will recruit [X]% above minimum requirement ([Y] staff vs [Z] required) to provide: holiday/sickness cover, float capacity, turnover buffer. If primary recruitment falls short, contingency sources: [list].

Training schedule:

  • Induction: [X] hours (Days 1-3)
  • Mandatory: [safeguarding, health & safety, moving & handling, etc.] — [Y] hours
  • Service-specific: [care approaches, client needs, local protocols] — [Z] hours
  • Shadowing: [A] hours with existing provider
  • Total: [B] hours per person over [C] weeks
  • Competency sign-off: [assessment method, criteria]

Go-live readiness: No staff member delivers service until: [all checks complete, all training signed off, competency verified, shadowing complete].

Evidence to include:

  • Previous recruitment timelines (proof you can do it)
  • Current pipeline (if already recruiting)
  • Training records from previous mobilisations
  • Retention data (staff stay once recruited)

3. Systems and processes

What commissioners want:

  • Care management/record systems ready
  • Scheduling/rostering operational
  • Reporting systems configured
  • Communication tools working
  • Data migration (if applicable)
How to write it

Systems preparation:

Care records: [System name] configured for [service type], go-live [date]. Data migration from [outgoing provider]: [method, timeline, validation]. Access: [who, when, training provided].

Scheduling: [System name] with: [features relevant to service]. Rosters: prepared [X] weeks ahead. Shift allocation: [method]. Backup scheduling: [if system fails].

Reporting: Dashboard configured for [commissioner requirements]. KPI tracking: [which metrics, frequency, method of submission]. Incident reporting: [system, escalation, notification protocols].

Communication:

  • Internal: [radios/phones/app for field staff]
  • With commissioner: [named contact, frequency, method]
  • With service users/families: [how you’ll communicate]
  • Emergency: [24/7 on-call system]

Data protection: GDPR compliance. Staff training: [when]. Information governance: [protocols]. Data security: [measures].


4. Risk management

What commissioners want:

  • Risks identified (specific to this mobilisation, not generic)
  • Likelihood and impact assessed
  • Mitigation strategies
  • Contingency plans if mitigation fails
  • Escalation triggers and actions
How to write it

Risk register:

Risk 1: Recruitment shortfall

  • Likelihood: Medium | Impact: High
  • Mitigation: Multi-channel recruitment, [X]% contingency target, early start (Week 1), competitive pay, recruitment incentives
  • Contingency: If <[Y]% recruited by Week 4: activate agency staff (short-term), extend shadowing period, delay go-live with commissioner agreement
  • Trigger: <[Z]% recruited by Week [N]
  • Action: [specific steps]

Risk 2: Key staff departure

  • Likelihood: Low | Impact: High
  • Mitigation: Retention conversations, engagement activities, clarity on future
  • Contingency: Succession plan, knowledge transfer, recruitment acceleration
  • Trigger: [X] key staff indicate leaving

Risk 3: System failure

  • Likelihood: Low | Impact: Medium
  • Mitigation: Testing, backup systems, IT support on standby
  • Contingency: Manual processes, paper records, phone-based coordination
  • Trigger: System down >[X] hours

Risk 4: Service user/family resistance

  • Likelihood: Medium | Impact: Medium
  • Mitigation: Early communication, meet-and-greets, continuity where possible, reassurance
  • Contingency: Enhanced engagement, advocacy support, commissioner mediation if needed
  • Trigger: [X]% families express concerns

Risk 5: Outgoing provider non-cooperation

  • Likelihood: Low | Impact: High
  • Mitigation: Contractual handover requirements, commissioner involvement, positive relationship building
  • Contingency: Independent information gathering, recruitment acceleration, extended mobilisation
  • Trigger: [specific behaviours]

Risk governance: Weekly risk review in mobilisation meetings. Escalation to [named person] if any risk moves to “high” likelihood or impact.


5. Governance and oversight

What commissioners want:

  • Who’s in charge of mobilisation
  • How decisions get made
  • Quality gates (approval points)
  • Reporting to commissioner
  • Escalation protocols
How to write it

Governance structure:

Mobilisation lead: [Name, role, experience]. Responsible for: [overall coordination, timeline, issue resolution].

Steering group: [Who attends: project lead, HR, operations, commissioner rep]. Meets: [frequency]. Decisions: [authority, escalation path].

Quality gates: [Approval required before proceeding]

  • Gate 1 (Week 2): Recruitment plan approved, contracts signed
  • Gate 2 (Week 6): All staff recruited and in training
  • Gate 3 (Week 8): Systems live, training complete
  • Gate 4 (Week 10): Transition complete, ready for full responsibility
  • Gate 5 (Week 12): Mobilisation complete, business as usual

Commissioner reporting:

  • Week 1-2: Daily email updates
  • Week 3-8: Weekly written report + call
  • Week 9-12: Weekly report
  • Content: progress vs plan, issues, risks, mitigations, next steps

Escalation: If [specific triggers], immediate contact with [commissioner named contact]. Emergency: [24/7 contact details].


6. Stakeholder management

What commissioners want:

  • How you’ll communicate with service users, families, staff
  • How you’ll manage the relationship with the outgoing provider
  • How you’ll engage with wider stakeholders
How to write it

Service users and families:

  • Notification: [when, how, by whom]
  • Information provided: [what’s changing, when, what stays same]
  • Meet-and-greets: [arrangements for meeting new staff]
  • Concerns: [how to raise, who responds, timescales]
  • Feedback: [how we’ll capture and act on it]

Staff (new and transferring):

  • Welcome: [approach, materials, contacts]
  • Communication: [frequency, channels, content]
  • Concerns: [how to raise, support available]
  • Integration: [into team, culture, ways of working]

Outgoing provider:

  • Relationship: [professional, collaborative]
  • Handover: [what information, when, format]
  • Shadowing: [arrangements for new staff]
  • Dispute: [escalation via commissioner if needed]

Other stakeholders:

  • Health professionals: [notification, liaison]
  • Local authority: [contacts, protocols]
  • Advocates: [engagement, information sharing]

Sector-specific mobilisation

Supported living

Specific elements:

  • Property preparation (if new)
  • Service user transition (anxiety management)
  • Staff team formation (consistency)
  • TUPE if staff transferring
  • Key worker allocation
Response focus

Supported living mobilisation specifics:

  • Property: [inspections, modifications, furnishing, safety checks]
  • Service user transition: [X-week gradual handover, same staff where possible, family communication]
  • TUPE: [if applicable, staff transfer details]
  • Team building: [social events, consistent allocation planning]

Domiciliary care

Specific elements:

  • Rapid recruitment (often 20-50 staff)
  • Route planning and efficiency
  • Service user introduction (first visit protocols)
  • Continuity matching (keeping same carers)
  • 24/7 on-call establishment
Response focus

Domiciliary care mobilisation specifics:

  • Recruitment volume: [X] care workers in [Y] weeks
  • Route optimisation: [software, planning, efficiency targets]
  • Service user continuity: [matching new staff to existing relationships]
  • On-call: [24/7 system, response times, escalation]

Patient transport

Specific elements:

  • Fleet preparation and compliance
  • Driver recruitment and licensing checks
  • Route familiarisation
  • Patient communication (first journey protocols)
  • Controller/coordination systems
Response focus

Patient transport mobilisation specifics:

  • Fleet: [vehicle preparation, compliance checks, tracking installation]
  • Drivers: [licence verification, route training, patient communication training]
  • Systems: [booking system, scheduling, real-time tracking]
  • Controllers: [recruitment, training on routes and protocols]

Common mobilisation mistakes

1. Underestimating time

Mistake: 4-week mobilisation for complex service.

Fix: Be realistic. Better to propose a longer mobilisation and deliver early than fail.

2. Ignoring contingency

Mistake: No plan B for when things go wrong.

Fix: Identify specific risks and contingencies.

3. Vague staffing

Mistake: “We’ll recruit staff” without numbers or timeline.

Fix: Specific numbers, dates, sources, contingency.

4. Weak quality gates

Mistake: No clear approval points.

Fix: Named gates with criteria, before proceeding.

5. No commissioner engagement

Mistake: Mobilising in isolation.

Fix: Regular reporting, commissioner involvement, transparency.


Mobilisation checklist

Before submission, verify:

  • Timeline specific with dates
  • Phases logical and complete
  • Staff numbers calculated and detailed
  • Recruitment timeline realistic
  • Training content and hours specified
  • Systems named and configured
  • Risks specific (not generic)
  • Mitigations credible
  • Contingencies detailed
  • Governance clear (who’s responsible)
  • Quality gates defined
  • Reporting to commissioner detailed
  • Stakeholder communication planned

Need help with mobilisation planning?

We create detailed, credible mobilisation plans as part of our tender writing service. Contact us to discuss your next bid.

See our tender writing service

Want a fast, practical steer on your next bid?

Send the tender pack (or link) and deadline — we’ll confirm fit, risks, and recommended scope.