Compliance
What Is an ELD? A Plain-English Guide for Fleets
Electronic Logging Devices replaced paper logbooks for most commercial drivers. Here's what an ELD does and who needs one.

What an ELD Actually Is
An ELD, or Electronic Logging Device, automatically records a commercial vehicle's engine hours, movement, location, and miles driven, and ties that data to a driver's Hours of Service (HOS) log. It replaced the paper logbook most drivers used to fill out by hand at the end of a shift. The US FMCSA ELD rule and Canada's ELD mandate both require most commercial drivers who keep records of duty status to use one, rather than paper logs or basic electronic logging apps that don't meet the technical standard.
The device itself connects to the vehicle's engine control module, usually through the OBD-II or a 9-pin diagnostic port, so it can confirm the vehicle is actually moving rather than relying on a driver to manually start and stop a timer. That's the core problem ELDs were built to solve: paper logs and some legacy e-log apps were easy to fudge, intentionally or not. An ELD's engine-tied data is much harder to falsify, which is the whole point from a regulator's perspective.
Under the hood, an ELD is tracking a driver's status across four standard duty categories: off duty, sleeper berth, driving, and on-duty not driving. The device only knows what the engine tells it, movement, engine on/off, so a driver still has to manually indicate a status change like going on-duty before actually driving. What the ELD prevents is backdating or quietly editing the driving-time portion of that record after the fact.
Who's Exempt From the ELD Mandate
Not every commercial driver needs one. There are real, documented exemptions: drivers operating under the short-haul exception, those who use paper logs eight days or fewer in any 30-day period, driveaway-towaway drivers, and vehicles older than model year 2000 that don't have the engine control module an ELD needs to read. Claiming an exemption incorrectly at a roadside inspection can turn into an out-of-service order fast, so it's worth confirming your fleet's actual status rather than assuming either way.
The short-haul exception is the one most commonly misunderstood. It applies to drivers who operate within a 150 air-mile radius of their normal work reporting location and return there within 14 hours, and it's a narrow, condition-specific exception, not a general pass for anyone who happens to drive locally most days.
Why It's Usually Not a Standalone Device
For most fleets, the ELD isn't a standalone box. Geotab's GO device handles ELD/HOS logging and GPS tracking, engine diagnostics, and driver behavior scoring on the same hardware, reporting into the same MyGeotab dashboard. That matters practically: one device to install, one login for dispatch and safety to check, and compliance data that lives next to the tracking and safety data your team already looks at daily instead of in a separate app nobody remembers to open.
If you're evaluating ELD options, the practical questions are less about the log screen and more about what's underneath it: is the device on the FMCSA registered list, does it also give you GPS tracking and diagnostics so you're not paying for and installing two systems, and does the vendor actually support you if a driver gets flagged at a scale house. That last part matters more than most buyers expect until the day it happens.
There's also a straightforward procurement argument for buying combined hardware instead of a compliance-only ELD. Two separate devices means two installs, two logins, and two vendor relationships to manage if either one has a problem. A single device handling both jobs is one less thing that can go wrong, and one less bill to reconcile every month.
What Happens If You Don't Comply
The consequences of skipping or mishandling ELD compliance aren't limited to a single ticket. A driver caught without a compliant, properly used ELD during a roadside inspection can be placed out of service on the spot, and the violation typically factors into the carrier's CSA (Compliance, Safety, Accountability) score, which insurers, brokers, and some shippers do check when deciding who to work with.
This is why ELD compliance tends to get treated as a baseline operational requirement rather than a box to check once and forget. A fleet that's consistently compliant isn't just avoiding fines, it's protecting its safety score and, by extension, its insurance costs and its standing with the brokers and customers who look at that record before doing business.
Frequently asked questions
Is an ELD the same thing as a GPS tracker?
They're related but distinct: an ELD specifically logs Hours of Service and engine data for compliance, while GPS tracking is about location and trip history. Platforms like Geotab's GO device do both jobs on one piece of hardware, which is why most fleets end up treating them as a single system.
What happens if my ELD isn't on the FMCSA registered list?
Using a device that isn't FMCSA-registered is treated the same as not having an ELD at all during a roadside inspection, which can result in violations and an out-of-service order. Always confirm a device is on the current registered list before deploying it fleet-wide.
Do owner-operators need an ELD?
In most cases, yes, if they're required to keep records of duty status. The main exceptions are the documented FMCSA exemptions: the short-haul exception, drivers using paper logs 8 days or fewer in 30, driveaway-towaway operations, and pre-2000 model year vehicles.
Does an ELD violation affect a carrier's safety score?
Yes. ELD-related violations found during a roadside inspection typically factor into a carrier's CSA score, which insurers, brokers, and some shippers reference when deciding whether to do business with a carrier.
Related solutions & products
Get a free quote
What are you looking for?