How to Choose the Right Road Monitoring Technology in the PAS 2161 Era

Road closed in the UK due to floods

Route Reports

October 27, 2026

PAS 2161 Is the Starting Point: What Should Highways Teams Look for Next?

For years, the question around road condition monitoring was relatively straightforward: how do we survey the network and meet our reporting requirements?  PAS 2161 has changed that.

‍

Local highway authorities in England now have a wider choice of technologies capable of producing the road condition data required under the new standard. The current list of demonstrated technologies includes different approaches to capturing, analysing and presenting condition data — from dedicated monitoring hardware and specialist survey vehicles to smartphone-based systems.

‍

More choice is good for the sector. But it also makes the buying decision more complicated.

Because PAS 2161 approval provides a baseline. It doesn't make every approved technology operationally equivalent.

‍

And with the 2026 ALARM Survey estimating a record £18.62 billion carriageway repair backlog across England and Wales, choosing technology that simply produces another dataset is unlikely to be enough.

For councils reviewing their options, we think there is a more useful question to ask:

Which technology will give our highways team the most useful intelligence for the other 364 days of the year?

‍

Six Areas Worth Looking At

‍

1. Start with the outcome, not the technology

Before comparing cameras, apps, AI models or dashboards, define what you actually need the technology to achieve.

  • Is the priority to simply meet national reporting requirements?
  • Improve visibility of network condition?
  • Reduce manual inspections and use resources more effectively by automating routine data collection and focusing skilled people where their expertise adds the most value?
  • Identify defects earlier?
  • Build stronger evidence to support investment decisions and demonstrate why budget has been prioritised in particular areas?
  • Create a more current picture of the network that can support everyday operations?

‍

These requirements can overlap, but they aren't necessarily the same.

‍

A technology designed primarily for periodic strategic surveys may be very good at that job. Another may be designed around high-resolution asset imagery. Others may be better suited to frequent defect monitoring. 

‍

This is why feature-by-feature comparisons can quickly become misleading. Don't start by asking which system collects the most data. Start by asking what you need that data to help your team do differently. Once that outcome is clear, comparing the market becomes much easier.

‍

2. Look closely at how the data is captured

“AI road monitoring” now covers some fundamentally different technologies.

‍

For example, smartphone-based systems use a phone mounted within a vehicle to capture road imagery. At the other end of the spectrum, specialist survey providers use dedicated vehicles equipped with sophisticated imaging technology.

‍

Route Reports takes another approach.  Our technology uses a dedicated device installed within vehicles already travelling the network. Once installed, capture happens automatically as those vehicles complete their normal journeys.

‍

Why does that distinction matter here? Because the way data is captured affects the consistency and repeatability of the information you receive. A useful principle is:

‍

If you want to understand change, you first need consistency in how you measure it.

‍

A fixed camera remains in a known position. Its relationship with the road doesn't change from one journey to the next, and the system can be calibrated around that position.

‍

That becomes particularly important when you're interested not simply in whether a pothole or defect exists, but its dimensions, exact location and what happens to it over subsequent journeys.

There is also a practical question that is easily overlooked during procurement:

‍

What does the driver actually have to do?

Does something need mounting or positioning before a journey? Does an application need starting? Does a specialist survey need scheduling? Or does collection happen automatically?

‍

A few additional steps may seem insignificant.  Multiply them across thousands of journeys, different drivers and an entire network, and they can become much more significant.  There is also the question of when the data can be used.  Live?  Or later than this once data has been collected, downloaded, and inputted to the relevant reporting system (or systems.)  All of these elements have a huge bearing on not only what the data is, but how readily usable and useful it is for stretched highways teams.  This brings us onto our next point…

‍

3. Ask how current the data really is

“Real-time” is used so frequently in technology that it can mean almost anything. For highways teams, there is a more useful question:

‍

How long is it between a vehicle passing a defect and somebody being able to do something with that information?

