ELD Compliance Across a Small Fleet: Mandate Rules, Exemptions, and Fines

ELD compliance for a fleet isn't just multiplication — it's a management problem with different failure modes than a single-truck operation.

A solo owner-operator with one ELD has one device to monitor, one set of logs to review, and one driver whose understanding of the rules they can verify directly. When something goes wrong, they know immediately because they're in the truck.

A fleet owner with five trucks has five devices that could be revoked, five drivers with different route profiles that may qualify for different exemptions, five ELD log streams to review, and five points of failure at any roadside inspection. A device revocation that goes unnoticed for 60 days isn't a single problem — it's five potential out-of-service orders every time one of those trucks rolls through a weigh station with the wrong device.

The rules are the same. The compliance challenge is categorically different. This guide covers what fleet managers are responsible for, how to track exemptions across mixed vehicle and driver profiles, what device revocations mean for a fleet, what violations cost at scale, and what a real fleet ELD program looks like.

Who the ELD Mandate Applies To — Per Vehicle, Not Per Fleet

The ELD mandate requires electronic logging devices on commercial motor vehicles where the driver is required to maintain Records of Duty Status (RODS) under FMCSA hours-of-service regulations. The key word is "required" — because the trigger for ELD compliance is the RODS obligation, not simply the presence of a CMV.

Vehicles subject to the mandate: Any CMV with a gross vehicle weight rating (GVWR) or gross combination weight rating (GCWR) over 26,000 pounds, or any CMV with three or more axles regardless of weight, that operates in interstate commerce and is driven by a driver required to keep RODS.

The fleet-level complication: Not every vehicle in your fleet may have the same ELD requirement. A mixed fleet running a combination of CDL tractors and sub-26,000-pound box trucks has different compliance requirements per vehicle. A fleet where some drivers qualify for the short-haul exception and others don't has different logging requirements per driver, per day. Managing ELD compliance at the fleet level means knowing the requirement for each vehicle-driver combination, not applying a blanket rule across everything.

The Exemptions a Fleet Manager Must Track

Exemptions are per vehicle, per driver, and per trip — not fleet-wide. The most common exemptions and the compliance tracking they require:

Short-Haul Exception (150 Air-Mile Radius)

Drivers who operate within a 150 air-mile radius of their normal work reporting location, return to that location at the end of each shift, and drive no more than 11 hours are exempt from the ELD requirement and from keeping RODS entirely. They may keep paper timecards instead of driver logs.

Fleet tracking requirement: The exception is lost on any day the driver exceeds the radius. If a driver typically qualifies under the short-haul exception but occasionally runs a load that takes them beyond 150 air miles, they need ELD coverage for that day — and paper timecards won't satisfy the requirement. For fleet managers, this means knowing which drivers are operating in short-haul mode and having a protocol in place to ensure ELD-required days are covered when routes change.

A common fleet mistake: short-haul drivers who share vehicles with long-haul drivers. The vehicle may or may not have an ELD, and the driver may or may not need it, depending on the day's operation. Having clarity on the relationship between vehicle and driver assignment matters for exemption management.

Pre-2000 Engine Model Year Exemption

Vehicles with engines manufactured before model year 2000 lack the standardized engine diagnostic ports (OBD-II and SAE J1939) that ELDs require for mandatory engine synchronization. The exemption applies to the engine model year, not the vehicle title year or registration year.

Fleet tracking requirement: The relevant date is the engine's model year — not the chassis year, not the registration year, not the title year. A 1999 truck with an engine replacement using a 2002 or later engine is no longer exempt. Track engine model year separately from vehicle model year in your fleet records. If you've had engine replacements on older units, the exemption status may have changed and may be applied incorrectly.

Glider kit clarification: A glider kit (new cab and chassis paired with a pre-2000 engine) retains the ELD exemption based on the engine model year. The physical age of the cab is irrelevant.

Driveaway-Towaway Operations

When the vehicle being operated is itself the commodity being transported — a new truck delivered from a manufacturer to a dealership, a vehicle being repositioned between facilities — the operation may qualify for the driveaway-towaway exemption. The configurations are driveaway (driving the vehicle to its delivery point), towaway (towing the vehicle as cargo via saddle mount, full mount, or towbar), and transportaway (vehicles on a transport device).

