Get a demo →

Minnesota DOT e‑ticketing requirements

Required on some projectsMinnesota Department of Transportation (MnDOT)

Last verified September 26, 2026

MnDOT requires a contractor-provided Material Delivery Management System (MDMS), its term for e-ticketing plus hauler and delivery-event data, on contracts that include Special Provision 2061, Quality Management - E-Ticketing. The provision covers plant-mixed asphalt (2360), permeable asphalt stabilized base (2363), and stone matrix asphalt (2365). MnDOT still uses paper weight tickets as the basis of payment.

Required on some projects: E-tickets are required only on contracts that include the provision or meet a size threshold.

Key dates

2018
First MnDOT e-ticketing pilots on two HMA projects.
October 2022
More than 83 MDMS asphalt projects completed (FHWA-HRT-23-047).
2025
MnDOT's stated target for full implementation, as reported by FHWA in June 2023. Whether it was met is not confirmed in a MnDOT publication.

Materials and project scope

  • Plant-mixed asphalt (2360)
  • Permeable asphalt stabilized base (2363)
  • Stone matrix asphalt (2365)

Contracts that include Special Provision 2061 (Quality Management - E-Ticketing). FHWA reported in 2023 that the provision was not mandatory until full deployment and that MnDOT picked projects with good internet access. MnDOT and its MDMS platform partner told Tread in May 2026 that MDMS is required on virtually all asphalt paving jobs; that is an internal call note, not a published source.

Spec references

  • SP 2061: Quality Management - E-Ticketing (Material Delivery Management System), referenced by the MnDOT Inspector's Job Guide
  • AASHTO MDMS-1: AASHTO standard specification for Material Delivery Management Systems (MnDOT-led)

E-ticketing platform

  • Contractor's choice of MDMS (MnDOT does not require a specific vendor)
  • Veta (MnDOT/pooled-fund intelligent construction data platform)
  • AASHTOWare Project (MnDOT's system for daily work reports)

Data requirements

MDMS covers source, hauler, loading and delivery events, testing and contract administration, and agency verification data. The Inspector's Job Guide says inspectors check that no e-ticket fields are missing and download a daily CSV export into the AASHTOWare daily work report. MnDOT uses geofences at the source and job site for timestamps, and records split, partial, and rejected loads. Signatures are not required on paper tickets or e-tickets on MDMS contracts.

What contractors should do

  1. Give MnDOT staff and the Advanced Materials and Technology unit logins to your MDMS before the first delivery, and keep access open until 90 days after final acceptance.
  2. Train the Engineer on your MDMS at least 7 calendar days before MDMS work starts.
  3. Keep producing paper weight tickets; MnDOT still collects them at least daily for the basis of payment and the Schedule of Materials Control.
  4. Check whether your MDMS meets the extra items in S-xx.5A for the single $5,000 lump-sum monetary adjustment, and contact the AMT unit to verify it.
  5. Confirm your haulers' trucks can be tracked through the source and job-site geofences your MDMS uses.

What haulers should do

  1. Expect the contractor to require tracking on your truck, because MDMS records hauler data and geofence entry and exit times.
  2. Keep carrying the paper weight ticket; MnDOT still pays from paper tickets on MDMS jobs.
  3. Report split, partial, or rejected loads to the contractor so they are recorded in the MDMS.

Official pages

Other states

See all 50 states and DC