Fleet Rabbit
Fleet Rabbit integrationFleet and logisticsInspection and maintenance app

AI inspections for Fleet Rabbit

Read the photos on every pre-trip and post-trip inspection in Fleet Rabbit, including the items the driver marked pass, and see what the checklist did not catch.

How a Fleet Rabbit inspection is built

Overview

A DVIR is a record of what the driver reported, and a pass is the most common thing a driver reports. Fleet Rabbit turns the paper inspection into a structured one: the driver picks the vehicle and the type, works a checklist item by item marking each pass or fail with notes, documents a fault with photos, and signs. A fault becomes a corrective action and, from there, a work order carrying the vehicle, the description and the photos. Every one of those photos is there because somebody had already found the problem. RapidEye reads the vehicle, the driver and the checklist from Fleet Rabbit along with all the photos on the inspection, and returns a finding per issue tied to the unit and the inspection it came from.

The passes get read tooTwenty-three items marked pass and signed is a claim. The photos either back it up or they do not.
Shift to shift on one unitPost-trip against the next pre-trip, so damage lands on the shift it happened in, not the driver who found it.
Fleet Rabbit stays the recordNo inspection, fault, corrective action or work order changes. RapidEye reads and reports.

How it works with Fleet Rabbit

Fleet Rabbit's inspection module already breaks the day into named records, and each one is a place photographs are taken. The checks follow the same shape.

  • The pre-trip inspection. The driver has not driven yet, so whatever the photos show came off the last shift or the yard. RapidEye reads them against the unit's previous post-trip and names anything new: a fresh scrape on a fairing, a light out, a tire that was not like that last night.
  • The post-trip inspection. This is the one taken at the end of a long day, and it is the one that gets rushed. RapidEye reads what is actually in the frame rather than what got typed into the notes field.
  • Faults and corrective actions. A documented fault carries a description and photo evidence, and its corrective action sits in a state until somebody moves it. RapidEye keeps the photo from when the fault was raised beside the photo from after the repair, so a closed corrective action has a picture behind it.
  • Work orders from defects. Fleet Rabbit converts a DVIR defect into a work order automatically. The photos on the work order are the driver's; RapidEye adds what else is visible on that unit, so the technician is not surprised on the lift.
  • Incident reports. An incident carries photos, a severity rating and the conditions at the time. RapidEye reads those against the unit's inspection history, which is what turns an account of what happened into a dated comparison.
  • Trailers, chassis and equipment. Fleet Rabbit runs equipment-specific forms across vehicle types. RapidEye knows what each type is supposed to look like at your company and reads it that way.

Each finding names the unit, the part of the vehicle, where in the photo it is, what kind of problem it is, how serious, the earlier and later photos, and a suggested next step. It lands in the RapidEye dashboard and, if you want it there, a Slack channel or an inbox for the shop and the safety manager. You decide whether it becomes a fault in Fleet Rabbit. If your drivers shoot a walkaround video instead of stills, or you want a check written against a standard of your own rather than ours, that is a setup conversation, not a limit.

How to connect Fleet Rabbit to RapidEye

  1. A Fleet Rabbit account with your vehicles on it. The vehicles, trailers and inspection forms you want checked. Assets you do not inspect stay out of it.
  2. The inspection photos you already collect. Fleet Rabbit's mobile inspection captures photos straight from the device camera, so RapidEye reads what is already on your inspections. Where a form asks for no photo at all, RapidEye sends a capture link that opens on any phone, no app to install, with a fixed set of angles per unit.
  3. A conversation with us. Tell us you run Fleet Rabbit and which units to start with. We connect it with your team. Drivers keep running the same pre-trip and post-trip checks on the same phone.

How a Fleet Rabbit inspection is built

Checked against Fleet Rabbit's product documentation, September 2026.

Fleet Rabbit is inspection, maintenance and compliance software for truck fleets, and its inspection module is a genuinely good piece of design: three steps, select the vehicle and the inspection type, work the checklist, sign and submit. According to Fleet Rabbit's own product documentation (fleetrabbit.com), the DVIR carries the driver, the vehicle, the type (pre-trip or post-trip), the date, odometer and location tracking, a live progress count of items passed and failed, and a digital driver signature, and it is built to satisfy FMCSA 396.11 with records exportable to PDF and Excel for an audit. Here is what one looks like when it is submitted.

