Road User Charging in Australia

Stakeholder feedback across the ITS Australia survey paints a clear picture: there is strong, informed support for road user charging as a necessary evolution of Australia’s road funding model, but that support is conditional on how the scheme is designed and introduced. 

Expert industry respondents canvassed from ITS Australia membership see RUC less as an abstract technology project and more as a practical response to the erosion of fuel‑excise revenue and the need for a clearer, fairer user‑pays system as EVs and more efficient vehicles become mainstream.

Across the responses, revenue sustainability and fairness between vehicle types and regions emerge as the dominant policy objectives, consistently ranked above emissions reduction and congestion management. Stakeholders broadly agree that all vehicles should ultimately contribute, yet they warn that reforms must avoid the perception that RUC is simply an “EV tax” or an additional impost layered on top of existing charges. Instead, they argue that RUC should be framed as modernising and progressively replacing legacy funding instruments, including fuel excise, rather than stacking new charges on top of old ones. 

On implementation, the survey reveals a strong preference for a “simple first, smart later” pathway. The clear majority view is that initial schemes should focus on straightforward, odometer‑based distance charging that is easy to explain, low‑cost to administer and relatively light‑touch from a privacy perspective. More complex telematics‑based models – with time‑of‑day, location and congestion components – are seen as valuable future options, but not an appropriate starting point given concerns about cost, social licence and political risk. Respondents repeatedly stress that trying to solve revenue, congestion and emissions all at once, with a highly data‑intensive system on day one, is more likely to delay or derail reform than to secure durable change.

Privacy, cyber security and data governance feature prominently as non‑negotiable design conditions. Many respondents favour a base model that collects only what is strictly necessary to calculate charges – typically distance totals over a period – with any detailed location data either not collected or stripped out early in the process. There is strong advocacy for explicit legal limits on secondary use, with RUC data clearly ring‑fenced from law enforcement, general surveillance and unrelated regulatory purposes, backed by robust assurance and independent oversight. Stakeholders also highlight the importance of user transparency and choice, including the ability to see and verify their own records and to opt into more data‑rich options only where there are clear benefits in return.

Equity and political acceptance are recurring themes throughout the qualitative responses. While there is support for a consistent user‑pays principle – including EVs “paying their way” – respondents are acutely aware of potential impacts on low‑income households, regional and remote drivers, and people who rely on longer-distance travel. The prevailing view is that the core tariff structure should remain simple and transparent, and that social equity objectives are better handled through targeted concessions, credits or caps delivered via existing welfare and tax systems, rather than through an overly intricate RUC price schedule. Several respondents also emphasise that the greatest barriers to successful RUC are likely to be political and perceptual rather than technical, underscoring the need for a clear narrative about fairness, replacement of fuel excise, and visible reinvestment in the road network.

Taken together, the findings suggest that the ITS and transport technology community is ready to support RUC as a major structural reform, provided it is anchored in clear objectives, implemented in an incremental and pragmatic way, and underpinned by strong safeguards around privacy and equity. The sector looks to ITS Australia to play a convening and standards‑shaping role – supporting pilots, national architectures and harmonised data standards, and helping articulate a coherent transition from fuel excise to distance‑based charging – rather than simply endorsing any specific technical solution. 

For decision‑makers, the message is that there is a window of opportunity: a well‑designed, clearly explained RUC can command both stakeholder and public support, but an over‑complex or perceived “double tax” scheme risks losing legitimacy before it begins.

The RUC survey captured responses from stakeholders across the transport ecosystem. The instrument is expert/stakeholder‑facing, not a general public poll, so sentiment reflects informed practitioners and industry perspectives, not lay opinion.

Primary policy objectives of RUC

Ranked objectives (via average scores) focus on:

• Revenue sustainability – maintaining a stable, fuel‑neutral funding base is a primary objective.
• Fairness – particularly between vehicle types and regions, including a view that EVs should “pay their way” while avoiding inequity for rural/low‑income users.
• Emissions reduction and congestion management – widely seen as valid but secondary levers that RUC could support, especially if location/time weighting is used.
• Reducing dependence on rego/fuel tax – recognised as necessary given EV uptake and efficiency gains.

Sentiment summary:

• Strong conceptual support for RUC as a revenue and fairness reform, with conditional interest in using it to manage emissions and congestion where politically feasible.
• Several responses stress the need for a clear, singular policy intent (revenue vs emissions vs congestion) to avoid confusion and policy failure.

Preferred technology and operating models

• Odometer‑based approaches (self‑reporting, verified, API‑linked to registration) are widely seen as the most viable starting point due to simplicity, cost, and lower privacy risk.
• Telematics and smartphone apps are recognised as strategic for future congestion/time‑of‑day/location pricing, but many caution “do not start with telematics” because of cost, public acceptance, and privacy concerns.
• Several advocate hybrid models:
  • Default odometer reporting, with opt‑in telematics for more sophisticated pricing or incentives (e.g. congestion management).
  • Pre‑paid km bundles, annual true‑up, or manufacturer / service‑centre reporting to keep administration light.

Sentiment summary:

• Pragmatic and incremental: start with simple, odometer‑centric RUC, then evolve to telematics‑enabled models as acceptance and vehicle connectivity grow.
• Strong preference to separate “distance only” and “location‑based” tiers, with users opting into higher‑data options in exchange for richer benefits or pricing flexibility.

Recommendation (technology design):

• Stage 1: Implement a national odometer‑based RUC (manual, API, or third‑party inspection) for all relevant vehicles, aligned with rego renewal.
• Stage 2: Introduce opt‑in telematics / smartphone options to enable time‑of‑day, route and congestion‑sensitive charging, especially for fleets and heavy vehicles.
• Design principle: Keep day‑one technology “minimum viable”; do not delay RUC implementation waiting for perfect telematics coverage.