‍

Different technologies answer that question differently.

‍

Some capture imagery or video before uploading it for cloud processing. Some are designed around scheduled surveys. Others combine different datasets collected at different frequencies.  Route Reports uses edge processing, which means AI analysis can take place within the device fitted to the vehicle.

‍

The advantage of a GPU

Inside a Route Reports device is GPU-enabled processing capability.  That sounds technical, but its purpose is straightforward: it gives the device the computing power to analyse imagery where it is being captured, rather than simply recording everything and sending the raw footage somewhere else to be understood later.

‍

Relevant detections and imagery can then be transmitted as the vehicle moves around the network, supported by multi-network mobile connectivity.

‍

The result is a much shorter relationship between capture and insight.

‍

Instead of: Survey → upload → process → wait → review the ambition becomes much closer to:

‍

That difference won't matter equally for every use case.  If you're commissioning an annual strategic assessment, receiving results later may be perfectly acceptable.

‍

But if you want the same technology to support defect management, inspections, resident enquiries or response after severe weather, data freshness becomes much more important.

‍

So rather than asking a supplier, “Is your data real-time?”, ask:

‍

Which data is available when, how has it been processed, and exactly when can my team see and use it? 

‍

It’s also crucial to understand what the team’s involvement and potential workload is here – if there is a need here – i.e. what has to happen to move the data from collection to the systems used to analyse it and make decisions, and who does that part?

‍

4. Don't just compare accuracy. Compare the evidence behind each detection‍

PAS 2161 has rightly placed accuracy and repeatability at the centre of road condition monitoring.  The approval process provides councils with important assurance that demonstrated technologies can meet the relevant requirements.

‍

But once you're comparing approved technologies, “Is it accurate?” is only the beginning.  The more revealing question is:

‍

What do I actually get when something is detected?

For an individual defect, that could include:

‍

  • its precise location
  • current imagery
  • classification and measurements
  • the date and time it was detected and
  • evidence from previous detections.

‍

That last point is particularly important.  Knowing there is deterioration at a location is useful.

‍

Knowing this is the same defect we saw previously, this is what it looked like then, and this is what it looks like now gives an engineer much richer evidence on which to make a decision.

‍

When historical network information is retained it allows teams to review previous observations and imagery and make a direct, quick, comparison over a set period of time.  It also creates an important distinction:

‍

A detection tells you what is there. History gives you context for what to do about it.

‍

That context becomes increasingly valuable as authorities move towards more preventative approaches to maintenance.

‍

The Government has committed £7.3 billion of capital funding for local highway maintenance between 2026/27 and 2029/30, alongside stronger expectations around asset management, transparency and long-term planning.

‍

Better decisions therefore depend on more than simply knowing where defects are.  Teams increasingly need to understand what is changing, how quickly and where intervention is likely to have the greatest impact.

‍

5. Understand what happens to the data before it reaches you

One of the less visible differences between monitoring technologies is what happens between the camera seeing the road and information appearing on your screen.

‍

This is worth understanding.  Ask suppliers:

‍

  • Where does the AI processing happen — on the device, in the cloud or both?
  • Does an entire video need to be uploaded?
  • What happens when mobile coverage disappears?
  • What information is stored locally?
  • How and when is imagery anonymised?
  • How much raw data needs to move around the system?

‍

These questions matter for speed and resilience, but also for privacy and data management.

Route Reports' edge-processing architecture means processing can happen within the vehicle, with relevant information then transmitted to the platform. The system is also designed to anonymise imagery on the device before relevant imagery is uploaded.

‍

For councils covering large rural areas, connectivity deserves particular attention too. A system that works perfectly with strong mobile coverage still needs a strategy for the stretches of network where that coverage disappears.

‍

These aren't necessarily the exciting questions on a technology demonstration.  They can be some of the most important ones once the system is operating every day.

‍

6. Think beyond today's PAS 2161 requirement

