Running trucks and wondering how fleet management ELD setups fit together? An ELD records driving time for compliance, while fleet software builds on that data for dispatch, safety and maintenance. Use the ELD as the base layer.
| Item | Value |
|---|---|
| ELD compliance date | December 18, 2017 |
| Grandfathered AOBRD use allowed until | December 16, 2019 |
| Paper-log exception | Not more than 8 days in any 30-day period |
| Vehicle exception | Vehicles manufactured before model year 2000 |
| Record and supporting document retention | 6 months |
These figures come from the FMCSA final rule as published in the Federal Register. Rules and exceptions can change, so check the source before you rely on them.
What fleet management means once ELDs are in the cab
Fleet management is the day-to-day work of keeping trucks, drivers and freight moving safely and legally. Before electronic logs, much of that work ran on paper, phone calls and memory. An ELD changes it because the truck now produces a steady record of when it moves and who is driving.
The ELD itself is narrow by design. Its job is to record a driver’s duty status so that hours-of-service limits can be checked. If you want the basics of the device first, read what is an electronic logging device and come back here for the fleet view.
A fleet management system (FMS) is the wider software layer. Many products bundle an ELD with other tools, and the FMCSA rule text itself refers to fleet management systems that include an ELD function. That bundling is why buyers often compare the two together even though they solve different problems.
What an ELD gives a fleet manager
- Driver hours remaining, so dispatch can plan loads that a driver can legally finish.
- Records that are ready for a roadside inspection.
- Unassigned driving events that need to be reviewed and assigned to the right driver.
- A clean audit trail for logs and supporting documents.
For a small operation, that may be all you need. For a larger one, the ELD becomes the data source that other systems draw on, so its reliability matters more as the fleet grows. A weak device undermines every tool built on top of it.
What it does not do on its own
A basic compliance ELD does not choose routes, score driving behaviour or schedule maintenance. Those features come from add-on modules or a separate platform. Check what a product includes before assuming it covers them.
The compliance baseline every fleet starts from
The federal rule applies to most motor carriers and drivers who must keep records of duty status. The FMCSA final rule set a compliance date of December 18, 2017. Carriers that had already installed a compliant automatic on-board recording device (AOBRD) could keep using it through December 16, 2019.
That grandfathering window has long since closed, so a fleet buying equipment today starts from a registered ELD. The rule requires interstate carriers to use only an ELD that appears on the FMCSA’s list of registered devices. Our guide to the eld registered devices list explains how to check a model.
For a wider look at inspections, penalties and recordkeeping, see eld compliance. This overview stays focused on running a fleet.
Fleet managers sometimes assume the rule is simple and uniform. In practice, your obligations depend on the type of operation, the age of the vehicles and the pattern of each driver’s work. A carrier with a mix of long-haul and local drivers may need ELDs for some drivers and not others.
Keep a simple register that lists each driver, the basis on which they log hours, and the date you last reviewed that basis. Review it whenever routes or assignments change. This one document answers many audit questions quickly.
Who is excepted
The rule lists some drivers who may keep using paper logs. Two of the best known are below, taken from the same Federal Register rule.
- Drivers who use paper records of duty status for not more than 8 days during any 30-day period.
- Drivers of vehicles manufactured before model year 2000.
An FMCSA FAQ, reproduced on a third-party documentation site, also treats vehicles with engines predating model year 2000 as exempt, even if the registration shows a later model year.
If you run mixed equipment, track which trucks and drivers rely on an exception and keep proof ready. Authorised safety officials can ask for records that support it.
Choosing and rolling out an ELD across a fleet
Fleet buying decisions are rarely about the device alone. The better questions are about registration status, support, data access and how the software fits your dispatch routine. Our guide on how to choose an eld walks through a full checklist.
A sensible shortlist process looks like this:
- Confirm each candidate appears on the FMCSA registered list.
- List the features your operation needs beyond logging, such as messaging, vehicle inspection reports or reporting tools.
- Ask for a trial with a few drivers before committing the whole fleet.
- Check how drivers get help when something fails on the road.
- Read contract terms on length, hardware ownership and data export.
Budgeting without surprises
Pricing usually mixes hardware, a monthly subscription per truck, and sometimes setup or cancellation fees. Quotes vary widely, and we do not publish prices here because they move. For the cost categories to compare, see eld cost.
Installation and connection type
Some devices plug into the engine port or are wired in, while others pair with a phone or tablet. Each approach has tradeoffs for reliability, theft and driver handling. The bluetooth eld vs hardwired eld comparison covers them in detail.
Plan the physical work too. Mixed fleets with older trucks may need different adapters, and downtime during fitting affects your schedule. Our eld installation page covers what to expect.
Using ELD data to run the operation
Once logs flow in, the real value is in how dispatch and safety staff use them. Treat the data as a planning tool first and a compliance record second. The two goals reinforce each other when drivers trust the system.
Dispatch and planning
Hours remaining for each driver let dispatchers match loads to drivers who can legally complete them. This reduces last-minute reshuffles and late deliveries. It also helps you spot drivers who are about to run out of hours before a problem appears.
Log quality and unassigned driving
The rule describes unassigned driving time as driving that occurs when no driver has logged in. It is visible to authorised safety officials who view the ELD records. Reviewing and resolving these events promptly keeps your records tidy.
Supporting documents and retention
The FMCSA rule continues to require that motor carriers retain records of duty status and supporting documents for 6 months. Build that into your filing routine, whether documents are scanned or stored in your fleet software. Missing paperwork is a common weak spot, so assign one person to own it.
Working with customers and shippers
Accurate hours data helps you give customers realistic delivery windows. When a driver is close to the end of their available time, dispatch can warn the receiver early rather than apologise afterwards. Over time this builds a reputation for dependable service, which matters as much as the compliance record itself.
It also helps with appointment planning, although you should not treat ELD data as a complete record without other documents.
Keeping the data tidy
Good habits make the system more useful and less stressful. Agree on a few rules and stick to them.
- Drivers certify each day’s log promptly instead of letting days stack up.
- Remarks are written in plain words so that an inspector can follow them.
- The office reviews exceptions weekly, not only before an audit.
Going beyond logs
- Safety coaching based on driving events, if your platform offers it.
- Maintenance reminders tied to engine data.
- Location views for customer updates.
- Fuel and idling reports for cost control.
These are optional extras outside the federal ELD requirement. Weigh each against its price and against how drivers will react to being monitored.
Driver trust, privacy and harassment protections
Fleet technology works best when drivers accept it. The FMCSA rule includes technical and procedural provisions meant to prevent ELDs from being used to harass drivers. One example is a required mute function, so a driver in the sleeper berth is not interrupted by a fleet management system that includes an ELD function.
The mute function is meant to ensure that a driver in the sleeper berth is not interrupted by such a system. Read the details in our guide to eld driver harassment rules.
Data handling matters as well. Location and driving data are sensitive, and carriers should decide who sees what and for how long. For a closer look, see eld driver privacy.
Practical steps for managers
- Explain to drivers what the system records and why.
- Write down who in the company can view or edit logs.
- Never use messaging or alerts to push a driver to break hours limits.
- Give drivers a clear way to raise log corrections or complaints.
Rolling out and reviewing your ELD program
Building a rollout plan drivers will accept
Drivers who first hear about a new device on the morning it is installed tend to distrust it. A short, honest briefing before the change does more than any feature list.
Start with a pilot group of drivers who have different routes and different comfort levels with technology. Their feedback will surface problems such as weak phone signal in rural areas, confusing screens, or awkward mounting positions. Fix those before the rest of the fleet is switched over.
Training that sticks.
Drivers need to know a handful of tasks well: logging in, changing duty status, adding remarks, certifying a day’s log, and handing over data at a roadside inspection. Give every driver a printed quick-reference card for the cab, because the device may be the very thing that is not working when they need help.
- Show drivers how to read their remaining hours.
- Walk through how to accept or reject proposed log edits.
- Practise the roadside data transfer steps for your specific model.
Roles inside the office.
Decide who reviews logs, who handles unassigned driving, who talks to the vendor and who keeps supporting documents. In small offices one person covers several roles, which is fine if the duties are written down. In larger operations, a single owner for ELD administration prevents tasks from slipping between dispatch, safety and payroll.
Common mistakes fleets make with ELDs
Some errors show up again and again, and nearly all are avoidable. Knowing them in advance saves time during audits and roadside checks.
- Buying an unregistered device. Look up the exact model and version on the FMCSA list rather than trusting a sales page.
- Ignoring unassigned driving. Events left unclaimed pile up and look careless to anyone reviewing the records.
- Treating the ELD as a surveillance tool. Pressure on drivers damages retention and can cross into harassment territory.
- Forgetting supporting documents. The log is only part of the record, and the paperwork behind it must be kept for the full retention period.
- Skipping exception paperwork. If a truck or driver relies on an exception, be ready to show why.
- Locking into a long contract too early. A pilot period reveals problems that a demo hides.
Judging whether your ELD setup is working
A device that records hours is doing its basic job, but a fleet should ask for more. Choose a small set of measures and review them on a regular schedule. Keep the list short so that someone actually reads it.
Measures worth tracking.
- How many unassigned driving events are open and how old they are.
- How often drivers contact the office about device problems.
- Whether log edits are requested by drivers or pushed by the office.
- How inspections involving log review turn out.
- Driver feedback on usability, gathered in a simple survey or a meeting.
When to switch providers.
Changing vendors is disruptive, but staying with a poor fit is costly too. Signs that it is time to look around include repeated outages, slow support, hidden fees, or a product that falls off the registered list. Before you switch, confirm that you can export your historical logs, because you must keep them for the retention period regardless of vendor.
Plan the changeover for a quiet period and run the old and new systems in parallel only as far as the rules permit. Tell drivers the date, the new login steps and where to get help.
Small fleets and owner-operators
A one-truck business has the same legal duties as a large carrier unless an exception applies, but it has fewer people to absorb the admin. It often wants a simple device, predictable pricing and little setup. Many owner-operators skip fleet extras and choose a plain registered ELD.
If you lease on to a carrier, ask who supplies the device and who owns the data. Our page on eld for owner operators covers those situations.
Whatever your size, confirm any exception in writing before leaving the ELD off a truck. The rule says a driver who qualifies may still operate a vehicle fitted with an ELD, so having the device does not cancel the exception.
Frequently asked questions
Is an ELD the same as fleet management software?
Show answer
No. An ELD records driver duty status for hours-of-service compliance. Fleet management software is a broader set of tools, and some products bundle an ELD into it.
Do all fleets need an ELD?
Show answer
Most carriers whose drivers must keep records of duty status do. The Federal Register rule lists exceptions, including paper logs used not more than 8 days in any 30-day period and vehicles manufactured before model year 2000.
How long do I keep logs and supporting documents?
Show answer
The retention period in the FMCSA rule is 6 months for both logs and the paperwork behind them. Confirm it against the current regulation before you set a policy.
Can any ELD be used for compliance?
Show answer
Interstate carriers must use a device that appears on the FMCSA’s list of registered ELDs, per the rule. A vendor’s claim alone is not enough, so verify the listing.
Can an ELD be used to harass a driver?
Show answer
The rule prohibits it and includes protections such as a mute function in sleeper berth status. Our site is educational and cannot handle complaints, so use the FMCSA’s official channels.
