If you’re trying to understand FMCSA Supporting Documents Requirements, the big mistake is treating every trip paper like it has to stay in the cab forever. It doesn’t. Some records support hours-of-service, some belong in carrier files, and some are only there to help you through a roadside inspection.
This guide breaks that apart in plain English. You’ll see what counts as a supporting document, how long a carrier must keep it, what an ELD changes, and what a driver should actually have ready on the road.
What FMCSA Supporting Documents Are—and Why ELD Users Still Need Them#
FMCSA supporting documents are records from the driver or motor carrier that help verify a driver’s time, location, and duty status. Even if you use an Electronic Logging Device, or ELD—the device that records hours-of-service activity electronically—you still need source records that back up the RODS, or Records of Duty Status, when those records exist.
Under 49 CFR Part 390, FMCSA compliance duties depend on the operation, driver, and vehicle involved. That matters because there is no one universal paperwork stack that applies the same way to every truck, trip, or carrier.
Supporting documents are evidence behind a driver’s record of duty status#
A supporting document is basically proof behind the log. It can show where the truck was, when something happened, and whether that timing lines up with the driver’s duty status.
That proof can come from normal business records like dispatch notes, receipts, or shipping records. The key is not whether the paper looks official. The key is whether it helps confirm on-duty, driving, or off-duty activity.
An ELD records duty status, but it does not replace source records#
An ELD creates the electronic log, but it doesn’t replace every other trip record. If you fuel, cross a scale, get a dispatch message, or sign a delivery receipt, those records may still help explain or support what the ELD shows.
That’s why supporting documents still matter during a compliance review or investigation. They help a carrier show that the log record is backed by real-world trip activity instead of standing alone.
Separate supporting documents from roadside paperwork#
This is where a lot of drivers get crossed up. Supporting documents are mainly about hours-of-service support and carrier retention, not a blanket list of papers that must always ride in the truck.
A CDL, registration, insurance evidence, permits, or shipping papers may matter at roadside for other reasons. But that is different from the FMCSA supporting-document rule under 49 CFR Part 395.
Which Records Count as FMCSA Supporting Documents?#
FMCSA supporting documents usually include business records that can verify a driver’s duty status, date, time, or location. Under 49 CFR Part 395, common categories include bills of lading, itineraries, schedules, dispatch records, expense receipts, payroll records, settlement sheets, and electronic mobile communications.
Common supporting-document categories#
A bill of lading is the shipping document that identifies the freight and shipment details. An itinerary is a planned trip or stop schedule. A settlement sheet is a payment record showing load or trip compensation details.
FMCSA’s examples and categories include records such as:
- Bills of lading
- Itineraries
- Schedules
- Dispatch records
- Expense receipts
- Electronic mobile communication records
- Payroll records
- Settlement sheets
- Similar records that help verify hours-of-service activity
In real life, that can include a fuel receipt, scale ticket, toll record, delivery receipt, dispatch message, or pay record. Not every one of those will count every time, but each can become relevant if it helps verify a driver’s status, time, or place.
The four details that make a document useful#
A qualifying supporting document may contain four basic details: the driver’s name or identification number, date, location, and time. Those details are what make the document useful for matching trip activity to the driver’s log.
That doesn’t mean every record with one trip detail automatically qualifies. A document tied to a load but not tied clearly to the driver’s duty status may not do much for hours-of-service support.
Examples that may contain more than one required detail#
A fuel receipt might show a time stamp, date, and location. A scale ticket may show date, location, and truck information. A dispatch message may show the driver, load reference, and timing of an instruction.
That matters because one record can carry several data points at once. A record that helps place the driver in a certain place at a certain time is more useful than a random paper with no clear tie to the trip.
How Many Supporting Documents Must Be Kept—and for How Long?#
Under 49 CFR Part 395, a motor carrier must retain up to eight supporting documents for each driver for each 24-hour period, drivers must submit supporting documents within 13 days after receiving them, and carriers must keep those documents for six months from the date they receive them.
The eight-document retention limit per driver per 24-hour period#
The rule in § 395.11 is often shortened to the “eight-document rule.” For each driver and each 24-hour period, the carrier must retain up to eight supporting documents, following the selection and retention rules in Part 395.
That does not mean you should stop collecting records after eight exist. It means the regulation sets a retention framework for supporting documents tied to hours-of-service review.
The six-month carrier retention period#
The motor carrier’s job lasts longer than the driver’s handoff. Once the carrier receives the supporting documents, it must retain them for six months.
That retention period matters during audits because the issue usually isn’t whether a driver once had the record. The issue is whether the carrier can still produce it when asked.
The 13-day submission timeline#
Drivers must submit supporting documents to the motor carrier within 13 days after receiving them. That includes records that come in electronically, not just paper receipts tucked in the visor.
This is where small operations get burned. A receipt that stays on your phone camera roll with no upload, no label, and no match to a duty date is easy to lose when someone needs it fast. If your process feels shaky,
What to do when records arrive electronically#
If the document comes by app, email, dispatch platform, or text-based system, don’t assume it’s “already in the system” and therefore handled. Confirm where it lives, how it’s tied to the driver and date, and whether the carrier can retrieve it later.
A simple process works best: upload or save it promptly, label it by driver and duty date, and make sure the carrier can find it without digging through unlabeled files.
How to Handle Documents Missing a Date, Time, Location, or Driver ID#
A supporting document should normally include the driver’s name or ID plus the date, time, and location. But if a driver has fewer than eight supporting documents and some do not contain all four elements, FMCSA allows a document to still be used if it includes the driver’s name or ID and at least one of the other key elements.
The standard information a supporting document should contain#
The cleanest record includes all the basics: driver name or ID, date, location, and time. That gives the carrier something solid to compare against the ELD record and trip activity.
When one of those pieces is missing, the document may still have value. But incomplete records are harder to defend and harder to sort during an audit.
The rule for fewer than eight documents#
If you have fewer than eight supporting documents and some don’t show all four elements, FMCSA’s rule allows a narrower standard. A document may still be acceptable when it has the driver’s name or ID plus the date, location, or time.
That is an exception, not a shortcut. It doesn’t mean you should throw away fuller records or rely on weak paperwork when better records exist.
How to avoid creating an incomplete record trail#
Don’t alter the record to make it look complete. Keep the original document, attach it to the right duty date, and preserve related records like dispatch messages or ELD activity that help explain it.
The goal is a believable trail, not a perfect stack of paper. If a receipt is thin on detail, pair it with the related trip record instead of trying to make the receipt do all the work.
What Belongs in the Truck Versus the Carrier’s Records#
Most FMCSA supporting documents are carrier-retained records, not a universal in-cab paperwork list. Drivers still need certain credentials, shipping papers, permits, and ELD materials available on the road, but many hours-of-service support records are meant to be submitted to and retained by the carrier rather than permanently kept in the truck.
Documents and information that may be reviewed during a roadside inspection#
A Commercial Driver’s License, or CDL, is the license required to operate certain commercial motor vehicles. A USDOT number is the federal identification number used to track a carrier’s safety and compliance record.
At roadside, an officer may ask for documents tied to the vehicle, driver, cargo, or trip. That can include registration, proof of insurance, CDL, shipping papers, permits where applicable, and inspection-related records depending on the operation.
Records that should be accessible through the ELD#
FMCSA’s ELD guidance makes clear that ELD users must be able to display and transfer applicable hours-of-service records for an inspection. Drivers also need the required ELD instruction materials and, when required by the ELD regulations, blank grid graphs.
Knowing how to transfer ELD data matters just as much as having the device mounted. A driver who can’t produce or transfer the record during an inspection can create a roadside problem fast.
Carrier files that do not need to ride in the cab#
Under 49 CFR Part 396, vehicle inspection, repair, and maintenance records have their own recordkeeping rules. Those are different from hours-of-service supporting documents under Part 395.
That means a generic “everything DOT-related goes in the truck” approach is sloppy. Some records belong in the cab, some belong in your carrier file system, and some need to be available electronically instead of in paper form.
Why state and operation-specific requirements can add paperwork#
Required in-vehicle documents can change based on cargo, permits, state rules, and how the carrier operates. Interstate and intrastate operations can also bring different paperwork demands.
If you need to verify a carrier’s operating record or status, use SAFER. Treat online cab checklists carefully, because they often mix federal, state, permit, and company paperwork into one misleading list.
A Simple Supporting-Document System for Owner-Operators and Small Fleets#
A good supporting-document system is simple: capture records as they happen, label them clearly, match them to the right driver and duty date, keep them for the required period, and make sure they can be retrieved fast. The real test is not storage alone. It’s whether you can find what you need before an audit turns into a scramble.
Capture records as they are created#
Don’t wait until the end of the week. As receipts, tickets, and delivery records come in, photograph or upload them right away.
That habit matters most for one-truck owner-operators because the same person is driving, dispatching, billing, and filing. Delay creates gaps.
Tag every record for retrieval#
Use a consistent file label. A practical label includes driver name or ID, date, truck number if needed, document type, and trip or load reference.
That beats a phone folder full of filenames like IMG_4821. Searchable records save time when someone asks for proof later.
Match records to the correct driver and duty date#
This is where compliance systems either work or fall apart. A document has to connect to the right driver and the right 24-hour duty period, not just the right customer or load.
Check that your ELD, dispatch, accounting, and document storage process don’t leave blind spots between systems.
Review exceptions before an audit or investigation#
Set a routine to review records with missing details, late uploads, or mismatched dates. Fix the filing issue while the trip is still fresh instead of months later.
Audit prep should feel like record retrieval, not detective work. If you’re not sure what system fits your operation,
Test whether records can be searched and exported#
Before you trust any setup, test it. Can you search by driver? By date? Can you export a clean set of records if an auditor asks?
If the answer is no, the system is only half-built. For a small fleet, simple and searchable usually beats fancy and messy.
FAQ#
What are the FMCSA requirements?
FMCSA requirements are not one single checklist. For supporting documents and logs, start with hours-of-service rules under 49 CFR Part 395. For broader carrier and driver obligations, look at 49 CFR Part 390. For vehicle inspection, repair, and maintenance records, use 49 CFR Part 396. Then layer on any state, cargo, permit, or operation-specific rules that apply to your truck. That’s why a good answer always depends on what you haul, where you run, and whether you’re looking at roadside paperwork, log support, or carrier file retention.
If I have fewer than eight supporting documents that don’t contain all four required items, which element is considered acceptable?
If you have fewer than eight supporting documents, a record may still be acceptable if it includes the driver’s name or ID plus at least one of these: date, location, or time. The safer move is to keep the original record exactly as it was created and preserve related evidence, like dispatch records or ELD activity, that helps explain it. Don’t rewrite the document or try to “fix” it by hand unless your carrier has a formal process that preserves the original. The point is to show a credible record trail, not create a cleaner-looking one after the fact.
What are 10 important documents used in transportation?
A practical list includes the bill of lading, rate confirmation, proof of delivery, fuel receipt, scale ticket, dispatch record, ELD record, vehicle registration, proof of insurance, and inspection report. Those are common transportation documents, but they do different jobs. Some help prove freight details, some help support hours-of-service, and some are there for licensing or roadside review. Not all ten are FMCSA supporting documents in every situation, and not all are required for every operation. The right list depends on your equipment, cargo, authority, state rules, and how your carrier handles records.
What documents should be in a dot vehicle?
Build an operation-specific cab checklist instead of relying on a generic internet list. Common items may include the driver’s CDL, registration, proof of insurance, permits when required, shipping papers, and any ELD instruction materials or blank grid graphs required by the ELD rules. Some records belong in the truck because they may be reviewed roadside. Others belong in the carrier’s retained files and do not need to live in the cab full time. Check your state rules, cargo type, permit needs, and carrier policies so your in-vehicle documents match your actual operation.
Why do supporting documents still matter if I already use an ELD?
Supporting documents still matter because the ELD shows the log record, while source documents can help verify whether that log lines up with real trip activity. A fuel receipt, dispatch message, scale ticket, or delivery receipt can help explain where a driver was and when. During an audit or investigation, that matters. ELDs reduce manual log problems, but they don’t erase the need for records that support the log when those records are created in the normal course of business. Think of the ELD as the timeline and supporting documents as the proof behind parts of that timeline.
