A pre-trip inspection is not a form the driver completes so the vehicle can leave. It is the decision about whether the vehicle should leave at all. Done properly, the checklist catches a soft tyre, failed brake light, fluid leak, cracked mirror, or missing warning triangle while the truck is still inside the depot — where the problem is cheaper, safer, and easier to control.
This is practical fleet-operations guidance, not a legal inspection standard. Adapt the checklist to the manufacturer's instructions, the vehicle class, the load, and your current regulatory and insurance requirements.
Use the same sequence every time. A repeatable walkaround reduces skipped items and makes the result easier for dispatch and the workshop to review.
Record the odometer and fuel level with the check as well. Those readings are not substitutes for the physical inspection, but they create a reliable departure baseline for maintenance intervals, trip distance, and fuel reconciliation.
Make the checklist part of departure.
Kora gives drivers a structured 20-point pre-trip check in the field app. Failed items require a note, can carry a defect photo, and a critical failure holds the trip for review instead of letting it quietly start.
Weak inspections produce a page full of ticks. Strong inspections produce a clear release decision. The record should answer who checked which vehicle, for which trip, what failed, what evidence was captured, and who allowed the vehicle to move.
The worst time to debate whether a brake or tyre defect is serious is when a client is waiting and the load is already on the vehicle. Write the release policy before that moment. As a practical baseline, a fleet should hold a vehicle for authorised review when the check finds a brake fault, dangerous tyre damage, a significant leak, insecure steering or doors, a failed seatbelt, badly impaired driver visibility, or lighting faults that make the planned journey unsafe.
Not every failed item has the same severity. A missing first aid item and a damaged brake hose are both failures, but they should not produce the same workflow. Classify defects as hard stops or warnings, name who can clear each class, and keep the decision attached to the inspection. Drivers should never have to negotiate safety by phone with no record.
The final point is where inspections start paying for themselves. A recurring tyre, light, or fluid failure should feed the maintenance plan, not vanish after the day's dispatch is rescued. Connect the inspection history to the vehicle record and use it to find repeat problems before they become roadside downtime. For the wider maintenance workflow, read the guide to reducing vehicle downtime with better records.
A current NTSA inspection certificate shows that the vehicle completed the applicable official process at a point in time. It does not show that every tyre, lamp, mirror, or fluid level is ready this morning. The pre-trip check covers that daily operating gap. Your document register covers a third problem: making sure the official certificate, insurance, and other required records do not expire unnoticed.
Strong fleets run all three: scheduled maintenance and formal inspection, a documented readiness check before work, and expiry tracking for vehicle and driver documents. None replaces the others.
A pre-trip inspection is the driver’s documented walkaround and cabin check before a vehicle begins work. It confirms basic readiness across fluids, brakes, tyres, lights, safety equipment, mirrors, windscreen, horn, doors, and seatbelts. It is an operating control, not a replacement for scheduled maintenance or an official NTSA inspection.
A familiar, well-organised 20-point check can often be completed in about 10 to 15 minutes, but there is no useful target that justifies rushing. Vehicle size, trailers, specialised equipment, weather, and a suspected defect all add time. Measure whether the check is complete and credible, not whether the driver beat a stopwatch.
Every fleet should define hard-stop defects for its vehicles and work. A practical baseline is to hold a vehicle for review when the check finds a brake fault, dangerous tyre damage, a significant fluid leak, insecure steering or doors, a failed seatbelt, seriously impaired visibility, or lighting faults that make the planned journey unsafe. The defect should be assessed and cleared by an authorised person before departure.
No. An NTSA inspection is an official periodic roadworthiness process for vehicle classes that require it. A pre-trip check is the operator’s routine readiness check before daily work or a particular trip. One does not replace the other: a current inspection certificate does not prove that a tyre was undamaged or a brake light worked this morning.
Paper can work when the fleet is small and supervisors consistently review, file, and act on every result. It becomes weak when forms go missing, failed items cannot carry photos, dispatch cannot see the result, or nobody can find repeated defects by vehicle. A digital checklist is most useful when it connects the inspection to the exact trip, blocks departure on critical failures, and preserves the record for maintenance review.
The driver should describe the defect clearly and attach evidence where useful. Dispatch or the workshop then decides whether the vehicle is held, assessed, repaired, or replaced. The important control is that a failed item cannot disappear between the driver’s phone and departure: the decision, the person who made it, and the work that cleared the vehicle should remain connected.
Inspect before you dispatch
Kora connects the driver’s pre-trip check to the assigned vehicle and trip, records notes and defect photos, and holds critical failures for review before work begins.
