Can continuous improvement survive the life of a contract?
An ambitious tender response will not improve a bus network on its own. The live contract must require decisions, evidence and follow-through.
People search for
In this article
We have sat on tender evaluations where a Supplier’s continuous-improvement proposal was thoughtful, practical and well presented. It won strong marks. A few years later, the same proposal had become a document that nobody used in the monthly contract meeting.
This is not always a failure by the people involved. Priorities change, staff move to other jobs, operational problems take over, and an improvement that requires funding, data or an Authority decision can be deferred. Tender evaluation often rewards the quality of a promise and plan. The contract must govern what happens when that promise meets everyday service pressures.
A promise needs a route into the contract
An Authority should be able to trace its tender requirement into the live arrangements. If a bidder is asked for a rolling Improvement Plan, the contract should state when the plan is submitted, who reviews it, what evidence it must contain and how agreed actions are monitored. If the tender response proposes a way to improve reliability, passenger information or the handling of complaints, the Authority needs to decide whether this is a binding commitment, an option to develop or an illustrative idea.
The distinction matters. A plan submitted once at mobilisation can satisfy an administrative requirement without changing a single passenger journey. A rolling plan gives the Authority and Operator a reason to revisit the evidence: perhaps recurring missed connections after school, a pattern of cancelled journeys or avoidable failures in a local ticketing product. It should include a named owner, a realistic delivery date and a record of whether the expected result was achieved.
Some improvements will require funding, a change to the specification or a formal contract variation. The process should ensure that a justified proposal reaches a decision and that both parties can see the consequences of delay.
Where contracts tend to lose momentum
In practice, momentum is usually lost in one of four places:
- an improvement plan has no review date
- a proposal is left unresolved because the parties disagree
- payment has no connection to the result
- the governance meeting can note an issue without deciding it.
| Contract provision | What the Authority should be able to see |
|---|---|
| A recurring improvement plan | Updated actions, owners, milestones and evidence from the previous period |
| A route for unresolved proposals | A stated escalation or decision point when the Authority and Operator cannot agree |
| Proportionate performance consequences | How a sustained failure or a verified improvement affects the payment or performance regime |
| A decision-making governance forum | Minutes that record approval, rejection, deferral and the reason for it |
| Evidence requirements | The service data, customer feedback or other test that will demonstrate the result |
A fifth weakness is evidence. A plan populated with assertions about better service tells an Authority very little if it does not identify the relevant data, passenger feedback or operational record.
A payment mechanism can help, but it is not a substitute for management. Link a modest, measurable part of the regime to matters the Operator can influence rather than create a large theoretical incentive that neither party can administer. A performance deduction will not resolve a recurring problem if nobody is responsible for proposing the fix.
The governance forum needs sufficient decision-making power or a prompt route for escalation. A monthly meeting that only receives reports becomes a filing system. The papers should distinguish actions that the Operator can take within the existing service from those that require an Authority instruction, budget decision or contractual change.
Keep tender and delivery connected
The tender should assess how the bidder will operate these arrangements, including the quality of the proposed evidence and the seniority of the people who will take part. The draft contract should then make the successful approach usable without reproducing every page of the tender response. Procurement, operational and legal teams need to do this together. It is difficult to repair after award.
LiteFranchise™ includes a contract suite with governance, KPI and payment provisions, and describes continuous improvement as part of its approach to Authority-led transport. Authorities must still tailor any framework to their network, local priorities and the evidence they can reasonably review.
Useful questions
Before finalising a procurement or reviewing a live contract, ask:
- Does the contract require the improvement plan to be refreshed and reviewed, rather than merely submitted at mobilisation?
- What evidence must an Operator provide before an improvement is accepted as delivered?
- When the Authority and Operator cannot agree a target or proposal, who must decide and by when?
- Does the performance regime create a credible consequence for sustained drift, while keeping the measures practical to administer?
- Do the contract meeting papers show which actions are within the Operator’s control and which need an Authority decision?
More on Continuous Improvement & Performance
