AI inspections for Limble

Overview

Limble is unusual among maintenance systems in that photos arrive from both ends of a job. A requester with no Limble account scans a QR code, tags the asset and uploads a picture of what is wrong; a technician opens the task in the mobile app, works through its instructions, and uploads a picture of what they found or of the finished job. Those two pictures, taken hours apart by people with different reasons for taking them, are a before and an after that nobody ever puts side by side. RapidEye reads them, with the asset, the location and the time, and returns a finding per problem: damage, wear, a cleaning miss, a missing part, a safety issue, with how serious it looks and the photos behind it.

How it works with Limble

Limble sorts work into work requests, work orders and PMs, and the photos on each answer a different question. The checks follow that split.

• Work requests. The picture a requester attaches is the only image of the problem before anyone touched it. RapidEye reads it against how that asset and that space have looked before, so a request about a jammed door can also surface the water stain spreading behind it.
• Work orders closed from the phone. The technician's completion photo is checked for the state of the whole area, not only the part that was fixed: the panel back on, the guard replaced, the floor clear, the spare parts not left where someone will trip.
• Recurring PMs. The same asset comes round on the same schedule with the same instruction set, so its photos line up in a sequence. A belt fraying across six months reads as a trend, not six unremarkable pictures.
• The spaces, not only the equipment. Restrooms, corridors, kitchens, loading docks and grounds sit in the location tree next to the assets. What the camera caught around the asset is condition data about the space, and it is read as such.
• Contractor work. When the person closing the task is the person invoicing for it, the photos attached to their instructions are the independent account of what got left behind.

Each finding names the asset, the location, what kind of problem it is, how serious it looks, the photos it came from, and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox for the maintenance team if you want it there. You decide whether it becomes a new work order in Limble. If your team captures something other than stills, a video walkthrough of a plant room, a 3D scan, or an inspection format of your own, that is a conversation with us and not a limit; the reading is not tied to one kind of file, and the standard it reads against is yours.

How to connect Limble to RapidEye

1. A Limble account with your assets and locations set up. Tell us which locations are in scope. Limble assigns roles by location, so this lines up with how your account is already organised.
2. The photos you already collect. The work request portals for your locations, and the tasks that carry a file or picture attachment instruction. If a PM that should carry photos does not yet, either add that instruction or use a RapidEye capture link, which opens on any phone with no app to install.
3. Add RapidEye as a user. From the Manage Users page, Add User, View Only role at the locations in scope. The connect panel has the details.

How a Limble task is built, and where a photo can live in it

Checked against Limble's help centre, September 2026.

Limble is a CMMS for work orders, preventive maintenance and asset tracking, and the unit everything is made of is the instruction. According to Limble's help centre documentation (limblecmms.com), instructions are line items included in a task, the things that need to get done in order to complete a task, and a task is built by opening it and clicking Add Instruction to choose a type. That choice is where a manager decides, in advance, what evidence a completed job will leave behind.

Advanced types go further into workflow: Assign PM, Start WO, Capture Signature, Request Approval, Reassign Task and Verify Location. Instruction sets let a group of these be reused across PMs, work requests and work order templates, which is how a photo requirement gets applied consistently rather than one task at a time.

Who else can put a photo into Limble?

Anyone in the building, and this is the part people underuse. Limble documents that work requests let anyone in your organization request maintenance work, even those without a Limble account, through a portal reached by QR code, URL or email, and that the portal acts as a digital ticketing system that intakes all requests and generates tasks from them. The default form asks for a title, a description under How can we help?, the requester's name and email, Where or What is Having the Problem? to link an area or asset, and Add Picture/Document, which Limble introduces with the line that a picture is worth 1,000 words: the requester may not have the same maintenance speak as your technicians, so a photo gives the team a better idea of the problem.

Each location gets its own portal and form, plus a global portal covering every location, and every asset card carries its own work request QR code. So a photo of any asset in the estate is one scan away from a person who was standing in front of it. What none of it does, and no CMMS does, is look at the picture. The instruction is answered, the ticket is generated, the task is completed, and the image sits on the record. Reading it is the piece RapidEye adds.

Limble integration FAQ