How to Get a Public Transport Contract Mobilisation Right

Winning a public transport contract is a milestone. But the award letter is not the finish line — it is the starting gun for one of the most demanding phases of the entire contract: mobilisation.

Mobilisation is the period between contract award and the first day of live service, when an incoming operator turns a written bid into a working operation. It is where commitments made on paper meet the reality of depots, drivers, fleets, systems and customers. Get it right and the contract starts with momentum and client confidence. Get it wrong and you spend the first year recovering from a difficult start that was entirely avoidable and you never really catch up with staff, stakeholders or suppliers.

This guide sets out how public transport contract mobilisation works in practice: what it involves, how long it takes, who you need in your team, how to govern it, and how it is increasingly scored within large-scale bids. It is written for operators, bid teams and transport authorities working across bus, rail, light rail and emerging mobility.

Surbon Consulting has supported 8 large scale mobilisations and demobilisations across the UK and internationally, covering heavy rail, bus and coach, metro and tram. We draw on that experience throughout — focusing on what actually determines whether a transition succeeds, not just what the plan says on paper.

What is contract mobilisation in public transport?

Contract mobilisation is the structured process of preparing to take over and deliver a public transport contract between the point of award and the start of live service. It is the bridge between winning the work and running it.

In practice, public transport mobilisation covers everything that has to be ready before the first customer boards under your management: timetables registered, depots accessible, fleet inspected, staff transferred, systems migrated, suppliers novated and reporting frameworks live. The whole effort is coordinated through a contract mobilisation plan — a single, owned document that brings together every workstream, dependency and milestone leading up to Day 1 readiness.

There are two types of moblisation  

• Greenfield – Start from scratch. In theory that sounds easier but as the operator there is a lot of work to set up management systems, recruit staff and IT.
• Brownfield – Involves a service transition from an incumbent were you are taking over a live operation that must keep running throughout. That makes operator handover one of the defining features of transport mobilisation. You are dependent on the outgoing operator for information, assets and continuity at the very moment they are winding down their own involvement, and managing that handover well is often the difference between a smooth start and a chaotic one.

Why mobilisation makes or breaks a contract

A bid is a beautifully written promise. Mobilisation is where you prove you can keep it. Everything an authority believed about your organisation when they awarded the contract is tested in the weeks before and after Day 1 — and first impressions, once formed, are hard to shift.

The reason mobilisation carries so much weight is that risk is concentrated in a short window. Operational readiness has to be achieved across multiple workstreams simultaneously, against a fixed go-live date that cannot move. A disciplined contract mobilisation checklist keeps that complexity visible and under control, but the underlying truth is simple: this is the period where service continuity is most fragile and where client confidence is won or lost. Manage transition risk well and you enter the contract with credibility and goodwill. Manage it badly and you start on the back foot, spending political and operational capital you would rather have saved for the contract itself.

The cost of a poor start

Mobilisation failure rarely looks like a single dramatic event. More often it is an accumulation of small things that were left too late: a depot that is not ready, a rota that does not work, a ticketing system that was not tested in time. Individually they look manageable. Together, on Day 1, they produce operational disruption that customers feel immediately.

The consequences compound quickly. Missed or unreliable services generate customer complaints, which attract media and political attention. Performance shortfalls against contractual targets trigger KPI penalties that hit your margin from the outset. And because public transport is so visible, a poor start carries reputational damage that outlasts the operational problems themselves — affecting your standing not only on this contract, but on the next bid you submit to the same authority.

What clients notice in the first 100 days

The first 100 days set the tone for the entire contract. Authorities, customers and stakeholders are watching closely, and what they notice is rarely the detail of your project plan — it is whether the service works and whether you are honest about where it does not.

Three things shape their judgement. 

1.  Service reliability: are vehicles running on time, are customers being carried, are the basics being delivered?
2. Client reporting: is your data accurate, on time and consistent, or are you scrambling to produce numbers that should already exist? 
3. How you handle problems. Every mobilisation hits issues; mature operators get ahead of them through early, transparent issue escalation rather than hoping they go unnoticed. Strong early contract performance, reported clearly and backed by candour when things go wrong, builds the trust that makes the rest of the contract easier to run.

Why the pressure is higher than most operators expect

Even experienced operators underestimate the mobilisation pressure involved, because a public transport transition is not only an operational exercise — it is a public one.

