The Rules Didn’t Change. The Scrutiny Did.

Every once in a while, DOT puts something out that does not look like a big deal. This is one of those times. No new rule. No new regulation. No headline grabbing mandate. Just a reminder. And if you have been around this industry long enough, you know those reminders usually mean one thing. Someone looked under the hood and did not like what they saw.

What Happened

The Office of Drug and Alcohol Policy Compliance issued a notice reminding employers and Substance Abuse Professionals to follow the return to duty process exactly as written in 49 CFR Part 40. Not loosely. Not close enough. Exactly. Because what they are seeing right now is inconsistency, and in some cases, shortcuts.

Where Things Are Breaking Down

The return to duty process is not complicated, but it is specific, and that is where problems creep in. According to the notice, issues are showing up in a few key areas such as SAP evaluations not being conducted properly, employers accepting incomplete SAP reports, employees being returned to duty without a verified negative return to duty test, and follow up testing plans not being executed. None of those are gray areas. Every one of them is a compliance failure. And here is the part that matters. Nothing in the rule changed.

The SAP Is Not a Suggestion

The SAP is the gatekeeper in this process. They evaluate the employee, prescribe education or treatment, determine when the employee is eligible to test, and set the follow up testing plan. If that process is not followed exactly, the employee is not properly cleared to return to safety sensitive work. There is no workaround for that.

What Done Right Actually Looks Like

A compliant return to duty process includes a face to face initial SAP evaluation, completion of required education or treatment, a follow up SAP evaluation, a directly observed negative return to duty test, and a follow up testing plan with at least six tests in the first twelve months. Miss one of those steps and the file is incomplete. Incomplete files have a way of becoming audit findings.

Where Employers Get Exposed

This is where it gets real for motor carriers. The Designated Employer Representative cannot return a driver to duty until the SAP follow up report is complete and the negative return to duty test is verified. Also, follow up testing is not a replacement for random testing. It is in addition to it. That is a detail that gets missed more often than it should.

Why This Matters Right Now

This notice is not about changing the rules. It is about enforcing them. If you connect this to everything else happening right now such as Clearinghouse tightening, data accuracy focus, MOTUS rollout, and increased audit scrutiny, it all points in the same direction. Documentation and process discipline are no longer optional.

The Quiet Risk Sitting in Your Files

Here is the uncomfortable question. If someone walked in tomorrow and pulled your return to duty files, what would they find. Complete documentation, verified steps, and clear SAP credentials, or gaps that were good enough at the time. Because right now, FMCSA is telling you exactly where they are looking, and it is right there.

What You Should Do Next

This is not complicated, but it does require attention. Audit your return to duty files, verify SAP qualifications and documentation, confirm every required step is present, and ensure follow up testing plans are active and tracked. Do it now while it is still your idea.

Bottom Line

Nothing changed. The expectation did. In this environment, the difference between compliant and exposed is not what you intended to do. It is what you can prove you did.