If you manage a DOT drug and alcohol testing program, you already know random testing has to be unannounced. What often gets overlooked is a smaller but critical detail: documenting the exact time an employee is notified of their random selection.

This is why InOut Labs provides Participant Notification Letters to every client — and why we recommend logging notification time as a standard part of your random testing procedure.

The logic below is written around FMCSA-regulated CDL drivers, but it applies equally to FAA, FRA, FTA, PHMSA, and USCG-regulated employees under 49 CFR Part 40.

FMCSA Requires Random Tests to Be Unannounced

49 CFR 382.305 requires that random drug and alcohol tests be unannounced and spread reasonably throughout the year. Employers cannot give advance notice that would allow an employee time to alter their behavior before collection.

Why it matters: Recording the exact time of notification helps demonstrate that the selection was genuinely unannounced and that the driver had no reasonable opportunity to avoid or delay the test.

Drivers Must Proceed Immediately After Notification

FMCSA’s Best Practices for DOT Random Drug and Alcohol Testing guidance states that once a driver is notified of selection, they must proceed immediately to the collection site. Unnecessary delay can be evaluated as a refusal to test.

Why time documentation helps: Logging both when the driver was told and when they arrived at the collection site creates a two-point timeline—proof that the driver moved promptly, consistent with regulatory expectations.

Part 40 Ties Notification Timing to Employer and Collector Actions

Under 49 CFR 40.61, if a driver fails to appear for a scheduled test or doesn’t report within the authorized time window, the collector must notify the employer’s Designated Employer Representative (DER). The DER then has the responsibility of determining whether a refusal occurred, drawing on the definitions of prohibited conduct in 49 CFR 40.191.

Why this matters: These are two different actors with two different duties—the collector’s obligation to report a failure to appear, and the employer’s obligation to evaluate it. Accurate notification timestamps give the DER the context needed to determine whether the driver complied appropriately or whether the delay should be evaluated as a refusal.

Refusal to Test Has Serious Consequences

Per FMCSA’s guidance on failed or refused tests, a refusal is treated the same as a positive result. It requires immediate removal from safety-sensitive duties and completion of the full return-to-duty process before the driver can resume covered functions.

Why timestamping helps: You need to be able to show whether a late arrival was a genuine refusal, which carries significant regulatory and employment consequences, or simply a misunderstanding. Precise timestamps are often what settles that question.

Supports Your Recordkeeping and Audit Trail

DOT and FMCSA recordkeeping requirements (see the CARAT Record Keeping Requirements) require employers to track and retain documentation covering selection, notification, and any refusals.

Why it matters: The notification timestamp becomes part of your audit trail—evidence that you followed proper procedure at every stage, from selection through completed collection.

The Two-Point Timeline: Notification and Arrival

It’s worth being precise about what “documenting notification time” actually protects.

On its own, a notification timestamp only tells you when the driver was told. Its real value comes from pairing it with the time the driver reported to the collection site.

Together, these two data points let you measure the gap between selection and collection—which is exactly what regulators and auditors want to see when evaluating whether a test was unannounced and whether the driver responded promptly.

How InOut Labs Helps: Participant Notification Letters

This is exactly why InOut Labs issues a Participant Notification Letter for every random selection.

Each letter identifies the employee, confirms whether they were selected for drug testing, alcohol testing, or both, and spells out exactly what they need to bring to the collection site:

  • Government-issued photo ID
  • Federal Custody and Control Form (CCF) or eCCF
  • Signed Authorization Form (for alcohol tests)

Critically, the letter includes a signature line where the employee acknowledges receipt and records the date and time they were notified.

That single line is what turns notification into documented, defensible evidence—giving employers a clear record for their DOT random testing program without adding manual tracking work to your team’s plate.

Want to see what this looks like in practice? Download a sample Participant Notification Letter.

Frequently Asked Questions

Do I have to document the time a driver is notified of a random test?

DOT regulations don’t specify an exact recordkeeping format for notification time, but documenting it is a best practice that directly supports your obligations under 49 CFR 382.305 and Part 40, and it strengthens your position in an audit or refusal determination.

What happens if a driver doesn’t report right away after being notified?

The collector notifies your DER, who must determine whether the delay constitutes a refusal to test under 49 CFR 40.191. Documented notification and arrival times are often the deciding evidence in that determination.

Does this apply outside of FMCSA/CDL drivers?

Yes. The same unannounced-notification logic under Part 40 applies across all DOT modal agencies—FAA, FRA, FTA, PHMSA, and USCG.

Questions About Your Random Testing Program?

Have questions about your random testing program or Participant Notification Letters? Contact InOut Labs.