Public contracts unsurprisingly come with public accountability. Elected representatives, local media and customer groups all have a stake, and a difficult start can quickly attract political scrutiny that a private contract would never face. Stakeholder expectations are high and not always aligned: the authority, customers, transferring staff, unions and your own board may each want something different from Day 1. Above all, a transport mobilisation is a live service transfer — the network has to keep moving while you change everything behind it. There is no quiet period of a week to get ready in. That combination of visibility, accountability and continuous operation is why mobilisation deserves senior attention from the moment of award.

How long does mobilisation take? Timelines by contract type

There is no single answer to how long mobilisation takes — the mobilisation timeline depends heavily on the mode, the complexity of the assets and the maturity of the market. A software-led micro-mobility scheme can be mobilised in a matter of months; a complex, union-heavy rail or bus operation can take well over a year.

As a broad guide, the contract mobilisation period is outlined in Table 1.

Table 1: Mobilisation timelines by contract type

What determines your mobilisation window?

The headline figures above are starting points, not guarantees. Several factors push your window longer or shorter.

• Fleet complexity is one of the biggest drivers. Taking on a large, mixed or ageing fleet — or new vehicles arriving on a tight delivery schedule — demands far more time than a small, standardised one. 
• Depot access is closely linked: if the depots you need are still occupied by the outgoing operator until close to Day 1, your engineering and operational preparation is compressed into a narrow window. 
• People are the other major variable. A transfer of several hundred staff, of combined with the union engagement required to do it well, takes time that cannot be rushed without creating risk. 
• IT systems migration — moving from the incumbent’s IT, ticketing and control-room systems to yours — is almost always more involved than it first appears, and is a frequent cause of timelines slipping.

The interaction between these factors matters as much as any one of them. A bus franchising mobilisation with new electric vehicles, a brand-new depot and a large transferring workforce can take far longer than its nominal nine months, because the dependencies stack on top of each other. A rail mobilisation may be shorter on paper but is constrained by regulation and rolling stock arrangements that cannot be accelerated. The lesson is to build your timeline bottom-up from the actual assets, people and systems involved, rather than assuming the sector average will apply to your contract.

A note on markets new to franchising

Timelines lengthen further in new franchising markets — places where competitive contracting of public transport is relatively recent. Here, the constraint is rarely the assets; it is the market maturity and the political environment around the transition.

Where established processes for transfer do not yet exist, every step takes longer to agree, and union negotiations can dominate the schedule. On one French mobilisation, French union negotiations took around two and a half years — not because the operation was unusually complex, but because the industrial and political context required it and it was one of the first privatisation of its kinds. 

International transport mobilisation consistently shows this pattern: the more novel franchising is to a market, the more time you should allow for consultation, negotiation and relationship-building. Surbon Consulting’s work across the UK and the Middle East — including metro and tram mobilisations in less mature franchising environments — has reinforced how decisive local context is in setting a realistic timeline.

Building your mobilisation team: roles and responsibilities

Core mobilisation team structure

A mobilisation succeeds or fails on the strength of its team. Because the work spans operations, engineering, people, customer, finance and IT simultaneously, the mobilisation team needs to be structured around clearly defined workstreams, each with an accountable lead.

Most effective structures sit within a simple PMO structure: a Mobilisation Director at the top, supported by a project management office that maintains the plan, tracker and reporting, with workstream leads owning delivery in their areas. This is not a loose working group; it is a proper project governance model that mirrors the transport operations team you will eventually run, so that the people preparing the contract are aligned with those who will deliver it. A typical structure looks like this:

Table 2: Mobilisation team structure

The role of the Mobilisation Director

The Mobilisation Director is the single most important appointment you will make. Day to day, this person is the client interface — the face the authority deals with, the holder of the overall plan, and the one accountable for delivering Day 1. They chair governance, track progress, manage the relationship with the outgoing operator and own the risks that sit across workstreams.

The Mobilisation Director is the escalation point and the decision-making authority when workstreams conflict — and they will conflict. Engineering needs depot access that operations also needs; finance needs information that IT is still chasing. Someone has to hold the whole picture and make the call. That is why mobilisation leadership cannot be a part-time or junior appointment. A Mobilisation Director needs the seniority to make decisions, the credibility to hold difficult conversations with the client and the outgoing operator, and the bandwidth to give the role the attention it demands. Treating it as a side task delegated to someone already running another job is one of the most common — and most expensive — mistakes operators make. It needs focus. 

Workstream leads: what each one owns

