English language proficiency has been a driver qualification requirement under 49 CFR 391.11(b)(2) for decades. Since June 25, 2025, inspectors have been placing drivers who fail it out of service. On August 10, 2026, FMCSA proposed writing that consequence into the federal rules themselves, under docket FMCSA-2026-0826, with public comments due October 9, 2026.

Most of what has been written about this rule is for compliance managers and lawyers. This post is for the dispatcher at a 5 to 30 truck carrier. When one of your drivers is placed out of service at a scale house, the compliance problem turns into a dispatch problem inside the hour: a loaded trailer that is not moving, a broker waiting on an ETA, and a pickup tomorrow that now has no driver.

One thing up front. Howdy Dispatch is not an ELD, not a compliance product, and does not assess, verify, or certify anyone's English. This is not legal advice. For the rule itself, read the docket.

What is the FMCSA English language proficiency out-of-service rule?

The proposed rule published in the Federal Register touches three places in the regulations:

49 CFR 390.5 and 390.5T, where "out-of-service order" is defined. The proposal adds ELP violations to that definition.
49 CFR 391.11, where a new paragraph (c) says a driver who violates the ELP requirement is placed out of service.
A border commercial zone exception. A driver whose trip stays inside a U.S.-Mexico border commercial zone would not be placed out of service for ELP alone. That exception falls away if there is evidence the driver has operated, or intends to operate, beyond the zone. The rule text lists the evidence: bills of lading, dispatch records, equipment interchange receipts, driver statements, or other shipping documents.

In plain terms, what inspectors have been doing since mid-2025 under FMCSA's May 20, 2025 enforcement guidance would become part of the regulations, not just a policy.

How does the roadside English assessment actually work?

According to the proposal, the roadside assessment has two steps:

A driver interview. The inspector talks with the driver to see whether they can respond to official questions, the kind of back-and-forth about the trip and the paperwork that happens at every inspection.
A highway traffic sign recognition assessment. This only happens if the driver passes the interview.

Fail either step and, under the proposal, the driver is placed out of service.

We are not going to coach anyone on the assessment. That is between the driver, the inspector, and the regulation. What we can talk about is what happens to your operation the minute it goes wrong.

How many drivers have been placed out of service for ELP?

The scale changed fast once enforcement did. FMCSA's own numbers, from the regulatory analysis in the proposed rule:

Period	ELP violations	Out-of-service orders
January 1 to June 24, 2025	7,812	33
June 25, 2025 to March 19, 2026	60,399	19,045

That is 33 out-of-service orders in the first half of 2025 and 19,045 in the nine months after enforcement changed. On the day the rule was published, FreightWaves reported that the Department of Transportation said more than 26,000 commercial drivers had been placed out of service for ELP since strict enforcement was reinstated. Keep those two numbers separate. FMCSA's table stops at March 19, 2026. The 26,000 figure is DOT's later statement.

The regulatory analysis is also useful for a different reason. When FMCSA estimated the cost of the new border-zone out-of-service orders, it assumed about $800 per truck per day of downtime (rounded up from FleetNet America estimates of $448 to $760, covering lost revenue, fixed costs, and delay). And it assumed that a carrier would need, on average, two days to locate and dispatch a driver, and for that driver to reach the truck and continue the trip.

Read that sentence again as a dispatcher. The agency's own baseline is that a stranded truck takes two days to get moving again. That is the number your planning should beat.

Why is an out-of-service order a dispatch problem, not just a compliance problem?

Here is a scene. The names are made up.

It is 2:40 in the afternoon. Your driver, call him Ray, is running a loaded reefer of fresh produce from Garden City, Kansas to a grocery DC in Fort Worth. It is a 480-mile run for a broker we will call Blue Mesa Freight at $2.45 a mile, a little under $1,200 for the load, with a 5:00 a.m. delivery appointment. Ray gets waved into a weigh station on US-287 and pulled around back for an inspection. Forty minutes later he is out of service.

Now walk the next 60 minutes from the dispatcher's chair.

