Study CV-0226 · September 2026 · 152 programmes · Five markets

Only 5.9% of traffic enforcement programmes demand AI. None set a standard for it.

AI in Traffic Enforcement: Authority Mandate or Vendor Offer? A five-year audit of 152 validated traffic enforcement procurement programmes across five markets, three continents and 30 countries, published between June 2021 and May 2026.

Mandatory
4.6%
7 of 152 programmes specify AI as a compulsory element of the delivered system
Required or mentioned
1.3%
2 of 152 name AI without compulsory framing, or record a passing mention
No AI language
94.1%
143 of 152 contain no reference to AI, machine learning or computer vision
0
Zero performance standard

Not one of the 152 programmes attaches a performance standard to an AI function.

01

What the data shows

Mandate strength
AI mandate level · 152 programmes
None 143 (94.1%)
Mandatory 7 (4.6%)
Required 1 (0.7%)
Mentioned 1 (0.7%)
AI is not absent from traffic enforcement. In the overwhelming majority of published procurement programmes, the authority simply did not specify or demand it.
02

Where AI language appears

Rate within each group
By market
Australia / New Zealand
35.3% 6 of 17
United States
3.2% 2 of 63
Europe (excl. UK)
2.9% 1 of 35
United Kingdom
0.0% 0 of 28
Canada
0.0% 0 of 9

Australia and New Zealand hold 6 of the 9 AI-positive programmes from 11.2% of the dataset.

By delivery model
Outsourced / managed service
9.8% 8 of 82
Direct procurement
1.4% 1 of 70

8 of the 9 AI-positive programmes sit in outsourced or managed service contracts.

By deployment mode
Mobile (incl. trailer)
28.6% 8 of 28
Work zone
12.5% 2 of 16
Average speed
3.1% 1 of 32
Fixed / semi-stationary
2.0% 1 of 50
School zone
0.0% 0 of 20
Red-light
0.0% 0 of 39

Deployment modes overlap: a programme deploying more than one mode is counted in each, so the rows do not sum to 152.

Joint conditions

AI language clusters in outsourced mobile programmes, most of which also procure secondary detection. Elsewhere it is close to absent.

03

Five-year rate

2021 to 2026

The share of programmes containing AI language, calculated separately for each year, shows no sustained movement across the study period. The rate in 2025 is no higher than in 2021.

2021*
1 of 11
2022
2 of 40
2023
2 of 42
2024
3 of 33
2025
1 of 21
2026*
0 of 5
Programmes published
Containing AI language

* Partial years: 2021 covers June to December, 2026 covers January to May.

04

Authority mandate or vendor offer?

Study assessment

If an authority demanded AI, adoption is led from the top, against a published standard. If a supplier offered it, adoption is pushed from the bottom, against no standard at all.

SignalIf authorities were leadingWhat the record shows
Contract modelAI specified in direct procurements the authority designs8 of the 9 AI-positive programmes are outsourced. Of the 70 procurements an authority ran directly, just one names AI, and only as a passing mention.
WordingFunction-specific requirements drafted per jurisdiction6 of 9 repeat the same phrase, “artificial intelligence enabled”, across independent jurisdictions
Test attachedAccuracy, validation and audit terms that can be enforced0 of 152 attach any performance or audit term
Sensing layerRequirements covering radar and LIDAR processing as well as cameras0 of 152 attach AI to radar, LIDAR or sensor fusion
Capability vs requirementBehaviour detection procured with the technology named3 programmes procure behaviour detection and name no AI at all
Study assessment

These observations are consistent with adoption led from the supplier side rather than specified from the authority side.

This is an inference, not a measured finding: the records show what was written, not who proposed it.

05

Conclusion

Author’s assessment

Every AI reference in the dataset points at the camera. None points at the radar or LIDAR sensors. Authorities should extend their AI requirements to the sensor, and state the standard it must meet and how it stays compliant under type approval.

The technology is ready, and it is already producing enforcement evidence. The specification has not caught up. Authorities that write AI requirements now will set the standard the market builds to. Those that do not will buy the capability anyway, on terms written by someone else.

06

Full report, data and citation

Read the full report

The complete findings report, with all tables, figures and the author's assessment, is free to download. No registration or email is required.

Raw data available on request

The record-level dataset behind every figure on this page (152 active records, 37 rejected records, Dataset v16.1) is available for review to journalists, researchers and practitioners. Email dudi.cohen@curvidia.com with your organisation and intended use.

Suggested citation

Cohen, D. (2026). AI in Traffic Enforcement: Authority Mandate or Vendor Offer? An Analysis of 152 Validated Traffic Enforcement Procurement Programmes, June 2021 to May 2026. Curvidia. Study CV-0226, Dataset v16.1.

07

Methodology

Dataset v16.1
Sample

152 validated programmes published between June 2021 and May 2026 across the United States, Europe (excluding the UK), the United Kingdom, Australia and New Zealand, and Canada: 30 countries in total.

189 records were examined. 37 were rejected where the enforcement function could not be confirmed, a framework carried no award, or validation found the record unsupported.

Scope

Core automated enforcement: speed, red-light and average speed, in any deployment context, including fixed, mobile, school zone and work zone.

AI applied to any detection function is in scope: camera and image analysis, and radar, LIDAR and other sensor processing. Back-office functions are not assessed.

What counts as AI language

Artificial intelligence, AI, machine learning, deep learning, neural network, computer vision, video analytics, and named AI detection products, applied to any sensing modality.

Number plate recognition (ANPR or ALPR) on its own is not counted. Plate reading predates the technologies measured here.

Mandate levels
  • Mandatory: AI specified as a compulsory element of the delivered system
  • Required: AI named as a requirement without compulsory framing
  • Mentioned: AI referenced with no requirement attached
  • None: no AI, machine learning or computer vision language
Sources

TED (Tenders Electronic Daily), UK Find a Tender, UK Contracts Finder, SAM.gov and US state portals, AusTender and Australian state portals, GETS (New Zealand), CanadaBuys, MERX and BCBID. Supplier releases, regulatory disclosures and government announcements used for confirmation only. 35 distinct source designations.

Validation

Every record is confidence-rated against its source: High 114, Medium 28, Low-Medium 9, N/A 1.

All 9 AI-positive programmes are award notices recorded at High confidence, the study's highest source-verification tier.

Limitations
  • The study measures language in procurement records, not deployed technology. A programme with no AI language may still be delivered using AI, so 5.9% is a floor for capability and a measure only of specification.
  • Only publicly documented procurements are included. An AI requirement in an unpublished specification would not be captured.
  • All classification decisions were made by a single analyst. Type approval and legal metrology frameworks were not assessed.