Fleet tracking requirement: Car haulers and auto transport carriers frequently encounter this exemption, but it applies specifically when the vehicle being transported IS the cargo — not when any vehicle is being moved. A car hauler transporting customer vehicles on a trailer is using the trailer to transport freight, not operating in driveaway-towaway mode. The distinction matters and the two operations require different documentation.

8-or-Fewer RODS Days in 30-Day Period

Drivers who keep paper RODS for 8 or fewer days within any rolling 30-day period may use paper logs for those days. This exemption is primarily relevant for carriers whose operations mostly qualify for the short-haul exception but occasionally run beyond the radius.

Fleet tracking requirement: This is a rolling 30-day calculation, not a monthly reset. A driver who used paper RODS on days 1–8 of a 30-day window cannot use paper logs on day 9 even if the calendar month has changed. Fleet managers who apply this exemption need to track it per driver on a rolling basis.

Device Registration: What Fleet Managers Must Monitor

Every ELD in your fleet must be registered on FMCSA's official registered device list at eld.fmcsa.dot.gov/list. FMCSA actively revokes devices when vendors fail to maintain compliance with technical standards, and the revocations happen on an ongoing basis throughout the year.

The 2026 revocation pattern: FMCSA has continued removing devices from the registered list through 2026. Earlier rounds of revocations (GTS ELD, UTRUCKIN, ELD365 ELOG, IRONMAN ELD, FACTOR ELD, various AirELD variants in early 2026) affected carriers across the industry. Additional devices have been removed through the year. The pattern is consistent: FMCSA identifies technical non-compliance, issues a revocation notice, and gives carriers 60 days to replace the device before out-of-service enforcement begins.

The fleet exposure: For a solo operator, a device revocation means one truck at risk. For a 5-truck fleet running the same revoked device across multiple vehicles, every truck is exposed simultaneously. A revocation that goes unnoticed until a roadside inspection can produce five out-of-service orders in a single week.

The monitoring requirement: A device that was on the registered list when you purchased it may not be on it today. Fleet managers should verify that every device in every truck is currently listed — not just listed when originally installed. The check takes minutes on the FMCSA portal and should be on a defined schedule.

What verification looks like at the fleet level: Your ELD vendor and device model need to appear on the registered list. Verify the specific device model, not just the company name — some vendors have registered some models but not others. For a fleet, build this check into a quarterly compliance calendar: pull the list, verify every device model in your fleet against it, document the check.

What ELD Violations Actually Cost a Fleet

Violations hit carriers at three levels: the immediate cost per incident, the CSA score damage that follows, and the downstream insurance and broker access consequences that accumulate.

Per-Incident Costs

No ELD / unregistered device: Immediate 10-hour out-of-service order, civil penalty $1,000–$16,000 per violation depending on severity and whether the violation is classified as egregious.

ELD malfunction without proper documentation: If a driver's ELD malfunctions and they don't follow the required procedure (notification to carrier within 24 hours, revert to paper RODS, FMCSA notification if repair extends beyond 8 days), the malfunction becomes a violation. The malfunction itself isn't a violation if documented correctly — the failure to document is.

ELD tampering or log falsification: Maximum civil penalty of $15,846 per entry for knowing falsification. Criminal penalties possible for egregious patterns.

Inability to transfer logs at inspection: If neither Bluetooth nor email transfer works when an inspector requests logs, the inspector has discretion to issue a violation. CVSA's 2026 inspection focus explicitly included data transfer capability — inspectors are specifically testing whether both transfer methods work.

CSA Score Impact

ELD violations fall under the Hours-of-Service Compliance BASIC, which has an intervention threshold at the 65th percentile. Under the 2026 SMS overhaul, out-of-service ELD violations carry double severity weight (weight of 2 versus 1 for non-OOS violations).

For a fleet, violations accumulate from every driver and every truck under the same DOT number. One truck generating a pattern of ELD violations doesn't stay siloed — it compounds with other trucks' records into a fleet-level percentile. A fleet at the 70th percentile in HOS Compliance triggers FMCSA scrutiny, gets added to priority inspection lists, and faces potentially higher-intensity inspection scrutiny at every weigh station.