The principle that makes the structure work is straightforward: each workstream lead owns their plan, their risks and their client relationships within their area. The Engineering Lead owns fleet and depot readiness end to end; the People Lead owns TUPE and union engagement; the Customer Lead owns communications and accessibility. Delivery accountability sits with them, not with the centre.

The Mobilisation Director coordinates across these workstreams but does not substitute for the expertise within them. Their job is to manage mobilisation dependencies, resolve conflicts and keep the whole programme coherent — not to do the risk management that each lead is responsible for in their own domain. This distinction matters. When a director tries to own everything, detail gets missed and leads disengage. When workstream ownership is genuine — when each lead carries real responsibility for their plan and their client relationships — issues surface earlier and get resolved closer to where the knowledge sits.

Mobilisation governance: the meeting structure that keeps mobilisation on track

Governance is what turns a list of tasks into a controlled programme. It needs to be established in week one, not allowed to evolve. Without a clear meeting cadence, approval process and decision log from the outset, approvals stall, decisions get made informally in corridors, and the project quietly loses coherence — usually without anyone noticing until a milestone is missed.

Good mobilisation governance does three things: it gives every workstream a regular forum to report into, it creates a clear route for escalation, and it produces a single source of truth — typically a weekly report — that the whole programme and the client work from.

The four levels of mobilisation governance

In practice, mobilisation governance operates across several connected layers, each with a distinct purpose.

• Project team meeting drives operational delivery; 
• Steering group provides strategic oversight and an escalation route
• Client mobilisation meeting keeps the authority aligned against the plan; and the three-way transition meeting brings the incoming and outgoing operators together with the client.

 A typical structure looks like this:

Table 3: Mobilisation governance structure

The three-way meeting is the most complex dynamic in the structure. It brings together parties whose interests are not aligned: the outgoing operator has their own commercial position to protect, even as they are contractually required to support the handover. Expect friction, and design the meeting — with clear actions, owners and a shared record — to manage it.

What to expect when working with the outgoing operator

Working with the outgoing operator is one of the least comfortable parts of mobilisation, and it is worth being honest about why. You are dependent on an organisation that may be commercially motivated to be slow, guarded or unhelpful and are still annoyed that they lost the building. The outgoing operator is running their own demobilisation at the same time as you mobilise, with very different incentives — and information sharing is rarely as straightforward as the contract implies.

Expect commercial friction. Data you need arrives late or incomplete; questions get partial answers; access is granted grudgingly. Some of this is deliberate and some is simply the result of a winding-down team with competing priorities. The practical response is to rely on the handover obligations written into the contract, to escalate through the client when cooperation breaks down, and to document everything. The demobilisation process mirrors mobilisation in structure but runs on opposite incentives, and planning for that reality from the start is far more effective than being surprised by it.

Mobilisation questions in large-scale bids: what to expect and how to score

Mobilisation is not only something you do after winning — it is something you are judged on while bidding. For most large-scale public transport tenders, there is almost always a specific question on your mobilisation approach, and how you answer it can directly affect whether you win.

In our experience of public transport procurement, the transport bid mobilisation question typically carries somewhere between 3% and 10% of the overall bid score, depending on contract complexity. That is significant. Tender evaluation of mobilisation is one of the clearest signals an authority gets about whether you can actually deliver what you are promising — which is why strong bid scoring here is so valuable.

How mobilisation is scored in transport bids

Understanding the mobilisation weighting matters because of what it can do at the margins. At 3% it is a useful differentiator; at 10% it can be the difference between winning and losing, especially in a close competition where the leading bids are separated by a point or two. A weak mobilisation answer can pull down an otherwise strong submission and cost you the contract award.

It also helps to understand what evaluators are really assessing. The evaluation criteria are not only about the plan itself; they are about bid confidence — whether the panel believes this team can be trusted to take over a live public service without disruption. A high technical score on mobilisation comes from demonstrating not just a credible method, but a credible team behind it as well as deliverable.

What evaluators want to see

Strong mobilisation responses share a consistent set of features. Evaluators are looking for evidence, named accountability and realism — not generic reassurance. In practice, the highest-scoring answers demonstrate:

• a clear planning process and governance structure, showing how the work will be controlled and escalated;
• named mobilisation team appointments — including the Mobilisation Director — and their relevant senior experience;
• treatment of operations, assets, planning and people as distinct workstreams, each properly owned;
• a credible, constructive approach to the outgoing operator, acknowledging the friction rather than ignoring it;
• evidence of delivery from previous mobilisations: timelines met, issues resolved, and client references that stand up;
• Day 1 commitments, including how social value will be delivered from the very first day of the contract.

