The Fine Forecast
Average speed enforcement: when one journey becomes one case
Edited by
Autor
The Fine Hub

Average speed enforcement: when one journey becomes one case
Most fines are built around a moment: a camera, a flash, a time stamp. Average speed enforcement works differently. It measures the time a vehicle takes to cover a known distance and calculates the average speed over that stretch. The offence is a journey, not a point, and that changes how a fleet should handle the case.
Why the difference matters
A point camera produces a photograph with a plate and a speed reading. A stretch produces two observations and a calculation. The evidence is stronger on the facts, because the driver cannot argue about a single reading, but it is also more dependent on the system having identified the right vehicle at both ends. That is where fleet cases go wrong: not on the speed, but on the vehicle and the driver.
The technology is spreading. Average speed systems are part of the Dutch expansion to at least 1,450 enforcement locations by 2030, and later in 2026 a pilot starts with average speed enforcement on urban roads, the first in the country. On the A7 between Hoorn and Purmerend the effect was visible quickly: after the system was switched on, the number of drivers exceeding the limit fell by around 90 percent within two weeks.
What changes in the process
Three things. The evidence window widens, because the journey has a start and an end, so the driver match has to cover a period rather than a second. The dispute route narrows, because arguing about the measurement rarely works. And the volume arrives in a different pattern, because a stretch catches every vehicle that passes rather than the ones that happen to speed at a fixed point.
For a fleet with pooled vehicles or shift changes, that first point is the hard one. Two drivers can use the same vehicle within the measured period, and the case does not say which one was driving at the relevant moment. A record that stores who had the vehicle booked will not settle it.
What to review
Check whether the intake can store a start and end time for a case, not only an offence timestamp. Check whether the driver record can be queried by time rather than by booking. And check the dispute process: if a case is challenged, does the fleet have the route data and the vehicle data to support it?
A practical next step
Identify the stretches your vehicles use most and treat them as a separate category in reporting. Average speed cases behave differently from point cases in deadline, evidence and dispute, and grouping them with the rest hides both the volume and the failure pattern.
Your fine management, fine-tuned.
