MASH Compliance for Work Zone Devices: What It Means for Your Inventory

There is a specific conversation that happens on federal-aid projects, usually at the worst possible moment, and it goes like this. An inspector points at a row of sign supports and asks whether they are MASH compliant. The superintendent says yes. The inspector asks for documentation. And it turns out that nobody knows when those supports were bought, from whom, or under what crash-test criteria they were evaluated — because for the entire history of the company, a sign support was a sign support.

MASH turned an undifferentiated commodity into an asset with a compliance attribute attached to its manufacture date. Most traffic control companies have not restructured their purchasing or inventory records to reflect that, and the gap surfaces as a field dispute rather than as a planning problem.

This is a practical explanation of what MASH is, what the implementation agreement actually requires, and how to audit an inventory that was accumulated before anyone was tracking any of it.

Standing caveat: crashworthiness acceptance is administered through federal eligibility determinations and state approved-products practice, and states differ. Nothing here substitutes for the requirements of the agency having jurisdiction over your project.

What MASH is, and what it replaced

MASH — the Manual for Assessing Safety Hardware — is AASHTO's crash-test evaluation standard for roadside safety hardware. It defines the test vehicles, impact speeds and angles, and evaluation criteria used to determine whether a device performs acceptably when struck.

It replaced NCHRP Report 350, which had governed since the 1990s. The substantive reason for the change was that the vehicle fleet moved. NCHRP 350's test vehicles no longer represented what was actually on the road — heavier pickups, higher centers of gravity, different crash dynamics. Hardware that performed acceptably against a 1990s test fleet did not necessarily perform acceptably against a modern one.

The practical consequence for a contractor is narrower than the engineering debate: a device now has a crash-test lineage, and that lineage is tied to when it was manufactured.

The stakes behind the standard are the ones the whole industry lives with. NHTSA's Fatality Analysis Reporting System recorded 850 work zone fatalities in 2024 across 763 fatal crashes, a figure that has not meaningfully improved in five years. Crashworthy hardware is one of the few interventions that operates at the moment of impact rather than before it, which is why the acceptance regime around it is comparatively strict.

The regulatory hook that connects all of this to your job site is unglamorous but worth quoting. OSHA's construction standard at 29 CFR 1926.200(g)(1) states that "At points of hazard, construction areas shall be posted with legible traffic control signs and protected by traffic control devices", with paragraph (g)(2) requiring that the design and use of those devices conform to MUTCD Part 6. The manual's device provisions are where crashworthiness expectations enter the picture on the operational side.

The implementation agreement, in plain terms

FHWA and AASHTO published a joint implementation agreement establishing when MASH-tested hardware became mandatory, category by category, with "sunset dates" after which NCHRP 350 hardware could no longer be newly installed on National Highway System projects.

The schedule that matters most to traffic control companies:

• December 31, 2019 — temporary work zone devices manufactured after this date must have been successfully tested to the 2016 edition of MASH. Devices manufactured on or before this date, and successfully tested to NCHRP 350 or the 2009 edition of MASH, may continue in use through their normal service lives.
• December 31, 2017 — w-beam barriers and cast-in-place concrete barriers, for new permanent installations and full reconstruction on the NHS.
• December 31, 2019 — cable barriers, cable barrier terminals, bridge rails, transitions, and other longitudinal barriers.

Three features of that structure deserve emphasis because they are routinely misread:

It is a manufacture-date rule, not a purchase-date or install-date rule. A device bought in 2023 from old stock, manufactured in 2018, sits on the pre-sunset side of the line. Conversely, a device you have owned since 2015 does not become non-compliant because it is old — it is grandfathered through its service life. What you need is evidence of when it was made.

Grandfathering ends at end of service life, not at a date. "Normal service lives" is doing real work in that sentence. A barricade whose reflective sheeting has failed and whose frame is bent is not serviceable, and replacing it means replacing it with MASH hardware. This is the mechanism by which a fleet converts over time without a forced replacement event — and it is why device condition standards and MASH status are the same conversation, not two.