DVIR formTruck Pre-Trip Inspection23 items · 22 pass · 1 fail
Driver
Assigned
Vehicle
Selected
Type
Pre-trip
Signature
Captured
Brake systemFault documented, photo attached, work order createdFail
Tires and wheelsNo note, no photoPass
Lights and reflectorsNo note, no photoPass
Body and mirrorsNo note, no photoPass
The other nineteen itemsNo note, no photoPass
One item on this inspection has a photograph. It is the one the driver already knew about.

That is not a flaw in the form. It is what a checklist is: a fast, legible, auditable record of what a person says they found, and Fleet Rabbit makes producing one take minutes instead of a quarter of an hour. The limit is the same limit every checklist has ever had, on paper or on a phone. Twenty-two passes and a signature tell you the driver went through the list. They do not tell you what the truck looked like.

What happens to a fault

It becomes work, tracked in states. Fleet Rabbit documents fault records that carry a detailed description and photo evidence, a corrective action whose status moves as the repair progresses, and a direct link to the work order that resolves it, with the whole history kept as a searchable audit trail. On the DVIR side the same idea is expressed as defect status, and the platform generates the work order from the defect without anybody re-keying it.

Not takenA fault is on the record and nothing has moved yet. The photo the driver took is the only evidence of what it looked like that morning.
PendingAn inspector or technician has it. Fleet Rabbit tracks the corrective action; the condition of the rest of the unit is not part of that record.
TakenLinked to a work order and resolved. What is missing is a picture of the same spot afterwards, which is what RapidEye keeps.

Does Fleet Rabbit capture photos on inspections?

Yes, and well. Fleet Rabbit's documentation describes one-tap photo capture from the device camera, optional GPS location tagging, digital signature capture, voice-to-text notes, barcode and QR scanning, and an offline mode that syncs when the phone gets signal again, on Android, iOS and desktop. Faults take photo evidence; incident reports take up to six photos with a severity rating and the weather conditions. What is not described anywhere, because no fleet platform describes it, is anything that opens those photographs and tells you what is in them. A fleet running four thousand inspections a year has an archive nobody has the hours to read. RapidEye reads it, and the vehicle, driver, form and timestamps on the Fleet Rabbit record are what make each finding land on the right unit and the right shift.

Fleet Rabbit integration FAQ

Does RapidEye integrate with Fleet Rabbit?

Yes. RapidEye reads the vehicle, the driver, the inspection form and the timestamps from Fleet Rabbit, along with the photos attached to the inspection, then returns a finding per issue: damage, a defect the checklist did not catch, or equipment that is not on the vehicle, with the earlier and later photos. Inspections, faults, corrective actions and work orders in Fleet Rabbit are not changed.

Fleet Rabbit already captures photos on a fault. What does RapidEye add?

A photo in Fleet Rabbit exists because a driver marked an item failed and documented it. That is the small part of the inspection where somebody already knew there was a problem. RapidEye reads every photo from the inspection, including the ones taken beside items marked pass, and says what is in them.

Can RapidEye check a pre-trip inspection that came back all pass?

An all-pass sheet is precisely what it rechecks. A twenty-three item pre-trip checklist with twenty-three passes and a driver signature is a claim about the vehicle. RapidEye reads the photos taken during that inspection and confirms or contradicts it, naming the unit, the part of the vehicle and the spot in the photo.

Will RapidEye create faults or work orders in Fleet Rabbit?

No. Fleet Rabbit stays in charge of inspections, fault records, corrective action status and the work orders they generate. RapidEye reads and reports; your safety manager decides whether a finding becomes a fault in Fleet Rabbit.

Does RapidEye work with the custom inspection forms we built?

Yes. Fleet Rabbit lets you build equipment-specific forms with custom fields on top of its form library, and RapidEye reads the photos against whatever standard your form is trying to enforce. If your winter checklist cares about something ours does not, we set that up with you.

What about incident reports?

Incident reports in Fleet Rabbit carry photos, a severity rating, weather conditions and a description of what happened. RapidEye reads those photos against the unit's inspection history, which is what turns a damage claim from one person's account into a dated comparison.

Other fleet software RapidEye works with

Platforms where a driver, an inspector or a technician is already photographing a unit.

Sources

  • Fleet Rabbit product documentation, inspection and DVIR modulesfleetrabbit.com
  • Fleet Rabbit product documentation, maintenance and work ordersfleetrabbit.com

Sources are named at the publisher level and were checked against the publisher's live pages before this page was published.