The math matters: a fleet that gets 8 inspections per quarter across five trucks with one ELD-related OOS violation per quarter is accumulating four OOS-weight violations per year in the HOS Compliance BASIC. That's a pattern that moves the percentile and keeps it elevated for 24 months at rolling severity weights.

Insurance Consequences

Underwriters pull FMCSA SMS data at every policy renewal. A fleet with elevated HOS Compliance BASIC scores can expect premium increases of 20–40% above a comparable fleet with a clean record in that category. At a $60,000 annual fleet insurance base (5 trucks at $12,000/truck), a 30% increase is $18,000/year in additional premium — every year the scores stay elevated.

The 8-Day Malfunction Procedure — Fleet Version

When an ELD malfunctions in a single-truck operation, the driver manages the procedure personally. In a fleet, malfunction management is a carrier-level responsibility with specific timelines.

The required procedure when an ELD malfunctions:

1. The driver notes the malfunction on the ELD (if still capable of accepting input) or on paper.
2. The driver notifies the carrier's compliance contact in writing within 24 hours.
3. The driver reverts to paper RODS for the remainder of the malfunction period.
4. The carrier must repair, replace, or restore the ELD within 8 days of receiving driver notification.
5. If the 8-day window cannot be met, the carrier must notify the FMCSA Division Administrator within 5 days of the driver's original notification and request an extension. Failure to get an extension and continuing on paper RODS beyond day 8 is a violation.

What this means for fleet operations: Every driver running under your DOT number needs to know the malfunction procedure — not as theoretical knowledge, but as a documented process they can execute at 2 AM on the road without calling the office. That means:

• Written malfunction notification instructions kept in every cab
• Paper RODS forms (blank graph-grid logs) in every cab, sufficient for 8 days
• A defined carrier contact for malfunction notifications with 24-hour availability
• A repair/replacement protocol that can actually turn around a device within 8 days

For a fleet running 5 trucks, having zero spare ELD units means any malfunction forces you against the 8-day repair clock. Most fleet managers running 3+ trucks keep at least one spare registered device on hand. A replacement that can be shipped to a driver's location within 24 hours of notification keeps you well within the 8-day window without relying on expedited repair from a vendor.

Unassigned Driving Time: The Fleet-Level Problem

In a single-truck operation, unassigned driving is usually a simple error — the driver forgot to log in, or logged out and moved the truck a short distance. In a fleet, unassigned driving time is a compliance and audit risk that requires active management.

What generates unassigned driving: The ELD records movement whenever the engine is running and the vehicle is moving above a minimal speed threshold. If no driver is logged in when the vehicle moves, the ELD creates an "unassigned driving" record. This happens most commonly when: drivers forget to log in before moving the truck, a truck moves in a yard or facility and the driver has logged out, a second driver moves the truck without logging in, or the device has a connectivity issue that prevents it from receiving the driver's login.

The carrier's obligation: Carriers must review unassigned driving records and assign them to the correct driver within 13 days. Unassigned driving records that are never resolved accumulate in the ELD system. At a DOT compliance audit, a carrier with consistent patterns of unassigned driving that was never assigned looks like a carrier allowing drivers to run hours off the books.

Fleet-level management: Most fleet management ELD systems (Motive, Samsara, Geotab) surface unassigned driving events in the fleet dashboard with alerts. Build a weekly review of unassigned driving into your compliance calendar — identify the event, contact the driver to confirm the correct assignment, and resolve it in the system. Unresolved events beyond 13 days compound into an audit problem.

Choosing and Managing ELD Systems for a Fleet

Fleet ELD decisions differ from solo operator decisions in several ways. The capabilities that matter most at the fleet level:

Centralized driver management. The fleet dashboard should allow a compliance manager to view all drivers' ELD status, log compliance, and HOS availability from a single interface without logging in as each individual driver. The ability to identify which trucks are approaching HOS limits in real time is dispatch-critical.

Unassigned driving alerts. Automated alerts when a vehicle moves without a logged-in driver allow immediate follow-up rather than discovering the event days later.