It governs federal-aid work on the NHS; state practice varies above that floor. Many states apply equivalent requirements to their full program, and many specifications simply require devices from a state approved list without asking about route classification. Texas, for instance, publishes a Compliant Work Zone Traffic Control Device List identifying the specific devices approved for use on its projects, which is the operative document on a TxDOT job regardless of how one reads the federal agreement. State DOTs also publish their own MASH implementation guidance, and they coordinate on it — the multi-state Roadside Safety Pooled Fund MASH coordination effort is a useful window into how implementation questions are being worked through across agencies. Find your own state's guidance and read it once, properly.

The real problem: nobody recorded manufacture dates

The standard is not conceptually difficult. The difficulty is entirely evidentiary, and it comes from how traffic control inventory is normally acquired: in batches, over years, from multiple suppliers, tracked by count rather than by unit, with paperwork filed by invoice rather than by asset.

That produces a fleet where the compliance status of any individual device is unknowable. And the burden runs the wrong way — on a federal-aid project, an inspector is entitled to ask you to demonstrate eligibility, and "we have always used these" is not a demonstration.

The recovery path has three parts.

Purchase records. Invoices establish approximate acquisition dates and identify suppliers who can often confirm manufacture windows for a product line. This is tedious and it is the only route for legacy stock. It works better than most companies expect, because suppliers keep better records than their customers do.

Manufacturer markings. Many devices carry a manufacturer mark, model, and in some cases a date or lot code. Physically inspecting a sample of each category tells you what evidence exists before you plan an audit around it.

Eligibility letters. For each product line you deploy on federal-aid work, obtain the FHWA eligibility letter or the state acceptance record from the manufacturer and file it. Manufacturers provide these on request; most companies have simply never asked.

The forward-looking fix is smaller than the cleanup: make eligibility documentation a receiving requirement. When devices arrive, the manufacture date and the eligibility letter get recorded against the asset before the devices go into the yard. That is a purchasing-process change, and it belongs with the other receiving disciplines described in purchase orders and vendor management.

Running the audit

A defensible audit does not require unit-level records for every cone in the yard. It requires you to be able to answer, for each device category you deploy on federal-aid projects, three questions: what product is it, what is its eligibility basis, and what is the manufacture-date evidence.

A workable sequence:

1. Inventory by category and product line, not by count. "Type III barricades" is not a category for this purpose; "Manufacturer X Model Y Type III barricades" is.
2. Segregate by acquisition era. Anything purchased after the relevant sunset date should be MASH by default — verify with the supplier and file the letter. Pre-sunset stock is the population that needs evidence.
3. Collect eligibility letters for every current product line. One email per supplier. Do this first; it is the cheapest step and it resolves the forward-looking half of the problem immediately.
4. Sample-inspect legacy stock for markings. You are establishing what evidence physically exists, which determines whether an audit is feasible or whether attrition is the plan.
5. Decide the attrition policy explicitly. For legacy devices with no recoverable documentation, the honest options are to retire them from federal-aid work, assign them to non-NHS or private work if your agencies allow it, or replace them. Making that decision deliberately is much cheaper than discovering it device by device at inspections.
6. Write the receiving rule so the problem stops growing.

Attrition timing is a budgeting question as much as a compliance one, and it connects directly to equipment fleet replacement planning — a fleet that is being replaced on a known cycle converts to MASH naturally, while one replaced only on failure converts unpredictably and always at the worst moment.

The questions that come up on every job, answered plainly

"Our devices are old but they were legal when we bought them. Are we fine?" Generally yes, for as long as they remain serviceable, on the terms of the grandfathering provision. What you need is not new devices — it is evidence of manufacture date. The exposure is documentary, not physical.

"The agency's inspector says these are not on the list." Approved-products lists are the operative document on most state projects, and a device can be MASH compliant and still not appear on a particular state's list. Those are two different tests and both have to pass. Check the list before mobilizing, not at setup.

"We rented devices from another company for an overflow job. Whose problem is compliance?" Yours, on your project. Rented and borrowed devices need the same documentation as owned ones, and the time to ask for it is at the rental agreement, not at the inspection. Build the request into your subrental process.

