Inspections & DVIR
A DVIR (Driver Vehicle Inspection Report) is the report a driver files before or after a trip on the vehicle's condition. The inspections module covers three kinds of check — pre-trip, post-trip DVIR and periodic — plus the loop that drives every safety-affecting defect it finds through to a confirmed repair.
Who it's for
The driver submits inspections from the mobile app and acknowledges reviewing the last open DVIR before driving. The safety manager, fleet manager and organization administrator define checklist templates. The technician — along with the maintenance manager and organization admin — resolves defects and closes them out outside the full work-order cycle when a repair doesn't need one.
Checklist templates
A template is a checklist tied to a vehicle class: the set of components checked (service brakes, parking brake, steering, lighting, tires, horn, wipers, mirrors, coupling devices, wheels and rims, emergency equipment, plus a carrier's own additions), the inspection kind and the DVIR mode. The mode decides how often a DVIR is required: property-carrying vehicles report by exception — only when a defect is found — while passenger-carrying vehicles report daily, defects or not. Every submitted inspection snapshots the kind and mode at submission time, so editing the template later never rewrites history.
The defect → work order → repair → roadworthiness loop
A checklist item marked as failed reports a defect right away. If the defect is safety-affecting, this happens automatically: a high-priority work order is raised, linked to that defect, and the vehicle is marked not roadworthy — both without any human step. A defect moves through open → work-ordered → repaired → certified. Closing the linked work order (see Work orders) automatically drives the defect through repair and certification; if it was the last open safety defect on the vehicle, it also restores the vehicle's road-worthiness. A technician or maintenance manager can also resolve a defect directly, skipping the full work-order cycle — useful for a minor fix done on the spot.
The pre-trip review gate
A pre-trip inspection is paired with a requirement to review the last open DVIR: the driver must confirm — with an e-signature, stored only as a hash, never as a raw image — that they reviewed that last open DVIR before setting out.
In the background
Every day at 7:00, the system checks the vehicle classes under the daily mode and flags every vehicle with no inspection recorded that day — the notification lands with the compliance officer and the safety manager. Vehicles reporting by exception aren't checked this way — for them, no defect simply means no report was needed. Every day at 2:30, the system marks reports whose retention window has passed as eligible for disposal — 3 months for a DVIR, 14 months for a periodic inspection, measured from the date performed.
Performing it in the mobile app
The driver submits inspections and acknowledges the DVIR review from the mobile app, offline included — see Driver workflows. The technician also works the resulting defect work-order queue from there (see Technician workflows).