Which Employees Need Which Test? Mapping OSHA and DOT Requirements

What's the compliance problem that comes before scheduling a test?

Most hearing conservation and occupational health tracking problems get framed as scheduling problems: who's due, and when. But before a due date can be tracked, someone has to correctly answer a harder question: does this specific employee, in this specific role, fall under this specific regulation at all? A warehouse employee who occasionally drives a CDL route may be subject to both OSHA's noise standard and DOT's alcohol testing rules, while a similar-looking employee at the same site who never drives may only be subject to one. Get that mapping wrong and a due-date calendar will faithfully track the wrong requirement, or miss one entirely, no matter how well the scheduling itself works.

Why do OSHA and DOT requirements overlap without lining up?

OSHA and DOT/FMCSA regulate different things for different reasons, and their jurisdictions intersect rather than nest inside each other. OSHA's general industry standards, including 29 CFR 1910.95 hearing conservation and 1910.134 respiratory protection, apply based on workplace exposure, noise level or respirator use, regardless of whether the employee ever operates a commercial vehicle. DOT's testing rules under 49 CFR Part 40, run through FMCSA for commercial drivers, apply based on safety-sensitive function, principally operating a CMV, regardless of the noise or respiratory hazards present at a fixed worksite¹. A single employee can trigger both sets of obligations at once, or only one, depending on role, and the two regulatory schemes don't share a common employee list to check against.

What happens when the requirement mapping is wrong instead of the schedule?

A scheduling error is usually visible: a due date passes and nobody got tested. A mapping error is invisible until an inspection or an incident forces the question, because the tracking system never knew to ask about that employee at all. An employee moved from a warehouse role into occasional CMV driving without the safety office being told doesn't show up as a missed test, it shows up as a person who was never entered into the DOT random testing pool in the first place. That's a materially different failure than a late audiogram, and it's the kind of gap that a due-date calendar alone can't catch, because the calendar only tracks people already correctly classified.

Failure type	How it surfaces	What catches it
Late test (correct classification)	Due date passes with no completed test on file	A due-date tracking calendar
Missed classification (wrong or absent mapping)	Employee never appears in any tracking list for a requirement they're actually subject to	A role-to-requirement matrix reviewed on role change, not just a calendar

How does OSHA recordkeeping factor into a multi-regulation tracking gap?

OSHA's recordkeeping rules require employers to maintain accurate records tied to the specific standard that applies, and an inspector reviewing a hearing conservation program checks the same employer records that a DOT audit would review for a different set of employees under a different rule². When those two record sets are maintained in separate, disconnected systems, neither one built to flag a person who should appear in both, a role change or a new hire can fall into the space between them without either system generating an alert. The employer isn't out of compliance because a system failed; they're out of compliance because no system was ever asked to check that particular overlap.

How Foster's Compliance Workspace closes the mapping gap, not just the scheduling gap

Foster built its Compliance Workspace around an employee-by-requirement matrix rather than a due-date calendar bolted onto a spreadsheet, so the first question it answers for a given employee is which OSHA and DOT rules actually apply to that role, with the CFR citation attached, before it ever generates a due date. When a role changes, the matrix is what gets checked, not just the next scheduled test, which is what catches the case a calendar-only system misses: someone who should now be subject to a requirement they weren't tracked under before. Evidence records, audit exports, and CSV/PDF reports all trace back to that same matrix, so an audit response shows not just what was tested and when, but why each employee was in scope for each requirement in the first place.

Foster's on-site hearing testing and DOT BAT training programs feed the same employee record inside the Compliance Workspace, so a role change surfaces every requirement it triggers, not just the ones already being tracked. Programs auditing their current requirement mapping can start with a quote. For the scheduling layer built on top of this matrix, see Foster's post on keeping 12 plants on one testing schedule.

Frequently Asked Questions

Can one employee be subject to both OSHA and DOT testing requirements at the same time?

Yes. OSHA's general industry standards apply based on workplace exposure, such as noise level, while DOT's rules under 49 CFR Part 40 apply based on safety-sensitive function, such as operating a commercial motor vehicle. An employee can trigger both independently.

What's the difference between a missed test and a missed classification?

A missed test is a due date that passed without a completed test on file for someone already correctly tracked. A missed classification means the employee was never entered into the tracking system for a requirement they're actually subject to, so no due date was ever generated to miss.

What typically triggers a classification gap?

A role or duty change, such as a warehouse employee picking up occasional commercial driving duties, that isn't communicated to whoever maintains the compliance tracking system. The gap isn't a scheduling failure; it's that the employee's requirement mapping was never updated.

Does OSHA recordkeeping cover DOT testing records too?

No. OSHA recordkeeping requirements apply to OSHA standards; DOT testing records fall under separate 49 CFR Part 40 rules. An employer subject to both needs records that satisfy each, which is easier when both are tracked against the same employee-by-requirement matrix rather than two disconnected systems.

Sources

• OSHA: Laws and Regulations
• OSHA: Recordkeeping Requirements