Find out. How long until you know? If the answer is "when Ray finally calls, or when the broker calls asking why the truck stopped moving," you have already lost time you will not get back.
Locate. Where exactly is the truck? Which scale house? Is it parked safely with the reefer running?
Cover. Who on your roster can get to that truck, and how fast? Who is off duty close by, and who has hours left?
Notify the broker. Blue Mesa needs a straight answer and a new ETA before they start calling other carriers about tomorrow's loads.
Preserve the paperwork. The rate confirmation, the BOL, the inspection report, and whatever the officer handed Ray. The rule's own border-zone language names bills of lading and dispatch records as evidence of where a trip is going. It is the same load file you need for the broker and for any detention or layover conversation later.

A dispatcher needs three things in that hour: to know within minutes, to see where the truck is, and to have the whole load file in one place. When the roster lives in a spreadsheet and the BOL lives in a driver's camera roll, that hour gets spent hunting for paperwork instead of covering the load.

What should a small fleet do before October 9?

Read the docket and comment if it affects you. The proposal is open for comment at regulations.gov under docket FMCSA-2026-0826 until October 9, 2026. Small carriers are the ones who feel the downtime, and that is worth saying on the record.

Talk to your drivers. Make sure nobody hears about the two-step assessment for the first time from an inspector. That conversation is about expectations, not test prep.

Decide the coverage plan now, not at 2:40 p.m. Which drivers can pick up a stranded load, on which lanes, and who calls the broker? Write it down.

Here is a Monday-morning checklist you can run without any software at all:

A driver roster that shows who can cover which lanes and who has hours available on a given day.
One place where every load's rate con and BOL lives, not five inboxes and a group text.
A standing rule that any roadside stop gets reported to dispatch immediately, with the officer's name, badge number, and the outcome.
One named person who owns the broker call when a load stops moving.

If your office can do those four things, you are ahead of FMCSA's two-day assumption before you buy anything.

How Howdy Dispatch fits the stop

Howdy Dispatch is built for the hour after the stop. Here is what it does today, stated plainly.

Drivers report the stop from the iOS app. Incident reporting includes a pulled-over type for DOT inspections and traffic stops, with structured fields for the officer, badge, citation, and outcome, plus photo evidence. We covered the full feature in our post on driver incident reporting.
Everyone who needs to know, knows. When an incident is created, every dispatcher, admin, and owner on the company gets a push notification. Unresolved incidents also raise an alert chip on the HQ jobs page.
You can see where the truck is. The HQ live map shows the truck's last GPS position, so "which scale house" is not a phone call.
The load file is already in one place. The rate confirmation, the pickup and delivery photos, the manifest, and the incident photos all sit on the load record.

That load file exists in the first place because of how loads get entered. Our AI dispatch platform reads the broker's rate confirmation PDF and pre-fills the load: customer, origin, destination, mileage, rate, appointment times, and broker contact. The dispatcher reviews and saves. So when Blue Mesa calls, the rate con is already on the load, not buried in someone's Outlook.

What Howdy Dispatch does not do matters just as much here. It is not an ELD. It is not a compliance or driver qualification product. It does not test or verify anyone's English, and it cannot prevent, contest, or clear an out-of-service order. What it does is shorten the hour after one.

Frequently asked questions

Is the ELP out-of-service rule already in effect? Inspectors have been placing drivers out of service for ELP violations since June 25, 2025. The August 10, 2026 proposal would write that into the federal regulations. It is a proposed rule with comments open until October 9, 2026.

What does the border commercial zone exception cover? A driver whose trip stays inside a U.S.-Mexico border commercial zone would not be placed out of service for ELP alone, unless evidence such as bills of lading or dispatch records shows the trip goes beyond the zone.

How long does FMCSA assume a truck sits after an ELP out-of-service order? In its cost estimate for border-zone out-of-service orders, FMCSA assumes two days to locate and dispatch a driver and get the truck moving, at about $800 a day in downtime.

Can Howdy Dispatch help a driver pass the assessment? No. Howdy Dispatch does not assess or certify English proficiency. It helps the dispatch office find out about a stop fast, see where the truck is, and keep the load paperwork together.

Plan for the stop before it happens

The rule is a regulatory question, and the docket is where you answer it. The stranded load is an operations question, and your office answers that one every time a truck stops moving.

If you want the stop reported in minutes, the truck on a map, and the load file in one place, start a 14-day free trial of Howdy Dispatch.

FMCSA English Proficiency Rule: What a Small Fleet Does Now