The electronic logging device mandate solved the hours of service falsification problem that paper logs created. It did not eliminate the documentation obligations that surround hours of service compliance. ELD data is the core of an HOS record, but it is not the complete record. FMCSA regulations require carriers to maintain a set of supporting documents that corroborate the driver’s electronic log, and the absence or inaccessibility of those supporting documents creates compliance exposure during roadside inspections and carrier safety audits that the ELD data alone cannot resolve. Most carriers manage ELD data reasonably well because the mandate forced them to. Most carriers manage supporting documentation poorly because no single mandate forced a systematic approach to it.
What FMCSA Actually Requires Beyond the ELD
Under 49 CFR Part 395.11, motor carriers are required to retain supporting documents for each driver’s record of duty status. Supporting documents are records that can be used to verify the accuracy of a driver’s ELD data, and they include a specific set of document categories:
- Bills of lading, itineraries, schedules, or equivalent documents showing the starting and ending location of each trip
- Dispatch records, trip records, or equivalent documents
- Expense receipts related to on-duty not driving time including fuel receipts, weigh station tickets, and similar records
- Fleet management system communications including records of driver instructions, vehicle location data, or similar information generated by a fleet management system
- Payroll records, settlement sheets, or equivalent documents showing the driver’s compensation for the period
Carriers must retain these supporting documents for six months from the date of receipt. Critically, if a supporting document shows information that conflicts with the driver’s ELD record, the carrier has an obligation to investigate and resolve the discrepancy. An unresolved conflict between a supporting document and the ELD record is itself a compliance finding.
Why Supporting Documents Matter in an ELD World
The ELD captures when and where a driver’s duty status changed. It does not independently verify that the duty status reflected what the driver was actually doing. Supporting documents provide the corroborating evidence that the ELD record accurately reflects the driver’s actual activities. During an FMCSA compliance review or a roadside inspection where the ELD data raises questions, the supporting documents are what investigators use to either confirm or challenge the accuracy of the electronic record.
The most common HOS-related compliance finding in carrier safety audits is not ELD malfunction or falsification. It is the inability to produce complete, organized supporting documentation that corroborates the driver’s record of duty status. Carriers who maintain excellent ELD data but cannot produce the supporting document set face the same finding as carriers with incomplete records.
The Volume and Variety of Supporting Documents a Carrier Manages
A single driver working five days per week generates supporting documents across multiple categories every day. A fleet of 50 drivers generates thousands of individual supporting documents per month that must be retained, organized, and retrievable for six months. The scale of that documentation obligation is significant, and the variety of document sources compounds the challenge:
- Fuel receipts arrive from driver-submitted photos, fuel card transaction records, and paper receipts turned in at the terminal
- BOLs and delivery receipts are generated at pickup and delivery points in formats that vary by shipper
- Dispatch communications are generated in TMS systems, messaging platforms, and email threads that may not be systematically archived
- Weigh station receipts, toll records, and scale tickets arrive as paper documents from the cab
- Fleet management system location data may be stored in a separate system that is not integrated with the document record for the corresponding trip
When these documents arrive through different channels and are stored in different systems or physical locations, assembling a complete supporting document set for any given driver and date requires a time-consuming manual search that most carriers cannot execute quickly under audit pressure.
How Document Management Organizes Supporting Documentation
A document management system transforms supporting document retention from a reactive scramble into a proactive, system-driven process:
- Fuel receipts submitted by drivers through mobile capture are automatically indexed to the driver record and the corresponding trip date without manual filing
- BOLs and delivery receipts captured at pickup and delivery are linked to the trip record, connecting the load documentation to the HOS supporting document requirement automatically
- Dispatch communications archived from the TMS or messaging platform are stored with appropriate metadata connecting them to the driver and the date
- Paper receipts collected during trips are captured through mobile upload at the end of each day and indexed to the corresponding duty period
- Fleet management system location data is exported and archived with appropriate metadata to support corroboration of the ELD record
Paperwise supports transportation carriers in building driver-centric document archives that connect ELD supporting documents to the correct driver and duty period automatically, making the complete supporting document set retrievable in minutes rather than hours.
Retention Management and Audit Readiness
The six-month retention requirement for HOS supporting documents is straightforward on paper but operationally demanding at scale. A carrier with 50 drivers retaining supporting documents across all required categories is managing tens of thousands of individual records with a rolling six-month retention window. Manual retention management through filing systems that require periodic purging is unreliable and often results in either premature destruction that creates compliance gaps or indefinite accumulation that creates storage overhead.
Automated retention scheduling addresses this without manual oversight:
- Documents are assigned the correct retention period at the point of capture based on document type and driver association
- The retention clock starts from the date of receipt or creation automatically
- Documents approaching the end of their retention period are flagged for review rather than deleted automatically, providing a confirmation step before destruction
- Destruction is documented in a log that records what was destroyed and when, supporting any future inquiry about retention compliance
Responding to Roadside Inspections and Safety Audits
The practical test of supporting document management is whether the carrier can produce a complete, organized set of records quickly when an investigator requests them. At a roadside inspection, time pressure is immediate. During an FMCSA compliance review, the response window is defined and the completeness of the response directly affects the review outcome.
A document management system with driver-centric organization and full-text search capability allows safety staff to produce the complete supporting document set for any driver and any date range in minutes:
- All fuel receipts, BOLs, and dispatch records for a specific driver over a specific period are retrieved through a single search
- Documents are presented in an organized format that demonstrates systematic retention rather than ad hoc collection
- The complete record with timestamps and chain of custody information supports the carrier’s position that records are authentic and unaltered
Contact the Paperwise team to discuss how HOS supporting document management works alongside your existing ELD system and where the most significant compliance gaps exist in your current documentation approach.
