---
title: "Automated Dispatch and Driver Compliance: Why Eligibility Status Should Be a Dispatch Constraint in 2026"
id: "27706"
type: "post"
slug: "driver-eligibility-dispatch-constraint-clearinghouse-2026"
published_at: "2026-10-26T14:00:00+00:00"
modified_at: "2026-10-27T09:54:06+00:00"
url: "https://locus.sh/blogs/driver-eligibility-dispatch-constraint-clearinghouse-2026/"
markdown_url: "https://locus.sh/blogs/driver-eligibility-dispatch-constraint-clearinghouse-2026.md"
excerpt: "Why driver compliance status, from Clearinghouse and CDL status to medical certificates, belongs inside automated dispatch and not in a back-office check, with the real 2026 rules and an exposure model."
taxonomy_category:
  - "General"
---

[General](https://locus.sh/blogs/category/general/)

# Automated Dispatch and Driver Compliance: Why Eligibility Status Should Be a Dispatch Constraint in 2026

[Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/)

Last updated: Oct 27, 2026

11 mins read

A driver eligibility constraint is a dispatch rule that stops a driver from being assigned work unless the driver’s legal status to perform it is current, covering licence, medical certificate and Drug and Alcohol Clearinghouse status. In most fleets that status lives in compliance and HR systems, while the dispatch system only knows who is available, so an ineligible driver can be assigned because nothing in the allocation engine knows. Federal rules for CDL drivers say an employer may not permit a driver in prohibited status to perform safety-sensitive functions, and that definition includes time spent waiting to be dispatched. The practical fix is to carry eligibility into automated dispatch as a hard constraint with its own refresh schedule and audit trail.

## Key Takeaways

- Clearinghouse II did not create a new employer deadline in November 2026: states had to downgrade CDLs of prohibited drivers by 18 November 2024, and employer query duties are unchanged.
- FMCSA’s agenda lists a Clearinghouse proposed rule for November 2026 (RIN 2126-AC43), but its contents are not published, so treat it as a watch item.
- Under 49 CFR 382.107, safety-sensitive functions include time waiting to be dispatched, so the dispatch moment is inside the rule.
- FMCSA data reported by FreightWaves showed about 202,000 CDL and CLP holders in prohibited status as of 2 January 2026.
- In a 200-driver model, relying on the annual query leaves about 364 driver-days of exposure, monthly limited queries about 30 and an event feed about 8.
- Locus models driver certifications among its planning constraints, but its public pages do not describe Clearinghouse or medical-certificate integration.

## Why Driver Eligibility Matters in Dispatch: The Business Case

The rules attach to who may be permitted to work, and dispatch is where permission is granted.

- 49 CFR 382.701 requires employers to run a [pre-employment query](https://www.ecfr.gov/current/title-49/part-382/section-382.701) of the Clearinghouse and to query at least once per year, and 382.703 requires the driver’s consent before any query.
- FMCSA said in its 2016 final rule that the annual query is a minimum and that employers [may query more often](https://www.federalregister.gov/documents/2016/12/05/2016-27398) with the driver’s consent.
- Under 382.501(b), an employer may not permit a driver to perform safety-sensitive functions after a violation, and 382.107 defines those functions to include [time spent waiting to be dispatched](https://www.ecfr.gov/current/title-49/part-382/section-382.107) .
- The Clearinghouse II final rule set [18 November 2024](https://www.federalregister.gov/documents/2021/10/07/2021-21928) as the date by which states had to check the Clearinghouse and downgrade the CDLs of drivers in prohibited status, within 60 days of notification.
- FMCSA data reported by FreightWaves showed [202,345 drivers in prohibited status](https://www.freightwaves.com/news/the-industry-is-focused-on-200000-non-domiciled-cdls-but-there-is-another-200000-driver-story-nobody-is-covering) as of 2 January 2026, with 159,226 of them not having started return-to-duty.
- FMCSA’s penalty schedule lists a maximum civil penalty of [$7,155 per violation](https://www.ecfr.gov/current/title-49/part-386/appendix-Appendix%20B%20to%20Part%20386) for Part 382 Subpart G violations and $19,246 for other non-recordkeeping Part 382 violations.
- A driver’s medical certificate is valid for [up to 24 months](https://www.ecfr.gov/current/title-49/part-391/section-391.45) , and states must downgrade a CDL within 60 days of a not-certified status.

FMCSA’s 2026 regulatory agenda lists a proposed rule to modify the drug and alcohol testing and Clearinghouse rules, [RIN 2126-AC43](https://www.reginfo.gov/public/do/eAgendaViewRule?pubId=202510&RIN=2126-AC43)
, with a projected date of November 2026. The date is a projection, and we found no sign the proposal had been published as of 26 October.

| Also Read: How Locus Powers AI Dispatch for 3PL Providers in 2026 |
| --- |

## How to Make Driver Eligibility a Dispatch Constraint in Six Steps

The six steps move eligibility from a periodic check to a rule the allocation engine enforces.

### 1. List every eligibility condition and where it lives

Typical conditions are CDL class and endorsements, licence status, medical certificate expiry, Clearinghouse status, the driver qualification file and any employer-specific requirements. Record the system that holds each one.

### 2. Separate predictable conditions from event-driven ones

A medical certificate expires on a known date, so it can be scheduled. A Clearinghouse violation or a CDL downgrade arrives as an event, so it needs a refresh cadence or a feed.

### 3. Set a refresh cadence for each source

The Clearinghouse annual query is a minimum, and more frequent limited queries are allowed with consent. The motor vehicle record review is required at least every 12 months under 391.25. Choose cadences that match the exposure you can accept.

### 4. Enforce eligibility as a hard constraint

An ineligible driver should not be assignable, and the system should fail loudly and escalate when no eligible driver is available, not fall back silently to the next best option.

### 5. Respect consent and use limits

Clearinghouse queries need the driver’s written or electronic consent, kept for three years, and a driver who refuses consent cannot perform safety-sensitive work. Limit who can see eligibility detail, and have counsel confirm how results may be used.

### 6. Log every decision

Record why each assignment was allowed or blocked, who approved any exception and when the underlying status was last refreshed. The record supports the driver qualification file and any audit.

| Also Read: The Hardest Part of Agentic TMS is Not the AI. It is Deciding What the AI is Allowed to Do. |
| --- |

## Back-Office Check, Periodic Sync and Dispatch Constraint: Key Differences

| Approach | When status is checked | What happens at assignment | Exposure |
| --- | --- | --- | --- |
| Back-office check | At hiring and on a compliance calendar | Dispatch does not see eligibility | An ineligible driver can be assigned until the next check |
| Periodic sync | On a schedule, such as nightly or weekly | Dispatch sees last-synced status | Gaps equal to the sync interval |
| Dispatch constraint | Continuously, with scheduled expiries and event feeds | The engine blocks and escalates | Limited to the lag of the source itself |

## What to Look for in Dispatch System Software

### Eligibility as a first-class driver attribute

The software should hold licence class, medical expiry and compliance status as driver attributes with dates, not as free-text notes.

### Hard-constraint behavior

When a driver is ineligible, the system should refuse the assignment and surface the reason, and it should not quietly route around the problem.

### Integration with compliance systems

Look for APIs or connectors that load eligibility from HR, compliance or service-agent systems, with a stated refresh cadence.

### Override with approval and an audit trail

Any exception should require an authorized approver and a documented reason, and every decision should be logged.

### Real-time response to change

When a status changes, the real-time dispatch system should re-plan the affected routes and notify dispatchers immediately.

| Also Read: What 200,000 Drivers in Limbo in US Means for Your Routing Decisions |
| --- |

## Eligibility-Aware Dispatch in Action: Real-World Results

**Who is in scope.** Clearinghouse duties attach to CDL-required driving under 382.103, so the audience for this post is fleets running trucks.

| Vehicle or driver | CDL and Clearinghouse | FMCSA driver qualification and medical rules |
| --- | --- | --- |
| Single vehicle, GVWR 26,001 lb or more | Yes | Yes, in interstate commerce |
| Combination, GCWR 26,001 lb or more with a towed unit over 10,000 lb | Yes | Yes |
| Vehicle carrying 16 or more passengers, or placarded hazmat | Yes | Yes |
| Cargo van or truck, 10,001 to 26,000 lb, no placarded hazmat | No | Yes, in interstate commerce |
| Cargo van under 10,001 lb | No | Generally no |

State rules can differ, so confirm for your states.

**An exposure model on illustrative numbers.** The figures are assumptions. A fleet has 200 CDL drivers. Medical certificates run on a 24-month cycle, so about 100 renew each year. If 5% of renewals are late and the lapse is found after an average of 14 days, the fleet dispatches 5 drivers for 14 days each, or 70 driver-days, with a lapsed certificate. Separately, assume 1% of drivers a year, 2 drivers, have a status change such as a Clearinghouse violation or CDL downgrade. The driver-days they are dispatched while ineligible depend on how fast the fleet finds out.

| Detection method | Average lag | Driver-days dispatched while ineligible, per year |
| --- | --- | --- |
| Annual query only | About 182 days | About 364 |
| Monthly limited query | About 15 days | About 30 |
| Event feed or weekly check | About 4 days | About 8 |

Under 382.701, an employer may query more often than annually with consent, so the monthly row is available without new rules. We found no published FMCSA integration specifications for a live feed, so the last row depends on a service agent or an internal process and not on a federal API. Expiry dates, unlike events, need no query at all: loading the certificate date into the dispatch system removes the 70 driver-days in the first case. The model is arithmetic on assumptions and not a benchmark.

**A Fortune 50 parcel and logistics leader.** The enterprise’s decisioning layer models certifications, time windows, fleet types and customs requirements among its 250+ operational constraints for 4,500+ captive and third-party drivers under one customer-defined policy, with every autonomous decision logged for explainability, traceability and human override. Weekly execution rose from 75% to 92% across 51 sites. The case shows driver attributes working as planning constraints, and it does not mention Clearinghouse status. [Read the Fortune 50 case study](https://locus.sh/case-studies/fortune-50-parcel-centralized-dispatch/)
.

**A North American retailer.** The retailer, with a private fleet of several hundred trucks, runs Locus’s agents alongside its existing ERP and WMS, which stay the systems of record, with every autonomous decision governed by six mechanisms and human-in-the-loop override. It reported 80%+ less manual dispatch and 99%+ on-time store delivery. The case shows governed assignment of a private truck fleet, and it is not a compliance result. [Read the retailer case study](https://locus.sh/case-studies/retailer-multimodal-logistics-automation/)
.

## Common Driver Compliance and Dispatch Mistakes to Avoid

**Treating eligibility as a hiring event.** Status changes after hire, and an assignment made on last year’s check is made on stale information.

**Relying on the annual query alone.** The annual query is a minimum, so a violation can go unseen for months unless you query more often with consent.

**Failing silently to the next driver.** A hard constraint should refuse and escalate, because a quiet fallback to another driver can hide a staffing gap or assign the wrong person.

**Forgetting that waiting to be dispatched counts.** Safety-sensitive time includes waiting to be dispatched, so the dispatch moment is inside the rule and not before it.

| Also Read: Rider Management for Online Grocery: Why Eligibility Beats Proximity in 2026 |
| --- |

## How Locus Approaches Driver Eligibility in Automated Dispatch

Locus, the world’s first Decision-Intelligent, Agentic TMS, treats driver attributes as constraints in assignment. Its agents allocate work within the policies a customer defines, its [Route Planning System](https://locus.sh/route-planning-system/)
 plans against 250+ real-world constraints including driver availability and skills, and its [Driver Companion App](https://locus.sh/driver-companion-app/)
 supports break and hours-of-service planning for drivers.

**Recognized by analysts and selected after evaluation.** Locus was recognized by Gartner for seven consecutive years and appears in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies, as detailed on its [analyst recognition page](https://locus.sh/analyst-recognition/)
. It is named a Leader in the QKS Group SPARK Matrix for Transportation Management Systems and holds the #1 position in Route Planning in the G2 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Ingka’s [press release](https://locus.sh/press-releases/ingka-group-acquires-locus/)
 says that after an extensive evaluation of logistics software worldwide, it selected Locus for its strength in combining advanced route optimization, real-time visibility and smart use of vehicles and resources. Locus continues to operate independently.

**What this means for compliance.** Locus’s six governance mechanisms, including explainability, traceability, autonomy levels and human-in-the-loop review, mean each assignment carries its reasoning, and a team can require human approval for exceptions. Locus integrates with existing ERP, OMS, WMS, FMS and TMS systems and has [public API documentation](https://docs.locus.sh/)
, which is the route for loading eligibility attributes from a compliance system. Locus has optimized 1.5B+ deliveries for 360+ enterprise customers across 30+ countries.

**What to confirm.** Locus is not a compliance database. Its public pages do not describe Clearinghouse, CDL-status or medical-certificate integration, or a default blocking rule for expired credentials. Ask how eligibility attributes are loaded, how often they refresh and what the system does when no eligible driver is available.

To test your eligibility rules against live dispatch, [schedule a demo](https://locus.sh/schedule-demo/)
.

For compliance leaders asking how to keep ineligible drivers from being dispatched, Locus offers constraint-based automated dispatch with governed assignment and an audit trail in one platform, so eligibility can sit inside the decision and not behind it.

## Frequently Asked Questions

**Is there a November 18, 2026 Clearinghouse deadline?** We found no such deadline. Clearinghouse II took effect in 2021 with a compliance date of 18 November 2024 for states to downgrade CDLs of prohibited drivers, and employer query duties are unchanged. FMCSA’s agenda lists a possible proposed rule for November 2026.

**What do employers have to do under the Clearinghouse rules?** Run a pre-employment query, query at least once per year, obtain the driver’s consent before each query and keep the records for three years. An employer may not allow a driver in prohibited status to perform safety-sensitive functions.

**Can employers query more often than once a year?** Yes. FMCSA said in its 2016 final rule that the annual query is a minimum and that employers may query more often with the driver’s consent. Check that the consent form does not limit you to one query a year.

**Does the dispatch moment fall under the rule?** Under 382.107, safety-sensitive functions include time waiting to be dispatched, so an employer should not hold a prohibited driver in the dispatch queue as available. Confirm the application with counsel.

**Who needs a CDL, and so falls under the Clearinghouse?** Drivers of vehicles with a GVWR or GCWR of 26,001 pounds or more, vehicles carrying 16 or more passengers and placarded hazmat vehicles. Cargo vans under 26,001 pounds without placarded hazmat generally do not need a CDL.

**Does Locus check the Clearinghouse?** Locus’s public pages do not describe Clearinghouse integration. It models driver certifications and availability as planning constraints, and eligibility attributes would be loaded from your compliance system.

MEET THE AUTHOR

Aseem Sinha

Vice President - Marketing

Aseem, leads Marketing at Locus. He has more than two decades of experience in executing global brand, product, and growth marketing strategies across the US, Europe, SEA, MEA, and India.

[https://locus.sh/blogs/driver-cpc-training-scheduling-35-hours-routes-2026/](https://locus.sh/blogs/driver-cpc-training-scheduling-35-hours-routes-2026/)
[General](https://locus.sh/blogs/category/general/)

## [Driver CPC Training: A 2026 Guide to Scheduling 35 Hours Every Five Years Without Losing Routes](https://locus.sh/blogs/driver-cpc-training-scheduling-35-hours-routes-2026/)

How logistics operators can schedule 35 hours of Driver CPC periodic training every five years without losing routes: EU and UK rules, a bunching model, a scheduling plan and what to ask of software.

[Anas T](https://locus.sh/blogs/author/anas_locus/)

Last updated: Oct 27, 2026

[Read more](https://locus.sh/blogs/driver-cpc-training-scheduling-35-hours-routes-2026/)

[https://locus.sh/blogs/logistics-order-management-audit-touchless-order-rate-2026/](https://locus.sh/blogs/logistics-order-management-audit-touchless-order-rate-2026/)
[General](https://locus.sh/blogs/category/general/)

## [Logistics Order Management Audit: Five Measured Numbers That Show What Caps Delivery Speed in 2026](https://locus.sh/blogs/logistics-order-management-audit-touchless-order-rate-2026/)

Five measured numbers, from touchless order rate to re-decision time, show whether order-to-dispatch decisions cap delivery speed, with a worked model.

[Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/)

Last updated: Oct 27, 2026

[Read more](https://locus.sh/blogs/logistics-order-management-audit-touchless-order-rate-2026/)

Automated Dispatch and Driver Compliance: Why Eligibility Status Should Be a Dispatch Constraint in 2026

- Share
  - [Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Flocus.sh%2Fblogs%2Fdriver-eligibility-dispatch-constraint-clearinghouse-2026%2F)
  - [Twitter](https://twitter.com/intent/tweet?url=https%3A%2F%2Flocus.sh%2Fblogs%2Fdriver-eligibility-dispatch-constraint-clearinghouse-2026%2F&text=Automated%20Dispatch%20and%20Driver%20Compliance%3A%20Why%20Eligibility%20Status%20Should%20Be%20a%20Dispatch%20Constraint%20in%202026)
  - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Flocus.sh%2Fblogs%2Fdriver-eligibility-dispatch-constraint-clearinghouse-2026%2F)
  - [Email](mailto:?subject=Automated%20Dispatch%20and%20Driver%20Compliance%3A%20Why%20Eligibility%20Status%20Should%20Be%20a%20Dispatch%20Constraint%20in%202026&body=https%3A%2F%2Flocus.sh%2Fblogs%2Fdriver-eligibility-dispatch-constraint-clearinghouse-2026%2F)

- Print
- Download
- [Schedule a Demo](https://locus.sh/schedule-demo/)

### Is your team spending more time on fixing logistics plan than running the operation?

- Agentic transportation management from order intake to freight settlement
- Route optimization built on 250+ real-world constraints
- AI-driven dispatch with automatic execution handling

20%Cost Reduction

66%Faster Planning Cycles

[Schedule a demo](/schedule-demo/)

Insights Worth Your Time

[General](https://locus.sh/blogs/category/general/)

## [Locus 2026 UK Consumer Survey: Why Returns Visibility is Now the Conversion Engine for AI-Driven Shopping in UK Retail](https://locus.sh/blogs/returns-visibility-conversion-engine-ai-shopping-uk-retail-locus-q2-2026-consumer-survey/)

[Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/)

Last updated: Sep 11, 2026

[General](https://locus.sh/blogs/category/general/)

## [Locus 2026 US Consumer Survey: Generative AI isn’t Just Changing How Consumers Shop, it’s Breaking the Demand Patterns US Retail Was Built On](https://locus.sh/blogs/generative-ai-shopping-effect-retail-fulfillment-operations-locus-q2-2026-consumer-survey/)

[Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/)

Last updated: Jun 2, 2026

[General](https://locus.sh/blogs/category/general/)

## [Embedded vs Bolted-On AI: The Architecture Question European Logistics Buyers Are Asking](https://locus.sh/blogs/embedded-vs-bolted-on-ai-european-logistics-platform-architecture-business-benefits/)

[Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/)

Last updated: Jul 17, 2026

[General](https://locus.sh/blogs/category/general/)

## [Hybrid Fleet Management: How Owned, 3PL, Gig, ICE, and EV Capacity Actually Operate at Most Enterprises](https://locus.sh/blogs/three-workforce-fleet-reality-owned-3pl-gig-drivers/)

[Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/)

Last updated: Jul 18, 2026

[General](https://locus.sh/blogs/category/general/)

## [US Returns Hit $850 Billion in 2025: Why US Retailers Are Restructuring Reverse Logistics in 2026](https://locus.sh/blogs/850-billion-us-returns-ai-routing-reverse-logistics-2026/)

[Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/)

Last updated: Jul 18, 2026