← Back to Blog
Trucking News

Trucking News: September 19, 2026 — What Carriers Need to Know

Trucking News: September 19, 2026 — What Carriers Need to Know

September 19, 2026 — Fuel costs, CDL policy, driver-hours flexibility, and carrier liability are all moving at once. None of these developments provides an immediate fix for small fleets, but each could affect operating costs, recruiting, compliance, or cash flow in the weeks ahead.

High diesel prices continue to squeeze trucking margins

Trucking groups say there is no meaningful relief in sight for elevated diesel prices. That remains one of the most direct threats to carrier profitability because fuel is paid for immediately, while freight rates and shipper contracts may not adjust quickly enough to cover the increase.

For owner-operators, the impact depends heavily on deadhead, truck efficiency, and whether a fuel surcharge is actually tied to a reliable pricing index. Small carriers should review every customer’s surcharge formula instead of assuming the pass-through fully covers the cost. Route planning, fuel-card controls, and accurate trip costing are increasingly important. A transportation management system such as VAU0’s TMS tools can help compare fuel-heavy routes and identify loads that look profitable before fuel but lose money after the truck rolls.

High fuel prices make every planning mistake more expensive. The carriers with the clearest cost data will have the best chance of protecting margin when rates remain tight.

Congressional legislation would recognize trucker appreciation week

Legislation discussed by Congresswoman Harriet Hageman has drawn attention from trucking interests as lawmakers consider formally recognizing a trucker appreciation week. The proposal is primarily symbolic, but recognition matters to an industry that continues to struggle with driver retention, long hours, time away from home, and public misunderstanding of the work required to keep freight moving.

For small carriers, the practical value will depend on how they use the occasion. A formal appreciation week will not solve compensation or parking shortages, but it can support recruiting and retention when paired with specific actions: safety bonuses, better communication, predictable home time, or recognition for clean inspections and safe miles. Carrier owners should avoid treating appreciation as a one-day message while leaving operational problems unresolved. Drivers generally notice whether management follows through far more than whether it posts a slogan.

Super Ego CEO narrows claims in driver-led class action

Land Line Media reports that the CEO of Super Ego has withdrawn or narrowed some claims in a class-action lawsuit brought by drivers. The development does not end the case, and it does not determine the final outcome, but it may reduce the issues being litigated and clarify which allegations remain active.

Independent contractors and small fleets should treat this as a reminder to examine lease, pay, deduction, and settlement practices. Disputes often grow from unclear language, inconsistent deductions, fuel-charge treatment, escrow handling, or confusion over who controls the work relationship. Carriers should preserve contracts, settlement statements, messages, and policy acknowledgments in an organized system. A technology platform such as VAU0 can help keep operational and payment records together, but software does not replace a careful legal review. Companies facing a claim should consult qualified counsel rather than assuming a procedural change resolves the underlying exposure.

FMCSA non-domiciled CDL rule faces court challenge

A federal court challenge is putting pressure on the Federal Motor Carrier Safety Administration’s restrictions involving non-domiciled commercial driver’s licenses. The issue is significant because the rule affects who may qualify for or continue using a CDL when the license is issued to a driver who is not domiciled in the issuing state.

The legal fight creates uncertainty for carriers that employ affected drivers or rely on their availability for dispatch. A court challenge can change the timing or enforcement environment, but it should not be treated as automatic permission to ignore current requirements. Carriers need to verify each driver’s license status, supporting documents, medical qualification, and state records through established compliance procedures. Keep an audit trail showing when records were checked and what information was used. The VAU0 compliance resources can support a broader document-control process, but carriers should confirm the latest rule and court orders with official sources and legal advisers.

FMCSA tests a pause option for the 14-hour clock

FMCSA is testing a concept that would give truck drivers the ability to pause the 14-hour on-duty window under certain circumstances. The proposal addresses a long-standing complaint: a driver’s available workday can be consumed by shipper delays, receiver congestion, breakdowns, or other waiting time even when the driver is not meaningfully working.

