DVIR and ELD Compliance Explained for Small Fleets

You added your fourth truck last month, one of them now runs a route across the state line, and a driver asks whether you need electronic logs. You realize you do not actually know the answer — and you are not sure whether the daily inspection paperwork you have been doing is the right kind, or enough. That is a very common place for a growing fleet to be, and getting it wrong is expensive.

Here is the plain-English version. A DVIR (driver vehicle inspection report) is the documented inspection a driver performs on a commercial vehicle to catch defects before and after a trip. An ELD (electronic logging device) is hardware that connects to the engine and automatically records driving time to enforce Hours of Service (HOS) limits — the federal rules that cap how long a commercial driver can drive and be on duty. Both fall under the U.S. Federal Motor Carrier Safety Administration (FMCSA), and both apply to many, but not all, commercial vehicles.

This guide explains what each one is, who they apply to, the basics of HOS, what non-compliance can cost, and how software helps. One important thing up front: applicability, thresholds, and penalties are specific and they change, so treat this as general education and verify the current rules with FMCSA before you make decisions.

This article is general education, not legal or compliance advice, and it is deliberately careful about specific numbers.

Federal safety regulations for commercial motor vehicles are detailed, full of exceptions, and revised over time. The exact weight thresholds, air-mile radii, hour limits, exemptions, and penalty amounts that determine what applies to your fleet live in official FMCSA regulations and can change with new rulemaking. A blog post — including this one — is the wrong place to get an authoritative number to build your compliance program on.

So here is the rule for reading the rest of this piece: use it to understand the concepts and the shape of the requirements, and then verify every specific against the current FMCSA regulations at fmcsa.dot.gov, your state's department of transportation for intrastate operations, and, where the stakes are real, a qualified compliance professional or attorney. Where I mention a commonly cited figure below, I have flagged it as commonly cited precisely because you should confirm it rather than rely on it. Compliance is one area where "I read it somewhere" is not a defense at a roadside inspection or an audit.

A DVIR — driver vehicle inspection report — is the record a driver creates when inspecting a commercial motor vehicle for safety defects. The idea is simple and old: catch a bad brake, a worn tire, a broken light, or a leaking coupling before it causes a crash, and document that the check happened.

In general practice, drivers of covered vehicles perform inspections in connection with their trips and record any defects they find. A post-trip report typically notes defects or deficiencies that would affect safety, and if defects are found, they are supposed to be addressed and certified as repaired (or determined not to need repair) before the vehicle goes back out. Common inspection items include brakes, steering, lights and reflectors, tires and wheels, mirrors, coupling devices, the horn, windshield wipers, and emergency equipment.

Historically this was a paper form on a clipboard. Today it is increasingly a mobile app: the driver walks the vehicle, taps through a checklist, photographs a defect, and submits the report electronically, where a failed item can route straight to maintenance. The exact inspection requirements, what must be recorded, who must sign off, and how long reports must be retained are set by regulation and can vary by vehicle type and operation — so confirm the current DVIR requirements that apply to your fleet with FMCSA rather than assuming the general description here is complete.

An ELD — electronic logging device — is hardware that connects to a commercial vehicle's engine and automatically records driving time and related data. Its job is to create an accurate, tamper-resistant record of a driver's hours so that Hours of Service limits can be enforced without relying on handwritten paper logs.

The ELD mandate was introduced to replace paper Records of Duty Status (and older automatic recording devices) with a standardized electronic record for drivers who are required to keep HOS logs. An ELD captures things like engine hours, vehicle movement, miles driven, and duty status, and presents them in a format that a roadside inspector can review. Critically, an ELD used for compliance is supposed to be registered and self-certified with FMCSA against the agency's technical specification — not every app that tracks driving is a compliant ELD.

