Roadside inspection: how the transfer works

← All guides

A roadside inspection feels tense mostly because it feels unknown. In truth, the hours part of the stop follows a set pattern, and the rules wrote that pattern down. The officer wants to see your record for today and for the seven days before today. Your electronic logging device, the ELD, holds those records. You show them on the screen, and when the officer asks for the file itself, you transfer it in the way the officer names.

That is the whole job. You do not have to explain the whole week from memory. You do not have to rebuild anything at the window. The record speaks, the screen shows it, and the transfer sends a copy of it. This guide walks through the stop step by step, explains what the officer actually sees in each form, and lists the paper packet the rules require you to carry in the cab so the stop never turns on a missing sheet.

The stop, step by step

Stops vary a little by state and by officer, but the order below is the order the rules expect. Learn it once and you will recognise it every time.

1. The officer asks for your records

   The request is for the current day and the previous 7 consecutive days. That is eight days in total: today, still in progress, plus the full week behind it. Stay polite, keep your hands where the officer can see them, and let the officer lead. If you are in the middle of driving, the inspection starts when you are safely stopped.

2. Show the display first

   Open the roadside or inspection view on the ELD. The display shows a graph grid for each day, much like the old paper grid, plus the day's events: duty statuses, the times they started and ended, locations, and miles. The officer can look day by day. The screen works on the device itself, so a weak signal in the area does not block the display. The records live on the device and the display works offline.

3. The officer names a transfer channel

   If the officer wants the file, the officer will name the channel their system uses. You do not have to guess, and you do not have to offer a different one. Follow the steps for that channel on the instruction sheet in the truck. That sheet exists for this exact moment, when thinking clearly is hardest.

4. Add an output file comment if you are asked

   The officer may direct you to enter an output file comment on the record before transfer, under 49 CFR 395.24(c)(1)(iii). Type in the words the officer gives you, in the place the device shows for it. The comment rides with the file. It is part of the record for that transfer, not a note you add on your own.

5. Send the transfer

   Complete the sending steps and wait for the device to show that the transfer is done. If a channel fails because of the area you are in, say so plainly and follow the instruction sheet for the other steps it lists. The display itself stays available the whole time, so the officer can still read the record on screen.

6. Keep your copy and carry on

   The transfer sends a copy. Your records stay on your device and with your carrier, just as before. If the officer raises anything about a day, answer from the record on screen rather than from memory. When the stop ends, note the time and place for yourself while it is fresh.

What the officer sees on the screen

The display is built for a quick read at a window. For each day it shows the graph grid: a line across the day that steps between off duty, sleeper berth, driving, and on duty not driving. Under or beside the grid sit the day's events in order, with duty statuses, times, locations, and miles.

That matters for you in two ways. First, what the officer reads is the same record you see when you check your own day. There is no second, hidden version. If you look at your graph each day when you certify, you already know what an officer will see. Second, the grid makes gaps easy to spot. A missing location, a status that runs far longer than the work it covers, or a day that was never reviewed stands out on a grid in a way it never did in a stack of paper. A two-minute look at your own grid each evening is the cheapest inspection practice there is.

What the officer gets in the file

The transferred file is the standard output file described in Appendix A, section 4.8.2. Standard is the key word. The file carries header information — the carrier, the driver, the truck, and the dates — and the event records for the days requested. Each event record carries a data check, a kind of built-in mark that lets the officer's software confirm the record reads as a true record.

Because the file follows one standard, the officer's software reads it the same way regardless of brand. Your device does not send a picture of a log or a file only its own maker can open. It sends the same shaped file every ELD sends. That is why the officer can name a channel and expect it to work with the device in your truck: the channel and the file shape were both settled in the rule, long before your stop.

The two families of transfer

Appendix A, section 4.8.1, sets out transfer in two families. A device must support at least one option, and each option has two channels:

• Option 1, telematics: web services and email. The file travels over a network connection from the device to the officer's system.
• Option 2, local: a USB drive and Bluetooth. The file moves directly between the device and the officer's equipment, at the truck.

You do not need to master all four channels as theory. You need to know where your instruction sheet is, how your device starts a transfer, and how to follow the officer's choice on the day. Transfer channels differ by area: a network channel needs a connection, a local channel does not. The officer knows what works where they are working, which is one more reason the officer names the channel and you follow it.

One point deserves repeating, because it settles a common worry: no signal is no excuse for the display itself, and no signal is needed for it. The records live on the device. Opening the inspection view and showing eight days of grids works in a dead zone, in a tunnel of trees, anywhere. Signal only affects which sending channel can complete, never whether you can show your record.

Supporting documents at the window

The ELD record is the centre of an hours inspection, but it is not the only paper an officer can ask about. Under 49 CFR 395.11(g), a driver must make available, on request at roadside, any supporting document in his possession. Supporting documents are the papers of the trip — the kind of records that sit in the cab door pocket, a folder, or a phone — and the rule asks for them in whatever format the driver has them.

The practical lesson is simple: keep the trip's papers together and reachable, not scattered between the cab, the trailer, and home. If a document is in your possession and an officer asks for it, you hand it over. Keeping the folder tidy all week beats hunting for one sheet at the window.

The paper packet that must be in the truck

The ELD did not end paper in the cab. It changed which paper rides along. Under 49 CFR 395.22(h), the carrier must ensure the driver has onboard, in the vehicle:

1. An instruction sheet describing the data transfer mechanisms and the step-by-step for producing and transferring records to an officer.
2. An instruction sheet describing malfunction reporting and recordkeeping during a malfunction.
3. A supply of blank record-of-duty-status graph-grids sufficient for at least 8 days.

Read that list as three answers to three bad moments. The first sheet answers this guide's moment: an officer is waiting and you need the transfer steps in order, not from memory. The second answers the day the device fails: what to report, to whom, and how to keep the record by hand. The third is the paper itself for that day — enough blank graph-grids for at least 8 days, so a failure on a long run never leaves you without a lawful way to record your hours.

Check the packet the way you check fuel: before it matters. Sheets go missing during cab clean-outs. Blank grids get used as scrap paper. A packet checked on Sunday is a stop that stays simple on Thursday. The ELD user's manual should also be where the driver can reach it — the provider supplies the manual, and the sensible place for it is with the packet, in the cab, not in an office drawer two states away.

When the device cannot produce the records at all

There is one stop this guide does not cover, because the rules give it its own drill: the day the ELD truly fails and cannot produce the records. That is a malfunction, and 49 CFR 395.34 takes over — you show the hand-kept records you have been making on paper, and a separate set of clocks starts for fixing the device. The full drill, in order, is in our guide When the ELD breaks: the malfunction drill. The short version for the window is this: a broken device handled the way the rule says is a paperwork problem. A broken device ignored is a violation. The packet in your cab is what lets you handle it the first way.

A calm stop is a prepared stop

Nothing in an hours inspection is meant to be a memory test or a trick. The officer asks. The display shows eight days. The officer names a channel. You follow the sheet, add a comment if you are asked, and send the file. Drivers who find inspections stressful are usually missing one small thing — a sheet, a habit of looking at the grid, blank grids that ran out — and every one of those is fixable before the next stop. Look at your own grid today, check the packet tonight, and the next blue lights in the mirror become a routine stop instead of a bad day.

Rules checked October 2026. Rule sources: 49 CFR 395.24; 49 CFR 395.22(h); 49 CFR Part 395, Subpart B, Appendix A, sec. 4.8.