The Fare Follows the Passenger: Building Cross-Boundary Ticketing That Lasts

A passenger travelling from a market town to a regional centre may cross two or three administrative boundaries without noticing. The fare system, however, notices every one of them. In many UK regions in 2026, the result is a journey that is physically possible but commercially awkward: separate tickets, different conditions, uneven concessions and a passenger left to work out which combination is valid.

Cross-boundary ticketing is sometimes presented as a software problem. It is not. The technology matters, but the decisive issues are governance, money and trust. A ticket that works across operators is, in effect, a small contract between organisations that may compete elsewhere. Unless that contract is designed carefully, the pilot will work in the demonstration phase and fail when the funding runs out.

Begin with the journey, not the product

Transport authorities and operators should start by mapping the journeys that matter, not by selecting a ticketing platform. The relevant corridors are usually known: the hospital route that crosses a county line, the bus that feeds a rail station in a neighbouring authority, the college service used by students from three districts. These journeys provide the evidence base for fare simplification.

Simplification does not mean a single flat fare across a region. It means a small number of legible products that passengers can understand without reading aConditions of Carriage document. Zonal fares, daily caps and add-on tickets for the cross-boundary segment are all practical options. The test is whether a passenger can buy the right product at the first attempt and whether staff at the roadside can explain it consistently.

A useful discipline is to publish a simple journey matrix before designing the product. For each priority corridor, set out the existing fares, the number of operators involved, the concessions available and the points where validity changes. That matrix will expose anomalies early and give the pilot a baseline against which to measure success.

Follow the money before the launch

Revenue allocation is the point at which many multi-operator schemes stall. Operators will not sign up to a product that exposes them to uncontrolled revenue risk, and smaller operators are right to be cautious about a formula designed around the largest participant.

A workable allocation model should be agreed in principle before any passenger-facing launch. It does not need to be perfect, but it must be transparent. Options include allocation by validated journey data, by a pre-agreed corridor weighting, or by a hybrid model that uses data where it is reliable and a fallback formula where it is not. The key is to avoid a system in which one operator carries the cost of another operator’s commercial decisions.

Authorities can help by funding a shadow-running period. During shadow running, the product is recorded but not sold, allowing partners to compare modelled allocations with observed patterns. This is also the moment to test how the scheme treats disruption, replacement services and journeys that begin on one operator and finish on another after a delay.

Neutral governance matters as much as the formula. A multi-operator fare scheme needs a decision-making group with clear terms of reference, an independent chair where possible, and a dispute route that does not depend on the goodwill of the largest operator. If the scheme is hosted by a transport authority, the authority should be explicit about its dual role as funder and referee.

The back office is the product

Passengers see a ticket. Partners see a reconciliation process. If that process is slow, opaque or bespoke to each operator, the scheme will consume more management time than it saves.

A common data specification is therefore essential. It should cover ticket validation, journey records, concession categories, refunds and the treatment of incomplete journeys. Where existing standards can be used, they should be. Where they cannot, the pilot should fund a translation layer rather than require every operator to rebuild its own systems.

Data sharing also raises legitimate questions about privacy and commercial confidentiality. These should be answered in the scheme agreement, not left until a subject access request arrives. Aggregated journey data may be sufficient for allocation; passenger-level data should be collected only where it is necessary and retained only for as long as the scheme requires.

A useful principle is that the back office should be boring. Partners should be able to see how a payment was calculated, query an anomaly and receive an answer within an agreed period. If reconciliation depends on a single spreadsheet maintained by one officer, the scheme is not yet ready to scale.

Trust is earned at the roadside

Passenger trust is not built by a launch event. It is built by consistency. A cross-boundary ticket must be accepted without argument, refunded under clear rules and supported by staff who know what to do when the technology fails.

That means investing in frontline training and simple passenger information. Operators should agree a common charter covering validity, disruption, refunds and accessibility. The charter should be published in plain English and, where relevant, in Welsh and other community languages. Digital products should be accompanied by a non-digital route to the same fare, particularly for older passengers and those without smartphones.

The pilot should also include a visible complaints route. A passenger who cannot resolve a cross-boundary issue at the roadside will lose confidence in the whole scheme, not just the ticket. A single contact point, even if it simply triages to the right operator, is better than a list of separate customer service numbers.

A pilot designed to outlive its funding

Many ticketing pilots are evaluated on whether they worked, rather than whether they can continue. In 2026, with local transport funding under scrutiny, the second question matters more. A pilot should be designed from the outset with a transition plan: what will be mainstreamed, what will be stopped and who will pay for the residual costs.

The following checklist is a practical starting point for authorities, operators and member organisations preparing a cross-boundary fare scheme.

• Define two or three priority corridors and publish a baseline of existing fares, journey patterns and concession arrangements.
• Agree a written revenue allocation protocol before launch, including a shadow-running period and a dispute route.
• Adopt a common data specification for validation, reconciliation and refunds, with a clear privacy statement.
• Establish a neutral governance group with operator representation, authority representation and independent oversight.
• Publish a passenger charter covering validity, disruption, refunds and accessibility.
• Train frontline staff and test the scheme with real passengers before full launch.
• Set evaluation measures that include passenger confidence and operator administrative burden, not only ticket sales.
• Agree a funding transition plan that identifies which costs will continue after the pilot.

Cross-boundary ticketing will not solve every problem in regional transport. It can, however, make the network feel like a network rather than a set of adjacent franchises. The schemes that endure will be those that treat the fare as a governance arrangement as well as a price. If the money follows the passenger, and the rules are clear enough for staff and travellers alike, a multi-operator ticket becomes more than a pilot. It becomes part of the everyday expectation of regional travel.