That last point matters for small fleets shopping for tools. If HOS logging applies to you, you need a device and software that appears on FMCSA's registered ELD list and meets the current specification, not just any GPS or timekeeping app. And because the rules about which drivers must use an ELD (versus qualifying for an exemption) are specific, the first question is not "which ELD" but "does the ELD requirement apply to this driver at all" — which you should confirm against current FMCSA rules.

Hours of Service are the federal rules that limit how long a commercial driver may drive and be on duty, with the goal of reducing fatigue-related crashes. ELDs exist largely to enforce HOS, so the two concepts are joined at the hip.

The structure of HOS, described generally, includes a daily driving limit, a maximum on-duty window within which that driving must happen, a required rest break during the day, and weekly on-duty limits, plus a provision that lets a driver reset the weekly clock after enough consecutive time off. The figures most commonly cited for property-carrying drivers are an 11-hour driving limit within a 14-hour on-duty window after 10 consecutive hours off duty, a required 30-minute break after 8 cumulative hours of driving, and a 60-hour-in-7-days or 70-hour-in-8-days on-duty limit that can restart after 34 consecutive hours off.

Treat those numbers as commonly cited, not authoritative. Passenger-carrying rules differ from property-carrying rules, several exceptions exist (for adverse driving conditions, short-haul operations, and others), and the limits have been revised before and can be again. If HOS applies to your drivers, verify the current limits, exceptions, and how they apply to your specific operation directly with FMCSA. The concept to walk away with is that there are hard caps on driving and duty time, they are enforced electronically, and building your schedules as if drivers have unlimited hours is both illegal and unsafe.

This is where small-fleet owners most often guess wrong, so it is worth being careful and, again, general.

Broadly, federal DVIR, ELD, and HOS requirements attach to commercial motor vehicles operated in interstate commerce that meet certain criteria. The commonly referenced triggers include vehicles at or above a gross vehicle weight or weight rating threshold (a figure often cited around 10,001 pounds — confirm the current number and how it is measured), vehicles designed or used to transport more than a specified number of passengers, and vehicles used to haul placarded hazardous materials. If a vehicle qualifies as a CMV under these kinds of criteria and operates across state lines, it is generally in scope for these rules.

Two big wrinkles. First, interstate versus intrastate matters: operating entirely within one state can put you under that state's rules, which sometimes mirror the federal ones and sometimes differ, so a purely local fleet has a different analysis than one crossing state lines. Second, being subject to HOS is not the same as being required to use an ELD — several exemptions can excuse a driver from the ELD requirement even when other rules still apply.

Because the exact thresholds, the interstate/intrastate distinction, and the definitions are specific and have changed over time, do not self-diagnose from this paragraph. Confirm whether each of your vehicles and drivers is covered by checking current FMCSA regulations and your state DOT, especially as you add larger trucks or start crossing state lines.

The regulations include a number of exemptions, and a small fleet may well qualify for one — which is exactly why so many owners assume rules do not apply to them and turn out to be wrong. An exemption from the ELD requirement, for example, does not necessarily excuse you from the underlying Hours of Service rules or from keeping records another way; it changes how you comply, not always whether you comply. Each exemption has specific, technical conditions attached, and losing eligibility can be as simple as one driver exceeding the radius or the time window on one day.

So treat the list below as a map of what exists to investigate, not a checklist you can self-apply. For each one that looks like it might fit your operation, verify the current terms with FMCSA — the radius, the hours, the vehicle criteria, the model-year line — before you build your schedules or your paperwork around it. "We thought we qualified for the short-haul exemption" is a sentence that has gone badly for a lot of fleets at an audit. Here are the exemptions worth knowing exist:

Non-compliance is not a paperwork nuisance — it carries real operational and financial consequences, even if the exact amounts are not something to quote from a blog.

At a roadside inspection, HOS, ELD, or DVIR violations can result in citations and, for serious issues, an out-of-service order that sidelines the driver, the vehicle, or both on the spot — which means a stranded truck, a missed job, and a scramble to recover. Violations also feed into your carrier safety profile and CSA scores, and a poor safety record can raise insurance costs, invite more frequent inspections and audits, and in serious cases contribute to a downgraded safety rating that threatens your ability to operate. There are civil penalties for various violations as well.

