A single place to track the legislation, understand what it actually requires, and see how other councils are approaching the transition.
Everything UK councils need on Digital Traffic Regulation Orders
Not sure which situation fits your council? Get in touch and we can help you think it through.
Where things stand
The legislative journey to mandatory D-TROs
The Automated Vehicles Act 2024 already makes standardised, digital TRO data a legal requirement. The remaining step is a statutory instrument (SI) that sets the detail – expected to go before Parliament for a vote soon. Once it passes, councils will have roughly a 3-month window to bring new Traffic Orders into the D-TRO format.
The basics
What is a D-TRO, and why now?
A D-TRO is the digital evolution of the traditional TRO: map-based and standardised. It’s a single, real-time source councils, satnavs, and enforcement systems can all read.
It’s happening now because the Automated Vehicles Act 2024 makes this a legal requirement, not just a recommendation – partly so autonomous vehicles can read restrictions in real time, partly because councils have long wanted exactly this.
What actually changes for your council:
• TROs published as standardised, open, digital data
• New orders required in D-TRO format from the compliance date
• Service levels and application fees published for transparency
• Statutory consultee list reviewed to include AV industry stakeholders
• A “new burdens” funding process from the DfT is expected to follow, to help authorities meet the cost of compliance
Real examples
Councils already running on D-TROs
A few stories from teams who’ve already made the move – what changed for them day to day, in their own words.
The Essential Digital Traffic Orders Guide
A full how-to handbook for local highway authorities: legislation and timescales, the case for early adoption, build-vs-buy, procurement via G-Cloud, onboarding from legacy systems, and real case studies.
Benefits, end to end
What changes once you’re digital
Efficiency & speed
Faster drafting, review and approval, with real-time updates instead of reprinted documents.
Accuracy & consistency
Standardised templates and automated checks remove the errors that come with manual, text-based orders.
Accessibility & transparency
Public, current, and proposed restrictions are viewable online: easier consultations, fewer disputes.
Cost savings
Less paperwork, less physical storage, less reliance on a single specialist who holds all the knowledge.
Enforcement confidence
Integrates with ANPR and enforcement partners, cutting time spent on contested PCNs and FOI requests.
Kerbside & sustainability data
Standardised TRO data doubles as reportable insight — EV charging, cycle hangars, loading, sustainable kerb use.
Smart city & GIS integration
Connects with ArcGIS, asset systems, and other council platforms rather than sitting in a silo.
Environmental impact
Less printing and searching for parking; better-managed kerb space supports active and shared travel.
Find the right fit
Build it yourself, or buy a solution that’s D-TRO compliant out of the box?
Both are legitimate paths. The honest trade-off: in-house gives full control but carries long build times, ongoing maintenance, and no guarantee of compliance with the DfT’s data model. A purpose-built platform is compliant from day one and comes with a dedicated support team – the cost is less bespoke customisation.
How long does onboarding with a ready AppyWay solution actually take?
- The fast-track Mapper Lite route, aimed squarely at meeting the compliance deadline, is an instant solution.
- A full Traffic Suite implementation, including data migration and training – typically takes as little as 3 months (including full in-person team training for your extended team)
In-house development
- No guarantee of D-TRO compliance without dedicated GIS expertise
- High initial cost and lengthy discovery before you know if it’s even feasible
- Knowledge risk if the one person who understands the system leaves
Purpose-built D-TRO software
- Compliant with the DfT’s D-TRO data model out of the box
- Predictable subscription cost, minimal in-house resource needed
- Established integrations with enforcement, GIS, and EV charge point providers
- Dedicated Customer Success support, training, and peer user groups
Common D-TRO questions and myths
D-TRO questions, answered by the people who hear them daily (our AppyWay experts!)
What is the difference between Mapper Lite and Traffic Suite?
Won't switching to map-based orders create more work for our team?
Is TRO data only useful for legal compliance?
Is there a point to adopt D-TROs before the legal compliance deadline?
Do we need a GIS specialist on our team to run this?
Can we digitise new traffic orders and deal with the historical ones later?
What happens if our council waits until the D-TRO deadline is confirmed?
Built for todays’s challenges
Explore our traffic order suite
Not sure where to start? Let’s talk it through.
A short, no-strings call to talk through your council’s specific situation: team size, current system, and budget – and what a realistic path to compliance actually looks like.
You're in great company
Join some of the local authorities below that are using AppyWay to manage their kerb data.
Car park and estate order management and data sharing, contextualised with on-street regulations.
Promote public engagement in active travel, electrification and decarbonisation discussions.
Efficiently capture kerbside assets and restrictions, enabling map-based TRO management.