AI inspections for EquipmentShare T3

Overview

A T3 inspection proves a task was done, not what the machine looked like while it was being done. T3 knows where every asset is, how many hours it has run, when its next service interval falls, and which mechanic closed which ticket. The photos on those tickets are the one part it holds but nobody reads: they go on to prove a pass or a fail, and then they sit in the ticket. RapidEye reads them. It pulls the photos off inspection and work order tasks in T3, compares each machine to how it looked in earlier tickets, and returns a finding for the damage, the missing part or the safety condition that nobody wrote down.

How it works with EquipmentShare T3

Everything on the Service dashboard produces photos at some point, and each of those points is worth a different kind of read.

• Inspection task photos. A mechanic works a task list in the Link mobile app, sliding each step to the right as it is done, adding a photo where the task asks for one. RapidEye reads the frame behind the pass: a hose weeping where the tick says fine, a cracked cab glass in the corner of a tyre shot, a step or a handrail missing from the machine entirely.
• Failed inspection items. A failed item becomes a work order of its own, titled with whatever the mechanic typed and marked Soft Down or Hard Down. RapidEye reads the photo attached to the fail and grades what it sees, so an item written up as cosmetic and one that will stop the machine do not read the same on the report.
• Work order updates. The Updates section takes a photo, a file and a note with a timestamp and the user who posted it. That is the natural before and after of a repair, and RapidEye pairs them: what was broken on the way in, what the machine looked like on the way out.
• Return from a job or a rental. The interesting comparison is not one ticket, it is two. RapidEye holds every earlier photo of the asset, so damage that appeared between the last inspection and this one is dated to a window, not argued about.
• Cleanliness and site standards. Mud packed into a track frame, a cab full of bottles, a decal or a serial plate gone. None of it fails a task list, all of it costs money later, and it is all visible in photos you already have.

A finding names the asset, where on the machine, the kind of issue, how serious it is, the earlier and current photos, and a suggested next step, and it lands in the RapidEye dashboard or a Slack channel or inbox for the shop. Your team decides whether it becomes a work order in T3. Photos are only the easiest starting point: if your crews shoot video walkthroughs of a machine, or run a condition form of your own, or capture return-to-yard footage that never touches T3, that is a setup conversation, not a limit.

How to connect EquipmentShare T3 to RapidEye

1. A T3 account with the assets you service. Tell us which branches or groups to start with. T3 already scopes what a user sees by group, and assets outside that scope stay outside it.
2. Photos on the tasks. In Manage Task Lists, set the steps that matter to the Photo task type, or tick Require photos as proof of task completion. Mechanics keep adding them from the camera icon in Link exactly as they do now. If a machine is photographed outside T3, at the gate or on the truck, RapidEye can take those through a capture link that opens on any phone with no app to install.
3. Add RapidEye as a user in T3. An Owner or Manager adds the user from Company, then Users. The modal has the details.

How a T3 inspection carries a photo

Checked against the T3 help centre, September 2026.

T3 is EquipmentShare's fleet platform, and the part of it that matters here is the Service dashboard in the Fleet web app: four tabs, Work Orders, Inspections, Upcoming Service and Manage Task Lists. According to the T3 help centre documentation (estrack.com), the Work Orders tab toggles between Open, Closed and Billed tables, and a work order carries an asset, a branch, a description of the problem, a priority, a severity, tags, an assigned mechanic and a scheduled date. An inspection is created against the asset itself, from the Fleet Map in the Link mobile app, and it opens with the machine's hours and miles already filled in.

What a mechanic actually does inside either one is a task list, built in Manage Task Lists and attached to the ticket or to a whole maintenance group. The task list is where photos enter T3, and its five task types decide what each step leaves behind.

Photos reach a task from the camera icon in Link, either taken there or picked from the phone's library, and T3 tracks the upload separately in a Work Order Uploads window so a mechanic on bad site signal can see what has landed and retry what has not. The other photo slot is the Updates section on a work order or inspection, which takes photos, files and notes with a timestamp and the name of the user who added them. Whether a photo is demanded on a failed task, or on every task, is a company setting rather than something each mechanic decides.

When the inspection is completed, every failed item is written up as its own work order, and the mechanic marks each one at one of T3's two severity levels.

Can T3 tell you a machine got damaged?

Only if a person says so. Everything above is a faithful record of what a mechanic decided: the tick, the verdict, the severity, the note. T3's own documentation describes photos as evidence of a pass or a fail on a task, and nothing in it describes anything reading those photos back or comparing one machine against how it looked last month. That is the honest shape of the gap, and it is not a shortcoming of the platform: a fleet system's job is to know where the assets are and what has been done to them, and T3 does that at a scale EquipmentShare says runs past 410,000 connected assets. Nobody's job, in any fleet, is to sit and look at ten thousand task photos. That is the job RapidEye takes.

EquipmentShare T3 integration FAQ