Multi-Site Occupational Health Testing: Keeping 12 Plants on One Schedule

A safety director running one plant can carry the testing calendar in their head. A safety director running twelve plants across three states can't, and the gap between those two situations is where most multi-site occupational health programs actually fail. It isn't that the corporate policy is wrong. It's that the policy gets applied twelve different ways by twelve different plant managers, on twelve different clocks, and nobody at headquarters finds out which sites drifted until an OSHA inspector or a workers' comp claim asks for records that don't exist.

Why does testing drift more at multi-site employers?

A single-site hearing conservation or BAT program has one person who owns the calendar and one set of employee records to check. Add sites and that ownership splits: each plant manager schedules their own annual audiograms, tracks their own DOT random pool, and renews their own instrument calibrations on their own timeline. One site's supervisor is diligent and never misses an annual test date. Another lets a hearing conservation program slip three months past the anniversary because the person who used to schedule it changed roles. A third has high turnover among CDL drivers and can't tell which new hires still need a baseline audiogram or a DOT physical. None of this shows up as a single failure. It shows up as a pattern only visible if someone is comparing all twelve sites against the same standard at the same time, and most companies don't have that view until an inspection forces it.

What does OSHA actually require site by site?

OSHA's recordkeeping rule treats each physical location as its own establishment for most purposes. Under 29 CFR 1904.30, an employer with more than one establishment must keep a separate OSHA 300 log for each location expected to be in operation for a year or more, and each employee's injury and illness records get tied to the establishment where they work, not to the company as a whole. That establishment-by-establishment structure extends in practice to hearing conservation under 1910.95 and other exposure-based standards: an auditor evaluating one plant wants that plant's audiogram dates, that plant's noise monitoring, and that plant's training records, not a company-wide summary that can't be broken back out by location. A safety program that only tracks compliance at the corporate level can't answer the question an inspector actually asks, which is whether this specific site, on this specific date, had current records for this specific employee.

How is DOT testing different across terminals?

For carriers with a CDL workforce spread across multiple terminals, the driver qualification file requirements in 49 CFR Part 391, Subpart F apply to every driver regardless of which terminal they're based out of, and the file has to be complete and producible on request no matter where the driver physically works. A driver qualification file missing a current medical certificate or annual review doesn't become less of a violation because it's terminal three's problem and not headquarters'. The random alcohol and controlled substances testing pool under Part 40 is usually managed company-wide by design, specifically so a driver can't hide in a small terminal-level pool, but the underlying qualification records, training records, and BAT technician coverage still have to be tracked at the location where the driver actually reports. A multi-terminal carrier that manages DQFs as twelve separate filing systems will eventually find one terminal's files are current and another's are three drivers behind.

Where do multi-site programs specifically break down?

Failure point	What happens	Why it surfaces late
No shared due-date calendar	Each plant tracks its own annual audiogram and BAT recert dates independently	Corporate has no visibility until a site is already overdue
Inconsistent instrument calibration cadence	One plant's audiometer or BAT device calibration lapses while others stay current	Only discovered when that site's test results are challenged
New-hire onboarding varies by site	Baseline audiograms or DOT physicals get scheduled on different timelines depending on the local HR process	Gaps aren't visible until a specific employee's file is pulled
Turnover in the person who "owns" scheduling	Institutional knowledge about who's due for what leaves with the person	The gap doesn't appear until the next testing cycle is already late
No cross-site reporting format	Each plant keeps records in whatever format the local manager prefers	Corporate can't compare sites or produce a consolidated audit response quickly

What does a workable multi-site tracking model look like?

The employers who keep multi-site programs current generally do the same three things. First, they define requirements once at the corporate level, tied to the actual regulation and the actual retention period, rather than letting each site interpret the policy locally. Second, they track due dates per employee and per requirement, not per site or per program, so a specific person's specific overdue item is visible without someone manually cross-referencing spreadsheets. Third, they review the whole roster on a fixed cadence, not just when a site manager remembers to ask, so a slipping site is caught within weeks instead of at the next OSHA inspection or claim. None of this requires exotic tooling. It requires the requirement, the employee, and the due date to live in one system that every site feeds and corporate can see, instead of twelve independent local systems that nobody compares.

How does Foster handle multi-site tracking?

When we're on-site doing audiometric testing, spirometry, or BAT training across a multi-plant customer's locations, the recurring problem isn't the testing itself, it's that headquarters can't easily tell which plant is current and which one is quietly behind. That gap is what our Compliance Workspace is built around: an employee-by-requirement matrix that ties each person to the specific OSHA or DOT rule that applies to them, with the CFR citation attached, so a corporate safety director can see every site's due dates in one place instead of chasing twelve plant managers for a status update before an audit. It doesn't replace the testing we do on-site; it's how the due dates and evidence from that testing stay visible across every location between visits.

FAQ

Does OSHA allow one company-wide hearing conservation program across multiple plants?

Yes, a single written program can cover multiple locations, but the records and compliance status still get evaluated establishment by establishment under 1904.30. A company-wide policy document doesn't substitute for site-specific audiogram, monitoring, and training records that an inspector can pull for that location.

Can one safety manager realistically track testing due dates for a dozen sites manually?

It's possible with rigorous discipline, but the common failure mode is that manual tracking works until the person doing it changes roles or a site's local process quietly diverges from the rest. A shared, per-employee due-date view removes the dependency on one person's memory.

Do DOT driver qualification files need to be kept at the terminal or at headquarters?

Part 391 doesn't dictate physical location as long as the file is complete and producible on request, including electronically. The practical risk isn't where the file sits, it's whether it's actually current, which is a tracking problem more than a storage problem.

How often should a multi-site testing calendar be reviewed at the corporate level?

Monthly is a reasonable minimum for most programs; carriers with active DOT random testing pools or high-turnover sites often need a tighter cadence so a lapsed baseline or recert doesn't sit unnoticed for a full quarter.

What's the fastest way to find out which of our sites is behind right now?

Pull a per-employee, per-requirement due-date list rather than a per-site summary. Site-level summaries hide individual gaps; a flat list of every overdue requirement across every location surfaces the problem in one pass.

Foster runs on-site hearing testing, spirometry and fit testing, and BAT training across multi-plant customers, and calibrates the audiometers and breath alcohol devices those programs depend on. See our related post on why the training spreadsheet fails the audit, or get a quote for a multi-site testing schedule.

Sources

• 29 CFR 1904.30, Multiple business establishments (OSHA)
• 49 CFR Part 391, Subpart F, Qualification of Drivers (eCFR)