Pre-trip inspection checklist: the list, the rule, the proof

This post in 30 seconds.

• The rule splits in two, and most checklists blur it. The pre-trip is a duty to be satisfied the truck is safe (49 CFR 392.7 and 396.13). The DVIR is an end-of-day report, and for property carriers it is only required when a defect was found (396.11).
• The number that matters: in CVSA's 2025 International Roadcheck, 18.1% of vehicles inspected were placed out of service, and brakes, tires and lights led the violations. All three are on the walkaround.
• The problem a checklist cannot fix: a faked check and a real one produce the same tick. Only evidence on the exceptions tells them apart.
• Who this is for: fleet managers and safety or compliance managers at a US carrier or private fleet who need drivers to do the check, not just sign it. If you run under a UK O-licence, there is one paragraph for you near the end.

Watch a driver open the inspection app at 05:40. Thumb down the list: no defects, no defects, no defects, sign. Twenty-eight seconds, and the truck is rolling before the coffee is cold.

Nothing in the record says that happened. The form is complete, the signature is there, and the timestamp reads 05:40. If that tractor loses a brake chamber on the interstate at nine, the record says a proper check was done four hours earlier.

If you manage a fleet, you already know which drivers do the real thing and which do the thumb version. What you cannot do is prove the difference from the paperwork, and that is the gap this post is about. It covers the checklist itself in walk order, what the federal rule asks in plain words, why the check gets faked and how to make the honest version the faster one, and how to get a photo or a short video on every item that fails so the record shows what the driver saw.

Safety managers carry this one personally, because "the pre-trip was done" is a sentence you have to be able to stand behind after a crash. We build Venta Capture, a product of VentaVid, so the person standing at the truck can record the defect properly the first time, on the phone in their pocket, with the time and the place attached. Start a free account and run one walkaround through it before you judge it against your current form.

In this post:

• The short answer
• What the rule asks of the driver and the carrier
• The pre-trip inspection checklist, in walk order
• Why the check gets faked, and how to make the real one faster
• Photo and video per item: what to ask the driver for
• Frequently asked questions

The short answer

Before the truck moves, the driver has to be satisfied that eleven named parts are in good working order, and has to review and sign the last inspection report if there was one. That is the pre-trip, and it lives in 49 CFR 392.7 and 396.13.

When the day's work is done, the driver writes a report on any defect found or reported. That is the driver vehicle inspection report, or DVIR, in 49 CFR 396.11. Since December 2014, a driver of a property-carrying vehicle does not have to file one when nothing was found.

The carrier fixes the defect, or certifies that repair is unnecessary, before the vehicle goes out again, and keeps the report and the certification for three months. Electronic reports are fine. FMCSA put that in the text explicitly in a final rule published on 19 February 2026, effective 23 March 2026.

A checklist covers the first duty. A record that shows what was found, when, and what happened next covers the other three. Most fleets are strong on the first and weak on the rest.

What the rule asks of the driver and the carrier

I read the three sections side by side again for this piece, because most articles paraphrase them into a single "DOT requires a daily inspection" and that blur is where fleets get caught. Each section asks for something different, and none of them names a fine amount, whatever other posts like to invent.

392.7: be satisfied, on eleven items

No commercial motor vehicle may be driven unless the driver is satisfied that these parts and accessories are in good working order:

• Service brakes, including trailer brake connections
• Parking (hand) brake
• Steering mechanism
• Lighting devices and reflectors
• Tires
• Horn
• Windshield wiper or wipers
• Rear-vision mirror or mirrors
• Coupling devices
• Wheels and rims
• Emergency equipment

Note the verb: satisfied. The section does not prescribe a form, a duration or a walk order. It puts a judgement on a named person before the vehicle moves.

396.13: review and sign the last report

Before driving, the driver must be satisfied the vehicle is in safe operating condition, review the last DVIR if one was required, and sign it to acknowledge the review and that the required repairs are certified as done. The signature step does not apply to defects on a towed unit that is no longer part of the combination. Paragraph (d), new this year, says the report can be created and kept electronically under 390.32.

