If you run a trucking fleet, the question “Are we exempt from ELDs?” usually comes up at the worst time.
A new customer asks for proof of compliance. A driver gets pulled into a roadside inspection. You add a rental truck for a week. Or you hire an owner-operator who’s been on paper logs for years. Suddenly you’re trying to interpret exemptions in real time—while loads still have to move.
This guide is written to remove the guesswork.
You’ll get a clear breakdown of the most common FMCSA ELD exemptions, what “exempt” really means, what records you need instead, and what typically triggers an ELD requirement. The goal is simple: keep your operation compliant without creating extra paperwork.
An ELD exemption does not mean “exempt from Hours of Service.”
It also doesn’t mean you can operate with no records at all. It means your operation falls under a category where you can use something other than an ELD—such as time records (timecards) or paper Records of Duty Status (RODS)—depending on the exemption.
Here’s the clean way to think about it:
The confusion usually happens when fleets mix operations. A driver may be short-haul most days but occasionally runs outside that exception. That’s where “counting days,” recordkeeping, and compliance triggers matter.
Most fleets run into four exemptions far more than any others:
Let’s break each one down in plain language.
This is the exemption people mean when they say “local drivers don’t need ELDs.”
In general, a driver can qualify for the short-haul exception when they operate within a defined radius of their normal work reporting location, return as required, and stay within the applicable duty-time limits.
A common baseline for many fleets is:
Short-haul drivers who qualify typically use time records instead of RODS. That’s a big deal because it changes what your back office needs to manage.
Short-haul operations usually rely on time records that show things like:
This isn’t “no records.” It’s just a different record type than a full logbook.
Short-haul exemptions often get lost because of a few common realities:
If you’re running local plus occasional longer runs, this is where fleets need a simple process: know when you’re in short-haul, and know what happens when you’re not.
This is one of the most important exemptions for real-world operations because it covers a common scenario:
A driver normally qualifies for short-haul (and uses time records), but occasionally has days where they must keep RODS.
The 8/30 rule is generally understood as:
If a driver is required to keep RODS for no more than 8 days within any 30-day period, they may qualify to use paper logs instead of an ELD on those RODS-required days.
This is where fleets get tripped up.
If you don’t track it carefully, a driver can unintentionally exceed the threshold. That usually happens when:
The safest operational approach is to treat the 8/30 rule like a limit you manage actively. If you’re close to the line, you want to know before you cross it.
If a driver no longer qualifies for the infrequent RODS exception, they may need to use an ELD on days they are required to keep RODS (unless another exemption applies).
That’s why mixed fleets often choose a consistent approach—either strict day tracking or standardizing ELD usage to avoid surprises.
This exemption is simple to say and easy to mess up in practice.
The general rule is based on the engine model year, not the truck’s title year. Vehicles with engines manufactured before model year 2000 are commonly treated as exempt from the ELD mandate.
You can have a truck that looks “older” but has a newer engine. Or a truck that’s titled in a certain year but the engine was swapped.
If a newer engine (model year 2000 or later) is installed, the exemption typically no longer applies.
If you operate under a pre-2000 engine exemption, it’s smart to have documentation that supports the engine model year. The goal is simple: don’t leave a roadside conversation to guesswork.
Driveaway-towaway exemptions come up in specific industries, and they matter because they’re frequently misunderstood.
This exemption generally applies when:
In plain terms, it’s designed for situations where the “shipment” is the vehicle itself.
The most common issue is trying to apply driveaway-towaway logic to operations that don’t truly qualify—usually because the driver is towing or delivering something that is not the vehicle commodity in the intended sense.
If your business model relies on this exemption, it’s worth documenting your qualification criteria clearly so drivers and dispatch are aligned.
Agriculture is not a blanket “no ELD” category.
There are limited agricultural-related exceptions that can affect whether a driver is required to keep RODS during certain operations—often tied to seasonal definitions, location/radius concepts, and specific commodity movement.
The safest way to frame it operationally is:
If you haul agricultural commodities and want to rely on an ag-related exception, your compliance process should be clear, written down, and consistently applied.
The risk is assuming the exception applies “all day” or “for the whole trip” when it may not.
Being exempt doesn’t eliminate recordkeeping. It changes what recordkeeping looks like.
Most fleets end up in one of these buckets:
The mistake fleets make is blending these without a clear rule. Decide what applies on which days, and train to that.
If you want fewer problems at roadside, the best approach is to keep it simple and consistent. Depending on the exemption, that may include:
You’re not trying to build a binder. You’re trying to avoid uncertainty when an officer asks, “How are you tracking your hours?”
Most ELD problems don’t come from “not knowing the rule.” They come from normal operations that drift outside the rule.
Here are the common trigger events fleets should watch:
Dispatch expands the route, a stop gets added, or the day runs long. The driver is now outside the short-haul exception, and the fleet didn’t capture the change cleanly.
This is the classic slow creep. A day here, a day there, and suddenly you’re over the threshold. Without a tracking system, it’s easy to miss.
If your fleet owns older trucks, engine work can change whether the pre-2000 exemption applies. This is easy to overlook if it’s not part of your maintenance and compliance handoff.
If drivers are told “this is driveaway-towaway,” but the operation doesn’t truly fit the definition, it can create compliance exposure fast.
The fix is always the same: clear criteria, simple documentation, and a workflow that doesn’t depend on memory.
A malfunction is different from an exemption.
If a driver is required to use an ELD and the ELD can’t accurately record or display required information, the driver must follow malfunction procedures, which commonly include:
The key point: “It broke” is not a free pass. Fleets need a clean malfunction process so the driver can keep moving legally without creating bigger problems later.
Some fleets choose to use ELDs even when they qualify for an exemption. That’s not wrong. In many cases, it reduces admin stress.
Here’s why fleets often go voluntary:
Short-haul mixed operations are hard to manage perfectly. The 8/30 tracking can be a headache. Paper logs can be inconsistent. And compliance teams often end up chasing records at the worst time.
A consistent ELD workflow can reduce:
For many small-to-mid fleets, the win is consistency. One system. One process. Fewer surprises.
BIT is built for fleets that want compliance and visibility without complexity.
If your fleet is fully exempt every day, you may not need an ELD right now. But most fleets aren’t that clean. They run mixed operations, add rentals, cover longer routes occasionally, or rotate drivers across trucks.
That’s where a simple, driver-friendly ELD matters.
BIT ELD is designed to keep HOS workflows straightforward:
And because BIT is focused on practical fleet operations, it’s built to reduce “compliance admin” time, not add to it.
If you’re trying to standardize processes across a mixed fleet—or you’re tired of tracking exemptions manually—using one consistent ELD workflow can simplify your week fast.
The most common ELD exemptions include the short-haul exception (often tied to a 150 air-mile radius), infrequent RODS use (8 days in any 30), pre-2000 engine operations, and certain driveaway-towaway operations. Some limited agricultural exceptions may also affect logging requirements in specific circumstances.
Not necessarily. If you meet the short-haul requirements on a given day, you may use time records instead of RODS and may not be required to use an ELD. If you operate outside the short-haul requirements on a day, you may be required to keep RODS for that day.
If a driver is required to keep RODS no more than 8 days in any 30-day period, they may qualify to use paper logs instead of an ELD on those RODS-required days. The key is tracking those RODS days carefully so the driver doesn’t exceed the threshold.
It’s generally based on the engine model year, not the truck’s title year. If a newer engine is installed, the exemption may no longer apply. It’s smart to keep documentation that supports the engine model year.
Driveaway-towaway typically applies when the vehicle being driven is the commodity being delivered (for sale, lease, repair, etc.) or the operation meets the defined driveaway-towaway criteria. If your situation is borderline, don’t assume—set internal criteria and document it.
No. Owner-operators follow the same ELD exemption rules as carriers and fleet drivers. The exemptions depend on the operation and the vehicle, not whether the driver is an owner-operator.
Most exemptions don’t require a special FMCSA-issued “exemption form.” What you do need is proof you meet the exemption criteria and the correct records for the day (time records or paper RODS). Many fleets use internal checklists or declarations to keep things consistent.
Follow malfunction procedures immediately. Notify the carrier, use paper logs if the device can’t accurately record or display required information, and get the device repaired or replaced within the required window. Keep supporting documentation so you can show compliance during an inspection.