A logbook is how a commercial driver documents duty status throughout the day, including driving time, on-duty non-driving time, sleeper berth time, and off-duty time. Its purpose is to prove a driver stayed within federal hours-of-service limits. That record is kept one of two ways in the US: the paper grid, or an electronic logging device. For most drivers required to keep records of duty status, paper stopped being an option years ago.
KEY TAKEAWAYS
- A logbook tracks four duty statuses: driving, on-duty not driving, sleeper berth, and off-duty.
- Most drivers required to keep records of duty status must run an FMCSA-registered ELD. Paper logs survive only in a few specific carve-outs: short-haul work, older trucks, and infrequent long trips.
- Fatigue is a documented factor in commercial truck crashes, not merely a regulatory concern.
- Hours-of-service penalties are set by federal rule and adjusted for inflation. Current figures should always be verified against the current Appendix B to 49 CFR Part 386.
- Logbook data is worth more than compliance alone. Paired with vehicle health and location data, it can flag fatigue risk and maintenance gaps before they become violations.
In this guide, we cover what a logbook must contain, how paper and electronic records differ, who still qualifies for paper logs, why hours-of-service rules exist, what happens when records do not hold up at a roadside stop, and how pairing logbook data with vehicle health monitoring gives fleets a more complete compliance picture than duty status tracking alone.
Logbook basics at a glance
| Question | Answer |
| What is a logbook | A record of a driver’s duty status across a 24-hour period |
| Who needs one | Drivers required to maintain records of duty status under 49 CFR Part 395 |
| Paper or electronic | ELD required for most drivers. Paper allowed under a few specific exceptions |
| Retention rule | Drivers keep the current log plus the prior 7 days. Carriers keep records for 6 months |
What actually goes into a logbook
Four duty statuses form the entire framework: driving, on-duty not driving, sleeper berth, and off-duty. Every hour of a driver’s day lands in one of those categories, and the shape of that 24-hour grid is exactly what an inspector checks against the hours-of-service limits.
Under current FMCSA hours-of-service rules, most drivers can drive up to 11 hours after 10 consecutive hours off duty, within a 14-hour on-duty window. There is a mandatory 30-minute break after 8 hours of driving. Weekly caps sit at 60 hours across 7 days or 70 across 8, and a 34-hour restart resets the clock. The logbook, whether paper or electronic, is the proof that a driver stayed within those limits.
Paper logbooks vs. electronic logging devices
A paper log uses the familiar 24-hour grid, filled in by hand with duty status, miles driven, carrier details, and the time base for the day. It functions adequately right up until a driver fails to log a stop at the end of a long shift, and that gap is precisely what the ELD mandate was designed to address.
An ELD connects to the engine and begins recording driving time the moment the wheels move. Duty status changes sync as they happen rather than being reconstructed from memory hours later, which is a significant part of why most interstate carriers made the switch well before the mandate deadline.
Who still qualifies for paper logs
FMCSA established real exceptions under 49 CFR 395.1(e). A CDL driver working within a 100 air-mile radius of their normal reporting location, returning there each day, and staying within a 12-hour window does not need an ELD. Non-CDL drivers have slightly more room: 150 air miles and a 14-hour window under similar conditions.
A smaller exception creates compliance risk for fleets more often than it should: a driver who does not need to keep a record of duty status for more than 8 days out of any rolling 30 does not need an ELD for those occasional longer runs. The issue is that fleets tend to assume their entire short-haul group is covered and stop counting. Track exception days per driver, because a handful of extra trips outside the radius is sufficient to exceed that limit without anyone recognizing it until an inspector does. Trucks built before model year 2000 are also exempt, as their engines generally cannot connect to an ELD.
Why logbooks exist
Strip away the regulatory framework, and the reason is straightforward. A fatigued driver operating an 80,000-pound truck is a documented safety risk. FMCSA’s own Large Truck Crash Causation Study coded fatigue as an associated factor in 13% of the truck drivers involved in the crashes it examined, making it one of the more common driver-related factors the study identified. Logbooks exist to prove a driver had enough rest before getting back behind the wheel, and that duty status record is one input into the broader picture driver behavior monitoring gives a fleet.
For carriers, that record serves a second purpose. It provides documentary support if a crash is ever investigated, and it is typically the first item an inspector requests at a roadside stop. A log that is missing or internally inconsistent is not just a potential fine. It is grounds to examine the vehicle and the driver’s credentials more closely on the spot.
What happens when logbook records do not hold up
Hours-of-service penalties are set out in Appendix B to 49 CFR Part 386, and that schedule is adjusted for inflation periodically. Current penalty figures should always be verified directly against the current Appendix B, as a number accurate two years ago may not be accurate today. Driving-limit overages, recordkeeping gaps, and knowing falsification carry different penalty levels.
What does not change from year to year is the shape of the risk. Violations feed into a carrier’s Safety Measurement System score under FMCSA’s Compliance, Safety, Accountability program, and different violation types carry different severity weights. When FMCSA treats a violation as egregious, generally a driver caught more than three hours past a driving limit, the roadside response can include an immediate out-of-service order. The load sits until a replacement driver takes over or the original driver logs the required rest.
Level VIII wireless inspections (2026)
As of early 2026, FMCSA is in an operational test phase for Level VIII inspections, in which DOT officers check ELD compliance status wirelessly while vehicles are moving at highway speeds. Level VIII is not yet a nationwide enforcement requirement, but fleet managers should be aware that ELD data transmitted in real time can be reviewed remotely without the vehicle stopping. Logbook accuracy and ELD registration status are both visible in that transmission. Fleets whose drivers log duty status inconsistencies, or whose vehicles carry unregistered or revoked ELD devices, carry compliance exposure even when not subject to a traditional roadside stop.
Logbook and ELD compliance requirements
Drivers retain their current log plus the previous 7 consecutive days, and completed originals go to the carrier within the required window. Carriers keep those records for 6 months and must produce them for an audit on request.
ELDs must appear on FMCSA’s registered device list and running a device that has been delisted or revoked counts as running no ELD at all.
2026 ELD revocations
Drivers hang onto their current log plus the previous 7 consecutive days, and completed originals go to the carrier within the required window. Carriers keep those records for 6 months and need to be able to produce them for an audit on request. ELDs themselves have to stay on FMCSA’s registered device list. Running a device that’s been delisted or revoked is treated the same as having no ELD at all, and this isn’t a hypothetical risk. FMCSA removed five devices, MOONLIGHT ELD, HGRS ELD, HIGHEST ELD, TRUCKFORD ELD, and Sparkle ELD, from the registered list on August 6, 2026, and gave carriers until October 6, 2026 to switch to a compliant device. Miss a deadline like that and drivers can be placed out of service with no warning beyond the notice FMCSA already sent.
Best practices for keeping logbooks audit-ready
Training on duty status changes matters more than training on which button to tap. Most log errors trace back to a driver forgetting to switch status when a quick fuel stop turns into a two-hour dock delay, not to someone trying to cheat the system.
A weekly internal review catches problems a roadside check will not. Comparing logs against dispatch records surfaces mismatches while there is still time to address them, rather than after an auditor already has the records in hand.
Documenting the ELD malfunction process also matters. Carriers have up to 8 days to repair or replace a malfunctioning device, or to request additional time from FMCSA, but only if the malfunction is reported immediately rather than days later when someone notices. The clock starts at the moment of malfunction, not the moment of discovery.
Pairing hours-of-service data with vehicle health data closes a gap most standalone logging tools leave wide open. A driver pushing close to a duty limit in a truck that’s also overdue for service is a problem waiting to compound, and duty status data by itself won’t ever flag that. Most of this belongs inside a documented fleet safety program rather than living as separate habits across dispatch and maintenance.
The role of technology in modern logbook management
Going digital did more than satisfy a federal mandate. It converted hours-of-service data into something a fleet can work with operationally rather than simply file away. A dispatcher monitoring duty status, vehicle location, and remaining drive time on one screen makes more precise routing decisions than one relying on a driver’s radio update.
That is where the real value emerges: when logbook data integrates with the rest of the fleet’s operational picture. Duty status alone tells a fleet whether a driver is compliant at this moment. Duty status alongside engine health and route data tells a fleet whether that driver is approaching a compliance problem and a mechanical one simultaneously.
How Intangles supports logbook and fleet compliance
For trucking and logistics fleets managing tight HOS windows, the risk is not just a logbook violation. It is a mechanical fault that forces an unplanned stop with limited hours remaining, turning a compliance edge case into a compliance failure. Intangles addresses this at the vehicle health level, running continuously alongside whatever ELD system a carrier operates.
| Capability | How it supports logbook and HOS compliance |
| Predictive vehicle health monitoring | Detects developing engine and mechanical faults before they force an unplanned stop that consumes a driver’s remaining hours mid-route, preventing a maintenance problem from becoming an HOS violation. |
| ELD integration support (DriveTime ELD) | Intangles’ DriveTime ELD tracks driving hours and duty status in real time, creating a connected record of both compliance status and vehicle health in one platform. |
| Real-time fault alerts | Notifies fleet managers of emerging mechanical issues on active routes, enabling repair scheduling before a developing fault escalates into an out-of-service event that strands a driver with hours remaining. |
| Driver performance monitoring | Tracks driving behavior exceptions including harsh braking and overspeeding alongside duty status data, giving fleet managers a combined picture of compliance risk and driver fatigue indicators. |
A driver finishing a compliant shift in a truck with a developing cooling system fault is a problem that duty status data alone will never catch. That is the gap continuous vehicle health monitoring closes for HOS-constrained operations.
At Intangles, the fleets where logbook compliance and vehicle health data have the clearest combined value are those running tight delivery windows with limited driver slack. When a mechanical fault forces an unplanned stop, the downstream effect is not just a repair cost. It is a driver who runs out of hours before reaching the delivery, a missed window, and a compliance record that reflects an unplanned stop the fleet never anticipated. Predictive monitoring is what keeps that scenario from compounding.
Explore the platform or get in touch with our team to see how DriveTime ELD and predictive vehicle health data work together to keep drivers compliant and trucks moving.
KNOW MORE
Frequently Asked Questions
Can a fleet still use paper logs in 2026?
For most drivers, no. The exceptions that still apply cover short-haul operations within a 100 air-mile radius (CDL) or 150 air-mile radius (non-CDL), pre-2000 trucks, and drivers who stay under 8 days of recordkeeping in a rolling 30-day window. Outside those cases, an FMCSA-registered ELD is required.
What is the difference between a logbook and an ELD?
A logbook is the record itself, the duty status data for a given day. An ELD is the device that captures that record automatically rather than requiring a driver to write it down by hand at the end of a shift.
How far back do drivers and carriers need to keep records?
Drivers carry the current log plus the prior 7 days. Carriers retain records for 6 months and must produce them if FMCSA requests them during an audit.
Can a driver be pulled off the road for a logbook problem?
Yes. If FMCSA treats a violation as egregious, generally more than 3 hours past a driving limit, a roadside stop can result in an immediate out-of-service order until the driver logs the required rest.
Do logbook violations follow a carrier over time?
Yes. Violations feed into FMCSA’s Safety Measurement System score, which shapes insurance premiums and influences how frequently FMCSA selects a carrier for inspection.
Is switching to an ELD worth it beyond staying legal?
Most fleets find it is. Real-time duty status data lets dispatch plan around actual remaining hours rather than estimates, and paired with vehicle health data, it can surface problems a paper log would never identify.
We’re looking forward to meeting you