396.11: the end-of-day report, when there is something to report

Every driver prepares a written report at the completion of each day's work on each vehicle operated. The report identifies the vehicle and lists any defect or deficiency the driver found or was told about that would affect the safety of operation or result in a mechanical breakdown, across the same eleven items. The driver signs it, and on a two-driver operation one signature is enough if both agree on the defects.

Then the part that is about you rather than the driver. The carrier, or its agent, certifies on the report that the defect has been repaired or that repair is unnecessary, before requiring or permitting a driver to operate the vehicle. The carrier keeps the report and the certification for three months from the date the report was prepared.

And the sentence most drivers still get wrong: "Drivers are not required to prepare a report if no defect or deficiency is discovered by or reported to the driver." That has been the rule for property carriers since a final rule effective 18 December 2014. FMCSA estimated at the time that drivers were spending 46.7 million hours a year on no-defect reports, that the change removed roughly 95% of the reports being filed, and that the inspection duty itself did not change (Bulk Transporter's account of the rule has the numbers). Passenger carriers are treated differently and still file no-defect reports.

So the driver daily defect report is an exceptions document, and that is the design principle for everything below. A record that exists only when something was found is a stronger record than a pile of identical clean forms, provided you can show the check happened.

Two consequences worth writing into your own policy:

• A nil pre-trip still needs a trace. The regulation does not require a form for it, but your insurer, your safety rating and the plaintiff's lawyer will ask how you know the check took place. Decide what that trace is (a scan at the truck, a time-on-check, two fixed photos) and make it light.
• The three-month clock runs on the report, and so does your data retention policy. If your evidence system purges media at 60 days, your DVIR photos will disappear before the retention period ends. Set retention on the case, not on the file.

The pre-trip inspection checklist, in walk order

The list below follows the seven-step method in FMCSA's Model Commercial Driver License Manual, because it is the order your drivers were taught and the order that survives a cold yard. Items marked (392.7) are the eleven the regulation names. Everything else is what stops a truck at a roadside inspection anyway.

Build your form in this order, not in the order a spreadsheet was typed. A checklist that jumps from tires to horn to fifth wheel gets done from the cab.

1. Approach and overview

• General condition. Leaning to one side, fresh oil, coolant, grease or fuel under the vehicle.
• Around the truck. People, other vehicles, low wires, objects in the path.
• Last report. Review the previous DVIR if one was required; confirm the certification of repair before you sign (396.13).

2. Engine compartment

• Fluids. Oil, coolant, power steering, windshield washer at the marks; no leaks along hoses and fittings.
• Belts and hoses. Cracks, fraying, rubbing, correct tension.
• Steering components. Box secure, no leaks, linkage and tie rods tight (392.7).
• Front suspension. Springs, shocks, U-bolts, no cracked or shifted leaves.
• Front brake. Chamber, slack adjuster, lines and drum or rotor (392.7).

3. Inside the cab

• Start-up. Oil pressure rises, air pressure builds, voltmeter charging, no warning lights left on.
• Mirrors, wipers, washers, horn (392.7 for all four).
• Steering play. More than about two inches on a twenty-inch wheel is a defect (392.7).
• Emergency equipment. Fire extinguisher charged and secured, three reflective triangles, spare fuses if the truck uses them (392.7).
• Seat belt, glass, heater and defroster.

4. Lights and reflectors

• Headlights, low and high; four-way flashers; clearance and marker lights; reflectors clean and unbroken (392.7).

5. Walkaround: front, driver side, rear, passenger side

• Front. License plate, bumper, lights, windshield.
• Steer axle. Tire condition (the ABCs: abrasions, bulges, cuts), inflation, tread at least 4/32 inch in a major groove on the steer axle (393.75); rim cracks, lug nuts tight with no rust streaks, hub oil level and no leaks (392.7, tires and wheels).
• Fuel tank and cap, exhaust, frame and crossmembers, driveshaft, mud flaps.
• Drive axles. Tires at 2/32 inch or better, matched duals with nothing lodged between them, brake chambers and slack adjusters, air lines not chafed (392.7).
• Rear. Lights, reflectors, license plate, doors and latches, load secure.
• Coupling. Fifth wheel locked around the kingpin with no gap, release arm in, glad hands seated and lines not dragging, electrical cord connected (392.7).

6. Trailer

• Front and sides. Header board, landing gear raised and handle secured, side lights and reflectors, tandem release locked.
• Tires, wheels and brakes on every axle, same standard as the tractor.
• Rear. Lights, reflectors, ICC bumper, doors, seal number if sealed, cargo secured.

7. Signal check and brake tests

• Turn signals and brake lights front and rear with a second person or against a reflective surface.
• Air brake tests. Air build-up to governor cut-out, applied leak test with the engine off, low-air warning device, spring brake pop-out, then a tug test against the trailer brakes and against the tractor parking brake (392.7, service and parking brakes).

That is the full check. Done by a driver who knows what to look at, it takes fifteen to twenty minutes on a tractor-trailer, in the words of Rob Carpenter writing for FreightWaves.

The inspection checklist is not the hard part. Getting the fifteen minutes is.

Where the truck fails an item, the driver needs a way to say how badly. A cracked leaf spring and a marker light out are both defects, and one of them means the truck does not move. Decide your defect classification in advance, in two or three tiers, so the driver picks one rather than describing it in a free-text box at 05:45.

The tiers are a starting point. Your shop and your insurer may draw the lines differently, and the driver is still the person who decides whether they are satisfied under 392.7.

Why the check gets faked, and how to make the real one faster

The Carpenter piece has the clearest description of the failure I have read.

The driver "taps the 'no defects' button, signs it electronically, and starts driving. Total time: 30 seconds. Total inspection: none. The DVIR exists. It is completed. It is filed. It is also fiction."

Nobody does that because they are careless about brakes. They do it because of how the morning is built.

• The time is unpaid. A driver on mileage pay earns nothing for the fifteen minutes. The check is off the clock in practice even where it is on duty on paper.
• Dispatch wants the truck moving. A policy that says "thorough pre-trip" and a dispatcher who says "rolling by six" are in direct conflict, and the dispatcher speaks last.
• The form rewards the tap. Eleven yes boxes take twenty seconds. A real finding takes a description, a call and possibly a lost load. The form punishes honesty with paperwork.
• The tick looks identical either way. A real check and a fake check produce the same record. Nobody upstream can tell, so nobody upstream reacts.

A fleet where the walkaround records are always clean has not found a way to run perfect trucks. It has found a way to stop reporting. Carpenter's version: a fleet with 500,000 to a million miles on the trucks and no defect DVIRs "has a pencil-whipping checklist," not a DVIR program.

The roadside numbers say what a real check would find. In CVSA's 2025 International Roadcheck, inspectors ran 56,178 inspections over three days in May and placed 10,148 vehicles, 18.1%, out of service. Brake systems accounted for 24.4% of vehicle out-of-service violations, tires for 21.4%, and lights for 12.8%.

Every one of those is a walkaround item a driver can see, hear or measure in the yard. Roadcheck is not a random sample, and the fleets stopped skew towards the ones inspectors have reason to look at. It still says that when an examiner looks, there is usually something to find, and most of it is on the list above.

So design the morning so the honest check is the fastest path through it.

1. Pay for the time or schedule it, and tell dispatch. Fifteen minutes on the clock before the first pickup, in the plan, so nobody has to steal it.
2. Make the form follow the walk. Seven zones in the order the driver moves. A form that matches the vehicle walkaround can only be completed at the truck; a form that jumps around can be completed anywhere.
3. Photos on the exceptions only, plus two fixed shots. A picture of every item turns fifteen minutes into forty and produces sixty useless images. A picture of every failed item, plus two fixed proof shots (the tire and wheel on the steer axle, the coupling), takes ninety seconds and proves presence.
4. Show time-on-check to the driver and the manager. Show it as a number, without turning it into a trap. A 90-second check on a combination is a conversation, and drivers know it.
5. Spot-check against the record, not the driver. Pick three trucks a week and walk them yourself after the pre-trip. A spot check that finds a defect the form missed is your training material for the toolbox talk.
6. Consequences for the fake, never for the finding. The driver who reports the cracked leaf spring and loses two hours must never come off worse than the one who tapped through. If the reporter gets the grief, you have taught the whole yard to tap.
7. Close the loop where the driver can see it. A defect that vanishes into a maintenance system with no answer teaches drivers that reporting is pointless. The inspection sign-off should come back to the driver who raised it.

If you want to see what an exceptions-only flow looks like against your own form, book a demo and bring last month's DVIRs.

Photo and video per item: what to ask the driver for

Think about what the shop learns from "brake chamber leaking, driver side rear." They learn to walk to the driver side rear. They do not learn whether it is a hiss at the fitting or a chamber split open, whether the slack adjuster is out of range as well, or whether the truck was safe to bring in or should have been towed. The fitter finds out when the truck arrives, which is the expensive moment to find out.

A timestamped photo and twenty seconds of the driver talking over the defect answer most of that before anyone touches a wrench. That is the point of putting evidence on the exceptions. The person who has to make the first decision gets to see the defect before the truck arrives.

When the check runs through a guided capture link rather than a tick sheet, the flow looks like this. The driver receives a secure, personal capture link, or scans a QR code in the cab, and the whole thing runs in the phone's browser. No app, no account, in the driver's own language.

1. Scan the unit. A QR or barcode on the door pillar opens the flow already tied to that tractor. A torch for a dark yard, and a typed fallback.
2. Confirm the driver and the trailer. Name and driver number, trailer number, whether it was coupled this morning. The one field that closes the most common gap in fleet records.
3. Walk the seven zones as yes or no. Each zone in walk order, with a required-items counter so the driver can see what is left.
4. A "no" opens a photo slot. With an example photo showing the angle you want and one line of instruction: "hand or tape next to the damage for scale." Scale cannot be added afterwards.
5. Offer the video. "Point at it and tell us what you can see and hear." The spoken note is transcribed and searchable on the case, and a hiss on a recording is worth more than "leak" in a box.
6. Ask the two questions that route the case. Is the vehicle safe to move, and has it been tagged out. A "no" on the first goes straight to the duty manager, not into a queue.
7. Nil declaration if nothing was found. An explicit "I carried out the check and found no defects," with the two fixed proof shots and the driver's name. Light, but present.
8. Submit and get a reference number. The driver screenshots it on the way to the cab.

What arrives on your side is a case rather than a folder of images. Every answer is a structured field, the transcript sits next to the video, the case carries your own reference format plus a separate field for the unit or work order number your fleet system already uses. The guided video capture step, the link and QR delivery and the review and retake loop are described on their own pages.

The record is timestamped, located and sealed on arrival, and the honest version of that sentence is the one you should put in your policy. Each word carries a precise meaning:

• Timestamped. The server records when the submission was received. That proves when the record reached you. It does not prove when the defect appeared. Say that in your documentation before an auditor or a plaintiff's lawyer says it for you.
• Located. Geotagging puts the capture at the yard, to about eleven metres. If the driver declines location, the case says so plainly and records it as neutral, not as a strike.
• Sealed. A sealed submission carries a SHA-256 fingerprint and a downloadable manifest, so anyone can verify later that the photos and answers are the ones that arrived, unaltered.
• Logged. The audit trail shows the link created, each time it was opened, the submission received, who claimed it, who assigned it, every note and every status change. That is the three-month record 396.11 asks for, assembled as it happens rather than reconstructed later.

Two more product facts that matter for a fleet, stated plainly. Photos taken in the session are marked as taken through the flow; a photo pulled from the gallery is marked as unverified for time and place, with a plain-language note on what can and cannot be shown about it. And a retake request goes back to the driver in one click, names the missing step, asks why they are recording again, and links the new material to the original case rather than starting a fresh one.

From there the case moves like a job. Statuses you define (reported, assessed, out of service, awaiting parts, rectified, signed off), an owner rather than an inbox, escalation to a manager with a reason, a response time in hours on the route, and a view link a subcontract fitter can open without a login. Conditional routing and the connection into your maintenance system are set up around your process on a scoping call; a standard walkaround flow you adjust yourselves.

Three things a capture system does not do, so nobody on your team oversells it:

• It does not decide whether the truck is safe. The driver is satisfied under 392.7, a competent person assesses the defect, the carrier certifies the repair. The record shows who did what and when.
• It does not make a fake check impossible. It makes the fake more work than the real thing, and it leaves a trail that a spot check can test.
• It does not replace your maintenance system. It feeds it, with the photos and the driver's words attached to the unit number the system already has.

The rules for making a defect photo hold up (angle, scale, context, one item per frame) are in photo evidence for inspections, and yard plant has its own version of the pre-use check in forklift daily check records.

Want to build the defect branch on your own form this week? Start for free and put it in front of one driver tomorrow morning.

If you also run vehicles in the UK

The UK equivalent is the DVSA daily walkaround check: a driver or responsible person checks the whole vehicle or combination before it is used on the road, at least once in every 24-hour period in service, and a report listing defects is kept for at least 15 months with the assessment and the repair. The shape is the same as the FMCSA duty; the retention is longer and the nil-defect convention is different. If that is your world, the record side is worked through in digital HGV walkaround check records, and the check itself is defined under HGV daily walkaround check.

Frequently asked questions

Is a pre-trip inspection legally required?

Yes. Under 49 CFR 392.7 no commercial motor vehicle may be driven unless the driver is satisfied that eleven named parts, from service brakes to emergency equipment, are in good working order. 396.13 adds that the driver must review and sign the last driver vehicle inspection report if one was required.

Do I need a DVIR if there are no defects?

For property-carrying vehicles, no. Since a final rule effective 18 December 2014, 396.11 says drivers are not required to prepare a report if no defect or deficiency is discovered or reported to them. Passenger carriers are treated differently, and your own policy can still ask for a light nil trace.

How long should a pre-trip inspection take?

Fifteen to twenty minutes on a tractor-trailer for a driver who knows what to look at, and longer for a new driver or a combination they have not seen before. A check logged in under two minutes was done from the cab. Build the time into the schedule rather than hoping drivers find it.

Can the pre-trip and the DVIR be done on a phone?

Yes. Electronic records have been allowed under 49 CFR 390.32, and FMCSA's final rule of 19 February 2026, effective 23 March 2026, added explicit language to 396.11 and 396.13 saying the reports may be created and maintained electronically. The carrier still has to certify the repair and keep the report and certification for three months.

What are the minimum tire tread depths?

49 CFR 393.75 requires at least 4/32 of an inch in a major tread groove on steer axle tires and at least 2/32 of an inch on all other tires. The same section prohibits running on a tire with exposed ply or belt material, tread or sidewall separation, a flat or audible leak, or a cut deep enough to expose the ply.

Does a photo timestamp prove when the defect happened?

No. A server-verified receipt time proves when the record reached you, which is a useful and defensible fact on its own. When the damage occurred is established by the photo itself, the driver's account and whatever the shop finds.

Do drivers have to photograph every item?

No, and you should not ask them to. Photograph every item that fails, with something in the frame for scale, plus one or two fixed proof shots that show the driver was at the truck. Sixty photos of a clean truck cost fifteen minutes and prove nothing a nil declaration with two shots does not.

Start with one terminal and one truck type

Pick one terminal and one truck type, write the walk order down, and build the flow that collects only the exceptions. Run it for two weeks next to the current form and compare the defect count.

If the new one finds more, you did not have clean trucks before. You had a clean form.

What it takes to start.

• Free plan, no credit card. Build the walkaround flow, run it on your own yard, then hand it to a driver.
• Live in 10 minutes for a first standard flow. Stuck? Book a free setup call and we build it with you.
• Everything goes out in your own branding, in the driver's own language, with no app to install.

The VentaVid team builds Venta Capture and runs the free setup call on your own inspection form.

See Venta Capture on your pre-trip inspection checklist

Or start for free and build the defect branch this afternoon. If you would rather see it against your own DVIRs first, book a demo and bring a month of reports.