AI inspections for Texada Software

Overview

A Texada Inspection is a structured record of one asset at one moment, and your fleet produces more of them than anyone opens. Texada already carries the asset, the contract, the work order and the ticket in one system, and its Inspection forms already pull photos out of the yard and off the truck. What the forms cannot do is compare a photo to the last twenty taken of that machine, or answer against a standard nobody wrote a checkbox for. RapidEye reads the photos on Texada Inspections, tickets and check-ins together with the asset, the contract dates and the branch, and returns one finding per issue.

How it works with Texada Software

Texada already sorts the work by the document the photos hang off, so the reading follows the same shape. An asset leaves on a delivery ticket, sits on a contract, comes back through a check-in, and gets a work order when something is wrong. Each of those stops leaves photos behind on an Inspection.

• Check-out and delivery. The evidence that settles what gets invoiced. RapidEye reads the Overview Photos as a condition statement and records what was already on the unit when it left the yard, so a scratch that has been on the counterweight since spring never becomes an argument in November.
• Check-in and pickup. The frames everybody wants read. A cracked lens, a torn seat, a bent guard rail, a missing hydraulic hose comes back as a finding naming the asset, where on the machine, how bad, and the two sets of frames it sits between.
• Work order Inspections. A mechanic's photos are the only dated evidence that a repair happened and that the machine came back different. RapidEye keeps the before and the after on the asset, so a warranty or billback conversation has something to point at.
• Standalone Inspections. Yard walks, PM checks, a unit pulled off rent for a look. Texada lets any Service and Rental Mobile user submit one against an asset, even with no form attached, and those photos are read the same as the rest.
• Missing attachments and setup. A bucket, a set of forks, a jib, a manual in the cab holder, a fire extinguisher. These are not damage, and they are what turns into a call from the jobsite. Findings for them are typed separately so they route to the yard and not the claims desk.
• Coverage of the capture itself. When an angle is dark, out of focus, framed past the boom or simply missed, RapidEye names which one, so the unit gets walked again while it is still in the lane.

Every finding names the asset, the spot on the machine, the type of issue, how serious it is, 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 a branch inbox. Nothing is decided for you: your counter or service team chooses whether it becomes a work order or a charge inside Texada. 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 the thing you care about is not named here, ask us and we will set it up with you.

How to connect Texada Software to RapidEye

1. A Texada account with your fleet in it. The assets you rent and service, with the Inspection forms already assigned to their models and product groups. Whatever a branch is set up to inspect today stays exactly as it is.
2. The photos already on your Inspections. Texada Inspection forms carry photo fields, and the Check-In / Check-Out screen has its own Overview Photos and Damage sections, so the frames exist. Tell us which forms and which branches matter and RapidEye reads those. If a yard photographs units in another app or shoots video walkarounds instead, RapidEye reads those too.
3. Read access for RapidEye. Add RapidEye as a user in Texada, from the User Menu under Settings, Company Settings, Users. Your drivers, mechanics and yard workers keep the same forms and the same routine.

What a Texada Inspection actually holds

Checked against Texada's knowledge base, September 2026.

Texada Software runs rental and service for equipment dealers and rental companies, and Inspections sit at the centre of how condition gets recorded. According to Texada's help centre documentation (texadasoftware.com), an Inspection form is a series of questions built in Service, Rental and Financials (Classic) and completed in Service and Rental Mobile, and the forms attach themselves: any form assigned to an asset's model, or failing that its product group, is added automatically to the documents that asset appears on. A mechanic on an articulated boom lift can be handed a generic work order form plus a boom-specific one, and a response can trigger behaviour on its own, so an engine marked not functional flags the asset for maintenance and pulls it out of available rental inventory.

There are three kinds, and they are filled out by different people at different moments.

The forms themselves are built from a fixed set of field types. Two of them put pixels in the system and the rest put text in it.

The Check-In / Check-Out screen in Service and Rental Mobile is its own path into the same idea. A yard worker searches for a customer or scans a barcode, opens their contracts, taps a piece of equipment, and lands on an Inspection screen with an Overview Photos section and an Add Photos button. Ticking Damaged opens a Damage section for photos of the damaged area and a damage code. Finish the assets, proceed, review, take the customer's signature, and the whole thing is sent through to Rental Management for counter staff. Some products cannot be returned without this: Texada documents an "Item Can't be Returned Automatically" message for exactly that case.

Does Texada already read inspection photos?

Yes, at check-in. Texada's AI Damage Detection compares the before photos from a check-out or delivery ticket with the after photos from a check-in or pickup ticket, flags newly detected damage, sends a notification to the inspector's phone with the damaged area highlighted, and files an entry on an AI Damage Detection list page in Rental Management (Next) for a counter operator to judge. It returns one of four results.

Texada is precise about what makes this work: both before and after photos are needed, at least three per side of the transaction, four sides ideal, up to ten used per inspection, good light, one machine per frame, and it recommends making a mandatory Walk Around form with Front, Right, Back and Left image inputs so staff actually take them. That is a well-drawn feature and a good reason to keep photographing units.

What no Texada page describes is a reading of everything else. The work order Inspections a mechanic fills out, the standalone Inspections from a yard walk, and the accumulated Inspection history on an asset over dozens of contracts are stored, viewable one at a time, and exportable as PDFs. Nobody opens them at fleet scale. That is where the integration earns its place: RapidEye reads the whole trail rather than a single before-and-after pair, holds a baseline per asset rather than per contract, and reports against the standards a rental business cares about beyond damage, missing attachments, wear on a wear part, cleanliness, and service issues a form never had a question for.

Texada Software integration FAQ