Key technical and interoperability challenges

Common themes across narrative responses:

• Privacy, security, and data protection repeatedly identified as top concerns.
• National consistency and interoperability: need a nationally agreed approach, EU‑style standards, and coordination across Commonwealth, states, toll roads, and private providers.
• Heterogeneous fleet:
  • Older vehicles without connectivity.
  • Managing both connected and non‑connected vehicles without unfairly penalising one group.
• Equity and political acceptance: some respondents argue the main challenge is political and perceived fairness, not the technology itself.
• Integration challenges: with registration, tolling, enforcement, OEM data, and third‑party telematics, plus risk of vendor lock‑in.

Sentiment summary:

• Respondents broadly believe technology is available and workable, but governance, standardisation and politics are the real risks.
• There is low tolerance for fragmented, jurisdiction‑specific solutions that complicate user experience and undermine trust.

Recommendation (architecture and standards):

• Establish a national RUC system architecture and data standards (APIs, formats, assurance frameworks) covering distance collection, settlement, and enforcement.
• Use assured providers (for telematics and data services) with clear certification and audit regimes to minimise fraud and ensure reliability.
• Build interoperability with existing tolling back offices and fleet telematics, but avoid letting any single commercial actor dominate the ecosystem.

Phasing and community needs

Key equity and phasing themes:

• Strong expectation that RUC should ultimately apply to all vehicle types, including EVs and ICE, with EVs not permanently exempt.
• Many respondents favour simple distance‑based pricing, with flexibility to layer in weight, emissions, and location factors over time.
• Divergent views on concessions:
  • Some favour universal, simple RUC with separate welfare/tax instruments handling equity (e.g. via Services Australia or tax system).
  • Others support targeted concessions or caps for regional/remote users, low‑income households, people with disability, small operators, often via credits, distance caps or rebates, not complex pricing schedules.
• Several emphasise “keep it simple initially” – start with plain distance‑based RUC replacing fuel excise, then refine for equity and externalities.

Sentiment summary:

• Equity matters, but complexity is a major risk for acceptance and operation.
• There is limited support for building extensive social policy into the core tariff structure; instead, use simple pricing + separate concessions/credits.

Recommendation (equity and phasing):

• Phase‑in:
  • Begin with EVs and possibly heavy vehicles (where the fairness and “pay their way” arguments are strongest), but avoid creating a narrative that RUC is “only for EVs”.
  • Move towards all vehicles on a consistent RUC as quickly as politically feasible.
• Equity mechanisms:
  • Use distance credits, caps, or rebates for regional/remote and low‑income users, administered via existing concession systems rather than complex RUC tables.
  • Consider weight‑ and emissions‑sensitive rates for heavy vehicles and larger private vehicles to reflect road wear and policy objectives.

Privacy, Cyber‑Security and Data Governance: Required protections

Top issues:

• Data minimisation: many respondents want distance totals only, with no or limited location data for the base scheme.
• No secondary use: strong calls for clear legislative limits – RUC data must not be used for law enforcement, surveillance, speed enforcement, or unrelated government purposes.
• Anonymisation and encryption:
  • Suggestions include rotating cryptographic identifiers and onshore storage.
  • Preference for independent governance and strong audit over both public and private operators.
• Choice and transparency:
  • Users should be able to view their data and charges, choose between distance‑only vs location‑based options, and have clear consent mechanisms.

Sentiment summary:

• High privacy sensitivity but also recognition that tolling and telematics models already exist; RUC can emulate best practice.
• Acceptance is more likely if base RUC is privacy‑light and location‑based features are optional and well‑explained.

Recommendation (privacy design):

• Codify privacy‑by‑design in legislation:
  • Base scheme collects only what is strictly necessary (e.g. km totals per period and coarse road class/zone), with location‑level detail stripped or aggregated early.
  • Explicit legislative prohibition on non‑RUC uses of the data.
• Provide simple, user‑facing data portals so drivers can see, verify and dispute their RUC records.

Integration with ITS and Payment Systems: Opportunities and barriers

Opportunities:

• Integration with tolling back‑offices, fleet management systems, and existing digital payments to reuse infrastructure and simplify billing.
• Use of ITS data to support congestion pricing, demand management, and better network analytics.

Barriers:

• Policy and legislative fragmentation, lack of national system architecture, and jurisdictional rivalries.
• Public mistrust, privacy concerns, and fear of “big brother” tracking.
• Legacy commercial arrangements and potential “rent‑seeking” by toll operators or private providers if not well regulated.

Recommendation (integration strategy):

• Treat tolling, ITS, and RUC as part of a coherent national mobility charging ecosystem, but avoid over‑integrating on day one; keep RUC functionally independent while reusing back‑office capabilities where it reduces cost and complexity.
• Develop a national integration roadmap led by government and informed by ITS industry and research institutions.

What should happen to fuel excise?

There is strong, consistent sentiment that:

• Fuel excise should be reduced, rebated, or ultimately removed as RUC is rolled out to avoid double charging.
• Many advocate a phased approach:
  • Maintain excise initially, then gradually lower it as more vehicles come under RUC, ensuring revenue stability.
• Several respondents explicitly warn that double taxation will destroy public acceptance and that RUC must be framed as a replacement, not an addition.

Recommendation (transition from excise):

• Publish a clear transition pathway where fuel excise is progressively reduced as RUC coverage expands, with no net increase in total road‑related taxation in the early phase.
• Use modelling and communication (potentially with ITS Australia support) to show typical users “before and after” cost comparisons