"Does this apply to a city street job?" The joint implementation agreement addresses federal-aid work on the National Highway System. Many agencies apply equivalent requirements more broadly, and many specifications simply require devices from the state list regardless of classification. The only safe answer is the one from the agency having jurisdiction — the same pattern described in how state DOT requirements vary.

"A device was damaged and we replaced it mid-job with an older spare." This is the most common way a compliant setup drifts out of compliance, and it happens because the spare came off a truck rather than out of a controlled inventory. If you hold a mixed fleet, the replacement stock on the truck needs to be the compliant stock.

Why this is an inventory-systems problem, not a procurement one

It is tempting to treat MASH as a purchasing matter — buy compliant devices, done. That misses where the failures actually occur.

Compliance is asserted at the moment of deployment, on a specific job, about specific physical objects. To make a true assertion you have to know which devices went to which job, and that is an inventory-tracking capability, not a purchasing one. A company that buys exclusively MASH hardware but tracks devices as undifferentiated counts still cannot answer the inspector's question, because it cannot connect the compliant purchase to the object standing in the lane.

That is the structural reason this lands hardest on companies running spreadsheets: a spreadsheet cell holding "42 Type III barricades" has no room for a manufacture date, an eligibility letter, or a current location, and the moment you add columns for those you have started building an asset register by hand. The devices that most need this treatment are also the ones most likely to move between jobs mid-phase — which is where a count-based record diverges from reality fastest, as described in tracking traffic control devices by job site.

The practical threshold is roughly this: if you hold both pre-sunset and post-sunset stock in the same categories, and you work federal-aid projects, you need device-level records. If your fleet is uniformly post-sunset, category-level documentation plus eligibility letters is generally enough. Knowing which situation you are in is itself worth the audit.

The commercial consequences worth planning for

Damage recovery gets more expensive. When a device destroyed on a job must be replaced with MASH hardware, the replacement cost may exceed what your damage-recovery language contemplates. Review the numbers in your damaged and lost device charges against current replacement pricing rather than historical.

Rental rates should reflect the asset, not the category. If MASH devices cost more to acquire, rate cards built on legacy costs quietly erode margin as the fleet converts. This is one of the inputs in traffic control device rental rates.

Prequalification and bid submittals increasingly ask. Owner agencies and primes have begun asking for device compliance representations at submittal. Being able to answer without a scramble is a small competitive edge that costs nothing once the records exist.

Mixed fleets need deployment rules. If you hold both pre- and post-sunset stock, someone has to make sure the right devices go on the right jobs. That is an inventory-routing problem — the same one described in tracking devices by job site — and it is unmanageable if devices are tracked only as counts. It becomes manageable when a device is an asset record with attributes, which is how Traffic OS models equipment: a device has a home yard, a current job, a rate, and any attribute you need to route it correctly — including its compliance basis.

What to tell your crews

Field crews do not need the regulatory history. They need three operational rules, stated in a way that survives a tailgate briefing.

Do not substitute devices across the compliant and legacy pools. If your company runs a mixed fleet, the segregation only holds if crews respect it when something breaks at 3 a.m. Colour-coding or physically separating the pools in the yard does more for this than any policy statement.

Report damage rather than field-repairing it. A welded, drilled, or improvised repair can void the basis on which a device was accepted, because the tested article is the manufactured one. A device that has been modified is a device you cannot vouch for.

Photograph what went out. If the deployment record includes photos, the question of which devices were on a job on a given date becomes answerable rather than arguable — the same reason field capture matters everywhere else in this business.

What to take away

MASH did not make traffic control harder to perform. It made traffic control inventory into something that has to be known rather than merely counted. The companies that find this painful are the ones whose equipment records were a number in a spreadsheet; the ones that find it routine are the ones already tracking devices as assets.

The three actions worth taking this month, in order of cost-effectiveness: request eligibility letters from every current supplier, add manufacture date and documentation to your receiving process, and decide explicitly what happens to legacy stock you cannot document. None of the three requires new equipment. All three prevent the conversation that starts with an inspector pointing at a row of sign supports.

If you want device-level records that survive an audit — with acquisition dates, documentation, and current location on one asset — that is what our equipment model is built around, and a demo can be run against your own yard rather than a sample dataset.