By now, most people in the trucking industry have at least heard about the Brandon Blackburn case. What started as a shocking headline quickly became something more serious: a reminder that even a federal compliance system can have weak points if the right controls are not in place.
According to the FreightWaves investigation, Blackburn was able to register as a Substance Abuse Professional, or SAP, inside the FMCSA Drug and Alcohol Clearinghouse, clear a high volume of drug and alcohol violations, and operate in that role without proper credentials. For carriers, that immediately raised two concerns. First, how was that possible? Second, and more importantly, what needs to change now?
That is where the conversation should be headed. The bigger issue is no longer just how this happened. It is what FMCSA should fix next, and what carriers should be watching while those changes are still pending.
The Problem Is Not Complicated
At its core, this was not a highly technical or difficult-to-understand failure. The Clearinghouse allowed someone to operate in a critical role without first verifying that he was actually qualified to be there. That role is not minor. SAPs are responsible for evaluating drivers after drug and alcohol violations and determining when they are eligible to begin the return-to-duty process.
If that part of the system is not secure, then the integrity of everything that follows becomes less certain. A return-to-duty clearance may appear valid on the surface, but if the person making that determination was not properly credentialed, carriers are left relying on records that may not fully hold up under scrutiny.
That is what makes this case so important. It exposed a weak point in the FMCSA Clearinghouse that affects how carriers assess driver eligibility, compliance risk, and hiring decisions.
What FMCSA Should Be Looking At
There are several practical changes FMCSA should be considering if it wants to close the gaps highlighted by this case. These are not complex reforms. They are basic controls that would help strengthen the system and reduce the likelihood of a similar issue happening again.
Credential Verification Should Happen Before Access Is Granted
One of the most obvious fixes is also one of the most important. A system should not allow someone to operate as a SAP based primarily on self-attestation. For a role with this level of responsibility, credentials should be verified before a user is ever allowed to perform evaluations or clear drivers in the system.
That one safeguard would go a long way. If FMCSA had a stronger credential verification process upfront, the Blackburn case likely never becomes the story it did.
High-Volume Activity Should Be Flagged Immediately
Another issue is the volume of activity. According to the FreightWaves report, Blackburn was clearing drivers at a pace that should have raised serious questions. Any system handling return-to-duty decisions should be able to recognize unusual activity patterns and escalate them quickly.
If one SAP account is clearing far more drivers than normal, that should trigger an immediate review. Not eventually. Not after outside reporting forces attention onto it. Right away. High-volume behavior is one of the easiest warning signs to monitor, and it should already be part of any credible compliance database.
Documentation Should Be Required at Every Step
One of the simplest ways to strengthen the FMCSA Clearinghouse would be to require documentation throughout the return-to-duty process. If the system required records tied to each step, it would become much harder for anyone to move drivers through the process without actually doing the work.
That documentation should include the SAP evaluation, proof of treatment or education completion, return-to-duty testing, and the follow-up testing plan. Requiring those records to be uploaded and connected to the file would create a much more defensible chain of compliance.
The Reality Is These Changes Take Time
Even if FMCSA responds to this case with meaningful reforms, carriers should not expect those changes to happen overnight. Federal systems do not move quickly. Policy changes, approval processes, technical updates, and implementation timelines all take time.
That means carriers are still operating in the same environment that allowed this issue to happen in the first place. Until stronger controls are in place, the burden does not sit entirely with regulators. Carriers also need to adjust how closely they review driver records, return-to-duty files, and supporting documentation.
In other words, waiting for FMCSA to fix the system is not enough. Carriers still have to manage the risk that exists right now.
What Carriers Should Be Paying Attention To
While the industry waits to see what changes FMCSA may make, carriers should be paying closer attention to a few practical areas. None of these require a complete overhaul of an existing compliance program, but they do require more awareness and stronger internal review.
Repeated SAP names across driver files should stand out. Return-to-duty processes that move unusually quickly should get a second look. Documentation should be reviewed for completeness and consistency rather than simply collected and filed away. And carriers should remain alert for any FMCSA updates, industry guidance, or enforcement focus that develops in response to this situation.
These are not dramatic changes. They are reasonable steps that can help carriers identify issues before those issues become legal, insurance, or operational problems.
Why This Is Bigger Than One Case
It would be easy to treat this as the story of one bad actor and stop there. That would be a mistake. The deeper problem is not just that one person allegedly exploited the system. It is that the system appears to have allowed it.
That is what makes the FreightWaves reporting so significant. The concern is not limited to one account. Thousands of SAPs were reportedly registered through the same general process, which suggests this was not simply a one-off anomaly. It points to a broader weakness in how the FMCSA Clearinghouse verifies critical roles and monitors the integrity of return-to-duty activity.
Most of the time, the system may work the way carriers expect it to. But this case is a reminder that when it fails, the consequences can be much larger than one file or one driver.
Where Compliance Strategy Starts to Shift
For years, many compliance programs have been built around a straightforward goal: meet the requirement, keep the documentation, and pass the audit. That foundation still matters. Carriers still need to follow the rules, maintain files, and complete the required checks.
But situations like this are changing the expectations around compliance strategy. Increasingly, it is not just about whether a box was checked. It is about whether the decision behind that box can still be defended later.
That means carriers are now being pushed toward a more active model of compliance. They need to verify what they can, watch for what the system might miss, and make sure their records support the decisions they made. That is a more involved process than simple checklist compliance, but it is also a more defensible one.
How Compliance Partners Fit Into This
This is one reason more carriers are leaning on outside compliance support. It is not necessarily because their internal teams are incapable. It is because the scope of risk is shifting, and many safety departments are already working at capacity.
A compliance partner like US Compliance Services can help carriers review driver records with a stronger focus on risk, not just file completion. That includes identifying repeated SAP names, spotting unusual timelines in the return-to-duty process, reviewing documentation for gaps or inconsistencies, and helping build procedures that go beyond the minimum requirement.
That kind of support also creates something many carriers do not think about until they need it: proof. Proof that the company did more than rely on a status result. Proof that it took reasonable steps to review, verify, and protect its operation after a known risk became visible.
That can matter a great deal if a file is ever questioned by a plaintiff attorney, an underwriter, or an auditor.
What to Expect Moving Forward
There is a strong chance this situation will lead to some level of change. FMCSA may tighten SAP registration requirements, increase oversight, improve tracking of unusual activity, or require stronger supporting documentation within the Clearinghouse itself.
Those would all be positive steps. But even if they happen, no compliance system is ever completely risk-free. There will always be some degree of trust built into the process.
The difference now is that carriers are more aware of where that trust can break down. That awareness should shape how they approach compliance review, documentation, and driver file oversight moving forward.
Final Thought
What caught so many people off guard about this case is that it did not expose widespread wrongdoing by carriers. It exposed how much trust the industry was placing in a system that looked stronger than it may actually have been.
Now that the gap is more visible, the response needs to be practical. Pay closer attention to return-to-duty records. Tighten internal review where you can. Do not rely on one data point when the stakes are this high. And if your team does not have the bandwidth to do that thoroughly, bring in outside help that knows what to look for.
Because at the end of the day, compliance is not just about staying within the rules. It is about making sure the decisions you make today will still stand up later.
Read part one of our series on this topic: When Compliance Isn’t Enough: What the Brandon Blackburn Case Should Be Teaching Every Carrier
Read part two of our series on this topic: How to Audit Driver Files After the FMCSA Clearinghouse Loophole
