AI inspection review for Record360

Overview

A Record360 inspection is a complete record of a unit at a moment, and there are more of them than anyone can open. Record360 guides a driver, technician or counter agent through a workflow on a phone, requires the photos and video before the inspection can be submitted, time stamps it, holds the signature, and stacks it onto that unit's history. That capture problem is solved. What is left is a reading problem: a hundred locations running checkout and return every day produce more media in a week than a damage recovery team can look at in a month, so the frames that would have paid for themselves sit unopened. RapidEye reads all of them, and returns a finding per issue with the unit, the spot, the severity and the frames.

How it works with Record360

Record360 already organises the day into workflows, so the checks follow them. A unit moves through checkout, rental, return and service, and each stop leaves a set of frames behind. RapidEye reads the frames from each stop against the ones before it.

• Checkout inspections. The set your billable claims will stand on. RapidEye reads it as a condition statement and tells you what was already on the unit when it left, so a return finding is never argued about a scratch that was there in March.
• Return inspections. The one everybody wants read and nobody has time for. A curb rash on the right rear alloy, a torn seat bolster, a cracked mirror housing, a missing load bar comes back as a finding naming the panel and the two frames it sits between.
• Delivery and pre-delivery inspections. A unit that leaves the yard should leave ready. RapidEye reads the PDI media for the things a rushed walk misses: a chipped windscreen, a warning lamp lit in the cluster shot, a decal peeling, a tyre down to the wear bar.
• Service and maintenance inspections. These frames are the only dated evidence that a repair happened and that the unit came back different. RapidEye keeps the before and the after against the unit so a warranty or billback conversation has something to point at.
• Cleanliness and readiness. Not damage, but the reason a customer complains. Sand in the footwells, a stained headliner, an empty document wallet, a missing floor mat. Findings for these are typed separately so they route to the wash bay and not to the claims desk.
• Coverage of the capture itself. When a required angle is dark, framed past the panel or missed on the sequence, RapidEye says which one, so the unit gets rewalked while it is still in the lane.

Every finding names the unit, where on the unit, what kind of issue, how serious, the frames before and after, and a suggested next step. Findings land in the RapidEye dashboard and, if you want them there, in a Slack channel or an inbox per location. Nothing is decided for you: you choose whether it becomes a task, a work order or a charge inside Record360. And this list is a set of examples, not a boundary. RapidEye reads whatever documentation your teams already produce, video walkarounds and 3D scans included, and reports against whatever standard you hold your fleet to, so if your use case is not named above, ask us and we will set it up with you.

How to connect Record360 to RapidEye

1. A Record360 account with units in it. Whether inventory arrives by scheduled import, by live lookup from your rental or dealer system, or is keyed in by hand, RapidEye works from the units Record360 already knows about.
2. The workflows that carry the photos. Tell us which ones matter: checkout, return, delivery, PDI, service, or one of your own. Record360 already requires the media on those forms, so the frames exist and no capture step changes.
3. Read access to the inspections. Tell us you run Record360 and we set the access up with your team. Your drivers and technicians keep the same app, the same guided checklist, the same routine.

What a Record360 inspection actually holds

Checked against Record360's product and developer documentation, September 2026.

Record360 is mobile inspection software for rental, fleet and service operations, and it has been built around asset condition since 2013. According to Record360's developer documentation (record360.com), the platform is organised around four objects that matter here: the unit, which is the asset with its reference number, VIN or serial, make, model, year and its running meters; the workflow, which is the form the inspector follows for a given event; the inspection, which is one completed pass through a workflow on one unit; and the task, which is work assigned to a person or a location. Every inspection is filed against a unit, so a unit carries its own condition history for as long as you have run the platform.

1. CheckoutGuided walk before the unit leaves, with the pre-existing damage documented and the customer signature attached.Baseline
2. Out on rentNothing captured. This is the window every later dispute is actually about.Gap
3. ReturnThe same workflow run again. Record360 puts the two side by side for comparison.Comparison
4. ServiceA separate workflow, usually a different person, filed against the same unit.History

Run that loop a few thousand times and the unit's history is the most valuable thing in the account, and the least read.

The mobile app is built for people working away from a desk. Record360's product pages describe capture that keeps working offline in low-connectivity environments and syncs when the device reconnects, guided step-by-step forms, required fields that block submission until the right photos and inputs are there, and 360 AI Blur Detection, which gives the inspector real-time feedback so a soft frame is caught while the unit is still in front of them. Inline Photos attach media to a specific checklist item rather than to the inspection as a whole. Draft inspections can be started at a desk and handed to a teammate to finish on a phone in the field.

Does Record360 already flag damage in photos?

Yes, at the point of capture. Record360's own materials describe AI that flags missing photos, skipped steps and potential damage before an inspection is approved, and side-by-side comparison so a reviewer can see checkout against return in one view. That is real work already done, and it is why a Record360 fleet is such a good place to add reading: the frames are consistent, sharp, complete and filed to the right unit, which is exactly the input a condition model wants.

What RapidEye adds is the pass across the whole archive rather than the pair in front of you. Record360's comparison is a person's tool, and it is a good one, but it needs a person: someone has to pick the unit, open the two inspections and look. RapidEye reads every inspection in every workflow at every location the day it lands, holds the full sequence of appearances for that unit rather than the most recent two, and separates the mark that arrived on this rental from the four that were already there. That is the difference between evidence you could produce if asked and a queue of issues that arrived this morning.

What about units that are not vehicles?

They are the same problem. Record360 is used across heavy equipment, truck and trailer, and auto rental, and RapidEye reads condition on a physical thing over time regardless of what the thing is. An excavator's undercarriage, a reefer's door seal, a scissor lift's guard rail and a sedan's rear quarter are all just surfaces with a history. What changes per asset class is the finding taxonomy, which we set up with you against your own standard.

Record360 integration FAQ