← Back to Blog
Trucking News

Trucking News: August 12, 2026 — What Carriers Need to Know

Trucking News: August 12, 2026 — What Carriers Need to Know

GUEST - Truckers News Highlights

Today's truckers are navigating a rapidly changing landscape, and staying informed is key. This update will get you up to speed with the latest developments across the trucking industry. Understanding these changes helps you stay compliant and competitive. Let's dive into the news that matters most to you.

Canadian Provinces Remove Unsafe Trucking Companies

In a bold move to improve road safety, a Canadian province has taken decisive action by removing 20 unsafe trucking companies from its highways. This crackdown aims to eliminate risks posed by non-compliant carriers that could jeopardize both public safety and the industry's reputation. For smaller operators and independents, this serves as a critical reminder of the importance of maintaining rigorous safety standards.

Carriers operating in and around Canada should remain vigilant and ensure all operations meet or exceed safety regulations. While this measure primarily affects Canadian roads, it underscores a broader trend where non-compliance is increasingly intolerable. Staying compliant is not only a legal necessity but a strategic advantage. For guidance on maintaining compliance, you can check out our resources on the VAU0 compliance page.

Trucking Industry Fears NYC Delivery Protection Act

The proposed Delivery Protection Act in New York City could significantly impact the logistics landscape by hiking costs and constricting the supply chain. Industry advocates warn that implementing such legislation could burden carriers with additional expenses that might not translate into better service or protections. For small and independent carriers already operating on thin margins, this poses a substantial concern.

The act's intent to curb delivery-related issues might seem beneficial at a glance, but it underscores the need for balanced regulations that protect interests without stifling operations. Understanding potential legal changes and planning for their impacts is crucial. Stay tuned for updates on this legislation, as being proactive will keep you ahead.

FMCSA Codifies English Language Requirements

The FMCSA is moving forward with codifying English language proficiency requirements for commercial drivers. This regulation aims to improve communication on the road, enhancing safety both for drivers and other road users. While existing guidelines require basic proficiency, this formalization could mean more rigorous testing and assessments.

For carriers, especially those managing a diverse workforce, this development highlights the need to ensure all staff are adequately prepared for compliance with language requirements. Implementing language training programs could be an important step towards maintaining compliance and avoiding penalties. VAU0 provides helpful tips on staying compliant with hardware and software at our TMS page.

FMCSA Cracks Down on Non-Compliant ELDs

The FMCSA is following through on its promise to crack down on non-compliant Electronic Logging Devices (ELDs). This action seeks to rectify the ongoing issues with ELD reliability that can affect both safety and administrative efforts within trucking companies. Non-compliance with ELD regulations may result in severe fines and operational limitations.

Small carriers must ensure that their technology is up to date and compliant with the latest federal requirements. Running frequent checks and audits on your ELD systems can prevent unnecessary violations and fines. Ensuring a seamless transition to compliant devices will also enhance operational efficiency and safety.

The removal of unsafe trucking companies in Canada is a loud message: safety and compliance are non-negotiable in today's trucking environment. Every carrier, regardless of size, should take heed and prioritize stringent adherence to safety standards.

What Carriers Should Do This Week

  • Review your compliance with all safety standards to avoid potential violations.
  • Keep abreast of legislative changes, like NYC's delivery protection act, and prepare to adjust your operations strategy accordingly.
  • Ensure your ELDs and software systems are up to date to avoid penalties from FMCSA crackdowns.
  • Consider implementing or enhancing English language proficiency training for all drivers.
  • Visit the VAU0 compliance page for detailed guides and resources.
← 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 →