Your Vehicle Inspections Summary report tells you how many Digital Vehicle Inspections each of your technicians completed, how many vehicles they covered, and how they rated the items they inspected — Passed, Needs Attention, Failed, or N/A. It is the fastest way to see whether your team is actually running inspections on the cars you bring in, and whether those inspections are surfacing real findings you can talk to your customer about. The four cards at the top — Orders with Inspection, Total Inspections, Completed Inspections, and Completion Rate — give you an inspection-adoption snapshot, and the table below shows per-technician performance so you can coach, celebrate, and spot who is skipping the inspection step.
Filters
| Filter | Default | What it does |
|---|---|---|
| Countries | your shop's country | (HQ only; only appears when your company has shops in more than one country) narrows which locations appear in the Locations filter below it |
| Locations | all your locations (HQ only) | limits the report to inspections on orders at the shops you select |
| Order Status | all statuses | limits to inspections on orders in the statuses you pick — Estimate, Repair Order, or Invoiced |
| Inspection Completed Date | off (no date filter is applied unless you pick one) | limits to inspections marked Complete within a date range. The date picker shows this month, but that range isn't applied until you explicitly choose a period |
| Invoiced Date | off | limits to inspections on orders that were invoiced in a date range. Estimates and open Repair Orders have no invoiced date, so they drop out when this is active |
| Paid Status | all | limits to Paid, Unpaid, or Partially Paid orders |
| Fully Paid Date | off | limits to inspections on orders fully paid within a date range. Unpaid and partially paid orders drop out when this is active |
| Users | all users | limits to inspections rated by the technicians you pick; includes an Unassigned option for items without a rater |
Date Filters
Inspection Completed Date, Invoiced Date, and Fully Paid Date are three separate questions and can be used together:
- Inspection Completed Date = "I want data about inspections my techs actually finished" — use when the question is "what DVI work did we do this period?"
- Invoiced Date = "I want data about completed/closed jobs" — use when the question is "what inspections were on jobs we finished and billed this period?"
- Fully Paid Date = "I want data about money that came in, regardless of which jobs it relates to" — use when the question is "what inspections were on jobs we got paid for this period?"
- Multiple date filters active at once = intersection — orders must satisfy all the date conditions. This is a narrow, restrictive view; most routine reporting uses one date mode only.
Neither mode is more "correct" — they answer different questions.
Understanding Each Number
| Card | What it means | What it doesn't include | When it's useful | Notes |
|---|---|---|---|---|
| Orders with Inspection | the percentage of orders at your selected locations that had at least one inspection started | this percentage's denominator is every order at the selected locations — it doesn't narrow by Order Status, Paid Status, or the three date filters | when you want to know "is my team actually doing DVI on the cars coming in?" | adding a status or date filter usually drops this percentage because the top of the fraction shrinks but the bottom stays the same |
| Total Inspections | the number of distinct inspections in your filter scope | un-started inspections and templates nobody used | when you want a fast count of how much inspection work happened | if an inspection had items rated by more than one tech, it's counted once here but once per tech in the table — don't be surprised if the table column totals more |
| Completed Inspections | the number of inspections your techs actually marked Complete | inspections where every item is rated but the tech never flipped the "Complete" switch | when you want to measure "are we finishing what we start?" | a low number here compared to Total Inspections usually means your team is leaving inspections half-finished |
| Completion Rate | Completed Inspections divided by Total Inspections, as a percentage | — | when you want a single number to track whether your DVI process is getting followed through | the card has a tooltip showing the formula |
| Inspector | the technician (by name) who rated items on the inspections in your filter | — | finding your strongest and weakest inspectors at a glance | "Unassigned" means items without a rater on file. Deleted employees show with "(Deleted)" next to their name |
| Location | the shop where the inspector's work happened (HQ only) | — | spotting performance differences across shops | if a tech worked at multiple shops, only one location name shows on their row — look at Vehicle Inspections Detail for the full per-inspection breakdown |
| Inspections | how many distinct inspections each technician rated at least one item on | — | per-tech volume comparison | summing this column can be higher than Total Inspections when inspections had multiple raters — that's normal |
| Vehicles | how many of the inspector's inspected orders had a vehicle attached | orders with no vehicle on file; two orders on the same vehicle count as two | measuring inspection volume when vehicle context matters | this is really "orders with vehicles", not unique vehicles |
| ARO | average total of the orders the inspector touched | — | seeing which inspectors tend to get put on bigger tickets | this is NOT the inspector's labor billed. It's the average ticket size of the orders they inspected |
| Items Rated | count of inspection items the inspector rated, including N/A | items nobody rated (blank / skipped) | comparing thoroughness between techs | — |
| Items Rated % | percentage of in-scope inspection items that were rated | — | spotting techs who skip items on their inspection sheets | this is out of every in-scope inspection item, not just the items on templates the tech ran |
| Passed | items the inspector marked Green / Pass | items rated using custom statuses other than Green/Yellow/Red/N/A | quickly seeing how often the inspector finds the car healthy | — |
| Needs Attention | items the inspector marked Yellow / Needs Attention | — | spotting techs who are surfacing coachable issues — this is the upsell conversation driver | — |
| Failed | items the inspector marked Red / Fail | — | spotting techs who are flagging safety-critical issues | — |
| N/A | items the inspector explicitly marked Not Applicable | — | spotting templates that aren't fitting the cars being worked on | N/A is not counted in the Avg. Finding % — you can mark items N/A without affecting that percentage |
| Avg. Finding % | combined rate of Yellow plus Red items, out of Green + Yellow + Red | items marked N/A; un-rated items | measuring how often an inspector's work surfaces something for your advisors to talk to the customer about | this is a findings rate — it lumps Needs Attention with Failed. If you want a pure fail rate, you can calculate Failed divided by (Passed + Needs Attention + Failed) yourself |
Click the assigned user’s name to view the details of all inspections performed by this user. Clicking the name will open the Vehicle Inspections Detail report with the same filter definitions you had defined in the Vehicle Inspections Summary report.
Common Questions
Q: Why is Orders with Inspection so much lower than I expected? A: That percentage compares orders with inspections (the top of the fraction) against every order at the selected locations (the bottom). If you added an Order Status filter or a date filter, only the top of the fraction shrinks — the bottom stays the same. So tightening a filter almost always pushes the percentage down. For the truest "are we doing DVI?" reading, leave only the Locations filter active.
Q: Why doesn't the Inspections column in the table add up to Total Inspections at the top? A: Because an inspection can be rated by more than one technician. The top card counts each inspection once. The table column gives each technician credit for any inspection they rated items on, so one inspection rated by two techs adds 1 to the top card but 2 across the table. Both numbers are correct — they're answering slightly different questions.
Q: Why is the ARO column different from what I see in my Sales report? A: ARO here is the average total of the orders your inspector touched — it's not the same as your shop's overall ARO and it's not the inspector's labor billed. It's a rough signal of ticket size on the orders your inspector is on. For shop-wide ARO, use the sales reports.
Q: Why does my Completion Rate look low when I know my techs are doing the work? A: Completion Rate counts only inspections that were explicitly marked Complete. If your techs rate every item but never flip the switch to Complete, the inspection doesn't count. This is a training opportunity — marking Complete is how the system knows the inspection is done.
Q: One of my technicians shows up as "(Deleted)". Why? A: That employee left the company but their historical inspections stay in the report so your totals stay accurate. The "(Deleted)" label helps you see that their work is included but they're no longer on staff.
Q: Why is there an "Unassigned" row? A: Some inspection items don't have a specific tech attached as the rater — usually items set before the tech logged in, or items imported from an older template. They get grouped into "Unassigned" so you can still see them.
Q: A tech's inspection from yesterday isn't showing up. What's wrong? A: A few possibilities. Either the inspection has no items rated yet (it won't appear), or you have Inspection Completed Date turned on and it's outside your date range, or the inspection's order is in a status or paid state your filters exclude. Clear your date filters and check again.
Tips for Getting the Most Out of This Report
- Use Inspection Completed Date for period coaching. To review a tech's DVI output for "last month," turn on Inspection Completed Date and set it to the prior month. Your top Completion Rate tech is the one to model best practices from.
- Watch Avg. Finding % for upsell conversations. Techs running inspections with very low finding rates are either inspecting clean cars or rubber-stamping the sheet. Techs with high finding rates are generating the conversations your advisors turn into approved repairs. Pair this with ARO for a full picture.
- Keep an eye on Completion Rate as a process health metric. A healthy DVI program closes out at 90%+ Completion Rate. If you're below that, your techs are starting inspections they never finish — worth a team huddle to fix the workflow.
Still have questions? Feel free to reach out to us through the chat icon. Thanks for reading!
Comments
0 comments
Article is closed for comments.