This is a test, not a nationwide change to the hours-of-service rules. Drivers and dispatchers should not begin using a pause procedure unless and until it is authorized and the requirements are clearly defined. If the concept advances, documentation will be critical. Carriers will need consistent guidance on qualifying pauses, status changes, supporting records, and what happens when a driver resumes work. Dispatchers should also avoid building schedules around unapproved flexibility. The safest preparation is to track detention and delay data now, so the company can determine whether a future pause option would improve utilization without creating new compliance risk.

What carriers should do this week

  • Recalculate fuel cost per mile by truck and lane, including deadhead, and verify that fuel surcharges reflect actual exposure.
  • Review driver agreements, deductions, settlements, and lease records for unclear language or inconsistent treatment.
  • Audit CDL, medical-certification, and qualification files for any driver affected by non-domiciled licensing changes.
  • Continue following the current hours-of-service rules while tracking detention and delay events that could support future operational changes.
  • Use driver appreciation efforts to address concrete issues such as communication, home time, equipment condition, and timely pay.
← Back to Blog For Carriers →
Why We Built ESSE Instead of Buying Another TMS | ESSE Blog
Our Story

Why we built ESSE instead of buying another TMS

In 2022, we were running a small fleet and spending approximately $400 per truck per month on software. TMS license, ELD subscription, e-sign service, separate accounting integration. Four different logins. Four different monthly invoices. Four different support teams to call when something didn't work.

None of it talked to each other without manual data entry.

The software evaluation that changed everything

We spent three months evaluating every major TMS and fleet management system on the market. AscendTMS, McLeod, Motive, EZLogz, KeepTruckin, TruckingOffice, Axon. We signed up for demos, trials, and in two cases, paid for actual subscriptions to test them properly.

What we found was consistent across almost all of them: the software was built by people who had never dispatched a truck. You could tell immediately. The terminology was slightly wrong. The workflows assumed steps that no real dispatcher would take. The ELD and TMS were always separate systems that "integrated" — meaning they sometimes shared data, if you configured things correctly, and the configuration broke whenever either vendor pushed an update.

"The best way to evaluate trucking software is to use it under real pressure. Not in a demo. Not in a test environment. On a real load, with a real deadline, when a broker is calling every 30 minutes for an update."

The specific things that were broken

Without naming specific vendors: one major TMS required five screen transitions to update a load status. Not five clicks — five full page navigations. On a mobile browser from a truck stop, that meant 45 seconds to tell a broker the truck was loaded. Another system had beautiful analytics dashboards but couldn't tell you, in real time, how many hours of drive time your driver had remaining without navigating to a separate compliance module.

The ELD market was worse. Most ELD systems were designed to satisfy FMCSA's technical requirements — which they did — while making the user experience as painful as possible. Drivers hated them. When drivers hate their tools, they find workarounds. Workarounds create compliance risk.

The moment we decided to build

The decision was made on a Tuesday afternoon when our dispatcher spent 40 minutes re-entering data from a rate confirmation PDF that our ELD had already captured in a different system. The information existed. It was digital. It lived in three different places that didn't talk to each other, and a human was manually transferring it between systems.

That's not a technology problem. That's a lack of ambition problem. Nobody had decided to solve it because the existing systems were profitable enough without solving it.

What we decided to build instead

One platform. ELD and TMS as the same system, not integrations. AI that reads rate confirmation PDFs so dispatchers don't have to. A dispatcher — eventually an AI dispatcher — that covers nights and weekends so loads don't get missed. E-sign built in, not bolted on.

And priced at zero through 2026, because the goal was to prove the product worked before asking carriers to pay for it.

Two years in: did it work?

The Rate Con AI has a 95%+ accuracy rate on standard broker formats. ERETH ELD passed FMCSA's technical certification. Our AI dispatchers book real loads for real carriers after hours. The carrier dashboard still occasionally has a minor bug — we fix them the same day they're reported.

Would we have been better off just using an existing system and focusing on freight? Financially, in the short term, probably yes. But we would have kept paying $400 per truck per month for software that we knew was mediocre. And we would have missed the opportunity to build something that actually works the way the industry needs it to work.

We don't regret it.

← Back to Blog Next: Our first AI broker call →