A fleet pilot needs a written stopping rule

A fleet pilot is useful when it reduces a specific uncertainty. It becomes less useful when vehicles remain labelled experimental indefinitely, gathering data that nobody has agreed how to interpret. A written stopping rule makes the pilot a decision process with a defined purpose and an accountable conclusion.

Identify the uncertainty

State what is unknown about the proposed operating arrangement. It may concern charging access, a conversion, route variability or driver workflow. Separate that question from issues already understood. A pilot that attempts to answer every possible fleet question risks collecting scattered observations without resolving the condition that prevents a purchasing decision.

Select an assignment that exposes the uncertainty fairly. Avoid a convenient route solely because it makes deployment easy, or an exceptional route solely because it appears demanding. Explain why the chosen work represents the intended fleet segment. This allows reviewers to understand where the conclusion can reasonably be applied.

Agree evidence before launch

Specify which records and observations are needed. These could include completion of assigned work, charging readiness, interventions and user feedback tied to particular tasks. Decide who will collect each item and how missing records will be handled. Evidence gathered inconsistently can make the final discussion depend more on memory than on the pilot.

Distinguish operational outcomes from technical diagnostics. The supplier may need detailed vehicle information to investigate a fault, while the fleet needs to know how the interruption affected service. Both can be useful, but they should not be confused. A technically interesting result does not necessarily answer whether the organisation can repeat the work dependably.

Define decision points

Agree the conditions that would support expansion, require changes or justify stopping. These conditions should relate to the uncertainty, not to arbitrary enthusiasm for the programme. Include a review date and an owner for the recommendation. The stopping rule can allow further targeted work when a material question remains unresolved.

Avoid interpreting any intervention as automatic failure. A planned change to allocation may be practical at scale, while constant exceptional support may not be. The review needs to describe the resources and responsibilities that repetition would require. This is where operations, finance and procurement should challenge the result together.

Preserve the learning

Write a conclusion that identifies the tested configuration, assignment and support arrangement. Retain the boundaries and unresolved issues. A successful pilot on one work pattern is evidence for that pattern, not a general promise about every asset in the fleet. A stopped pilot can still produce useful information for a revised specification.

Move the decision into the ordinary replacement and infrastructure plans. If the result remains outside those processes, the pilot has not completed its business purpose. A clear stopping rule helps the organisation turn evidence into action, while avoiding the temptation to extend the exercise simply because a difficult choice still needs to be made.