Is e-ticketing federally required? No — here's the real picture
It's common to hear that there's a "federal e-ticketing mandate." There isn't. The confusion comes from the Federal Highway Administration's Every Day Counts (EDC) program, which identifies proven, market-ready innovations and encourages state and local agencies to adopt them. E-ticketing was one of the innovations in EDC Round 6 (EDC-6), covering the 2021–2022 deployment cycle.
EDC is voluntary. FHWA provides technical assistance, peer exchanges, and tracks how far each state has progressed — but it does not require any state to adopt e-ticketing. Where e-ticketing is mandatory, it's because a state DOT wrote it into its own standard specifications or a project special provision — not because of any federal rule. That distinction matters: your obligations depend entirely on the state and the specific contract you're delivering to.
What "e-ticketing" actually means at the scale
In the DOT materials context, e-ticketing is the digital capture and real-time transfer of delivery-ticket data — gross/tare/net weights, material, truck ID, timestamps, and often GPS — in place of the paper ticket the driver used to hand to an inspector. The goal is fewer keying errors, less time spent at the roadside, a safer inspection process, and a clean digital audit trail for both the agency and the contractor.
It applies to the materials that move across a scale or batch plant on highway work: hot-mix asphalt, ready-mix concrete, and aggregate. Most states started with asphalt because it's the highest-volume, most time-sensitive material on a paving job — but the same delivery-ticket data model extends naturally to aggregate.
State-by-state status in 2026
This is the part that gets misreported. You'll see vendor press releases claiming "twelve states require e-ticketing." In reality, FHWA's own language is more careful — it describes about ten states as "applying" e-ticketing, and applying covers everything from a small pilot to a hard requirement. The table below uses honest status labels. It reflects public information as of June 2026 and leans conservative where a true blanket mandate couldn't be confirmed.
| State (DOT) | Status (2026) | Scope & notes |
|---|---|---|
| Virginia (VDOT) | Requires | Required for asphalt plant mixtures; other materials optional and expanding. The clearest current requirement. |
| Georgia (GDOT) | Requires from 2026 | Phasing in under its specs after a 2025 dual-ticket pilot that covered aggregate and concrete. Prospective — confirm the current spec. |
| Utah (UDOT) | Standard practice | Used on essentially all asphalt paving projects since its 2019 pilots; delivered through the state's digital tools. |
| Wisconsin (WisDOT) | Adopted, expanding | Standard-spec provision for electronic load tickets; on select contracts and growing. Covers asphalt, concrete, and aggregate. |
| Pennsylvania (PennDOT) | Piloting / rolling out | Pilot program handling aggregate, concrete, and asphalt; broad rollout in progress. |
| North Dakota (NDDOT) | Statewide pilot | Central agency portal piloted across concrete, aggregate, and HMA in anticipation of wider rollout. |
| Kentucky (KYTC) | Adopted (asphalt) | Early adopter; specifies data attributes such as truck ID, timestamps, net weight, mix temperature, and GPS. |
| Iowa, Minnesota, Missouri, Alabama, Florida | Applying / piloting | Within FHWA's group of states actively applying e-ticketing, mostly on asphalt. Generally allow-and-expand rather than confirmed blanket mandates. |
| California (Caltrans) | Moving to all-electronic | Piloting in 2025 with the goal of eliminating paper tickets for asphalt, ready-mix, and aggregate; broader rollout targeted as early as late 2026. |
So is it "asphalt only"? Not for long
If you run an aggregate operation, the honest takeaway is this: the requirements that exist today are mostly asphalt-first, but aggregate is squarely in the path. Georgia's pilot already covered aggregate and concrete. Wisconsin, Pennsylvania, and North Dakota include aggregate in their e-ticketing specs or pilots. The data model is the same regardless of material, so once a state stands up an e-ticketing program for asphalt, extending it to aggregate is a policy decision, not a technical one.
The practical risk isn't that aggregate gets singled out — it's that a producer supplying a DOT job suddenly finds the contract's special provisions call for electronic delivery tickets, and the scale house is still on paper or a desktop system that can't export clean digital records.
How to get ahead of it
You don't need to predict exactly when your state will move. You need a scale house that already produces clean, digital, exportable ticket data — so that meeting an e-ticketing requirement is a configuration step, not a software replacement project. A few things to look for:
- Digital tickets by default. Every weighing captured as a structured record — gross, tare, net, material, truck, timestamp — not a paper pad that someone re-keys later.
- Clean data export. The ability to push ticket data out in standard formats so it can feed an inspector portal, an approved e-ticketing provider, or your accounting system without manual retyping.
- A defensible audit trail. The certified weight recorded straight from the indicator and never altered, with a record of who did what and when.
- Anywhere access. Office, pit, and roadside all seeing the same live ticket data — the whole point of going digital.
This is exactly how CloudAgg is built: cloud-native scale ticketing where every ticket is a digital record with the certified weight captured unaltered, an audit trail on every transaction, and clean data export. CloudAgg isn't itself a state DOT e-ticketing portal — for DOT-contract work you should always check whether the project requires a specific approved provider — but it gives you the structured digital ticket data that any e-ticketing requirement is built on. If you're weighing aggregate for jobs that may go electronic, see how it works for quarry & aggregate operations.