A motorist who has just paid to replace a tyre is unlikely to be impressed by a computer identifying the pothole that damaged it.
The driver already knows where the hole is. So do the neighbours who slow down before reaching it and the commuters who have learned to steer around it.
Their question is when someone will fix it.
That frustration is understandable. But it should not lead us to dismiss a tool that could help the Ministry of Works make better decisions about road maintenance.
Minister Clay Sweeting says the ministry’s road assessment software, costing approximately $45,000 annually, does considerably more than locate potholes. It analyses footage collected by inspectors to assess road surfaces, markings and other defects, helping officials prioritise repairs and check contractors’ work.
There is a sensible purpose here. Public money should be directed according to the condition and use of a road, the danger it presents and the work required. A reliable record could help prevent maintenance decisions from depending on who complains loudest or has the best political connection.
Mr Sweeting deserves credit for being willing to improve how his ministry works.
He should also understand why the public’s patience is limited. People experience road maintenance through the journey to school, the delivery that arrives late and the repair bill they had not budgeted for. Confidence will come when those experiences improve.
The ministry should therefore connect every assessment to a decision. A serious defect should generate an inspection, a repair instruction and a timetable. Where permanent work must wait, officials should explain why and take appropriate steps to reduce the immediate danger.
An expanding database of damaged roads would be little comfort if the repair crews remain unable to keep pace.
The ministry should publish straightforward measures of progress: how quickly dangerous defects receive attention, how much scheduled work is completed and how often repaired sections require further work. Those figures would give taxpayers a fair basis for judging the system’s annual cost.
Contractor accountability offers a particularly useful opportunity.
If officials can compare a road before and after work, they should use that evidence when inspecting jobs and approving payment. Contracts should establish the required standard and the responsibility for correcting defective work. Taxpayers should not repeatedly finance repairs that fail because the original job was inadequate.
Engineers must remain responsible for interpreting what the technology finds. A visible surface defect may require further investigation before the right remedy can be chosen. The software should help them focus their attention, while professional judgment determines the work.
Planning between agencies deserves equal attention. Before resurfacing a road, the ministry should establish whether utility work is imminent. Residents should not have to watch a newly finished surface being opened again because public bodies failed to coordinate their schedules.
Mr Sweeting has also outlined plans for an interactive reporting system through which residents could submit pothole and drainage complaints.
That service should acknowledge each report, provide a reference number and tell the resident what happens next. People will be more willing to report problems formally when they can see that someone has received the information and acted on it.
There should also be clear guidance for motorists seeking an assessment of damage allegedly caused by road defects. A fair process requires evidence, accessible instructions and a response within a reasonable period.
The debate should move beyond whether artificial intelligence belongs in road maintenance. The ministry should be encouraged to use tools that improve its work and held accountable for what follows.
Motorists do not need to understand the software. They need to arrive home without another damaged tyre, another dangerous swerve or another repair they cannot afford.
That is how this investment should be judged.



Comments
Use the comment form below to begin a discussion about this content.
Sign in to comment
OpenID