MySyara OS
If you want to know how to do a digital vehicle inspection (DVI), here's the short version: open the repair order (RO) on your tablet, work through the template item by item, photograph each finding with light and angle that a non-mechanic can read, grade each item green, yellow, or red, write a note with a measurement not just a label, and send the report to your advisor before it goes to the customer.
That's the workflow. Knowing how to do a digital vehicle inspection well, the kind that actually gets yellow and red items approved, comes down to three things: sequence, photos, and notes. This article covers all three from the tech's side of the bay.
If you want the shop-owner view first, the explainer on what a digital vehicle inspection is covers the why, the costs, and what it won't fix.
Before You Reach the Car: Setting Up the Inspection Right
Two minutes of setup before you touch the vehicle saves ten minutes of advisor call-backs later.
Match the template to the job. A 10-point quick-lube template and a 50-point pre-purchase walk are not interchangeable. Know which one the advisor opened, or open the right one yourself.
Check the vehicle history. If your system shows a prior report on this car, spend 30 seconds looking at what was yellow last time. Items that moved from yellow to red in one visit are a different conversation than items that have been yellow for three visits. That context belongs in your note.
Note the mileage in. This is a timestamp on every condition claim in the report. If a customer disputes a finding three months later, mileage-in and mileage-out are your anchor.
Grab your lighting equipment now. Under-car photos in poor light are the single most fixable cause of approvals that go nowhere. Pull the flashlight or clip light before you start, not after you've already photographed six items in the dark.
See how MySyara OS handles DVI and inspections if you want a sense of what the template and RO workflow looks like on the tool side.
How to Do a Digital Vehicle Inspection: The Step-by-Step
The order you inspect items is also the order the customer reads the report. Follow this sequence consistently and two problems disappear: you stop forgetting items, and the report reads like a logical narrative instead of a random list.
1. Open the repair order and select the correct template. Confirm it matches the job type before you photograph anything. A mismatch wastes your time and the advisor's.
2. Note mileage in and check prior vehicle history. Thirty seconds on the history screen tells you which yellow items are new and which have been there for three visits, worth knowing before you grade anything.
3. Complete the exterior walk-around, four corners, and photograph pre-existing condition. Wide shot of each corner, then any pre-existing damage with a close photo. These photos are your liability anchor; skip them and you own anything the customer claims happened in your bay.
4. Inspect under-hood items with proper lighting and photograph each finding. Fluids at the dipstick or cap, not the reservoir from two feet away. Belt condition close, not from across the engine bay. Battery terminals where corrosion is visible.
5. Move to the lift: undercarriage, brakes, suspension. Light every item before you raise the camera. For brake pads, one context shot showing the caliper, one close shot of the pad face. For shocks, photograph both sides. This is where most of the report's approval value lives, and where most photos fail.
6. Inspect tires, wheels, and interior. Tread depth gauge in the groove for the photo, not held next to it. Sidewall for cracking or bulge. Then cabin filter, wipers, warning lights, TPMS.
7. Grade each item green, yellow, or red. Green: within spec, no action needed. Yellow: within spec now, attention needed in 30 to 90 days: always include a timeline in the note. Red: action needed now. A red item with a blank note means the advisor has to call you before the approval can move forward; don't leave them blank. Budget 15 to 20 minutes for a practiced tech on a standard 27-point walk, 25 to 30 for a 50-point first-time customer visit.
8. Annotate photos for all yellow and red items. Draw a circle or arrow on the worn area. Add a measurement as text, "2mm" written in the annotation removes any need for the customer to guess at scale. This takes ten seconds per photo and is the step most techs skip.
9. Write specific notes for yellow and red items, then review before submitting. Canned notes are fine for green items. For yellow and red, write a sentence specific to this vehicle. Do a 30-second final check before you tap send: catch missing photos or blank notes now, not after the advisor has already called the customer.
Marcus, a four-year tech at a six-bay shop in Phoenix, Arizona, used to start every walk wherever the car was most accessible: usually tires, because they were right there at knee height. His reports read out of order. The advisor called him back two or three times a week to ask why brake pads showed up two-thirds of the way through the report, after several unrelated items. Marcus drilled the four-corners, under-hood, lift, tires, interior sequence for one week. Advisor call-backs dropped from three or four a week to roughly one. Same work, same time. The difference was in how the report read. (Illustrative, name is fictional, scenario is representative.)
The Photos That Get Work Approved
AutoVitals' analysis of shop data found that reports with 30 or more photos and at least 60% annotated correlate with better customer engagement (AutoVitals best practices, vendor-published data 2023-2024). The benchmarks are useful. What nobody explains is how to hit them usefully rather than just numerically. Thirty blurry photos are worse than 15 sharp ones.
Lighting before the camera. Bring light to the subject before you raise the tablet. A phone flash pointed directly at a brake caliper gives overexposed metallic blur. A flashlight held to the side, illuminating the pad face, gives a readable image. This is the most common fixable photo failure in a DVI walk, and it costs nothing except the habit of reaching for the light first.
Context then detail. For brake pads: one wide photo showing the caliper and pad in context, then one close photo of the pad face showing wear. For fluids: photo on a white rag or white cap background where color is legible. For tires: full sidewall, then tread depth gauge in the groove. Context first, detail second: the customer sees where the item lives, then what the problem is.
Draw on the item. Use the annotation tools in the app on every red and yellow photo. Draw a circle or arrow on the issue. Add a measurement as text. Ten seconds per photo.
When to use video. A 10 to 15-second clip beats a still for: a component with noticeable play or movement, a fluid leak where seeing the drip matters, a warning light that cycles during a road test. Video for static items wastes the customer's time. Use it where motion is the point.
Diane, a technician at a family-owned shop in Melbourne, Australia, sent a report with 22 photos on a vehicle that needed AUD 1,800 in brake and suspension work. The advisor called the customer. The customer said the photos "didn't show anything." Diane had photographed the right items but from too far away, in a dark bay, with no annotation. She retook four photos with her phone light and a circle drawn around the pad face. The advisor re-sent the report. The customer approved everything the same afternoon. The re-shoot took eight minutes. (Illustrative, name is fictional, scenario is representative.)
Notes That Answer the Customer's Next Question
A label is not a note. "Brake pads worn" tells the customer nothing they don't already know from the red color-code. A note answers: how worn? Why does it matter? What happens if I don't fix it?
The three-part structure. Every note on a red or yellow item needs: (1) the observation with a measurement, (2) why that measurement matters, and (3) what happens next if left alone.
"Front left brake pads at 2mm, minimum safe thickness is 4mm. At this level, pads can reach metal-on-metal contact under hard braking. If left, the rotor needs replacement too, roughly double the cost."
A note like that turns a red flag into a conversation the customer has already had in their head by the time the advisor calls.
Voice-to-text is faster than typing. Speaking "Front right CV boot is cracked and showing grease leakage, replacement recommended before next service" while standing next to the vehicle takes five seconds. Typing it takes 30. Across a 30-item walk, that difference adds up.
Don't diagnose from the report. "Noise from front suspension area, recommend diagnostic" is the right note. "Front control arm bushing failure causing knocking noise" is a diagnostic conclusion that belongs in the RO after the customer approves a diagnostic check. Overreaching in notes erodes trust when you're wrong and creates liability when you're right.
What Sloppy Work Costs the Shop
Vague notes. One advisor callback to clarify a yellow item takes 5 to 10 minutes off the advisor's desk and pulls you off the lift. Three of those a day across the shop is 15 to 30 minutes of combined idle time on a workflow that should be self-documenting. A good note eliminates the callback.
Bad photos. A customer who can't read a photo asks the advisor to explain it by phone. The advisor calls you back to re-photograph. The approval window, the 30 to 60-minute period when the customer is most engaged, closes during that loop. The work often doesn't get approved that day. The re-shoot takes eight minutes. It should have been eight minutes the first time.
An undifferentiated report. A report where everything is red, with no prioritization, triggers customer suspicion. AAA's consumer guidance on auto repair exists specifically because customers need help knowing how to protect themselves. A DVI is supposed to close that trust gap, not widen it. Grade green where green is honest, yellow with a timeline, red only for genuine urgency.
When approval failures and advisor call-backs start affecting what the shop collects per hour, that shows up in your shop's effective labor rate. The full workflow from inspection to invoice is at MySyara OS's workflow walkthrough.
Frequently Asked Questions
How long does a digital vehicle inspection take?
Budget 15 to 20 minutes for a practiced tech on a standard 27-point walk, or 25 to 30 minutes on a 50-point first-time visit. Most shops fold a flat-rate inspection item into the job to cover the time.
How many photos should a DVI have?
AutoVitals' shop data suggests 30 or more photos per vehicle with at least 60% annotated as a benchmark. More useful guidance: photograph every red and yellow item with at least two shots (context then detail), and include at least two photos per green category to show you looked. Quality beats count.
What is the difference between a DVI and a multi-point inspection?
A multi-point inspection (MPI) is the list of items and the standard for evaluating each. A DVI is how that list is delivered: on a tablet, with photos and notes, sent to the customer as a report. Every DVI is an MPI. A 27-point checklist on paper handed to the advisor is an MPI. The same list on a tablet with photos and a customer link is a DVI.
What should a good DVI note contain?
Three elements: the observation with a specific measurement ("front left brake pad at 2mm"), the context for why it matters ("OEM minimum is 3mm, safe threshold is 4mm"), and the consequence of waiting ("continued use risks metal-on-metal contact, which adds rotor replacement to the cost"). Yellow and red items need a tech-written observation specific to this vehicle.
Do I need to photograph green items?
Not every one, but on a first visit from a new customer, photograph the major green categories: exterior overview, under-hood overview. A report where everything visible is yellow or red reads as a sales document. Green photos are evidence that you report what you find, not just what generates work.
A solid DVI is not a longer checklist. It's a consistent sequence, photos a non-mechanic can read, and notes that answer the customer's next question before they ask it. Get those three things right and you'll produce reports that get work approved. That's the job.
Try MySyara OS free, the inspection workflow, the RO, and the customer report all live in one place.
Run your shop on MySyara OS
Work orders, inspections, scheduling, invoices, customers, and inventory — one platform, plans for every shop size.