AI defect photo review for Motive

Overview

A Motive inspection is a complete, compliant record of what the driver reported. The Driver App walks the parts list, takes Major or Minor on each defect, holds the note and the photo, captures the safe or unsafe declaration and the signature, and pushes the whole thing to the Fleet Dashboard the moment it is certified. What it does not do is look at the picture. RapidEye reads the defect photos and notes from those inspections, along with the vehicle, the driver and the time, and returns a finding per issue, so a photo taken at 5am in a dark yard reaches a person the same day instead of sitting in a report nobody opened.

How it works with Motive

The Driver App organises an inspection around parts, defects and a safety declaration, so the checks follow the same structure. Take these as examples of where photos already exist rather than the limits of the product: RapidEye reads whatever a team documents, photos, a video walkaround, an inspection format of your own, and scores it against the standard your fleet holds.

• Major defects. The ones that stop the truck. RapidEye reads the photo and says what it shows, how bad, and which part, so maintenance is planning the repair before the driver has finished signing.
• Minor defects. The ones that queue. Read together over weeks, they stop being a list and start being a pattern: the same mirror mount on the same unit, the third tyre note on the same axle.
• Trailer inspections. A separate flow in the app with its own Trailer ID and parts. A trailer handed between drivers is the classic case of damage with nobody's name on it, and the photo history is what gives it one.
• Photos on a clean inspection. Some fleets ask for a short set of shots on every unit, defect or not. Those are the ones RapidEye compares against the last time the unit was photographed, which is how damage nobody reported gets found.
• The trailer or truck interior. Cab condition, cargo area, load securement left behind, debris in the box. Nothing on a DVIR parts list covers it, and it is visible in the photos anyway.

Each finding names the vehicle or trailer, the part or spot, the kind of problem, a severity, the photos it came from and a suggested next step, and it lands in the RapidEye dashboard plus a Slack channel or an inbox for maintenance if you want one. Nothing is written back into Motive: your team decides whether it becomes a work order, a driver conversation, or a note on the unit.

How to connect Motive to RapidEye

1. The inspection forms you already run. Under Admin, Maintenance, Inspection Forms, with the vehicle parts and the custom defect list your fleet built. Nothing about the form needs to change, and forms created as the Asset type stay on trailers and non-powered assets the way Motive requires.
2. Photos on the defects. Motive already carries them: the driver taps the camera icon while entering defect details. If you want condition read on every unit rather than only where a defect was reported, ask for a short set on every inspection, or use a RapidEye capture link that opens on any phone with no app to install.
3. Add RapidEye as a fleet user. Admin, then Fleet Users, then Add user, with a role that can see inspections. The modal has the details.

Inside a Motive defect, and what happens to it after

Checked against Motive's help centre, September 2026.

According to Motive's help centre documentation (gomotive.com), a fleet admin builds the form first: Admin, Maintenance, Inspection Forms, create the form, choose Vehicle or Asset as the type (a choice Motive flags as critical because it cannot be changed after saving), add vehicle parts, add a custom defect list, set the driver signature declaration, and assign it to vehicles. The driver then works that form in the Driver App from Logs, adds an inspection, picks Vehicle Inspection or Trailer Inspection, fills in the general information, and goes part by part: the thumbs-up icon where the part is fine, the explanation icon where it is not. That second tap opens the entry below.

Fields as documented in Motive's inspection articles. Severity tags shown in RapidEye's own styling.

Answering No to the safety prompt is the strongest thing a Motive inspection can do on its own: Motive documents that the vehicle status updates immediately in the Fleet Dashboard, fleet managers get an automated alert, and a driver who later selects that unit hits a blocking alert warning them not to move it, which they must override deliberately by choosing Create inspection. From there the defect runs a hand-off that Motive describes in four moves.

1. Driver
   Certify and saveThe report goes to the fleet manager and maintenance team. Motive documents that a submitted inspection cannot be changed; a mistake is corrected with a new inspection.
2. Maintenance
   Corrected, or Need not be correctedThe status maintenance sets on the defect, visible back in the driver's inspection history in the app.
3. Driver
   Sign off, or rejectThe driver acknowledges the fix by signing, or rejects the correction and adds comments for follow-up.
4. RapidEye
   Read the photo, both timesWhat the defect photo actually shows when it is raised, and whether the photo after the repair matches the correction that was claimed.

Who reviews DVIR defect photos in Motive?

Whoever opens them. Motive's inspection articles are consistent and honest about this: a certified report is shared with the fleet manager and maintenance team, an unsafe designation raises an automated alert, and its FAQ says fleet managers and admins with the appropriate permissions can view submitted inspections in real time. Motive is doing exactly what a compliance record should do, which is put the photo in front of a person with the vehicle, the driver and the timestamp attached. The part that scales badly is human: at three hundred inspections a day, "can view in real time" and "is read" are different sentences, and the photos that never carried a defect flag are read by nobody at all. RapidEye is the piece that reads every one, holds the history of that unit, and pushes back only the ones worth a person's attention.

Motive integration FAQ