A pre-trip inspection app,
built around what FMCSA requires.
A pre-trip inspection app is supposed to prove one thing: the walkaround happened, any defect got written down, and nobody drove the truck again until it was fixed. That is not a nice-to-have, it is a federal requirement. FMCSA’s rules under 49 CFR 396.11 and 396.13 spell out exactly what a driver has to check before operating a commercial vehicle, and what has to happen if something is wrong, whether you track it on paper, in a generic form tool, or in a purpose-built app. Most fleets already lean on field service apps for dispatch and scheduling; a pre-trip inspection app is the compliance layer underneath that, tied to a specific vehicle instead of a job. This page walks through what the regulation actually requires, what the separate CDL walkaround test covers, and where free checklist apps run out of road.
11
Required systems under 396.11
3 mo
Minimum record retention
396.11 / .13
The two FMCSA sections that matter
$25/mo
Starting price to build your own app
The short version
Eleven systems, one signature.
To satisfy 49 CFR 396.11, a pre-trip inspection app has to capture a daily report covering 11 specific systems, list any defect the driver finds, get signed, and trigger repairs before the vehicle is used again. A cracked mirror or a worn tire is far easier to act on as a picture than a description, which is why photo upload attached to each defect is the first thing most fleets add on top of the bare checklist. Separately, 49 CFR 396.13 requires the driver to be satisfied the vehicle is safe, review the previous report, and sign off on it before operating. None of that requires a specific app or vendor, paper is legal, but the paperwork trail and repair certification is where a phone-based app usually earns its keep once you are past a truck or two.
What FMCSA requires
The rule, not the marketing.
Two sections of the Federal Motor Carrier Safety Regulations cover almost everything a pre-trip inspection app needs to do.
The daily report — 49 CFR 396.11
Every motor carrier has to require its drivers to prepare a written report at the completion of each day’s work on each vehicle operated, covering service brakes (including trailer brake connections), parking brake, steering mechanism, lighting devices and reflectors, tires, horn, windshield wipers, rear vision mirrors, coupling devices, wheels and rims, and emergency equipment. If the driver finds no defect, the rule does not require a report that day. Any listed defect that could affect safe operation has to be repaired before the vehicle runs again, and the carrier has to certify that. Reports, repair certifications, and review certifications all have to be kept for three months, and can be created and stored electronically under 49 CFR 390.32, though nothing requires that.
- Service brakes (including trailer brake connections)
- Parking brake
- Steering mechanism
- Lighting devices and reflectors
- Tires
- Horn
- Windshield wipers
- Rear vision mirrors
- Coupling devices
- Wheels and rims
- Emergency equipment
Before the engine starts — 49 CFR 396.13
Before operating a vehicle, the driver has to be satisfied it’s in safe operating condition, review the previous driver vehicle inspection report, and sign that report to confirm the review and that any required repairs were completed. That signature requirement drops away for defects listed on a towed unit that’s no longer part of the combination. This is the daily “before you drive” duty that sits right next to the reporting duty in 396.11.
Who’s exempt
The written daily-report requirement in 396.11(a) does not apply to private passenger carriers, driveaway-towaway operations, or a motor carrier operating only one commercial motor vehicle. That narrow exemption is from the report itself, not from every inspection duty a driver has, so read the full text against your own operation rather than assume it applies.
Does the 396.11(a) report requirement apply to you?
Pick the option closest to your operation.
Primary source: eCFR, 49 CFR 396.11 and 49 CFR 396.13.
How it fits together
The daily inspection loop.
396.11 and 396.13 aren’t two separate rules so much as one loop that repeats every time a vehicle changes hands.
- 1
Walk around and check the 11 systems
The driver physically checks service brakes, parking brake, steering, lights, tires, horn, wipers, mirrors, coupling devices, wheels and rims, and emergency equipment.
- 2
Write the report, if anything failed
No defect found means no report is required that day under 396.11(a). Anything flagged has to be written down and identified against the vehicle.
- 3
Repair and certify before the truck moves
The carrier repairs any defect likely to affect safe operation and certifies the repair, or certifies that repair was not needed, before the vehicle runs again.
- 4
The next driver reviews and signs
Before operating, the next driver has to be satisfied the vehicle is safe, review the prior report, and sign it to confirm that review, per 396.13.
Try it
Work through the checklist.
This is the same 11-item list every daily report has to cover. Check items off the way a driver would, and see what changes once everything clears.
The 11 required systems
0 of 11 checkedThis mirrors the minimum 49 CFR 396.11(a) list, not a specific app. Check an item to see how a driver would work through it before signing off.
A different test
The CDL pre-trip walkaround.
A lot of the search traffic behind “cdl pre trip inspection app” isn’t about daily fleet paperwork at all — it’s drivers studying for the pre-trip inspection portion of the CDL skills test. That’s a different rule, so here is the same comparison side by side:
| Daily DVIR | CDL walkaround | |
|---|---|---|
| Governing rule | 49 CFR 396.11 & 396.13 | 49 CFR 383.113 |
| What it is | A daily written inspection report | A one-time skills test to get licensed |
| Who does it | Every driver, every day of operation | CDL applicants, once, at the test |
| What's checked | 11 named systems on the vehicle driven | Engine compartment, cab, steering, suspension, brakes, wheels, sides, rear |
| The goal | A paper trail proving the defect was caught and fixed | Proving the applicant can identify safety-related parts out loud |
49 CFR 383.113 requires a CDL applicant to demonstrate basic pre-trip inspection skills, identifying safety-related parts and explaining what needs to be inspected to keep the vehicle safe, across these areas:
- Engine compartment
- Cab and engine start
- Steering
- Suspension
- Brakes
- Wheels
- Side of the vehicle
- Rear of the vehicle
- Air brake controls and monitoring devices, if equipped
For air brake–equipped test vehicles, applicants also have to locate and identify the air brake controls and monitoring devices, verify brake adjustment and secure air connections, and confirm the low-pressure warning and buildup timing work correctly. It’s a one-time skills test to get licensed, not the ongoing daily report covered above — memorizing the walkaround script is a study problem, and the DVIR further up this page is a compliance one.
Primary source: eCFR, 49 CFR 383.113.
Free options
Where “free” runs out.
A free PDF checklist or a generic free form app can satisfy 396.11 on paper — the rule cares about content and retention, not the tool. Where they usually fall short is everything downstream of the checklist itself: evidence, signatures, and repair tracking.
| Feature | Paper / PDF checklist | Generic free form app | Custom-built app |
|---|---|---|---|
| Covers your exact required-items list | Yes, if you build it yourself | Usually a fixed template | Yes, matches your fleet |
| Works with no signal in a yard or garage | Yes | Often limited or paid tier | Yes |
| Photo evidence attached to a defect | No | Sometimes, capped | Yes |
| Digital signature, including the two-driver rule | Manual signature only | Rarely built in | Yes |
| Repair certification tied to the report | Manual, kept separately | Not usually | Yes |
| Cost | Free | Free tier, paid for real usage | From $25/mo (Newly) |
If your inspection needs go past trucks, a full vehicle inspection app for a mixed fleet, or a general field inspection app for site walkthroughs, cover the same ground with a broader checklist. Some fleets outgrow the free tier of a generic form tool and build a small custom app instead, once the checklist, signature, and retention rules stop fitting a template someone else designed.
Beyond the checklist
What a compliance-grade app needs.
The 11-item list is the easy part. The harder requirements are the ones that only show up once a defect gets flagged or an auditor asks for proof, and they mostly need building offline-first app functionality underneath, since a lot of pre-trip inspections happen in a yard or garage with no signal. That part is its own problem worth reading up on separately.
- Photo evidence attached directly to a failed item, not a separate email
- A digital signature, and support for the two-driver rule when both agree on the same defects
- A repair certification step, so the report and the fix live in the same record
- Automatic three-month retention, exportable if a safety audit ever asks for it
- A generic checklist that isn’t actually yours — the required items are a floor, not a template
FAQ
Pre-trip inspection apps, answered.
Under 49 CFR 396.11(a), the daily driver vehicle inspection report has to cover at least 11 systems: service brakes (including trailer brake connections), parking brake, steering mechanism, lighting devices and reflectors, tires, horn, windshield wipers, rear vision mirrors, coupling devices, wheels and rims, and emergency equipment. If the driver finds no defect on any of them, the rule does not require a report to be filed that day.
Need a pre-trip inspection app built around your fleet?
Describe your checklist, your vehicles, and your reporting rules in plain English, and Newly builds the native app around them, with the database that stores every report attached from day one.