.svg){kind=small}
The Highways (Financing) Bill introduces a new licensing and regulatory framework for certain strategic roads in England, including a role for the Office of Rail and Road (ORR) as an independent economic regulator. For future licence holders, that changes the technical requirements of running a toll road.
This is not simply another tolling operation with a different contract. Licence conditions, charging rules, enforcement and reporting are now part of the operating model.
That raises a question for anyone bidding for or investing in a licensed toll scheme: what does the technology need to be capable of proving, reporting and managing?
What does being ORR-regulated mean in practice?
For a toll licence holder, ORR regulation means that charging and operating decisions sit within a regulatory framework. These are no longer purely commercial decisions. The technology therefore needs to provide reliable evidence of what has been charged, why it was charged and whether the operation is complying with its licence.
The Bill gives ORR powers to monitor this compliance, obtain information and take enforcement action where conditions are not met. It also establishes reporting and information disclosure requirements for regulated highways.
Charging itself is subject to controls. The Bill allows licence conditions to set the amount or maximum amount of tolls that can be charged, while an ORR code is intended to ensure tolling is fair and transparent.
That makes the technology behind the tolling operation part of the regulatory picture. A platform that can simply calculate a charge is not enough. Now, operators need to be able to show how that charge was generated, what vehicle event triggered it, what tariff or rule was applied and what happened afterwards.
The same applies to revenue. Transaction records need to be complete enough to support reconciliation and oversight. A number in a monthly report is less useful if the underlying transaction cannot be traced back to the original vehicle journey.
Regulation therefore becomes a standard technical requirement. The platform needs to support the operation every day, not produce a compliance report when somebody asks for one.
Why is free-flow tolling the starting point?
Free-flow tolling removes the need for vehicles to stop at a toll point, so detection, charging and payment have to happen without a physical barrier controlling the transaction. At the volumes and speeds expected on strategic roads, this is the operating model the technology needs to support.
The Bill specifically enables barrierless charging and identifies remote payment systems as a way to support smoother journeys while reducing congestion and safety risks. It also supports the adoption of modern tolling technologies like free-flow tolling.
That changes where the complexity sits. With a traditional barrier, the roadside infrastructure creates a physical checkpoint. The vehicle stops, the transaction can be resolved and the barrier controls what happens next.
Free-flow removes that checkpoint. A vehicle passes at road speed, while cameras and other roadside equipment capture the event. The platform behind that infrastructure then needs to identify the vehicle, apply the correct charge and manage what happens next.
For a regulated toll licence holder, the requirement goes further. The operator needs confidence that the system can do that consistently enough to support charging decisions that may later be questioned, disputed or reviewed.
What should a tolling platform be able to do?
A tolling platform needs to do more than identify vehicles. It should provide confidence in every charge, preserve the evidence behind each transaction, support transparent enforcement and continue operating reliably as volumes, rules and schemes change.
Accuracy
Every toll starts with a vehicle event.
The platform needs to distinguish reliable reads from uncertain ones and keep enough information about the capture to support the charging decision. An incorrect vehicle match can become much more than a technical error when it creates a financial liability for the wrong road user.
Accuracy should be judged across the whole transaction, not just by camera-read percentage. The question is whether the system provides confidence in the full charging event.
Auditability
A regulated operator needs to be able to reconstruct what happened.
That means retaining records that show the vehicle event, the charging rule, the amount charged and the subsequent payment or enforcement status. Reporting should support regulatory requirements without requiring teams to manually assemble evidence from across multiple systems.
The important test is simple: could the operator explain a disputed charge from the underlying record without reconstructing the journey by hand?
Fair enforcement
Non-payment is part of any tolling operation, but enforcement becomes particularly important when charging is taking place under a regulated framework.
The system needs to tell the difference between genuine non-payment and a failure elsewhere in the process. Evidence needs to be consistent, and the route from the original vehicle event through to any enforcement action needs to be visible.
Because the tolling framework includes penalties, appeals and disputes, enforcement needs to be closely connected to the original charging decision.
Scalability
The technology also needs to work beyond the first scheme.
A toll platform designed around one roadside configuration may appear perfectly adequate when choosing a system. But the challenge comes when the operator needs to introduce another charging point, change a tariff, support a different vehicle category or manage several licensed roads through the same operating environment.
Scalability is about more than transaction volume. It’s about whether the platform can accommodate new rules and infrastructure without creating separate systems that then have to be reconciled.
Intelligent capability
A modern tolling platform should also help operators spot transactions that need attention.
That could include unusual transaction patterns, lower-confidence vehicle reads or activity outside the normal behaviour expected for the scheme. The system should flag those cases for review rather than treating every transaction in the same way.
The purpose is not to replace operational judgement, but to direct that judgement towards the transactions where it is actually needed.
Why isn't older UK tolling infrastructure necessarily suited to this model?
Much of the UK's older tolling infrastructure was designed around individual sites, physical toll points and older operating models. The gap is not that older systems cannot process tolls; it’s that a new regulated model places greater demands on the data, reporting and flexibility behind each transaction.
A barrier-based system has a natural point of control. Vehicles stop, payment happens and the infrastructure provides a physical boundary around the transaction.
Free-flow changes that completely. There’s no vehicle stopping at the point of charge, so the back office has to create the certainty that the physical toll point once provided. The vehicle has already continued on its journey by the time the system needs to decide what happened.
That puts greater emphasis on the quality and availability of the underlying data. It also changes the importance of auditability. In older systems, some operational knowledge can sit across separate systems, reports and manual processes.
That can work while the operating model stays relatively fixed. A regulated licence creates a different requirement.
The operator needs to demonstrate compliance throughout the life of the licence. Charging rules may change, reporting requirements may develop and enforcement decisions may be challenged. The operation may also need to support new infrastructure or changing traffic patterns. A platform designed primarily to keep one toll point functioning may not have been built for those requirements.
This is the real procurement gap to look for. Not whether an existing system can detect a vehicle, but whether its underlying architecture can support a long-term regulated tolling operation without relying on manual workarounds to fill the gaps.
What should a bidder ask a technology partner before committing?
The most useful due diligence questions are operational rather than promotional. A bidder should be able to understand how the platform handles uncertain reads, proves individual charges, supports regulatory reporting, manages disputes and adapts when the scheme changes.
Before committing to a technology partner, it’s worth asking:
Can every charge be reconstructed?
Ask to see what the underlying record for a single transaction looks like, from the original vehicle event through to payment or enforcement.
How are uncertain reads handled?
A platform should have a clear process for uncertain reads rather than automatically billing every capture.
What evidence is retained?
Understand what is stored, for how long, and whether the operator can retrieve the information needed to support a dispute or review.
How are charging rules controlled?
A regulated scheme may have set tariffs and maximum charges. The operator needs to know how those rules are set up, tested and changed.
How does enforcement connect to the original transaction?
The evidence chain should remain intact from vehicle detection through to any penalty or recovery action.
What reporting can be produced directly from the platform?
The less manual reconciliation required to produce regulatory or financial reporting, the easier it is to maintain consistency.
What happens when the scheme changes?
Ask how a new tariff, vehicle class, charging point or additional road would be introduced. This shows whether the platform was designed for a long-term regulated operation or a fixed deployment.
How much of the operation depends on manual intervention?
Some intervention will always be necessary. The concern is whether people are resolving genuine exceptions or routinely correcting gaps in the system.
These questions move the focus from the roadside hardware to the technology running the wider tolling operation.
What does this mean for the technology decision?
For a future toll licence holder, the tolling platform is part of the operating infrastructure of the licensed road. It needs to support accurate charging today while providing the evidence, control and flexibility required throughout the life of the licence.
That makes platform selection about more than choosing equipment that can read registration plates. The roadside layer still matters, but it is only where the transaction begins. The more significant question is what happens after the vehicle has passed.
The real test is whether the platform can establish liability with confidence, explain how a charge was calculated, reconcile the money and provide the evidence needed for an appeal or regulatory review. It should also allow the operating team to change the scheme without rebuilding the technology around it.
For a licence holder working under regulatory oversight, those are not future enhancements. They need to be part of the operating model from the beginning.