AI inspections for Geotab
Read the defect photos your drivers take in the Geotab Drive asset inspection, and get back what the picture shows about the truck, not just which box was ticked.
How a Geotab asset inspection worksOverview
A Geotab asset inspection is a driver's report of what a driver noticed. The Drive app walks that report properly: pre-trip, in-trip and post-trip, a defect list you can shape to your own parts, a camera on each defect, a certification, and a red bar in the app until somebody with clearance marks the defect repaired. Everything it records is true. What none of it can tell you is whether the picture behind a defect is worse than the remark next to it, or whether the panel in the background has been getting steadily worse for a month. RapidEye reads those photos against the asset and the inspection date and returns a finding for each problem in the image.
How it works with Geotab
Geotab's inspection has its own moments and its own vocabulary, so the checks follow those rather than a generic idea of a walk-around.
- The defect photo itself. A driver taps the camera on an identified defect and writes a remark. The remark says "tyre". RapidEye says which tyre, where the damage sits on it, and what else the frame caught while the phone was pointed there.
- Carried-over defects. An unregulated defect carries to the next inspection automatically, and under Canadian rulesets a minor one can be carried too. Two photos of the same defect a week apart is a rate of change, which is the difference between a booked repair and a roadside failure.
- Pre-trip against post-trip. Last night's post-trip and this morning's pre-trip are the same asset, hours apart, usually different drivers. Damage that appears between them comes back with both pictures and the shift boundary between them.
- Trailers. A defect list can be set for devices, trailers or both. A trailer passes between tractors and drivers all week, which is exactly the condition where nobody ends up owning the dent. A dated photo record settles that.
- Repairs. A defect is closed with a repair status, a remark and a signature. A photo read before and after gives the closure something to stand on when a claim or an audit comes back to it later.
Each finding names the asset, where on it, what kind of problem, how serious, the photos it came from and a suggested next step, and lands in the RapidEye dashboard plus a Slack channel or an inbox for the maintenance office if you want one. Your team decides what happens inside MyGeotab. If your documentation is a different shape, video walkthroughs, a yard walk at the gate, a damage format of your own, that is something we set up with you rather than a limit of the product.
How to connect Geotab to RapidEye
- A MyGeotab database with asset inspections turned on. The feature is enabled by an admin, and defect lists apply to the groups you choose. Groups you leave out stay out of scope.
- Where the photos come from. Drivers can photograph an identified defect in the Drive app, and RapidEye reads those. If you want coverage of the whole asset rather than only what a driver flagged, a RapidEye capture link opens on any phone with no app to install and collects a fixed set of walk-around angles.
- Add RapidEye as a user in MyGeotab. The Connect panel has the name and email, plus the groups to select. Your drivers keep using the Drive app and change nothing about their shift.
How a Geotab asset inspection works, from the walk-around to the repair
Checked against Geotab's Support Center, September 2026.
Geotab calls it an asset inspection, drivers call it the circle check, and regulators call it a DVIR. According to Geotab's Support Center documentation (geotab.com), the Asset Inspection screen appears whenever a driver logs in to the Drive app, appears again at logout if the vehicle has moved, and can be opened from the Dashboard at any time, which is how a problem found mid-shift gets recorded rather than saved for later.
The driver picks a Checklist type, and an admin can supply custom lists beyond the default one. Sections can be set as required, which forces an explicit confirmation that nothing was found, or optional, where the driver speaks up only for a problem. Then the walk-around: record each defect, add a remark, and tap the camera icon to photograph it. If nothing is found the driver taps that no major or minor defects were found; either way the inspection ends with a certification that it was carried out in compliance with the applicable regulations. For a driver recording hours of service, a pre-trip completed after login moves the duty status to On Duty with a log annotated to say why.
What the three defect categories actually commit you to
Severity in MyGeotab is not a label, it is a rule about what happens next.
A significant safety risk. Must be resolved before another asset inspection can be performed on the asset.
Needs attention, not an immediate hazard. Also must be resolved before another asset inspection can be performed. Under Canadian rulesets a minor defect can carry to future inspections, and repairing it marks past inspections retroactively.
Outside federal compliance and not a safety matter. Left unresolved, it carries over to the next inspection by itself.
The next driver to take the asset meets any unresolved defect head on. They expand the previous inspection and mark each one Not repaired, Repaired or not a defect, or Repair not necessary for safe operation, then certify. In the shop, a mechanic with the right clearance clears the red bar in the app, and in MyGeotab the same defect is closed under Maintenance with a repair status, repair remarks and a Repair signed by field. The office can filter the whole inspection list by All, Only Defective, Only Repaired, Only Certified, or Repaired and Certified, and mass print what an auditor asks for.
Does anything read the defect photos?
Not in the fleet's day, no. The photo does everything that is asked of it: it proves the defect existed, it survives to the audit, and it gives the mechanic something to look at before the truck arrives. But the pictures accumulate one per flagged defect across every asset and every shift, and the maintenance office opens the ones attached to a defect that is already on fire. The quieter problem is upstream of that. A defect only enters the inspection if a driver noticed it, at the start of a shift, in the dark, on a checklist they have filled in hundreds of times. That is not a failing of the Drive app, which records faithfully what it is told; it is the limit of asking a person at 5am to be the sensor.
- Every defect photo read, not the ones that reached somebody's queue.
- The same defect across inspections, so a carried-over item is measured rather than remembered.
- What else the frame caught, which is where the defect nobody flagged usually is.
- A finding tied to the Geotab asset and date, so it lands on the right truck and the right shift.
Geotab integration FAQ
Does RapidEye integrate with Geotab?
Yes. RapidEye reads the photos your drivers attach to defects in the Geotab Drive asset inspection, along with the asset, the driver and the inspection date, and returns a finding for each problem it sees in the picture: how far the damage runs, what else is in the frame, and whether it is the same defect as last week or a new one. Your asset inspections, defect lists, repair statuses and certifications in MyGeotab are not changed.
Can a driver attach a photo to a DVIR defect in Geotab Drive?
Yes. Geotab's documentation for performing an asset inspection says that while walking around the vehicle, a driver records any defects found, adds remarks, and can tap the camera icon to take a picture of an identified defect. Those pictures are the ones RapidEye reads.
What happens to a defect nobody photographed?
That is the harder half, and it is a walk-around problem rather than a Geotab one. A defect only enters the inspection if the driver saw it, at the start of a shift, often in the dark, on a checklist they have completed hundreds of times. Where a fleet wants coverage rather than only what was flagged, RapidEye reads a short set of walk-around photos taken through a capture link that opens on any phone, and the findings still land against the Geotab asset and date.
Will RapidEye change a defect, a repair status or a certification in MyGeotab?
No. MyGeotab stays the compliance record. Repair statuses, repair remarks, the Repair signed by field and every certification stay exactly as your people set them. RapidEye reads and reports, and your maintenance office decides what to do inside MyGeotab.
Does RapidEye work with custom defect lists?
Yes. MyGeotab lets you build defect lists of your own parts and defects, apply them to groups, and mark parts as a required sign off, and drivers pick the list by name during an inspection. RapidEye reads the photos against the parts your list actually names, so a defect list built for refuse packers is read as a refuse packer and not as a tractor unit.
Is this useful for trailers as well as trucks?
Yes, and trailers are often where it pays. A defect list in MyGeotab can be set to apply to devices, trailers, or both, and the Drive app flags defects against a trailer the same way. A trailer moves between tractors and drivers, so damage on it is the kind that nobody ends up owning. A photo read at each inspection puts a date on it.
Other platforms where a driver check produces photos
Fleet systems in the same seat as Geotab, each with its own name for the inspection.
FleetioPhotos on Inspection Submissions from Fleetio Go, read item by item
SamsaraDVIR photos from the driver app, read alongside the maintenance record
MotiveInspection defects that Motive turns into work orders, read from the photo up
Whip AroundPre-trip and post-trip forms completed on a phone, every photo checked
Verizon ConnectNotes and photos added to prefilled DVIR checklists, read per asset
All fleet integrations
Sources
- Geotab Support Center, asset inspection documentation for the Drive app and MyGeotab, including defect lists and repairsgeotab.com
- Geotab product pages, driver vehicle inspection reportgeotab.com
Sources are named at the publisher level and were checked against the publisher's live pages before this page was published.
