Never miss aquery deadline.

Both query types, one place.

Annual limited and full queries — pre-employment, escalation, and re-checks — all on one driver timeline.

The rules require two kinds of query, and the portal runs both. A 49 CFR § 382.701 program is the annual query for every driver plus a pre-employment full query before anyone performs a safety-sensitive function — and the escalations that sit between them.

Every one of these lands on the same driver timeline, so the answer to “when was this driver last queried, and what came back?” is one click, not an archaeology project across emails and the federal portal.

Rolling or fixed — your call.

Per-driver anniversaries, or one annual date for the whole fleet. Scheduled automatically either way.

The rules require at least one query per driver every twelve months. How you space those out is up to you, and different fleets run different rhythms — so the portal supports both, and schedules them for you.

Pick the model that matches how you already think about your roster. Either way, the portal builds the schedule, counts down to each driver's next query, and surfaces due and overdue items on your Action Board — the single queue you already check for everything else that needs a decision.

Self-managed or managed by us.

Initiate queries yourself with the deadlines tracked, or hand the whole program to our team.

Some safety managers want to keep their hands on every query; others want the whole thing off their plate. You choose per program, and you can change your mind.

Managed is a natural fit if you already run your random pool with us through the DOT Consortium — one team, one point of contact, one drug & alcohol program from the pool to the Clearinghouse.

Consent, the easy way.

Drivers sign the limited-query consent from a secure link. Full-query consent is requested and tracked.

Consent is where most query programs get messy, because there are two different consents and they live in two different places.

1. 01

   General consent — the driver's authorization for limited queries. This one can be electronic and retained by the employer, so the portal captures it the easy way: the driver signs from a secure link emailed to them, or you upload a signed paper form. It's filed against the driver and reused for each annual limited query.

2. 02

   Specific consent for a full query — this one the rules require the driver to grant inside the federal Clearinghouse, and no employer can capture it anywhere else. The portal requests it, tracks whether it's been granted, and handles the federal portal steps for you so the full query completes without you babysitting it.

That split matters. A signed consent form with no matching query, or a query with no documented consent, is exactly the defect a reviewer writes up. The portal keeps the two paired on the driver record — the consent and the query it authorized, together — so the trail an auditor wants is the trail you already have.

A prohibited driver, caught.

A driver who comes back prohibited is flagged and held off safety-sensitive duty until return-to-duty clears them.

The whole point of the Clearinghouse is the moment a query comes back showing a driver is prohibited. Under 49 CFR § 382.501, a prohibited driver must not perform safety-sensitive functions until the return-to-duty process is complete — and that obligation is immediate.

When a query returns prohibited, the portal does what the rules require: the driver is flagged and held off safety-sensitive duty, surfaced on your Action Board, and kept that way until the return-to-duty process clears them. There's no window where a prohibited driver quietly stays on the board because the result got buried in an inbox.

Audit-ready by default.

Queries and consent stay on the driver record. One-click dossier when a review comes.

A compliance review or an insurance renewal turns your query program into a paperwork exercise — unless the paperwork was being kept all along. With queries and consent living on the driver record continuously, audit prep stops being a scramble.

• Query results. Every limited and full query — date, type, and outcome — retained on the driver record, not in a separate portal you have to remember to check.

• Consent trail. The driver’s signed general consent for limited queries, captured electronically and stored alongside the query it authorized — the exact pairing an auditor looks for.

• Cadence proof. The schedule itself is evidence: each driver’s next-due date and the history behind it show a query program that ran on time, every year.

• One-click dossier. When a compliance review or an underwriter asks, export an audit-ready Clearinghouse dossier for a driver or the whole roster — assembled, not reconstructed.

When a reviewer or underwriter asks, you export a Clearinghouse dossier for a driver or the whole roster in one click — the queries, the consent, and the dates, assembled and ready. You see it in your compliance ledger alongside everything else that has to stay current.

How it runs, day to day.

Five steps from a roster to a query program that never lets a deadline slip.

Put together, the program runs in five steps — and after the first two, most of it runs itself:

This is part of the Pro tier — live now alongside driver qualifications, onboarding, and the accident register. Everything in Essential stays free for drug & alcohol customers; query management is one of the controls Pro adds on top.