Get Back to Work limited offer: $475 (Standard $525). Use code SAVE50. Start Now
Call 888-895-8179

How Do Clearinghouse Consent Requests Work?

Full query consent is given electronically inside the Clearinghouse; declining it keeps a driver out of safety sensitive duty. ← FMCSA Clearinghouse

Short Answer

Before an employer can see the details of a violation in a driver's Clearinghouse record, the driver must give electronic consent inside the Clearinghouse for a full query. A general or limited consent obtained outside the Clearinghouse is sufficient for a limited query, which only tells the employer whether any violation records exist, without details. If a limited query shows that records exist, or if the employer needs a full query for a pre-employment decision, the employer must request the driver's electronic full query consent, and the driver must respond inside the Clearinghouse itself.

Detailed Explanation

Two Kinds of Consent

Under 49 CFR § 382.703, a limited query relies on written or electronic consent that the employer obtains from the driver outside the Clearinghouse platform, for example as part of the driver's application paperwork. It only confirms whether violation records exist. A full query requires the driver's electronic consent given inside the Clearinghouse for that specific query, and it reveals the violation type, date, and Return to Duty status.

What Happens When a Driver Declines Consent

If a driver refuses, or simply does not respond to, a full query consent request, the employer cannot see the details of any violation. Under 49 CFR § 382.703(c), the employer must then prohibit the driver from performing safety sensitive functions until consent is given.

Timing of Consent Requests

Full query consent is requested in two common situations: before hiring or contracting with a CDL driver for a safety sensitive position, and whenever an annual limited query surfaces a possible violation that needs to be confirmed through a full query.

Applicable Regulations

49 CFR § 382.703, part of Part 382, Subpart G, governs the consent requirements described above, including the requirement that an employer prohibit a driver from safety sensitive duty when full query consent is withheld.

Professional Observation

One misunderstanding I frequently encounter is a driver treating a consent request as optional in a way that carries no consequence. Declining consent does have a consequence. It prevents the employer from confirming the driver is clear to perform safety sensitive duty, and the regulation requires the employer to keep the driver out of that duty until consent is given.

Common Misconceptions

Misconception

Declining a full query consent request protects the driver's privacy without other consequences.

Reality

Declining consent does not hide a violation that exists. It simply prevents the employer from seeing the details, and the employer must then prohibit the driver from safety sensitive duty until consent is provided.

Why the Confusion Occurs

Drivers sometimes conflate consent with disclosure and assume that withholding consent is equivalent to having no violation at all.

Frequently Asked Questions

Does the driver have to give consent every time an employer runs a full query?

Yes. Full query consent is given electronically inside the Clearinghouse and applies to that specific query request.

Can a driver give consent in advance for a future full query?

The requirement described in the FMCSA rule is that the driver gives electronic consent inside the Clearinghouse for each full query. Consult clearinghouse.fmcsa.dot.gov or your C/TPA for how the platform currently structures the consent request and response process.

Related Articles

Primary Authorities/Sources

Have Questions About a Consent Request?

If a Clearinghouse consent request is connected to an open Return to Duty requirement, a DOT qualified SAP can help you understand where you stand in the process.

Schedule an Initial SAP Assessment

Reviewed by: Perret deLapouyade, CEAP, SAP
Reviewed date: July 12, 2026
Updated date: July 12, 2026
BOK ID: BOK-0046