Clearinghouse Full Query vs Limited Query

Full query before the first safety-sensitive function

The pre-employment query is a full query. It happens after the driver consents in the Clearinghouse and before the driver performs any safety-sensitive function. Driving is a safety-sensitive function. A road test, a yard move that is safety-sensitive work, and the first loaded mile are not a waiting room where you may skip the query. Order of operations: consent, full query, then the work. Not the work, then the query if the trip goes well.

Employers who hire on a Sunday and plan to query on Monday have already missed if the driver drove on Sunday. Do not put a driver in a truck as a favor while the consent email sits unopened. The database is the point of the rule. A conversation in which the driver says I am clean is not a query.

The account, the designations, and the reporting duties are the drug and alcohol Clearinghouse guide. This page will not rebuild that overview. If you do not have an employer account, stop and build it before you hire. The query cannot be run from a broker login or from memory.

What a full query shows

A full query tells the employer whether the Clearinghouse has a prohibition on the driver performing safety-sensitive functions. That is the hire-day question. It is not a criminal-background check, not an MVR, and not a physical. Those are other files. A full query that shows the driver is not prohibited is permission to proceed to the rest of the qualification steps. It is not, by itself, a complete driver file.

A full query that shows a prohibition is a stop. The driver does not perform safety-sensitive work. The way back is the substance-abuse-professional process, a return-to-duty test, and the follow-up plan, reflected in the Clearinghouse. Until that status changes, the carrier that uses the driver is using a prohibited driver. That conduct sits in 382.215 and 382.211 and is a single-occurrence automatic failure on a new-entrant audit. One trip counts. Do not negotiate a probationary load.

You will see the query result in the portal. Save it where your drug-and-alcohol records live. Do not rely on a screenshot in a text message as the only copy if you can download the record the Clearinghouse gives you.

Limited query: a yes or no, not a history

A limited query answers whether the Clearinghouse contains a record for that driver. It does not open the record. It is the tool for the annual check on drivers you already employ, described on the annual page. It is the wrong tool for the morning you hire someone.

Because it is only a yes or no, a limited query cannot tell you that a prohibition is old, resolved, or someone else's. A yes is not a green light with an asterisk. A yes is an instruction to run a full query and to keep the driver out of the truck until you do. A no means no record was found on that query. It does not freeze the future. The next annual query, and your duty to query before hire, still exist.

Do not run a limited query, see a no, and tell a new hire they are cleared for pre-employment. You asked the annual question on hire day. Ask the full question.

Consent, and what a refused consent means

Queries that reach a driver's Clearinghouse record require the driver's consent in the system. You cannot consent for them. You cannot accept a signed paper as a substitute for the electronic consent the database asks for. If the driver does not consent, you do not receive a result. No result is not a negative result. It is an absence. The absence means you do not use the driver for safety-sensitive work.

Treat a refused consent, a stalled consent, and an expired consent the same way. The driver is not dispatched until a query the rules recognize has been completed. Chasing the driver is allowed. Inventing a result is not. A note in the file that says driver promised to consent after this load is a note that you used the driver without the query.

Owners who are both employer and driver still need the consent path their consortium or administrator uses. You do not get to mark yourself consented on a spreadsheet and skip the database.

The 24-hour rule if a limited query hits

When a limited query shows that a record exists, the employer obtains a full query within 24 hours. During that time the driver does not perform safety-sensitive functions on the theory that the full query will probably be fine. The 24 hours is the deadline to obtain the full information, not a window of legal driving. If you cannot get consent for the full query, you still cannot use the driver.

If the full query then shows no current prohibition, you document it and return the driver to work if the rest of the qualification file allows it. If it shows a prohibition, the driver stays out. If you miss the 24 hours and keep using the driver, you have stacked a query failure on top of whatever the record contained.

Annual queries that come back no do not trigger the 24-hour full query. Do not order a full query out of anxiety and also do not ignore a yes. Read the result. Follow the branch that result requires. The annual page is where the 12-month habit lives. Do not merge the two articles into one vague query policy.

Owner-operators query themselves through a consortium design

A one-truck carrier is still an employer. The employer queries the driver. When those are the same person, the industry uses a consortium or a third-party administrator so the query is still a real Clearinghouse query and not a diary entry. This page does not list companies that sell that service. It says you need a design in which a full query happens before you perform safety-sensitive work and a limited query happens at least annually.

Do not create a second rule in which owner-operators are trusted and employees are queried. The database does not have that split. A prohibited owner-operator is prohibited. The certificate on the wall does not override the Clearinghouse.

If you are building the account the same day you want to dispatch, you are already late for that load. Move the load or move the start date. The query is faster than an audit and slower than a set of keys, which is why the keys have to wait.

Write the query type on the file name you save. Pre-employment full is not the same PDF as annual limited, and a year from now nobody should have to guess which gate was cleared. If the portal shows consent pending, the status is pending, not passed. Refreshing the page does not create a consent the driver has not given.

A driver who was queried by a previous employer still needs your query. Their old carrier's full query does not transfer to your USDOT as a pre-employment clearance. Order your own, after your own consent, before your own dispatch. The previous PDF in the driver's email is a souvenir, not your record.

Frequently Asked Questions