CDL log book compliance changed sharply when FMCSA reported HOS violations falling from 1.19% of driver inspections in December 2017 to 0.68% by April 2018, a roughly 43% relative reduction tied to ELD enforcement (FMCSA enforcement data). If you own a fleet or manage safety, your log review process is one of the clearest ways to keep a roadside inspection from becoming a larger compliance problem. Many fleets still treat the log as a trip diary, rely on an exemption that doesn't apply, or discover an ELD failure only after the driver is stopped. A CDL log book is an auditable record of duty status, connected to the vehicle, driver, time, location, and supporting documents. You need a process that verifies the record, preserves the audit trail, and gives your team a workable fallback when the electronic system fails.
Table of Contents
- What a CDL Log Book Actually Is and Why It Matters
- Hours of Service Rules the Log Book Enforces
- Paper Logs Versus Electronic Logging Devices
- What a Properly Completed Log Entry Looks Like
- Exemptions That Are Not What They Sound Like
- What to Do When the ELD Fails or Gets Revoked
- Practical Compliance Tips for Fleet Owners and Safety Managers
- Frequently Asked Questions About CDL Log Books
- What is a CDL log book?
- How long must you retain ELD records?
- Do short-haul operations need a full log book?
- What happens when an ELD fails?
- How many days can you use paper logs after a malfunction?
- What information must a RODS include?
- Does the ELD identify every HOS violation?
- What should you do if a device is revoked?
What a CDL Log Book Actually Is and Why It Matters
A CDL log book, formally a Record of Duty Status, or RODS, records a driver's duty status for each 24-hour period. It must reflect changes among driving, on duty but not driving, off duty, and sleeper berth. Each change requires the applicable city, town, or village and state, giving reviewers a record they can compare with the route, vehicle activity, and supporting documents (FMCSA ELD frequently asked questions).
Treat the log as compliance evidence, not a personal trip diary. During a roadside inspection, carrier review, or enforcement action, it shows whether the driver's recorded workday fits the hours-of-service rules. It can also reveal conflicts between the claimed duty status and the truck's movement, engine data, location history, bills of lading, fuel records, or other paperwork.
Why electronic records changed the review
Electronic records give inspectors and safety managers a clearer audit trail. They make duty-status activity easier to compare with vehicle movement and related records. FMCSA estimated an annual impact of 1,844 crashes avoided, 562 fewer injuries, and 26 lives saved from the technology's expected safety effect (FMCSA ELD enforcement information). The technology does not replace review. It makes inaccurate entries, unexplained edits, unassigned driving, and missing support easier to identify.
A traffic allegation can widen the compliance review. For practical context on how violations may affect a driver, see this resource on CDL traffic tickets from Ticket Shield, PLLC.
Review every log before an inspector does. Confirm certification, edits, unassigned driving, vehicle identification, and supporting documents. Use this CDL log book resource for truck drivers as a starting reference, then align the process with your dispatch system and equipment.
A clean log gives your fleet an audit trail. It should agree with the truck, the load, and the driver's explanation.
Hours of Service Rules the Log Book Enforces
For property-carrying operations, the log must show compliance with two separate limits. A driver may drive up to 11 hours after at least 10 consecutive hours off duty. The 14-hour driving window begins when the workday starts and continues through off-duty or sleeper-berth time. Off-duty time inside that window does not extend it (FMCSA property-carrier HOS guidance).
Both limits apply at once. Remaining drive time does not permit operation after the 14-hour window closes. A day that starts with on-duty work, includes loading and waiting, and ends with a late delivery can use the full window while staying below the driving limit.
Read the four duty statuses correctly
The four standard statuses should match what the driver did:
- Driving: The vehicle is moving under the driver's control.
- On duty not driving: The driver is working, including inspections, loading, unloading, fueling, or paperwork.
- Off duty: The driver is relieved from work and responsibility for the vehicle.
- Sleeper berth: The driver is using the sleeper berth under the applicable HOS rules.
Review each transition, not only the final totals. If the truck reaches a shipper while the record shows continuous driving, the log fails to account for the work performed there. If a driver records off-duty time while still responsible for the load or vehicle, that status may not reflect the actual duty.
A clean log should explain the day without guesswork. Dispatch, safety staff, and the driver need the same standard for deciding when work starts, when responsibility ends, and when a status change belongs on the record.
Know when short haul really applies
An eligible operation within a 150-air-mile radius may use time records instead of a full RODS under the conditions in 49 CFR §395.1. The record still needs the reporting time, release time, and total on-duty hours. This exception does not remove recordkeeping duties, and the operation must satisfy every applicable condition.
Check three points before approving a short-haul record:
- Did the operation remain within the applicable radius?
- Did the driver meet the conditions for the time-record exception?
- Does the record show reporting time, release time, and total on-duty hours?
Do not confuse an ELD exemption with a RODS exemption. A driver may fall outside an ELD requirement yet still need accurate records of duty status, or qualify for short-haul time records only while the stated conditions remain true. Use this plain-English HOS explanation to keep dispatch, safety, and management consistent.
Paper Logs Versus Electronic Logging Devices
Paper logs and ELDs record duty status, but they leave very different audit trails. Handwritten records depend on accurate entries and disciplined review. An FMCSA-compliant ELD captures the date, time, location, engine hours, vehicle miles, and authenticated driver, vehicle, and carrier identification. The FMCSA ELD final rule establishes the broader requirement, while the FMCSA ELD checklist identifies the technical functions the device must support.
Since December 18, 2017, most drivers required to prepare RODS have been required to use an ELD rather than paper logs. Carriers must retain ELD RODS and backup data for six months, according to FMCSA's implementation timeline. Paper remains valid for specific exceptions and emergency procedures. It is not a general escape from electronic logging requirements.
What the ELD adds to the record
During on-duty driving, an ELD records location to approximately a one-mile radius. It synchronizes time to UTC and keeps the current 24-hour period plus the previous seven consecutive days available for roadside review. The device must support on-demand transfer through telematics or local USB 2.0 or Bluetooth transfer, as specified in the FMCSA ELD checklist.
Edits require an explanatory annotation and driver approval. Automatically generated events cannot become final records without review. Safety staff should be able to explain every accepted edit, rejected edit, unassigned movement, and driver-vehicle association. That audit trail is one of the ELD's strongest advantages, but only when reviewers investigate exceptions instead of approving them in bulk.
Paper can still be valid, but only in the right place
Paper records may apply under an available exception or while the carrier follows the required malfunction process. They should never become an informal workaround for a driver who refuses to use the ELD. An ELD exemption and a RODS exemption are different questions, so confirm which rule applies before approving paper records.
Test roadside transfer before an inspection. Drivers should know the transfer function, the approved transfer method, and the location of malfunction instructions and blank paper records in the cab. For a practical review of manual records, use this guide to paper log books.
What a Properly Completed Log Entry Looks Like
A compliant CDL log book must tell a complete, reviewable story. Under 49 CFR §395.8, each record needs the required identifying and operational details, including the date, total miles, vehicle and trailer identifiers, carrier name, driver certification, home-terminal start time, remarks, co-driver information, total hours, and shipping-document or commodity details (49 CFR §395.8).
The home-terminal time basis deserves close attention. Dispatch records, payroll, safety reviews, and log timestamps should use the same standard. GPS may show local trip time, while the record follows the driver's home-terminal time. If reviewers compare those systems without aligning the time basis, a lawful workday can appear inconsistent.
Use the required fields as a review checklist
- Date and time basis: Confirm the record covers the correct 24-hour period and uses the home-terminal standard.
- Mileage: Compare total miles with the trip and vehicle activity.
- Truck and trailer identifiers: Match the equipment to the unit and load used.
- Carrier and driver identity: Check the carrier name, authenticated user, and driver certification.
- Duty-status timeline: Review gaps, overlaps, and transitions that do not fit the workday.
- Remarks: Explain delays, unusual events, edits, breakdowns, and other facts a reviewer may need.
- Co-driver information: Add it when the operation uses a team arrangement.
- Shipping or commodity details: Reconcile the entry with dispatch and load paperwork.
Certification closes the record
Certification confirms that the driver reviewed the entry and approved it as complete and accurate. Each ELD edit should state the reason for the change and receive driver approval. Safety staff should reject a pattern of late, unexplained corrections instead of treating them as routine housekeeping.
Reviewers should be able to understand the trip without relying on a verbal explanation. Missing identifiers, absent remarks, or shipping documents that do not reconcile can weaken an otherwise accurate record during a roadside inspection or later compliance review. A properly maintained audit trail shows who changed the record, why the change occurred, and whether the driver accepted it.
Exemptions That Are Not What They Sound Like
The compliance failure usually starts with one mistaken assumption: an ELD exemption does not automatically create a recordkeeping exemption. A driver may qualify to avoid an ELD and still need time records or paper records of duty status, known as RODS.
Five assumptions that expose fleets
Short haul means no record. The short-haul exception under 49 CFR §395.1(e) allows eligible operations to use time records showing reporting time, release time, and total on-duty hours. That exception depends on meeting its conditions. It does not erase the duty to document the workday.
A small fleet is automatically exempt. Fleet size does not settle the question. The driver's actual routes, operating conditions, and recordkeeping history determine whether an exception applies.
Paper is always available as a fallback. A driver who must maintain RODS cannot treat paper as a permanent substitute for an ELD. Repeated paper use can trigger the ELD requirement, so dispatch and safety staff must track qualifying operations instead of relying on habit.
A single interstate trip changes nothing. One trip outside the short-haul conditions can bring full RODS and ELD requirements into play. The dispatch review should identify that change before departure, then preserve the reason for the decision.
Every older or specialized vehicle follows the same rule. Certain drive-away and tow-away operations, along with vehicles manufactured before model year 2000, may qualify under separate criteria. The file should support the exact exception. “The truck is old” or “the operation is specialized” is not enough.
Keep an exemption decision record for mixed, seasonal, and occasional operations. Identify the condition used, the supporting documents, and the event that requires a switch to full RODS or ELD use. Use this guide to electronic log device exemptions when setting up that process.
Owner's rule: If you cannot explain the exemption through the route, duty record, vehicle, and operating condition, you have an assumption, not a compliance process.
What to Do When the ELD Fails or Gets Revoked
An ELD failure becomes a compliance event as soon as the device cannot accurately record or display hours-of-service information. Registration status matters too. A device that loses approval or appears on an FMCSA revocation list cannot support required records, even if the driver has used it without prior issues.
Follow the recovery sequence
- Record the malfunction: Capture the displayed message or malfunction code, and preserve screenshots or other device details.
- Notify the carrier: Have the driver contact dispatch or safety promptly. Record who was notified and when.
- Reconstruct the records: Rebuild the current 24-hour period and the previous seven consecutive days if those records are unavailable or cannot be retrieved.
- Continue compliant records: Use paper logs or approved logging software while the device cannot perform its required function.
- Keep cab documentation ready: The driver should carry the malfunction instructions, current records, and a clear explanation for roadside review.
- Open a repair record: Save technician communications, service tickets, replacement details, and the date the issue was resolved.
- Verify the replacement: Confirm that the replacement is registered, connected, and able to record and transfer data before relying on it.
Paper records generally cannot continue beyond 8 days without an extension through the applicable process. Follow the FMCSA malfunction guidance, and apply for relief before the limit expires. A replacement unit that has not been tested is not a recovery.
A revoked device creates a separate exposure. If FMCSA directs the carrier to stop using it, follow the stated deadline and switch to paper logs or another compliant method while arranging replacement. Continued use can lead to citations and out-of-service consequences.
Use these FMCSA ELD compliance resources to turn the response into a written cab and dispatch procedure. The record should show the failure, notification, temporary logging method, repair, and verification. That audit trail gives a reviewer a clear sequence instead of an unexplained gap.
Practical Compliance Tips for Fleet Owners and Safety Managers
A clean log review catches problems before a roadside inspection turns them into citations. Review more than available drive time. The ELD specification does not require the device to identify every HOS violation, so your carrier must run independent exception monitoring (FMCSA ELD checklist).
Run the review around the record's weak points
- Certification: Confirm every record is reviewed and certified. Federal rules require the record of duty status to reach the carrier within 13 days after the 24-hour period covered by that record (49 CFR Part 395).
- Unassigned driving: Find unexplained movement, assign it to the correct user, and add an appropriate annotation.
- Edits: Review accepted and rejected edits. Make sure each explanation matches the underlying event.
- Equipment identity: Check the tractor, trailer, carrier, and driver information.
- Supporting documents: Reconcile shipping documents, dispatch records, fuel activity, remarks, and unusual stops.
- Transfer readiness: Confirm the driver can produce the current record and prior inspection history.
- Registration and malfunction status: Check the device status and open issues. Do not assume a service provider has resolved them.
Review the fleet weekly for recurring exceptions. Repeated unidentified driving, late certification, and missing remarks point to a process failure, even when individual entries appear minor.
Assign ownership in writing. Dispatch must flag route changes that may affect exemption status. Drivers need clear instructions for duty changes and malfunctions. Safety staff must preserve a review trail showing what was found, who corrected it, and when the correction was approved. That trail protects the carrier by showing deliberate oversight instead of unexplained gaps.
Frequently Asked Questions About CDL Log Books
What is a CDL log book?
A CDL log book records a commercial driver's duty status during each 24-hour period. The formal name is the Record of Duty Status, or RODS. It gives inspectors and carriers a clear record for reviewing hours-of-service compliance (FMCSA ELD frequently asked questions).
How long must you retain ELD records?
Six months, counted from the record date, applies to both the ELD RODS output and its backup data. Set a retention process that preserves readable records for the full period.
Do short-haul operations need a full log book?
An eligible short-haul operation can use time records instead of full RODS. Those records still need the driver's reporting time, release time, and total on-duty hours.
What happens when an ELD fails?
The driver should document the failure, notify the carrier, reconstruct missing records, and use paper logs or compliant logging software until the device works again. Treat the malfunction as a compliance event, not a minor technical inconvenience (FMCSA malfunction guidance).
How many days can you use paper logs after a malfunction?
Paper records generally cannot continue for more than 8 days unless an applicable extension applies. The carrier should address the failure promptly and keep evidence of the repair process.
What information must a RODS include?
A complete RODS identifies the date, miles, vehicle, trailer, carrier, driver certification, home-terminal time, remarks, co-driver, total hours, and shipping-document or commodity information (49 CFR §395.8).
Does the ELD identify every HOS violation?
No. The device records required data, but the carrier must review exceptions and compare the record with supporting trip information (FMCSA ELD checklist).
What should you do if a device is revoked?
Follow the stated removal deadline, preserve existing records, use the approved fallback process, and install a compliant registered device. Do not keep relying on a revoked unit.
My Safety Manager can organize ELD reviews, driver qualification oversight, CSA BASIC monitoring, and DOT compliance tasks. Visit My Safety Manager to manage the CDL log book process consistently.
