DVIRs
DOT driver vehicle inspection reports — the pre- and post-trip inspections drivers sign, and how the shop resolves the defects.
A DVIR is the DOT-required driver vehicle inspection report for commercial fleet vehicles — different from a shop DVI. A driver completes one before or after a trip, signs it, and the shop clears any defects. You'll meet DVIRs when your shop services DOT fleets: the driver's side happens in the field portal, and your side is clearing the defects the driver flagged.
How a driver completes a DVIR
Start the inspection from the driver home. In the field portal, the driver opens Driver inspections and taps Start pre-trip inspection or Start post-trip inspection. On the New inspection screen they choose the Inspection type — Pre-trip, Post-trip, or Interim — pick a Vehicle from the ones assigned to them, and tap Start inspection.
Walk the checklist. Each item has an OK / Defect toggle. Marking Defect opens an editor: set the Severity — Minor, Major, or Out of service — write a Description of what's wrong, and tap Save. Required items are marked with a red asterisk.
Record the readings and safety call. At the bottom the driver enters the Odometer and Engine hours, answers Is the vehicle safe to operate? with Yes — safe or No — unsafe, and adds any Notes.
Sign and submit. The driver taps Sign & submit, types their Printed name, signs on the pad, and submits. Signing locks the report: a signed DVIR can never be edited, only resolved.
Clear defects from the shop
Open the DVIRs page. Click DVIRs in the shop. The list shows every report with Vehicle, Driver, Trip, Date, and Status columns. Use the filter chips — All, Draft, Signed, Resolved, and Out of service — to narrow it. A signed report with open defects shows a red count next to its status.
Open a report and read the defects. The detail page lists each defect with its component, description, and severity badge. An unresolved out-of-service defect carries a red OOS tag. The driver's signature and certification sit at the bottom.
Resolve each defect. If you have permission, click Resolve on a defect, write Resolution notes describing what was done, optionally add a Repair order ID, and click Mark resolved. Once every defect is cleared the report moves to Resolved.
What happens behind the scenes
A signed DVIR is a legal record — that's why signing locks it. The shop can never rewrite what the driver certified; it can only add resolutions on top. An Out of service defect is the serious one: it means the vehicle can't legally run until the fix is signed off, so it surfaces on the Out of service filter and alerts owners and managers. Marking a defect resolved with notes (and optionally the repair order that fixed it) is the paper trail that returns the vehicle to service. Which checklist a driver sees, and which drivers may inspect which vehicles, are set by managers under Settings.
Troubleshooting
The driver isn't assigned to any vehicles yet — the New inspection screen shows "No assigned vehicles." A manager assigns vehicles to drivers under Settings → Driver assignments, and the driver needs the Driver role first.
No. Signing certifies the report, so it locks permanently. You can't edit a signed DVIR; you resolve its defects instead. If the inspection itself was done in error, the driver runs a fresh one.
Marking defects resolved is a permission. If the button is missing, you don't have DVIR resolve rights — ask a manager. Technician logins are the most locked-down role in Meridian, so a missing button is usually a permission, not a bug.