DOT Compliance Checklist for Small Car-Hauling Fleets

Before you release the next load, can someone show why the company, driver, truck, trailer, and trip are ready? An uploaded document isn’t the same as a completed review. Neither is a repair appointment, a requested driver record, or an unanswered message to your insurance agent.

Use this fleet compliance checklist to assign the work and record the decisions. Organize it into four areas: company, driver, vehicle, and trip. One person may handle several areas in a small fleet, but each unresolved item still needs an owner, supporting evidence, and a clear next action.

Start with one DOT compliance review checklist

Create a review record with the company name, review date, reviewer, and affected drivers, units, or loads. Give each item an outcome: complete, open, or not applicable with an explanation. Check an item only after the designated reviewer has accepted its evidence. A request sent to someone else remains open.

Keep evidence beside the decision. “Inspection received” tells dispatch less than “Trailer T-04 inspection reviewed; separate brake defect remains open; assignment held.” Use plain language. If an item is not applicable, record who reached that conclusion and the operating facts behind it.

For a printable version, copy this checklist into your own controlled template. Add a revision date and space for evidence references. Treat a saved PDF as a dated working copy, not a permanently current statement of the rules.

Company: establish scope and assign the recurring work

Start with a one-page description of what you actually do. List your operating entity, whose authority you use, whether you transport customers’ vehicles or your own, and the jurisdictions involved. Record truck and trailer ratings alongside actual operating weights. Include a pickup-and-gooseneck combination rather than describing everything simply as “car hauling.”

Give that description to the person reviewing applicability. FMCSA’s USDOT-number guidance↗ (opens in a new tab) addresses registration screening; its operating-authority guidance↗ (opens in a new tab) addresses a separate authority decision. Record both conclusions and their assumptions rather than accepting a single “DOT paperwork complete” answer. (fmcsa.dot.gov↗ (opens in a new tab))

Review insurance filings and process-agent arrangements separately. FMCSA’s Insurance Filing Requirements↗ (opens in a new tab) page explains filing obligations, while Designation of Agents for Service of Process↗ (opens in a new tab) addresses process agents. Record the evidence needed for your operation. Keep customer insurance requests separate so they don’t become your only compliance reference. (fmcsa.dot.gov↗ (opens in a new tab))

Build a calendar from the resulting decisions. For each obligation, record its source, responsible person, due date, preparation date, submission evidence, and confirmation. Add jurisdiction-specific registration, tax, and permit questions for review with the responsible agencies. Don’t populate those fields by copying another carrier’s calendar.

Assign accident-record review too. 49 CFR § 390.15(b) addresses the accident register and copies of specified accident reports. Use it to establish the applicable documentation instructions. Separately, build a retention schedule by record category, with a source and owner for each decision. Avoid one blanket deletion date for the whole fleet. (ecfr.gov↗ (opens in a new tab))

As an internal routine, hold a short weekly open-items review. This is a suggested management cadence, not a regulatory deadline. Discuss overdue evidence, approaching dates, and work that could affect assignments. If you outsource a task, name the person inside your company who checks the provider’s response.

Driver: turn collected records into a readiness decision

Build a driver-review worksheet that separates “requested,” “received,” and “reviewed.” Use the driver’s name or internal ID consistently. Put the reviewer’s decision beside the evidence instead of expecting dispatch to interpret an employment file.

Use 49 CFR § 391.51 to review qualification-file contents. It identifies application, driving-record, road-test or accepted-equivalent, annual-review, and medical documentation provisions. Record which evidence applies, what has been reviewed, and what remains missing. This is a source map, not a declaration that every document applies identically to every driver. (ecfr.gov↗ (opens in a new tab))

Check licensing against the equipment you intend to assign. Record restrictions and unresolved questions before switching a driver between combinations. Use Part 383↗ (opens in a new tab) for the CDL review and Part 391↗ (opens in a new tab) for qualification. The resulting decision should identify the medical qualification evidence appropriate to that driver’s circumstances. (ecfr.gov↗ (opens in a new tab))

Handle drug-and-alcohol program questions through a designated reviewer using Part 382↗ (opens in a new tab), including § 382.701 for Clearinghouse queries. Record coverage, testing, query and consent outcomes, follow-up actions, and any restriction on safety-sensitive work. Don’t let a general hiring approval stand in for those decisions. (ecfr.gov↗ (opens in a new tab))

Keep dispatch’s view narrow and useful: assignment status, relevant restriction, next review date, and escalation contact. Decide separately who may access underlying medical, testing, and personnel records. Avoid copying sensitive attachments into a general load conversation.

Then test the operational handoff. Ask the driver to explain how they report a defect, raise an HOS concern, identify a loading problem, and request help after a roadside stop. Record training gaps separately from qualification-file gaps. Both need attention, but they need different corrective actions.

