AI checklist photo review for R.O. Writer

Overview

A DVI Suite checklist tells you which items a technician marked and in what condition; the pictures attached to those items are the only part that shows the vehicle. The checklist hangs off a ticket, an RO or an estimate, in the sequence the jobs sit in R.O. Writer. Each item gets a condition, comments and any number of images, and the whole thing goes to the customer by text, email or print. DVI Command then counts what happened: checklists opened, items completed, defects found, by service writer and by technician. RapidEye reads the part nothing counts. It takes the images, the ticket, the vehicle and the date, and returns one finding per issue in them.

How it works with R.O. Writer

DVI Suite is two halves that share a database: DVI Command on a computer at the counter and the DVI app in the technician's hand. RapidEye reads on the app's side of that, where the pictures are made, and delivers on the counter's side, where somebody can act.

• Images on checklist items. The main read. A technician taps the camera on an item and photographs the thing that failed: a cracked boot, a filter black with dust, a pad down to the backing plate. RapidEye returns a finding per issue with the spot on the vehicle, the kind of problem, a severity, and the frame it came from, so the service writer building the estimate has the list rather than a gallery.
• Items marked red with no image behind them. Nothing argues worse at the counter than a defect with no picture. RapidEye reports which items came back marked and unphotographed, broken out by technician and by checklist type, which is the fastest way to see which bays are documenting and which are typing.
• The Media tab on the ticket. Pictures and videos added to the job rather than to one item live here. RapidEye reads them as the record of the vehicle as it arrived, which is what a shop wants when a customer collects the car and points at a scuff nobody logged.
• This visit against the last one. R.O. Writer carries repair order history, declined parts and labor, and recommended services on the ticket. RapidEye keeps the image that made the case beside the line it belongs to, so when a declined item comes back around the writer can put last visit's picture and today's side by side instead of repeating a sentence.
• Whole checklists that went out thin. A checklist can be sent to a customer with an item unfinished or a picture missing. RapidEye flags the ones that left the shop without enough behind them, before the customer opens the text.

Each finding names the vehicle and the ticket, the spot, the kind of problem, how serious it looks, the image, and a suggested next step. Each one appears in the RapidEye dashboard, or in Slack or email if you route it there for the front counter. What happens next in R.O. Writer is yours: labor added from the checklist item, a note, a line left for the next visit. Photographs are the common case rather than the boundary. Shops that record video on the app, or that walk the vehicle with a phone, or that want findings scored against a sheet of their own, get that set up with us on the first call.

How to connect R.O. Writer to RapidEye

1. Your checklists and conditions, configured in DVI Command. The checklists your technicians run, their items, and the conditions that mark them are set under Configuration. Conditions with Require Image or Video switched on are the ones RapidEye has the most to read on, because R.O. Writer will not let the checklist go green without the picture.
2. Images attached on the items. Technicians keep tapping the camera button on a checklist item and the Media button on the ticket, the same way they do now. If a bay does not photograph findings yet, RapidEye sends a capture link that opens in any phone browser with nothing to install.
3. A Rapid Eye DVI user. Created in Central Service from DVI Command, then enabled in the DVI Users list. The Connect button has the exact path and fields.

Nothing about the bay changes. The same app on the same tablet, the same checklists, the same SmartStatus board, and the first findings arrive once the first checklists close.

How a DVI Suite checklist is built and what it carries

Checked against R.O. Writer's DVI Suite documentation, September 2026.

R.O. Writer is shop management software for independent repair shops, and DVI Suite is the inspection half of it, sold as an add-on and used inside R.O. Writer rather than as a second system. According to R.O. Writer's help centre documentation (rowriter.com), DVI Suite runs as DVI Command on a computer and the R.O. Writer DVI app on Android and iOS phones and tablets, with devices either kept to the shop network or reachable from anywhere. Everything is role based: a user is an Employee, a Service Writer, a Technician, or some combination, and the boxes ticked against that user decide what they can open.

A checklist attaches to a ticket, and a ticket is a repair order or an estimate. When several checklists are on one ticket, they appear in the same order the jobs sit in on the R.O. Writer side. The technician walks the list marking each item, and the icon on the checklist itself is a summary of that: green when every item passed, red when any did not. What an item can carry is the interesting part, because it is more than a checkmark.

Conditions and their colours as R.O. Writer's documentation describes them. The names, symbols and colours are configured by the shop; these are the categories the customer's copy of the checklist is built from.

Alongside the condition, an item takes comments, an animation where one is configured, labor that is added to the ticket automatically, and images. Images are attached from the camera button while the technician is on the item, and there is a separate Media screen on the ticket for pictures and videos added to the job as a whole, with a comment on each and the ability to draw on a picture for emphasis. A condition can also be set to require an image or video, and R.O. Writer takes that seriously: choosing that condition sends the technician straight to the Images screen, and the checklist icon stays red in both DVI Command and the app until the picture is there. On the counter side, DVI Command shows exactly which items are still missing one.

Does anything in DVI Suite look at the pictures?

Nothing does, and the Dashboard is the clearest way to see why that gap is structural rather than an oversight. It is a good report, built to answer questions about the inspection process, and it answers them precisely: how many repair orders were written, how many had checklists, how many checklists each service writer and technician opened and completed, how many items were in them, how many were completed, how many were marked as defects, and all of that as percentages, filtered by date range and by checklist type. Every one of those is a count of an action a person took. None of them is about the vehicle.

Left, the statistics R.O. Writer documents on the DVI Command Dashboard. Right, what reading the images gives you on top of them.

Put plainly: DVI Suite already does the hard half. It gets a picture taken of the right thing at the right moment, refuses to go green without one where you have asked it not to, and puts the result in front of the customer while they are still standing at the counter. That evidence is captured whether or not anyone ever opens it again, and at a busy shop nobody does. RapidEye is the second pass. It reads every image on every checklist and tells you what they show, which turns a photograph taken to sell one job into a quality record, a claim record and a picture of how each technician actually inspects.

R.O. Writer integration FAQ