The thread running through all of these is confidence. Evaluators want to believe that the team in front of them has done this before and will do it again here.

Why the people workstream is the hardest to get right

Of all the workstreams, the people workstream is the one bid responses most often underplay — and the one evaluators scrutinise most closely. The reason is that you are not describing a plan to recruit a new team. You are inheriting a live organisation, with all of its existing complications.

That inheritance includes ongoing recruitment gaps, active disciplinary cases, staff retention problems and union relationships that are already in play before you arrive. TUPE consultation is not a clean transfer of names on a spreadsheet; it is the transfer of real people with real concerns, at a moment of maximum uncertainty for them. A weak answer treats this as a process. A strong answer acknowledges the complexity honestly and shows how you will manage it — through early union engagement, realistic resourcing assumptions and genuine employee engagement from the outset. Demonstrating that you understand the human reality of a transfer, not just the legal mechanics, is one of the clearest ways to stand out and goes a long way to build trust in the early days of the new contract.

What goes into a contract mobilisation plan and why it’s not just a Gantt chart

A contract mobilisation plan is not a Gantt chart. A Gantt chart is a useful artefact within it, but the plan itself is something larger: a living document that coordinates different workstreams, each with its own dependencies, risks and client-facing obligations.

The distinction matters because a static plan gives a false sense of control. Mobilisation changes constantly as information arrives, assets are inspected and the outgoing operator engages — or does not. A good plan, whether you build it from a mobilisation plan template or from scratch, is updated continuously, owned actively, and used to drive workstream planning and dependency management rather than simply to record intentions. The sections below set out what each workstream needs to address from Day 1.

Operations and service delivery

The operations workstream owns everything required to run the service safely and reliably from Day 1. Service delivery readiness is the goal, and it rests on a defined set of deliverables:

• timetable implementation: finalising and registering timetables in good time, not at the last minute;
• depot access and a clear readiness schedule;
• control room setup and staffing, fully operational before go-live;
• contingency and disruption protocols for the inevitable early problems;
• a formal Day 1 operational sign-off process, so readiness is confirmed against criteria rather than assumed.

Common mistake to avoid

The most common operational error is assuming depot access will be straightforward. It frequently is not — the outgoing operator may occupy the depot until close to Day 1, or contract access rights may be ambiguous. Do not rely on goodwill or unwritten operational assumptions. Negotiate handover dates explicitly in the contract and confirm them in written confirmation early, while you still have leverage.

People and TUPE

The people workstream manages the transfer of staff and the relationships that come with them. Workforce planning here begins long before Day 1:

• TUPE transfer due diligence: understand exactly who is transferring, on what terms, and with what liabilities;
• review of the employee liability information provided, tested rather than taken at face value;
• early union engagement — do not wait to be approached;
• identification of recruitment gaps before Day 1, not after;
• a staff induction and training schedule, and an internal communications plan for transferring employees.
• Pensions transfer (always a challenge in Europe)

Common mistake to avoid

The classic mistake is treating TUPE due diligence as a legal formality rather than a people process. The legal mechanics matter, but they are not the whole task. Staff who feel uninformed during a transfer become disengaged quickly, and employee uncertainty during the people transition shows up immediately in service quality and workforce morale. Clear, early staff communication is not a nicety; it is operational risk management.

Assets and engineering

The assets and engineering workstream is responsible for fleet, depots and maintenance being ready and reliable from Day 1. Engineering readiness depends on:

• a fleet condition assessment at handover, conducted properly;
• transfer of the maintenance handover regime and schedules;
• depot infrastructure and access agreements confirmed;
• rolling stock lease novation or new agreements where required;
• an engineering team structure that is in place and ready for go-live.

Common mistake to avoid

The recurring error is accepting fleet condition at face value. The outgoing operator has little incentive to highlight problems with assets they are handing over. Wherever possible, conduct independent assessment and fleet inspection at handover, and insist on documented condition reports as handover evidence. Asset verification that you have carried out yourself is worth far more than assurances you have simply been given.

IT, data and cybersecurity

IT is the workstream that most often surprises operators, and its importance is growing. Transport is now one of the most targeted industries for cyber attacks in Europe — the 2024 ENISA Threat Landscape report ranked it the second most attacked sector on the continent, and incident volumes across transport have risen sharply over the past five years. A cybersecurity baseline is no longer optional; it is a Day 1 requirement.