ELD malfunction alerts. Fleet-wide notification when any device reports a malfunction — so the 24-hour driver notification clock and the 8-day carrier replacement clock start immediately from corporate awareness, not when the driver gets around to calling.

Multi-device management at the account level. Adding and removing vehicles from the fleet account, managing driver profiles across the system, and verifying device registration status across all fleet units should be manageable from a central account. The administrative overhead of managing ELD accounts per device rather than fleet-wide is significant at scale.

Data transfer capability both ways. Every device in the fleet should reliably support both telematics transfer and Bluetooth/USB transfer. CVSA's 2026 inspection focus on data transfer means inspectors are actively testing both methods. A fleet where two of five trucks have unreliable Bluetooth transfer has a predictable compliance problem at the next inspection.

ELD platforms with strong fleet management capability: Motive (formerly KeepTruckin) and Samsara both have well-developed fleet dashboards, centralized management, and HOS visibility tools. For larger small fleets (5–20 trucks), Geotab offers robust fleet management integration. All three are actively maintained, consistently on the FMCSA registered list, and have fleet-level compliance monitoring built into their core products.

Building the Fleet ELD Compliance Program

ELD compliance at the fleet level isn't a device purchase — it's a program. The components:

Device inventory and registration tracking. Maintain a spreadsheet (or fleet management system record) with every vehicle, the ELD device model and serial number installed in it, the installation date, and the last-verified date that device appeared on the FMCSA registered list. Update the registration verification field quarterly at minimum.

Exemption tracking per driver and vehicle. Document which vehicles are pre-2000 engine exempt (and why — engine model year on file), which drivers operate in short-haul mode and what the trigger is for an ELD day, and any other exemptions in play. When drivers or vehicles change, update the record immediately.

Driver training program. Every driver operating a vehicle in your fleet must know: how to log status correctly on your specific ELD device, how to initiate both data transfer methods (telematics and Bluetooth/USB) before they arrive at a weigh station, the malfunction notification procedure, how to complete paper RODS if the ELD fails, and what to do at a roadside inspection when the officer asks for logs.

Training isn't a one-time onboarding event. New devices, new rule interpretations, inspection focus areas that change annually — driver training should be refreshed at minimum annually and whenever device or rule changes affect your fleet.

Log review process. Someone at the carrier level needs to be reviewing ELD logs — not spot-checking, reviewing. The minimum is daily review of the previous day's logs across all vehicles, looking for: HOS violations or near-violations, unassigned driving events, missing log entries for days trucks were in operation, annotation quality (are drivers annotating correctly when the ELD prompts?), and data transfer test results when applicable.

Malfunction response protocol. Documented, distributed to every driver, tested before you need it. The 8-day window runs fast when a driver is on the road and doesn't know what to do next.

Quarterly compliance calendar. FMCSA registered device list verification, IFTA filing alignment with ELD mileage data, driver qualification file review, and CSA score check. ELD compliance doesn't exist in isolation — it's one component of a fleet compliance program that needs coordinated attention on a regular schedule.

Bottom Line

ELD compliance for a small fleet is a management responsibility that scales with every vehicle you add. The rules don't get more complicated with more trucks — but the surface area for failure does. One device revocation becomes five simultaneous OOS orders. One driver who doesn't know the malfunction procedure creates an 8-day compliance crisis you find out about after the clock has been running. One pattern of unassigned driving across multiple trucks looks like systematic off-the-books operation at a DOT audit.

The fleet owners who manage this cleanly aren't doing anything exotic. They have a device inventory they verify quarterly. They track exemptions per vehicle and driver so no one is applying the wrong rule. They have a log review process that surfaces problems before a weigh station does. They've trained every driver on malfunction procedure and put the backup materials in every cab. And they have a defined compliance contact who receives malfunction notifications within 24 hours — not two days later when the driver finally gets around to calling.

Build the program. Run the quarterly checks. Review the logs. That's what clean ELD compliance looks like at the fleet level.

If you'd rather have your drivers focused on driving than your compliance calendar consuming your management time, that's the kind of operational support a dispatch partner who takes compliance seriously provides. Atom Dispatch's compliance and ELD services handle device management, log review, and regulatory monitoring for carriers running fleets across all equipment types — so you're not doing compliance alone while also running a business.