← All articles

How to Record Test Outcomes for DOT Audits

How to Record Test Outcomes for DOT Audits

A random selection is only half the job. When an auditor asks why a selected driver was not tested, when collection occurred, or what the final result was, a spreadsheet note that says “complete” will not carry much weight. Knowing how to record test outcomes means building a record that shows the full path from selection to final disposition - without filling gaps from memory months later.

For DOT-regulated employers, the goal is not to create more paperwork. It is to maintain a clean, traceable testing history that supports your program when DOT asks. You run the pull, document what happens next, and retain records that can be reviewed in sequence.

Start With the Selected Driver Record

Record the outcome against the specific random selection, not just against the employee’s general personnel file. That connection matters. A result record should show that this driver was eligible in the testing pool, was selected during a defined selection period, and moved through the required follow-up steps.

At minimum, the selection record should preserve the driver’s name or unique employee ID, DOT mode or testing pool, selection period, test type, and the date and time of the random pull. It should also retain the selection method and the eligible-pool snapshot used for that pull.

The pool snapshot is particularly valuable. Driver rosters change. People are hired, terminated, transferred, or placed on inactive status. If an auditor reviews a February selection in October, you need to show who was eligible when the selection was made - not who happens to be on the roster now.

Use Statuses That Describe What Actually Happened

“Pending” and “completed” are too vague for a DOT testing workflow. A clear status history lets your safety team identify open items before they become missed tests, while giving an auditor a defensible sequence of events.

A practical workflow can use statuses such as:

| Status | What the record should show | |---|---| | Selected | Random pull date, time, pool, selection period, and selection documentation | | Notification issued | Notification date, time, delivery method, and the person who sent it | | Reported for collection | Collection date, time, and collection site or provider, if tracked | | Collection completed | Confirmation that the specimen or alcohol test was collected | | Awaiting final result | Collection is complete but the final verified outcome is not available | | Final result entered | Result category, result date, source document, and user who entered it | | Exception or unresolved | Reason, action taken, responsible party, and next review date |

The exact labels can vary by system, but each status needs a defined meaning. If “collection completed” sometimes means the driver arrived and other times means the laboratory received the specimen, the record will create confusion instead of evidence.

Timestamp each status change. The difference between selected, notified, and collected can matter when reviewing whether testing was conducted promptly and whether a delay needs an explanation. A status history should show who made each update and when, not simply display the current state.

Record the Final Outcome Only From the Right Source

Do not turn preliminary information into a final test result. Drug test outcomes should be entered based on the verified result reported through the proper process, including Medical Review Officer verification where applicable. For alcohol testing, record the confirmed result from the testing documentation and follow your company process for any required action.

The result field should be structured, not free-form whenever possible. Use defined categories that match your program’s reporting and review needs, such as negative, positive, refusal, canceled, invalid, or other outcome categories supported by your process. A standardized field makes it easier to identify incomplete records and prepare required management reports.

Alongside the outcome, record the result date, the document or provider report used as the source, and the person entering the result. If the outcome requires an employer action, keep that action separate from the result itself. For example, a positive result and the employee’s removal from safety-sensitive duties are related events, but they are not the same record.

That separation prevents a common problem: a result log that cannot tell an auditor whether it is reporting a laboratory or MRO outcome, an internal employment decision, or both.

Do Not Use “No Result” as a Catch-All

A driver can fail to produce a final result for several very different reasons. The test may still be pending. The collection may have been canceled. The driver may have been unavailable for a documented reason. There may be a refusal determination. Each scenario needs its own status and supporting notes.

If a selected driver was not tested during the selection period, document why, what follow-up occurred, and who reviewed the exception. Do not erase the selection or mark it complete to make the dashboard look clean. An unresolved record is better than a misleading one, provided it is actively managed and documented.

Keep Documents Attached to the Event, Not Buried in Email

Email chains, scanned forms, collection confirmations, and provider reports often contain the detail needed to explain an unusual outcome. If those documents live only in individual inboxes or paper folders, the record is fragile.

Attach or associate supporting documentation with the selected driver’s testing event. The record should make it easy to answer basic questions: Was the driver notified? When did collection occur? What source supports the final outcome? Was there an exception? Who resolved it?

Use consistent file names if your process includes uploaded documents. A format such as driver ID, selection period, test type, and document date reduces hunting later. Limit access to people with a legitimate role in the testing program, because test records carry confidentiality obligations as well as retention requirements.

Make Corrections Without Rewriting History

Testing records occasionally need correction. A collection date may be entered incorrectly, a result may be posted against the wrong event, or additional documentation may arrive after the initial entry. The answer is not to silently overwrite the old record.

Use a correction process that preserves the original entry, identifies what changed, records why it changed, and timestamps the user making the correction. A write-once final-result record, paired with an additive correction log when necessary, is much easier to defend than a file where values can change without explanation.

This is where paper logs and shared spreadsheets create unnecessary exposure. They can track information, but they rarely prove who changed a field or whether the eligible pool and outcome history were preserved at the time of the event. A system with locked pool snapshots, timestamped status changes, and documented result entry gives you a record that holds up beyond the person who originally managed it.

Build a Review Step Before the Period Closes

Do not wait for an annual review to find records stuck in pending status. At the end of each selection period, review every selected driver and identify records that lack notification evidence, collection confirmation, a final result, or an exception explanation.

This review should be operational, not ceremonial. Assign an owner to each unresolved item, set a follow-up date, and record the final disposition when it is known. For larger fleets or multi-company administrators, filter by location, pool, or client company so unresolved records do not disappear inside a large master list.

DTSMS Online is designed around this chain of evidence: a locked eligible pool, documented random selection, notification history, collection-status updates, and timestamped result records. There is nobody in between to reconstruct the story for you later.

Retain the Record According to the Rule That Applies

Outcome recording and record retention are connected, but they are not identical. Different DOT records can carry different retention periods, and company policy or another regulatory requirement may require longer retention. Apply the current requirements for your DOT agency and test type, and do not rely on a generic folder-cleanup schedule.

Your file should be exportable or reviewable as a timeline: selected, notified, collected, result received, result entered, exception resolved. That is the practical test. If a safety director, auditor, or new administrator can understand the event without calling the former employee who managed it, the record is doing its job.

Good outcome records do more than close a task. They let you spot incomplete testing activity early, answer audit questions with evidence rather than recollection, and keep control of a process that should never depend on a spreadsheet detective story.