Two practical realities make this workstream hard. First, even well-run organisations rarely hold a complete systems inventory — a clear map of every system, integration and data flow. When you take one over, you are often discovering the IT estate as you go. Second, mobilisation happens during a period of heightened emotion, and people do not always tell you what is really going on with the systems they are handing over. Information is incomplete, sometimes deliberately. The workstream therefore needs to cover:

• a systems inventory: what transfers, what needs replacing, and what no one has documented;
• data ownership and access rights, confirmed in writing — not assumed;
• driver app and control-room technology readiness;
• a cybersecurity baseline assessment;
• customer-facing technology tested before Day 1, not on it.

Common mistake to avoid

The most damaging IT mistake is leaving systems integration and migration too late. Late IT migration is almost always more complex than the outgoing operator suggests, and the consequences land directly on customers when ticketing or information systems fail on Day 1. Confirm data access rights early, build in parallel running wherever possible so you can test before you rely on it, and treat technology readiness as a long-lead item rather than a final-week task.

Customer and communications

The customer workstream protects the customer experience through the transition — and how much it involves depends heavily on whether the brand is owned by the authority or by the operator. Where the authority owns the brand, a transfer can be almost invisible to customers; where the operator does, a full brand transition is required. Either way, the workstream covers:

• a brand transition plan and debranding timeline where relevant;
• a customer communications schedule before and after Day 1;
• booking system continuity confirmed and tested;
• accessibility obligations reviewed and actioned;
• a media and stakeholder communications plan.

Common mistake to avoid

The mistake here is assuming customers will not notice the transition. They do. Even a small gap in service change communications creates complaints risk and, because transport is so visible, reputational risk that travels quickly. Invest in clear transition messaging early so that customer awareness is high before anything changes, rather than letting customers discover the change through a problem.

Finance, Commercial and Procurement

The finance, commercial and procurement workstream makes sure the contract is financially operational from Day 1. It covers:

• a contract baseline established and agreed with the client;
• supplier novation and sub-contractor transfers completed;
• payment systems and processes operational from Day 1;
• a financial reporting framework set up and tested before go-live;
• a procurement pipeline identified for the early contract period.

Common mistake to avoid

The most frequent commercial error is underestimating the time needed for supplier novation. Third-party dependencies move slowly: subcontractors and suppliers have no urgency about your Day 1, and subcontractor transfer often stalls without persistent chasing. Start the procurement and novation process early, track it actively, and treat commercial readiness as something that depends on parties outside your control — because it does. Underestimating procurement risk here is a common cause of avoidable Day 1 gaps.

Running a mobilisation and not sure if your plan covers everything it needs to? Surbon Consulting works with transport operators and bid teams to build transport mobilisation frameworks that hold up under scrutiny.

Key risks and how to manage them

Every mobilisation carries a recognisable set of risks. The value of naming them early is that most can be managed if they are anticipated — and most become serious only when they are ignored. The table below sets out the risks we see most often, why they occur, and how to manage them.

Table 4: Mobilisation risk register

The outgoing operator dynamic

Several of the risks above share a single root cause: the outgoing operator. It is worth treating this as a dynamic in its own right rather than a series of separate problems. The incumbent controls information and assets you need, while having a commercial incentive to protect both — and you cannot manage them as you would your own team, because they do not work for you.

The way through is structural, not personal. Rely on the information-sharing and handover obligations in the contract; escalate through the client when cooperation stalls; and avoid building a plan that assumes a level of cooperation you have no power to compel. The operators who handle this best plan for limited cooperation as the base case and treat anything better as upside.

Tools and technology for mobilisation projects

What your mobilisation tracker should include

Most of mobilisation is coordination, and coordination needs a single, shared tracker that everyone works from. It does not need to be sophisticated software — a well-disciplined shared tracker is often more effective than an expensive tool no one updates. What matters is that it captures the right fields and is kept current. At a minimum, your mobilisation tracker should include:

• workstream;
• action or milestone description;
• owner;
• due date;
• dependencies;
• RAG status (Red / Amber / Green);
• last updated;
• escalation required (yes / no).

The discipline of keeping this current — and feeding it into the weekly report — is what keeps governance honest and surfaces slippage while there is still time to act on it.

Frequently asked questions

What is the difference between mobilisation and demobilisation?

