AI photo review for Corrigo work orders

Overview

A Corrigo work order is a record of service, not a record of condition. It carries the asset, the property, the task, the NTE, the SLA, the timestamped check in and check out, the completion description, the repair code and every document anyone attached along the way. What it does not carry is a reading of those documents. Corrigo's job is to get work raised, dispatched, done, verified and invoiced across hundreds of sites and dozens of providers, and it does that; nobody's job is to open the photos on the four thousand work orders that closed this month. RapidEye reads them: the photos on the work order, plus the asset, the property, the dates and who attached them, and returns a finding per problem with the photos it came from.

How it works with Corrigo

Corrigo already sorts the work into shapes, and the checks follow those shapes rather than inventing new ones. Everything below is an example of the kind of thing RapidEye returns, not the boundary of it: RapidEye reads whatever documentation your team already produces, including video walkthroughs and 3D scans, and reports against whatever standard you care about at that property. If the job type you are thinking of is not on this list, it is a conversation, not a no.

• Reactive work orders. A tech checks in, fixes the thing, checks out and attaches two photos. RapidEye reads whether the reported fault is visibly resolved and, separately, what else is in the frame: the panel left open, the ceiling tile still stained, the leak that moved rather than stopped.
• PM and RM schedules. A PM schedule generates the same work order against the same asset on an interval, with Procedure Templates attached. That repetition is the useful part. RapidEye lines this quarter's photos up against the last four and reports drift rather than a single snapshot.
• Required Documents. Where a schedule carries a Photographic Proof of Work Done slot, Corrigo makes sure the slot gets filled. RapidEye is what reads the picture that landed in it, so a filled slot and finished work stop being the same claim.
• Provider work across the network. Work sent out over the network comes back through the CruChat with the provider's photos in it. RapidEye applies one standard to every provider on every site, so the pattern by vendor shows up without anyone building a scorecard by hand.
• Assets and spaces. Corrigo hangs equipment, room areas and spaces off a property in an asset hierarchy. RapidEye attaches every finding to that same asset, so the history reads as one story per unit rather than a pile of unrelated jobs.

Each finding names the property, the asset, where in the frame the problem is, what kind of problem it is, how serious, and the photos it came from, with the earlier photo beside the new one. It lands in the RapidEye dashboard and, if you want it there, a Slack channel or an inbox the facilities team already reads. What happens next in Corrigo is yours: verify the work order, reopen it, raise a child work order, or push back on the invoice. If your team documents in a format we have not named here, video, scans, or an inspection form of your own, we set that up with you.

How to connect Corrigo to RapidEye

1. The properties you want covered. Corrigo scopes a user record to Properties and Portfolios, so the scope you give RapidEye is exactly what it reads. Most teams start with one region or one portfolio and widen it.
2. The photos you already get. A provider dragging a file into the CruChat, a tech tapping the plus icon in the mobile app, a Required Documents slot on a PM schedule: all of it counts. For a job type that produces no photos today, RapidEye sends a capture link that opens on any phone, no app to install, a fixed set of angles at the asset.
3. Add RapidEye as a user. Users, then Manager, then add Rapid Eye with the properties above. The modal has the details.

How photos move through a Corrigo work order

Checked against Corrigo's help centre and developer documentation, September 2026.

Corrigo is JLL's facilities management platform, and it has two faces: Corrigo Enterprise, the back office where the requestor raises, assigns and verifies work, and CorrigoPro, where the service provider picks it up. A work order crosses between them, and photos can be attached at almost every crossing. According to Corrigo's help centre documentation (jllt.com), the provider side runs through a CruChat, a per work order message thread where actions and files are timestamped together.

1. NewRaised in the back office against a customer, a space, an asset and a task, or generated automatically by a PM or RM schedule. Corrigo's documentation notes that a work order cannot be deleted, only cancelled or recalled.
2. Waiting for acceptance, then OpenThe provider accepts or rejects. From here on, a file dragged into the CruChat message box attaches to the work order, with a prompt asking who should see it: Cru, CruLeads, or All, which includes the requestor.
3. Open: In ProgressThe tech checks in on site, by tapping Check In in the mobile app or through the IVR phone code. This is when equipment gets photographed, via the plus icon at the bottom of the CruChat screen.
4. Open: PausedWaiting on parts, on a quote approval against the NTE, or on tomorrow. The thread stays open and keeps collecting messages and files.
5. CompletedCheck Out prompts a description of the work done, a repair category and code where the requestor requires them, the equipment worked on, and a customer signature where that setting is on. Any Required Documents slot has to be filled.
6. Verified, then invoicedThe requestor rates the work during verification and, depending on settings, the provider cannot invoice until that verification is done. This is the last moment the photos are worth anything to you, and the moment nobody has time to look.

Steps where a photo can be attached to the work order.

In the back office those same files sit in the Documents section of the work order, each with a Share flag deciding whether the provider can see it. CorrigoPro caps an attachment at 20MB and 80 characters of file name. Two years after a work order is completed, recalled or rejected, CorrigoPro archives it on a fortnightly sweep, and archived work orders have to be retrieved before anyone can act on them again.

Can Corrigo require a photo before the work order closes?

Yes, and it is worth knowing about. Corrigo Enterprise has a feature called Required Documents, which CorrigoPro's developer documentation describes as the equivalent of filing cabinet drawers, each dedicated to a single document. A drawer is configured on a schedule and carries down to every work order that schedule generates. The examples the documentation gives are a Fire Sprinkler Inspection Checklist, an Elevator Inspection Certificate, and Photographic Proof of Work Done. Each drawer carries its own status:

Read that list closely and the shape of the problem is right there in the data model. Corrigo can tell you whether a photo exists and whether somebody clicked Reviewed. Neither Corrigo nor any other work order system claims to tell you what the photo shows, because that is a different kind of question. That is the question RapidEye answers, and Reviewed becomes a statement about the asset rather than about a click.

What Corrigo already gives an inspection layer to work with

More than most systems, which is why this integration is worth building. Each work order is tied to a specific asset in a hierarchy under a property, and equipment assets carry a TagID that drives QR code scanning in the field, so the photos arrive already labelled with what they are of. Schedules repeat against the same asset on a fixed interval, which is the closest thing in facilities to a controlled before and after. Verification sits between completion and invoice approval, which is a natural place for a finding to land. RapidEye plugs into that structure instead of asking your team to build a parallel one.

Corrigo integration FAQ