The Grace Period Ended Oct 6: ELD Revocation Is Now an Out-of-Service Problem
After Oct 6, 2026, carriers still on Aug 6 revoked ELDs face no-RODS citations and OOS. Inventory devices, set cover rules, watch the registry.
A driver rolls into a scale house on October 7 with an ELD that still looks fine on the dash. The identifier matches one of five devices FMCSA moved to the Revoked list on August 6. The officer does not ask for a paper backup as a courtesy. Under the bulletin, that truck is treated as operating without an ELD. The citation is 49 CFR 395.8(a)(1), no record of duty status. The driver goes out of service under CVSA OOS Criteria.
That is not a future rule change. The 60-day clock on the August 6 batch closed October 6, 2026. If your shop is still discovering which units run devices with identifiers MRS255, HRS169, HIG385, TRS263, or SPARK6 after the fact, you are not managing equipment. You are managing roadside surprise.
The August 6 action is one wave in a year-plus purge. Asset fleets feel it as parked power and missed revenue miles. Brokers feel it when a covered truck goes dark mid-move and the customer still expects the original ETA. Hybrids feel both when a company tractor and a brokered unit fail the same registry check on the same day. The ops question is no longer "did we buy a registered ELD once." It is whether device identifiers, cover holds, and roadside document packets are wired into how you actually run freight.
What Oct 6 changed (and what it did not)
On August 6, 2026, FMCSA removed five devices from the Registered ELD list and placed them on the Revoked Devices list for failure to meet the minimum requirements in 49 CFR Appendix A to Subpart B of Part 395. The five identifiers were MRS255, HRS169, HIG385, TRS263, and SPARK6.
Carriers had 60 days. The required steps were explicit:
Stop using the revoked devices and revert to paper logs or logging software for required hours-of-service data.
Replace them with a device from the Registered Devices list before October 6, 2026.
Before October 6, safety officials were encouraged not to cite 395.8(a)(1) or 395.22(a) for drivers still on those devices, and instead to review paper logs, logging software, or the ELD display as a backup. Beginning October 6, carriers still on those devices are considered to be operating without an ELD. Officials who encounter them should cite 395.8(a)(1) and place the driver out of service per CVSA OOS Criteria.
A provider can still fix deficiencies and return to the registry. FMCSA said as much, and still urged carriers not to wait. Hoping the vendor patches before the next inspection is not a cover plan.
The revocation pattern is the real story
October 6 was not a one-off cliff. It was the next date on a repeating calendar:
May 20, 2026: twelve devices revoked; OOS treatment for continued use began July 20, 2026.
June 23, 2026: one device revoked; OOS date August 23, 2026.
July 9, 2026: ten devices revoked; OOS date September 8, 2026.
August 6, 2026: five devices revoked; OOS date October 6, 2026.
The pattern is consistent. Roughly 60 days of paper or logging-software bridge, then 395.8(a)(1) and CVSA OOS for anyone still running the revoked identifier. Industry reporting on the August 6 batch put the cumulative total at 95 devices removed from the ELD registry since January 2025. That is not a boutique compliance footnote. It is a standing equipment risk for any shop that treats ELD choice as a one-time purchase.
Why replacements keep failing the second screen
On December 1, 2025, FMCSA announced a complete overhaul of ELD vetting. The stated problem was that the old path made it too easy to register non-compliant devices or re-register devices that had already been revoked, which produced repeated revocations and costly swaps for carriers.
The rebuilt process includes:
Initial review: verification of contact information, technical specifications, and device images.
Fraud detection: cross-checks against active, inactive, revoked, and in-process lists.
Category outcomes: Category 1 approved, Category 2 information requested, Category 3 further review, Category 4 denied.
That is why "we will just switch to another cheap unit" is a weaker answer in 2026 than it was two years ago. The registry gate is harder. Re-badging a revoked product into a new listing is the exact failure mode the December 2025 redesign was built to catch.
Self-certification is on the chopping block
In early October 2026, FMCSA Deputy Administrator Jesse Elison, speaking at a trucking cybersecurity conference in Long Beach, said the self-certification process "hasn't worked." Industry reporting on those remarks said the agency is working on a rule to end or rework self-certification, with no public timeline. Since the start of 2025, according to those remarks, only one or two new providers had been certified, hundreds of providers had been kept off the registry, and upwards of roughly 100 devices had been removed.
The same remarks touched adjacent operational friction: UX fixes for the Motus portal (launched May 2026) were hoped for in weeks, with backend work taking longer, and biennial-update inactivation enforcement had been suspended after the Motus rollout stumbled. Those points matter for carrier registration hygiene. They do not soften the October 6 OOS cliff for revoked ELDs. The hours-of-service device on the truck and the USDOT registration portal are related fraud and compliance projects, not the same roadside decision.
Assume the purge continues while the rule rewrite moves. Do not assume a friendly grace period will appear every time your preferred device lands on the Revoked list.
Decision 1: Inventory the identifiers your drivers actually run
Registered and Revoked lists are public. Your roadside outcome depends on the identifier in the cab, not the brand name on last year's invoice. Pull a live inventory, not a purchasing spreadsheet.
Capture ELD name, model, and ELD identifier for every power unit and leased driver you put on the road.
Match those identifiers against the current Registered Devices list and the Revoked Devices list, not against marketing pages.
Flag any unit whose identifier matches an August 6 revoked device (MRS255, HRS169, HIG385, TRS263, SPARK6) or any earlier revocation that already hit its OOS date.
Separate "device present" from "device registered." A working screen that produces a log is not enough after the grace window if the identifier is revoked.
For owner-operators and leased capacity, require the identifier before dispatch, not after a scale-house call.
Asset fleets can do this against equipment master data. Brokers have to force the question into onboarding and load acceptance, because the truck you covered yesterday may have swapped devices overnight. Hybrids need one view that covers company units and brokered trucks, or the exception will always hide on the side you are not watching.
Decision 2: Write cover rules for mid-move revocation and post-grace OOS
A truck that goes OOS at a scale mid-lane is a service failure with a compliance root cause. Decide the play before the phone rings.
Hard stop on known revoked identifiers. If the identifier is on the Revoked list and past its OOS date, that truck is not cover-eligible until it is on a Registered device (or properly on paper or logging software only during an active, agency-defined grace window).
Grace-window protocol. During a published 60-day bridge, require documented paper or logging-software RODS and a dated replacement plan. Do not treat "provider said they will fix it" as enough.
Mid-move failure mode. If a unit is discovered revoked after dispatch, define who calls the customer, who sources replacement capacity, who owns detention or layover cost, and what evidence packet goes to claims.
Broker versus asset split. Asset shops own the hardware swap and driver downtime. Brokerage shops own the cover swap and the customer promise. Write both paths. Hybrids need a handoff rule when a company truck fails and brokerage cover has to finish the move.
Customer communication script. "Our carrier's ELD was revoked and the driver was placed out of service" is better said once, with a new ETA, than discovered when the POD never arrives.
The commercial fight after an OOS is predictable: who pays the tow, the layover, the late penalty, and the replacement truck. The shops that bleed less have already assigned those costs in the carrier agreement and the customer SOP.
Decision 3: Treat registry watch as recurring ops hygiene
ELD revocation is now a calendar event, not an annual IT project. May, June, July, and August 2026 each produced a revoke-then-OOS cycle. Waiting for a viral industry post is how October 7 becomes your first alert.
Subscribe to FMCSA ELD news and industry-wide emails so revoke bulletins hit compliance and dispatch the same day.
Re-check identifiers on a fixed cadence (weekly during active waves, at least monthly in quieter stretches) and after every lease-on or equipment add.
Put registry status next to insurance and authority checks in carrier onboarding, not in a side spreadsheet.
Train roadside and safety teams on the difference between the grace window (paper or logging software accepted, citations for 395.8(a)(1) and 395.22(a) discouraged) and the post-grace window (no RODS citation and OOS).
When a provider claims a device is "back," verify it on the Registered Devices list before you clear the hold. FMCSA returns fixed devices to the list and informs industry. Your hold should clear on that update, not on a vendor email alone.
Encode uniqueness in the workflow, not in tribal knowledge
Every freight business mixes company trucks, leased owner-operators, and brokered capacity differently. A generic "ELD OK" checkbox will not match a dedicated fleet on one provider, a brokerage that touches fifty identifiers a week, or a hybrid that must freeze cover when either side fails a registry check. Soft customization of statuses, permissions, and document rules is how that uniqueness becomes enforceable.
Useful encodings include:
Equipment and driver ELD fields for name, model, identifier, registry status (registered, grace, revoked, unknown), and grace-end date.
Dispatch and cover holds that block tender or load assignment when status is revoked past the OOS date, or when status is unknown for high-risk lanes.
Roadside document packets that assemble current RODS method (ELD, paper, logging software), the identifier screenshot or extract, and the carrier's replacement attestation.
Alerts when registry inputs change so a new FMCSA revoke bulletin or an identifier mismatch on check-call updates status without waiting for a weekly audit.
Permissioned override for safety or compliance leaders only, with a required reason code, so sales pressure cannot clear an OOS-eligible truck.
When those rules match how your shop sells service and pays capacity, revoked-ELD risk becomes a controlled exception instead of a Friday afternoon scramble.
What to do this week
Export every ELD identifier on active power units and leased drivers. Match against the Registered and Revoked lists today, with special attention to MRS255, HRS169, HIG385, TRS263, and SPARK6.
Any unit still on an August 6 revoked device after October 6 is an immediate swap or park decision, not a vendor-ticket wait.
Publish a one-page mid-move OOS cover SOP for brokerage and asset desks (customer call, replacement capacity, cost ownership).
Add ELD identifier and registry status to carrier onboarding and to the pre-dispatch check for owner-operators.
Put FMCSA ELD news subscription and a recurring registry audit on the compliance calendar through year-end.
Align billing and claims on evidence required when a revoke-driven OOS creates layover or service failure charges.
The grace period for the August 6 five is over. The next bulletin will bring another 60-day clock. The operators who stay moving will treat ELD registry status like authority and insurance: a living control, checked before the truck takes the load.