Mobilisation and demobilisation are two sides of the same transition. Mobilisation is the incoming operator preparing to take over and start a contract; demobilisation is the outgoing operator winding down and handing it over. Both run in parallel during a contract transition, often through the same three-way meetings, but with opposite incentives. The incoming operator wants information, access and continuity; the outgoing operator is closing down its involvement and protecting its commercial position. Understanding that the handover process involves two organisations pulling in different directions is key to managing it well.

What does a Mobilisation Director do?

A Mobilisation Director leads the entire mobilisation and is accountable for delivering Day 1 readiness. Day to day, they own the client relationship, chair governance, coordinate the workstreams, and act as the risk escalation point and decision-maker when those workstreams conflict. Their job is workstream coordination and overall delivery, not doing each specialist’s work for them. Because the role requires the seniority to make decisions and the credibility to manage the client and the outgoing operator, it is not a role to give to someone junior or part-time.

How does mobilisation differ between bus and rail contracts?

The biggest differences come down to assets and regulation. Bus contract mobilisation typically centres on fleet and depot access, TUPE and union engagement, and usually runs to around nine months for a franchise. Rail contract mobilisation is shorter in nominal terms — often four to five months — but operates under much heavier regulation, with DfT oversight and the added complexity of rolling stock arrangements. In short, bus mobilisation tends to be dominated by depots, fleet and people; rail mobilisation by regulation and rolling stock. Both demand the same disciplined governance, but the long-lead risks sit in different places.

What should be in a transport contract mobilisation checklist?

A transport mobilisation checklist should be organised by workstream so that nothing falls between the gaps. As a minimum it should cover: operations readiness (timetables, depots, control room, Day 1 sign-off); people and TUPE (due diligence, union engagement, induction); assets and engineering (fleet condition, maintenance, depot agreements); IT and cybersecurity (systems inventory, data rights, cyber baseline, tested customer systems); customer and communications; and finance, commercial and procurement. Each item needs an owner, a due date and a clear definition of what ‘ready’ means. The checklist is not the plan, but it is how you prove the plan has been delivered.

How does mobilisation feature in transport operator bids?

In most large-scale tenders, mobilisation is a scored question worth roughly 3–10% of the overall bid evaluation, depending on complexity. A strong tender response sets out your planning process and governance, names your senior team, treats the workstreams distinctly, addresses the outgoing operator realistically, and provides mobilisation evidence from previous transitions. The most effective operator bid strategy treats mobilisation not as a standalone answer but as a mobilisation narrative that runs through the bid — reinforcing the message that your team can be trusted to deliver what it has promised.

How do you manage transfer of staff during contract mobilisation?

Good people management starts early and treats the transfer as a people process, not just a legal one. Begin with thorough due diligence on who is transferring and on what staff transfer terms, test the employee liability information you are given, and start employee consultation and union engagement before you are approached rather than after. Throughout, maintain clear workforce communications with transferring staff, who will be anxious about their future. The operators who manage people best are the ones who recognise that engaged, well-informed staff are the foundation of a reliable Day 1 — and that disengaged ones are an immediate operational risk.

Three ways Surbon Consulting can support your transport contract mobilisation

Mobilisation is high-stakes, time-bound and unforgiving of gaps — which is exactly why specialist support can make the difference. Surbon Consulting provides transport mobilisation support across the full lifecycle, from the bid that wins the work to the performance improvement that follows go-live. There are three main ways we help.

Bid strategy and mobilisation narrative

Before you mobilise, you have to win. We work with bid teams on bid strategy and a compelling mobilisation narrative — shaping the evaluation response to the mobilisation question, surfacing the right win themes, and building an evidence library of timelines met, issues resolved and client references that give evaluators confidence in your team. The goal is a mobilisation answer that scores well because it is credible, specific and clearly owned.

Mobilisation planning and delivery support

Once the contract is won, we support mobilisation planning and delivery support: building and running the project governance, establishing the workstream management structure, developing the living plan and tracker, and providing hands-on input through to Day 1 readiness. Whether you need an experienced pair of hands to run the PMO or specialist input into a single workstream, we can scale our involvement to match your team.

Performance improvement post-launch

Mobilisation does not end on Day 1. The early weeks of a contract often reveal issues that need rapid attention, and we provide post-launch improvement support to stabilise performance: KPI recovery where targets are being missed, operational performance reviews, and contract stabilisation that sets the foundation for continuous improvement over the life of the contract.