Magellan

Who Stops the Prohibited Driver Before Dispatch?

Connect Clearinghouse results, commercial driving privileges and dispatch instructions through a documented decision process.

A recruiter may see an apparently valid CDL, a testing vendor may have one result and dispatch may see an available driver. None of those views alone establishes that every applicable drug/alcohol and licensing condition has been addressed. The company needs a clear owner for the relevant checks and a visible instruction when an assignment cannot proceed.

The Clearinghouse return-to-duty resource (clearinghouse.fmcsa.dot.gov) explains that a driver with an unresolved drug/alcohol programme violation is prohibited from safety-sensitive functions until the applicable return-to-duty process is completed. Treat that as a separate issue from whether a license copy is present in the file. Do not use an informal manager's approval to override a prohibition.

Identify who performs the applicable query, who reviews the result, who communicates the operating restriction and who can document a later release. These are internal responsibilities; assigning them does not transfer the carrier's obligations to a vendor. Keep a backup owner so the next shift does not have to infer eligibility from an unanswered email or a driver's expectation that the issue is resolved.

Use the current Clearinghouse instructions for the applicable pre-employment or ongoing query and consent process. Do not assume that one consent form, one query type or a vendor account covers every circumstance. Confirm the driver identity and the employer relationship, and preserve the appropriate evidence of the completed process.

The Clearinghouse employer FAQs (clearinghouse.fmcsa.dot.gov) provide the current programme explanations. The relevant rules remain the authority for legal obligations. A company can maintain a query register showing driver identifier, query purpose, requested and completed dates, result location, reviewer and next required action. Avoid storing unnecessary sensitive details in a broadly accessible dispatch tool.

A pending response should be shown as pending. A submitted query is not a completed result, and a charge from a provider does not establish the content of the response. If the identity is wrong or consent is unresolved, address that problem through the proper process. Keep a record of what is known and what is not, rather than turning an incomplete screen into a green dispatch status.

FMCSA's Clearinghouse II explanation (clearinghouse.fmcsa.dot.gov) describes state commercial-driving-privilege consequences associated with prohibited status from 18 November 2024. A change to “not prohibited” in the Clearinghouse and reinstatement of state commercial privileges are related but separate steps. Do not assume that observing one automatically proves the other is complete.

Use the appropriate current records to resolve both questions. Also check other applicable qualification and assignment conditions. Medical-certification evidence, endorsements, restrictions and company or customer requirements should not disappear from the review simply because the drug/alcohol programme issue was addressed.

In a hypothetical case, a driver says a return-to-duty result was entered that morning. The responsible reviewer should verify the applicable programme status and any required licensing action rather than rely on the message alone. Record the evidence and actual release time. If an agency or provider must correct a record, keep the assignment instruction clear while that is being resolved. Do not create an undocumented “temporary exception” to a legal prohibition.

Dispatch needs an unambiguous instruction, the relevant assignment limit and a contact for resolution. It usually does not need the underlying confidential testing details. Use role-based access and keep programme records in the appropriate restricted location. A generic red label without an owner can create confusion without improving control.

Define how a status change reaches every relevant shift. A manual roster can work only if people use the current version and communicate changes reliably. A software flag can work only if the actual assignment path consults it and unauthorized users cannot bypass it. Verify the mechanism before claiming that the system prevents dispatch. This article describes a management control, not a verified feature of Magellan's TMS or website.

Test a hypothetical unavailable-driver scenario without involving a real applicant or triggering a live query. Can dispatch identify the hold? Can it arrange a different qualified driver? Can an ordinary user incorrectly change the status? Record the exercise as a test, not proof that every future case will be caught. Correct the process where the exercise exposes a gap.

The return-to-duty process and any follow-up obligations should be handled through the applicable programme and qualified participants. Do not describe one negative test, one email or one treatment-related document as the whole process. The employer's responsibilities and the driver's licensing situation need to be checked for the actual case.

Maintain a controlled task register for any continuing obligations that apply. Identify the responsible party, source requirement, relevant date and evidence of completion. Keep sensitive details separate from the operational roster. A reminder is useful, but the reminder being dismissed does not prove the underlying action occurred.

The internal release record should identify what was verified, which source was used and who made the authorized decision. Preserve the previous restriction and its resolution history. If new information arrives later, evaluate it through the appropriate process rather than assuming the old approval remains sufficient indefinitely. Obtain programme-specific or legal advice where interpretation is needed, instead of using a general blog example as an instruction for an individual driver.

Periodically test whether recruiting, the programme owner, a provider and dispatch understand their separate roles. Choose a review rhythm suited to the operation; do not present a monthly management check as a federal requirement or as proof that the programme is compliant. Look at evidence of completed actions, unresolved queries and communication failures.

Ask a concrete question: If an applicable result changes today, who will see it, who will decide what it means and how will the next assignment be handled? If that answer depends on one person remembering to send a message, make the handoff more reliable. Preserve actual events and avoid invented historical checks or backdated approvals.

The useful standard is a documented chain from the applicable query and programme result to the relevant driving-privilege check and operating decision. A testing vendor, a roster or a software platform can support parts of that chain. None should be described as a substitute for the applicable requirements or a guarantee that every driver shown as available is qualified for the next load.

Topics

Clearinghouse / Drug & Alcohol / RTD / Dispatch