The specific fine amounts, the triggers, and the severity tiers are set by FMCSA and DOT, they vary by violation type, and they change — so I am deliberately not quoting dollar figures here. If you want the current penalty schedule, get it from official FMCSA/DOT sources. The takeaway is directional but firm: the cost of a violation compounds well beyond any single fine, through downtime, higher insurance, audit exposure, and the liability multiplier if an out-of-compliance vehicle is ever involved in a crash. Compliance is cheaper than any of that.

Read the table as concepts, not compliance instructions. The three are easy to blur together because they show up in the same conversation, but they answer different questions. DVIR is about the vehicle's mechanical condition — is this truck safe to drive today. ELD is the recording device — how are we capturing what the driver actually did. HOS is the set of time rules the device is checked against — was the driver within legal driving and duty limits.

A fully compliant covered fleet generally needs all three handled together: inspections documented and defects resolved, driving hours recorded on a registered device where required, and schedules built to respect the limits rather than fighting them. They reinforce each other — a well-run DVIR process keeps unsafe trucks off the road, accurate ELD records keep drivers honest about hours, and realistic scheduling keeps you from pressuring drivers into violations in the first place. But which of the three apply to you, and exactly how, depends entirely on the applicability questions above: vehicle weight, passenger capacity, hazardous materials, and interstate versus intrastate operation. Do not infer your obligations from this table — confirm them with FMCSA and, for local operations, your state DOT.

Software turns compliance from a clipboard-and-shoebox chore into something that mostly runs itself, across three layers.

Digital DVIR. Instead of paper forms, drivers complete inspections in a mobile app, tap through the checklist, photograph defects, and submit electronically. Failed items can route straight to maintenance as work orders, and every inspection is timestamped and retained for audits. Tools like Whip Around are built specifically around this inspection workflow, and many broader fleet platforms include digital DVIR too.

ELD and HOS. For drivers who must keep electronic logs, you need an FMCSA-registered ELD — a device and app that appear on the agency's registered list and meet the current technical specification. Established providers of registered ELDs include Samsara, Motive, Geotab, and Garmin, among others. These systems record driving time automatically, warn drivers as they approach HOS limits, and present the logs a roadside inspector expects. Do not substitute a generic GPS or timekeeping app for a registered ELD where one is required.

Records and audit readiness. The quieter value is retention and retrieval. When inspections, maintenance history, and logs are stored and searchable, an audit or a roadside stop becomes a lookup instead of a fire drill. The point is not to buy the flashiest platform — it is to make sure the specific requirements that apply to your fleet are met with tools that are actually compliant, and to keep the records that prove it.

Deelo is a fleet-operations platform, and it is important to be precise about the boundary here: Deelo is not itself a registered ELD, and you should not treat it as your HOS logging device. Where a driver is required to keep electronic logs, use an FMCSA-registered ELD provider such as Samsara, Motive, Geotab, or Garmin for that specific function.

What Deelo Fleet does handle is the operations-and-records layer that sits around compliance. Digital vehicle inspections and defect capture, maintenance scheduling tied to real mileage, service history, and per-vehicle records all live in one place — so when a DVIR flags a defect, it becomes a tracked maintenance item instead of a note that gets lost. Because Deelo also runs Deelo Field Service for dispatch and Deelo Expenses for cost tracking, an inspection defect, the repair work order, and the repair cost all connect in a single system rather than three.

The honest summary: for the ELD device and HOS logging, choose a registered specialist. For running the fleet around it — inspections, maintenance, defect-to-work-order, records, and the dispatch and billing that make up the rest of a small service business — Deelo keeps it in one platform on one bill. And whichever tools you choose, verify what DVIR, ELD, and HOS rules actually apply to your fleet with FMCSA before you rely on any of them.