If you're running a fleet of 5–30 trucks and you're still treating ELD compliance as something your drivers handle on their own, you're carrying risk you probably haven't priced yet. The mandate passed years ago. The enforcement infrastructure is mature. The violations are predictable — which means they're avoidable.
Most small carriers running manual dispatch operations have a gap between what their ELD says and what their dispatch records show. That's the compliance exposure. That's what auditors and roadside inspectors find. That's what generates the CSA points that push your score into alert territory.
This post covers exactly where the gaps are, what they cost, and how a dispatch system that keeps load records and HOS data in the same place changes the exposure profile entirely.
What the ELD Mandate Actually Requires
The ELD mandate — FMCSA's electronic logging device requirement — went into full enforcement on December 16, 2019. It requires motor carriers operating commercial motor vehicles listed under 49 CFR 395.2 to use FMCSA-registered electronic logging devices to track hours of service. The rule covers most commercial trucks with a gross vehicle weight rating of 10,001 pounds or more.
There are exemptions, and small carriers frequently misunderstand them.
Pre-2000 model year vehicles
CMV model year 2000 or earlier are exempt from the ELD mandate. These vehicles were built before the technology existed, and FMCSA acknowledged that retrofitting them with compliant ELD hardware isn't always practical. If your fleet runs older equipment, this exemption may apply — but it only covers the vehicle, not the driver. The driver's HOS records still need to be maintained.
Driveaway-towaway operations
When a truck is being driven as part of a delivery of another vehicle — essentially, moving a CMV from one location to another as cargo — specific ELD exemptions apply. These are narrow and specific to the configuration of the tow. If your operation involves these scenarios, verify the exact conditions with your safety consultant before assuming the exemption applies broadly.
Short-haul drivers using paper logs
Drivers who qualify for the short-haul exception — operating within a 150 air-mile radius, returning to the same reporting location, and not exceeding 12 hours on duty — can use paper logs instead of an ELD. This is the exemption most frequently misapplied. The 150 air-mile radius is measured from the dispatch point, not the driver's home. Many owner-operators who think they're short-haul don't actually meet the air-mile requirement. If you're using the short-haul exception, the qualifications need to be met every day — not most days.
If none of those exemptions apply to your operation, you're required to use an FMCSA-registered ELD. Registered devices are listed in the FMCSA registry — using an unregistered device doesn't satisfy the requirement even if it tracks hours accurately.
What "compliant" actually means: Running a registered ELD is the floor, not the ceiling. The device has to be properly mounted and accessible to inspectors, connected to the vehicle's engine to auto-record engine status, and used by drivers to record their duty status. A registered ELD that sits in the cab without being actively used isn't compliant.
The 3 HOS Violations Small Carriers Get Cited For Most
FMCSA roadside inspection data and audit records show a consistent pattern for small carrier violations. The same three appear over and over — and they're not exotic compliance failures. They're the direct result of dispatch and driver coordination gaps that exist in any operation running on disconnected tools.
False log entries — editing recorded data
Drivers edit ELD logs to reflect what they should have done rather than what they did. The most common form: a driver who exceeded their 11-hour driving limit but needed to finish a load, so they edited the log to show "on duty not driving" during the time they were actually driving. FMCSA treats editing that obscures the actual duty status as a false log — a serious violation that carries a fine of $1,000–$11,000 per occurrence, depending on the carrier's history and the severity of the falsification.
The driver is the one who enters the edit, but the reason the edit happens is a dispatch problem. When a load assignment runs past the point where the driver has enough hours to complete it legally, and there's no system that caught this before dispatch, the driver faces a choice: fail the delivery or edit the log. Most drivers who edit logs are trying to serve a dispatch decision that didn't account for their available hours.
Missing or incomplete logs — no duty status recorded
Drivers who forget to log, or who are intermittently doing work-related tasks (unloading, waiting at a shipper, fueling) without switching their duty status in the ELD accumulate gaps that appear as violations during inspection. This is the most common citation for small carriers — and it's entirely an operational problem. A driver who's been at a receiver's dock for three hours and hasn't switched from "driving" to "on duty not driving" has an incomplete log. The ELD shows the gap. The inspector sees the gap.
With a proper dispatch system, the driver receives an alert when they've been stationary for a set period — and the system prompts them to update their status. Without that, it's left to the driver's judgment, and the inspection records show the results of that judgment.
Drivers operating past 14-hour window
The 14-hour on-duty limitation — no driver may drive more than 11 hours after 8 consecutive hours off duty — is one of the most frequently exceeded limits in small carrier operations. The reason isn't usually that drivers are ignoring the clock. It's that dispatch is assigning loads that require more hours than the driver has available from their start time.
A driver starts at 6 AM. They have until 8 PM to drive — 14 hours from start. A dispatch system assigning a 700-mile load that takes 11.5 hours of drive time has to account for the loading time, any stops, and the 30-minute break requirement. If those factors push the operation beyond the driver's available window, the system needs to catch it before the load is assigned — not after the driver is already committed. A dispatcher managing this manually has to manually calculate every leg, factor in break time, and track window expiration against every assignment. That's the gap.
What Happens When ELD Data Doesn't Match Your Dispatch Records
Every roadside inspection generates an inspection report. Every inspection report goes into FMCSA's Motor Carrier Management Information System. CSA scores are calculated from this data. A carrier with an inspection that shows an HOS violation generates CSA points in the Hours of Service BASIC — and that happens even if the underlying issue was a dispatch problem, not a driver problem.
The ELD has a record. Your dispatch system has a record. If they don't match, the auditor — or the inspector at the scale house — will ask which one is accurate. In most cases, both records will show gaps and inconsistencies. The ELD log shows the driver's actual movement. The dispatch records show the assigned tasks. When those two datasets disagree in a way that makes it look like the driver was working off-duty or operating in excess of their limits, the carrier absorbs the violation.
The FMCSA audit exposure from ELD/dispatch mismatch: During a compliance investigation, auditors compare ELD logs against load assignments, delivery receipts, and dispatch records. When a carrier can't produce dispatch records that align with their ELD logs, the audit presumption is that the dispatch record is incomplete — and the burden of proof for compliance is on the carrier. Incomplete records = audit failure. A carrier with 12 drivers running 3–5 loads per week has 36–60 opportunities per week for their ELD data and dispatch data to be out of alignment. Over 12 months, that's over 1,800 potential mismatch points.
Carriers with integrated dispatch systems don't have this problem the same way — when load assignments and driver HOS are in the same system, the assignment can't be created in a way that exceeds the driver's available hours. The mismatch doesn't accumulate because the system prevents it at the assignment stage rather than catching it during inspection.
How Dispatch Software Reduces HOS Violations
The mechanism is simple: instead of the dispatcher manually tracking driver hours against load requirements, the system does it continuously. When a load is being built, the system checks the assigned driver's current HOS status, calculates whether the load can be completed within the driver's available window, and flags conflicts before the assignment is confirmed.
This changes driver behavior in ways that are difficult to engineer without the system. When a driver knows that their dispatch system knows their available hours, the incentive to edit logs goes down — they won't get assigned a load they can't legally complete. When a driver is sitting at a dock and the system tracks their stationary time, the log status gets updated automatically rather than requiring the driver to remember to do it manually.
HaulPilot's dispatch system keeps load assignments and driver HOS status in a single record. When a driver is assigned a load, the system checks their available hours against the route requirement before confirming the assignment. Drivers can see their remaining window in the app, and dispatch gets automatic alerts when a driver's hours are approaching the point where they need to stop.
That single integration — dispatch planning that accounts for HOS — is what eliminates the three most common violations. It's not additional compliance overhead. It's building the constraint into the operational workflow so that the violation can't occur in the first place.
The Real Cost of ELD Violations: Fines, CSA, and Insurance
The direct fine for an HOS violation at roadside runs $1,000–$11,000 depending on severity and carrier history. FMCSA civil penalties for pattern-or-practice violations — where an investigation concludes the carrier has a systemic issue — can reach $15,000–$25,000 per violation. But the fine is the smallest part of the total cost.
| Cost Category | Typical Impact | Recovery Timeline |
|---|---|---|
| Roadside HOS fine | $1,000–$11,000 per violation | One-time, per event |
| FMCSA civil penalty | $15,000–$25,000 per violation | One-time, per investigation |
| CSA HOS BASIC points | +15–30 points per violation | 27-month window |
| Broker disqualification | Lost loads, access restrictions | Until score improves |
| Insurance premium increase | 15–30% on annual premium | Until next renewal cycle |
| Out-of-service order | Full operational halt | Until deficiency corrected |
Let's put real numbers to it. A 10-truck carrier paying $100,000 per year in commercial trucking insurance gets hit with an HOS violation that triggers a 20% premium increase at the next renewal. That's $20,000 per year in additional premium — every year, until the CSA score drops below the alert threshold. The violation fine might be $5,000. The insurance increase is $20,000 annually. Three years of that increase costs $60,000 — all from a single roadside stop.
Brokers are also checking CSA scores before tendering loads. A carrier with elevated HOS BASIC scores starts getting declined or routed to lower-rate loads because the broker's risk assessment factors in the carrier's safety profile. That's revenue loss that doesn't show up as a line item in the accounting — it's just fewer loads at the rate you need to run.
The HOS BASIC alert threshold is 65% of the intervention threshold. At that point, FMCSA flags you for potential investigation. A carrier with CSA scores approaching that threshold isn't "probably fine" — they're building toward a compliance review. The time to address the underlying HOS compliance gap isn't after the inspection that pushes the score past the threshold. It's now, while the score is still manageable and the record is still clean.
Related: if you've never been through a DOT audit, the audit readiness post covers exactly what FMCSA investigators check and where small carriers fail. The HOS records are one of the first things they pull.
The Compliance Gap Is an Operational Problem, Not a Driver Problem
Carriers who treat ELD compliance as a driver training issue keep solving the same problem in the wrong place. Drivers edit logs because the assignment was impossible to complete within legal hours. Drivers have gaps in their logs because the system they're running doesn't prompt them to update their status when they've been stationary for 30 minutes. Drivers operate past their 14-hour window because dispatch assigned them a load that required more hours than they had available.
Every one of those problems originates in the dispatch operation. The solution has to be there too — the driver can't solve a dispatch problem by driving better.
The carriers with clean ELD records aren't running different drivers. They're running dispatch that makes compliance the default rather than the exception.
See What Your Dispatch Operation's ELD Exposure Looks Like
We built a free dispatch cost calculator that models compliance overhead alongside operational costs. Most carriers who run it are surprised by how the number shifts when HOS compliance risk is factored in as a recurring cost rather than a one-time event.
Also worth reviewing if you're working through this for the first time: 5 Signs You've Outgrown Spreadsheet Dispatch covers the operational thresholds where manual tracking stops handling the complexity. And the dispatch-to-retention connection explains why drivers who work for carriers with clean operations tend to stay longer.