Random testing is one of the few pieces of a drug testing program that is designed to work precisely because employees cannot predict it. Unlike pre-employment or post-accident testing, which are triggered by a specific event, random testing runs on an ongoing basis with no announcement and no obvious pattern. That unpredictability is the entire point. It is also the part employers most often get wrong, sometimes without realizing it.
For employers required to run a random testing program, or those considering adding one voluntarily, understanding how a defensible random selection process actually works matters more than most people assume. A program that looks random on paper but isn’t, in practice, can undermine the deterrent effect it’s supposed to create and create real compliance exposure for regulated employers.
What random testing is actually meant to do
Random testing exists to deter drug and alcohol use by making the possibility of a test a constant, unpredictable presence rather than something tied to a known trigger. Pre-employment testing only matters on the way in. Post-accident testing only matters after something has already gone wrong. Random testing is the piece that’s supposed to influence behavior on an ordinary Tuesday, precisely because no one knows in advance whether that day is a testing day.
This is why random testing is treated differently from every other testing category. The value comes entirely from the fact that selection can’t be anticipated, worked around, or prepared for. Once a random program develops a pattern, whether that’s testing on the same day each quarter, always pulling from the same shift, or giving supervisors informal discretion over who gets picked, it stops functioning as random testing and starts functioning as something closer to for-cause testing with extra steps.
How a genuinely random selection process works
A defensible random selection process depends on using a method that gives every eligible employee an equal, unpredictable chance of being chosen each time selections are run. In practice, this means a computer-based random number generator applied against the full, current pool of eligible employees, not a manual method like drawing names from a hat or rolling dice, which can introduce bias or simply look arbitrary if the program is ever questioned.
Two details matter here that employers sometimes overlook. First, the pool needs to be refreshed immediately before each selection so it accurately reflects who is currently eligible, accounting for new hires, terminations, and any status changes. Second, genuine randomness means some employees may be selected more than once in a year while others may not be selected at all. That’s not a flaw in the system. It’s what statistically random selection actually looks like, and employers should understand this going in so an uneven distribution doesn’t get mistaken for a broken process.
Selection frequency and spacing
How often selections happen, and how the resulting tests get spread across the year, has a direct effect on whether a program actually deters anything. Running selections quarterly is generally treated as a minimum; more frequent selection cycles make the program harder to anticipate. Beyond the selection cycle itself, the actual test dates should fall in an unpredictable pattern across the year and across shifts, rather than clustering around convenient or recurring dates.
The same logic applies to timing within a shift. A program that always tests first thing in the morning, or only ever pulls people at the start of a shift, has created a predictable window that employees will eventually notice. Varying the timing, along with keeping selection lists confidential until the moment of notification, preserves the element of surprise that makes the whole program worth running.
Rates for DOT-regulated employers
For employers subject to DOT drug and alcohol testing rules, the random testing rate isn’t set by the employer. FMCSA sets a minimum annual percentage rate that regulated employers must meet, and that rate is tied to industry-wide positive test results reported each year. When industry positive rates stay low, the rate can be reduced; when they rise, FMCSA can increase it back up. As of 2026, the minimum annual random testing rate for controlled substances sits at 50 percent of the average number of driver positions, with a separate 10 percent minimum rate for random alcohol testing. Employers running a DOT program should check the current rate each year rather than assuming last year’s number still applies, since FMCSA can adjust it based on the data.
Non-DOT employers running voluntary random programs aren’t bound by this specific rate, but many choose to model their own program on it anyway, simply because it’s a well-established, defensible standard.
Common mistakes that undermine a random program
A few mistakes show up repeatedly in random testing programs, and most of them trace back to convenience quietly overriding randomness.
Giving supervisors informal input into who gets selected is one of the most common. Even well-intentioned discretion, like a manager suggesting someone be skipped because they’re mid-project, breaks the statistical integrity of the process and can expose the program to claims of selective or discriminatory enforcement if it’s ever challenged.
Letting the selection list leak before notification is another. If employees find out who’s on the list before they’re actually notified, the element of surprise is gone for that cycle, and word tends to spread fast in smaller workplaces.
A third is treating the pool as static. If new hires aren’t added and departed employees aren’t removed before each selection, the pool no longer reflects who’s actually eligible, and the program can end up testing people who’ve already left or skipping people who should have been included from day one.
Documentation that makes the program defensible
A random testing program needs a paper trail that shows the process was actually followed, not just that a policy exists describing how it should work. That generally means keeping records of the selection method used, the date and time each selection was run, who was drawn, when each selected employee was notified, and when and where the collection occurred. If a selection or a result is ever questioned, this documentation is what demonstrates the program was administered consistently rather than applied unevenly.
This is also where a lot of the quiet cleanup happens. Reviewing completion status regularly, rather than only reconciling numbers at the end of the testing period, makes it much easier to catch a missed selection or a notification that fell through the cracks while there’s still time to correct it.
Communicating the program to employees
Employees should understand, before any selection ever happens, that random testing is part of the program, roughly how selection works, and what’s expected of them once they’re notified, including how quickly they need to report for testing. This doesn’t mean explaining the mechanics of the selection algorithm. It means making sure no one is caught off guard by the concept of random testing itself, even though the timing of any individual selection stays unpredictable by design.
Clear expectations up front also reduce disputes later. An employee who was told during onboarding that random testing is part of the job is in a very different position than one who’s hearing about it for the first time when they’re notified they’ve been selected.
Choosing a specimen type for random testing
Specimen type matters for random testing in a way it doesn’t always for other testing situations, because random testing is meant to capture a snapshot of recent use rather than a longer look-back window. A cotton swab drug test is well suited to this, since oral fluid collection reflects a shorter, more recent detection window and can be administered on the spot without the logistics a urine collection site requires. That combination of speed and a recent-use window is part of why oral fluid has become an increasingly common choice for random testing programs, including under DOT’s 2026 rule permitting oral fluid as an approved collection method alongside urine.
Whatever specimen type a program uses, the collection method itself should stay consistent enough that results are comparable and the process is easy to explain if it’s ever questioned.
The bottom line
A random testing program only works if it’s actually random, not just labeled that way in a policy document. The mechanics matter: a genuine random selection method, a pool that’s kept current, unpredictable timing, tight confidentiality around who’s been selected, and documentation that shows the process was followed consistently every time. Get those pieces right and random testing does what it’s supposed to do. Skip a few of them and it becomes a program that exists on paper but doesn’t hold up to a closer look.
Sources
FMCSA, Annual Random Controlled Substances Testing Percentage Rate
FMCSA, Best Practices for DOT Random Drug and Alcohol Testing
Written and reviewed by Sarah, MouthSwabDrugTests.com