Use the driver qualification file checklist for the detailed file workflow. Keep this fleet-level checklist focused on who reviews the evidence and what dispatch does with the decision. (truckta.com)

Vehicle: connect inspections, defects, repairs, and release

Open a separate equipment record for each truck and trailer. Identify the unit, VIN, responsible maintenance contact, inspection evidence, service plan, and open defects. When you swap trailers, review the replacement trailer’s record rather than carrying forward the previous combination’s status.

Use 49 CFR Part 396↗ (opens in a new tab) for the inspection-and-maintenance review. Start with § 396.3 for maintenance records, § 396.11 for driver reports, and § 396.13 for driver inspection duties. Document applicability, exceptions, timing, evidence, and retention before setting your procedures. (ecfr.gov↗ (opens in a new tab))

Keep internal walkaround records, driver defect reports, periodic inspection evidence, roadside reports, and repair records distinguishable. Link related records without giving them the same label. Your reviewer should be able to follow a defect from its first report through the decision that closed it.

For a hypothetical example, suppose a driver reports an intermittent trailer-light fault. Record the symptom, affected unit, report time, and who assessed it. Attach the corrective work and follow-up inspection evidence. Under your internal workflow, keep the assignment pending until the designated reviewer records an equipment-release decision. “Shop notified” is an action, not that decision.

Build the equipment inspection procedure around the actual rig and manufacturer instructions. Include brakes, tires, lights, coupling components, ramps, decks, hydraulics, winches, and securement equipment where relevant. Part 393↗ (opens in a new tab) addresses federal equipment requirements; use it alongside the rig-specific review. Don’t substitute an improvised inspection for qualified assessment of a safety concern. (ecfr.gov↗ (opens in a new tab))

Review cargo securement separately from the carrier’s mechanical condition. § 393.128 addresses specific securement requirements for automobiles, light trucks, and vans within its scope. Record which cargo rules fit the vehicles and proposed securement method. Avoid a single attachment-count instruction for every load. (ecfr.gov↗ (opens in a new tab))

Use the fleet vehicle inspection checklist for the working inspection handoff. Keep this checklist’s vehicle outcome simple: reviewed evidence, unresolved issue, responsible person, and assignment status. (truckta.com)

Trip: test the assignment and close the exceptions

Review the assignment before promising the pickup. Put the driver, truck, trailer, load, lane, and appointments together. Check whether the approved company, driver, and equipment decisions still fit this move. A different trailer, substitute driver, heavier vehicle, or added stop should trigger a fresh look at the affected decision.

Build the schedule around more than loaded miles. Enter deadhead, vehicle inspections, loading, unloading, fuel stops, securement checks, and expected waiting. Leave room to revise the plan. In an illustrative dispatch scenario, a delayed gate release might require moving a delivery appointment rather than squeezing the remaining work into the original schedule.

For HOS and logging review, use § 395.1 for scope and exceptions, § 395.3 for property-carrier driving limits, and § 395.8 for duty-status records and logging methods. Record the applicable limits, records, and basis for any claimed exception. Recheck the logging arrangement when an assignment changes. (ecfr.gov↗ (opens in a new tab))

Record the route, loaded configuration, planned stops, and jurisdiction questions. Assign someone to resolve applicable weight, dimension, permit, and route restrictions with the responsible agencies before accepting the plan. Keep the load’s BOL, gate release, and condition report alongside the trip record, but label them separately from regulatory evidence.

Make cargo checks part of the trip instructions. § 392.9 addresses cargo inspection and reexamination duties, including timing and exceptions. Translate the applicable requirements into driver instructions and dispatch expectations, with a named contact for unresolved securement concerns. (ecfr.gov↗ (opens in a new tab))

Close the loop instead of collecting another attachment

At closeout, ask what changed: a defect, roadside inspection, logging concern, cargo issue, or missed document. Give each exception an owner and a next action. Keep a roadside report connected to its follow-up work; use the roadside inspection response workflow to organize that handoff. (truckta.com)

Periodically test retrieval with one completed trip. Can the responsible people connect its driver review, equipment status, assignment decision, and exception closeout without rebuilding the story from messages? Record missing links as process improvements, not as reasons to rewrite what happened.

For deeper follow-up, use Car-Hauling Safety and Compliance: A Practical Operating Guide. Its five resources cover driver qualification, Clearinghouse reviews, HOS planning, maintenance records, and automobile securement checks. (truckta.com)

Explore TruckTA compliance records with one concrete test: bring a redacted company record, driver document, and inspection record. Ask how Documents, company checks, and inspection records support your review process. Identify which collection, review, and retrieval steps are available and which remain your team’s responsibility. Use the software evaluation checklist to structure that test. (truckta.com)