PAS 2161 is an important change, but councils aren't really investing in a PAS return.  They're investing in a source of network intelligence that they may depend on for years. That changes the final procurement question:

‍

Will this technology still meet our needs as those needs evolve?

‍

TRL's ongoing approval process already reflects the fact that the market itself will continue developing.

Councils should therefore understand how easily a technology can evolve too.  This means understanding…

‍

  • If AI can models be updated?
  • Can new types of defects or assets be added?
  • Can intervention levels and inspection requirements be configured around the authority?
  • Can the platform evolve without replacing hardware or fundamentally changing the operating model?
  • And, increasingly, can the information ultimately connect with the systems teams already use?

‍

It’s also worth thinking about where the data goes next. The end goal shouldn’t be another isolated source of highway data or another platform for teams to manage.

‍

The real value comes when better network intelligence can feed into existing workflows and help teams make better maintenance decisions — whether that means validating a defect, prioritising an intervention or creating a stronger evidence trail.

‍

This is where the conversation around AI in highways is beginning to mature. Identifying defects is only one part of the picture.

‍

“The bigger opportunity is making that intelligence useful within everyday highway operations — connecting automated data capture with the people, processes and systems that ultimately turn insight into action.” Said Connell McLauglin, CEO of Route Reports.

‍

The Buyer's Checklist: 10 Questions To Ask Before You Choose

If you're currently evaluating road monitoring technology, we'd recommend taking these questions into supplier conversations:

‍

  1. ‍Is the exact technology being proposed PAS 2161 approved?
  2. What is it primarily designed to do beyond PAS compliant reporting?
  3. What does the driver need to do for data to be captured?
  4. Is the capture position fixed and repeatable between journeys?
  5. Where does the AI processing happen?
  6. How quickly after capture can our team use the information?
  7. What information and measurements sit behind each detection?
  8. Can we easily compare repeat observations and historical imagery?
  9. What happens to the data when connectivity is poor?
  10. How will the technology evolve as our requirements change?

‍

None of those questions has one universally “correct” answer. The right answer depends on what your authority is trying to achieve.  And that is really the point.

‍

PAS 2161 is the starting line, not the finish line

PAS 2161 has given councils something the market needed: a common standard and a clearer quality threshold for road condition monitoring.  But accreditation shouldn't remove the need to look under the bonnet.

‍

A smartphone-based system may provide flexibility and rapid deployment. A specialist survey vehicle may provide exceptional levels of imagery and asset detail. A dedicated monitoring device can provide consistency, automation and frequent intelligence from vehicles already travelling the network.

The important thing is understanding those differences and matching them to the required outcome, and importantly – one that will be future-proof and therefore a wise use of budget.

‍

At Route Reports, our approach has deliberately been built around making road monitoring part of everyday highway operations: fixed devices, automatic capture, calibrated cameras, GPU-enabled edge processing, current defect information, measurements, precise locations and historical evidence.

Not because collecting more data is the objective.  Quite the opposite.

‍

The objective is to turn the journeys already happening across a network into useful evidence that helps highways teams make better decisions.

‍

PAS 2161 answers one important question: Can this technology produce road condition data to the required standard?

‍

Now councils need to ask the question that comes next: What else can it do for our network?

‍

Work with us

If your team is reviewing PAS 2161 approved technologies or considering how road monitoring could support your wider maintenance strategy, we’d be happy to share what we’re seeing across the sector and explore what might work for your network.

‍

Our online demo shows how Route Reports combines automated capture, AI-driven inspections, edge processing, current network imagery and historical evidence in practice.

‍

Watch our online demo or get in touch to explore what better road monitoring could look like for your network.

‍

Transform the way you understand infrastructure

Complete the form to find out how we can upgrade your rail or road operations and maintenance systems, with AI enhanced hardware and software.
‍
Alternatively, email us at:
contact@routereports.com