Drug Testing for Multi-Location Companies
The problem with testing across many sites is not the testing. It is that each location gradually invents its own version of the policy, and nobody notices until two employees are treated differently for the same thing.
How Multi-Site Programs Drift
Nobody decides to run five different programs. It happens because each site solved its own problem locally. One plant uses the occupational clinic across the street. Another sends people to urgent care. A third has an arrangement with a mobile collector who comes out monthly. Each was sensible in isolation.
Two years later the differences are structural: different turnaround times, different panels, different paperwork, results going to different people, and no single place where anyone can see what happened across the company. When a decision is challenged at one site, the company cannot demonstrate that it applies the same standard at the others.
Running testing across several sites?Five questions, about a minute. A specialist follows up within one business day.
Request a SpecialistWhat Consolidation Actually Fixes
- One standard. Same triggers, same panels, same documentation at every location, with state exceptions written down rather than improvised.
- Central selections. Random draws made once, from the whole covered pool, rather than site by site at whatever interval each manager remembers.
- Local collection, coordinated centrally. Employees still test near where they work, but the arrangement is managed in one place.
- Consistent reporting. Results reach the same designated people through the same channel, wherever the test happened.
- One record set. Any test at any site retrievable without calling three locations.
- One point of contact who knows your program, rather than a vendor relationship per city.
The Site That Quietly Gets Skipped
Most multi-site employers have one: the location far from anything, where testing is a half-day round trip. It is the site with the lowest completion rate, and if your random program is ever examined, it is the first thing an attorney will find.
Remote collection for non-regulated testing solves much of this, because the employee does not travel. Where it does not apply, the answer is to plan that site's arrangement explicitly rather than leaving it to be handled ad hoc each time.
Rolling Out Without Disrupting Operations
- Inventory what each site does now. Usually the first time anyone has seen it side by side, and usually surprising.
- Settle the single standard, including which state exceptions are real and which were assumptions.
- Decide who receives results, centrally or by region.
- Sort the hard locations first, not last. The remote site is the one that determines whether the program works.
- Brief site managers before employees hear about it, since they will be asked first.
- Cut over on one date rather than site by site, which leaves two programs running at once.
Worth checking before you consolidate: whether any location is covered by a collective bargaining agreement with its own testing terms. Those do not disappear because the program was centralized, and finding out afterward is expensive.
Common questions
Should every location follow exactly the same rules?
As close to it as the law allows. One written standard, applied the same way everywhere, with documented exceptions only where a state requires something different. The danger in letting each site run its own version is not administrative untidiness, it is that two employees in the same role get treated differently and one of them notices.
Can selections still be random if sites have different headcounts?
Yes. The pool covers everyone in the covered population across all sites, and selection is made from that whole pool. Larger sites will come up more often simply because more of their people are in the pool, which is what random means. What breaks a program is running separate selections per site with different rates, or skipping a site because its manager is busy.
How do we handle sites without a clinic nearby?
This is where multi-site programs quietly fail: a site 70 miles from the nearest collection point gets tested less often than the others because it is inconvenient. Remote collection for non-regulated testing closes most of that gap, and where it does not apply, the collection arrangement for that site needs to be solved deliberately rather than left to whoever is on duty.
Who receives results at each site?
Your decision, and worth thinking about carefully. Some employers route everything to one central HR contact; others designate a person per region. Either works. What does not work is results landing with whichever local manager happened to order the test, because that is how confidential information ends up in a shared inbox.
What if different sites are covered by different union agreements?
Then the program has to account for them, the same way it accounts for state differences. Collective bargaining agreements can set out notice, testing triggers, and consequences that differ from your general policy. Tell your specialist which locations are covered by which agreement so the program does not contradict something you already signed.
One Program, Every Location
Request a testing specialist
Answer five quick questions. There is no cost and no obligation.
Sources and review
- SAMHSA - Drug-Free Workplace employer resources
- Minnesota Statutes 181.951 - Authorized drug and alcohol testing
This page is general information about employer drug testing, not legal advice. Drug testing rules differ by state and by industry. Check with your own counsel before setting or changing a testing policy.