Random Drug and Alcohol Testing Pool Controls: A Record Review Method

Published: September 18, 2026.

A controlled substances and alcohol testing program has two visible parts and one quiet part. The visible parts are the tests and the results. The quiet part is the pool: the list of drivers who are subject to random selection, the method used to select them, and the records that prove each step happened.

Research question and scope

This study asks how a carrier can review the administrative controls around its random testing pool using records it already keeps. It treats the pool as a bookkeeping system with three checkpoints: membership, selection, and completion.

It does not evaluate medical review officer determinations, interpret a test result, decide whether a driver violated a rule, or provide legal advice. Those questions are governed by 49 CFR Part 382 and by the testing procedures at 49 CFR Part 40, and they belong to qualified professionals and the administrator.

What the regulations require in outline

49 CFR Part 382 establishes the controlled substances and alcohol testing requirements for drivers subject to the Federal Motor Carrier Safety Administration's rules. Part 40 establishes the procedures that govern how testing is conducted. Together they describe the categories of testing, including pre-employment, random, post-accident, reasonable suspicion, return-to-duty, and follow-up testing, and they set recordkeeping expectations, including at 49 CFR 382.401 and 382.305.

The administrator publishes annual minimum random testing rates that carriers must meet. Because the rate can change from year to year, a review should confirm the current published rate from the primary source rather than reuse an old figure. This brief does not state a current percentage for that reason.

Checkpoint one: pool membership

Pool membership is the inventory of drivers subject to random selection. A review should be able to answer a basic set of questions from the record:

• Which drivers were in the pool for each selection period?
• When did each driver enter the pool and, if applicable, leave it?
• Does the pool match the list of drivers actually performing safety-sensitive functions?
• For a multi-employer consortium, is the carrier's list current with the consortium?

Membership errors are common at the edges. A newly hired driver who is not yet in the pool, a driver who transferred out, and a driver on an extended leave each create a question about the correct treatment. The carrier should state its policy for those cases in advance and apply it consistently.

Checkpoint two: selection

Selection is where the randomness claim lives. Under a random program, selections are made by a scientifically valid method and each driver has an equal chance of selection each selection period, in the ordinary case. A carrier that uses a consortium or a third-party administrator relies on that party's documented method.

A review can test selection records without re-running the random draw. For each selection cycle, confirm that a selection occurred, that it covered the full pool for that cycle, and that the selected drivers were drawn from the pool as it existed. Keep the selection list and the date it was produced. If selections were made by hand, the record should explain the method and show that it was applied consistently.

Checkpoint three: completion

A selected driver is not the same as a completed test. Completion records show whether the driver was notified, directed to a collection site, and tested within the applicable window. For each selection, the record should support one of a small set of outcomes: completed and reported, completed and cancelled with the required process, or not completed with a documented reason.

Measure the two checkpoints separately. Selection coverage asks whether the program selected drivers at the required rate. Completion asks, of those selected, how many provided a usable specimen within the rules. A program can have perfect selection coverage and poor completion, or the reverse, and each condition points to a different remedy.

Build the review table

One row per selected driver per cycle keeps the review reproducible:

Field	Purpose
Driver reference	Avoid names where possible; use a stable identifier
Pool entry and exit dates	Reconstruct membership at selection time
Selection cycle and date	Show that a draw occurred
Notification date	Start the completion clock
Collection date	Show the test was provided
Outcome state	Completed, cancelled, or not completed
Exception note and owner	Track the unresolved cases

The table should not become a copy of the testing file. It is an index that lets a reviewer trace each selection to its supporting records in the approved system.

A boundary case

Suppose a selected driver is on approved leave for the entire collection window and no test is completed. One reviewer marks the selection as satisfied because the driver was selected; another marks it as incomplete because no specimen was collected. The two readings produce different completion rates.

Define the treatment of leave, unavailability, and short-notice absence in advance. Record the driver's status at selection time and the reason the test was not completed. The point of the review is not to choose the more forgiving answer but to produce the same answer every time the case appears.

Reviewer agreement and reproducibility

Have a second reviewer independently rebuild the pool membership for one selection cycle and trace a sample of selections through to completion records. The reviewer should recover the same membership, the same draw, and the same outcome states. Include at least one cancelled test, one selection with a timing question, and one driver whose membership changed during the period.

Record corrections as dated notes. If the reviewers disagree on a category, the definition is not tight enough for a reproducible control, even if the underlying program is sound.

Interpretation boundaries

A record review describes the completeness and consistency of pool documentation. It does not establish that a driver used or did not use a prohibited substance, that a test was valid or invalid, or that a carrier complied with every procedural detail. A missing record is a documentation gap, not a positive or negative test result.

A clean review shows that the administrative steps are documented. It does not certify the program against the regulations. Only the administrator and qualified professionals make those determinations.

Limitations

Consortium records may lag behind a carrier's roster, and a carrier may not control the consortium's retention format. Terminated drivers, drivers on long leave, and owner-operators under contract can each change the correct pool treatment. Paper-based selection records can be difficult to reproduce if the method is not described. Any of these conditions can limit how far a review can go.

The findings apply to the named carrier, pool, and period. They are not a benchmark and should not be used to compare testing programs across carriers.

Source treatment

The Code of Federal Regulations and 49 U.S.C. 31306 describe the statutory and regulatory structure of testing programs. The National Archives provides general records-management context. Those sources frame the checkpoints this method reviews but do not supply a carrier's pool policy or a passing threshold. Where this brief names a local rule, such as leave treatment, it is a local choice.

Evidence-led conclusion

Random testing pool controls are reviewable when membership, selection, and completion are each documented at the time they occur. Measuring selection coverage and completion separately gives a carrier two honest rates instead of one ambiguous impression. The defensible output is a reproducible index of selections with named unresolved cases, not a claim about any individual driver.

References

1. Electronic Code of Federal Regulations. 49 CFR Part 382, Controlled Substances and Alcohol Use and Testing. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-382. Retrieved 2026-09-18.
2. Electronic Code of Federal Regulations. 49 CFR Part 40, Procedures for Transportation Workplace Drug and Alcohol Testing Programs. https://www.ecfr.gov/current/title-49/subtitle-A/part-40. Retrieved 2026-09-18.
3. Electronic Code of Federal Regulations. 49 CFR Part 379, Preservation of Records. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-A/part-379. Retrieved 2026-09-18.
4. United States Code. 49 U.S.C. 31306, Alcohol and Controlled Substances Testing. https://www.law.cornell.edu/uscode/text/49/31306. Retrieved 2026-09-18.
5. Electronic Code of Federal Regulations. 49 CFR Part 390, FMCSA General Rules. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-390. Retrieved 2026-09-18.
6. National Archives and Records Administration. Records Management Policy. https://www.archives.gov/records-mgmt/policy. Retrieved 2026-09-18.