AI inspections for Planon

Overview

A photo on a Planon job proves the visit happened; it does not tell anyone what the building looks like now. Planon files it perfectly: the photo an engineer takes on the app is stored in a communication log on the order, or on the maintenance activity it belongs to, next to the asset, the space and the person who did the work. What no estate has is the hour it takes to open a week of those logs across forty buildings. RapidEye reads the property, space and asset structure in Planon and the photos attached to the work, and returns one finding per issue, filed against the same building and the same asset.

How it works with Planon

Planon's Asset & Maintenance Management solution splits the work the way a maintenance office thinks about it, so the checks follow the same split.

• Reactive work orders. Someone reported a failure and an engineer went out. The photos on the job show the fault and the fix; RapidEye reads both and says whether the space around the repair came back to standard, or whether a ceiling tile, a scuffed corridor wall and a missing extinguisher sign went home with the fault report.
• Planned maintenance orders and their activities. A PPM order can carry several maintenance activities, sorted by asset code so a main asset and its sub-assets appear together. RapidEye reads the photos per activity and returns a condition line per asset, not per visit.
• Checklist items that came back with an observation. Planon lets an engineer mark an item Assessed with observation and add a reason. That is a sentence. RapidEye adds the picture behind it: how bad, how far it has moved since the last visit, and whether it is the same observation for the third quarter running.
• Condition assessments captured in the field. Planon's Asset Lifecycle Management module captures asset and facility observations against a pre-defined scoring method. RapidEye scores the same photographs consistently across every surveyor and every site, so two buildings inspected by two people are still comparable.
• Team orders and contractors. A job sent to a whole team is picked up by whoever accepts first. When the work is done by a contractor you do not employ, the photos are the only account of the site you get, and reading all of them is the whole point.

Each finding carries the building, the space, the asset, what kind of problem it is, how serious it is, the photos it came from and a suggested next step. It lands in the RapidEye dashboard and, if you want, a channel or inbox for the maintenance office. Nothing is written back to Planon: your team decides whether a finding becomes a new reactive work order. If your inputs are different, a video walkthrough of a plant room, a 3D scan of a floor, or an inspection format your own surveyors wrote, that is a setup conversation, not a limitation.

How to connect Planon to RapidEye

1. Your Planon property structure. Properties, spaces and assets as they are registered today. Assets mapped to buildings or spaces give the sharpest results, because that is the address every finding is filed to.
2. A source for the job photos. If your engineers already use the Photos block on a job, RapidEye reads those. If they do not, RapidEye sends a capture link that opens on any phone with no install: a fixed set of angles at the asset and the space around it, taken before the job is closed.
3. A Planon user for RapidEye. Add RapidEye as a user and link it to a user group, since Planon takes a user's rights from the function profile on the group. The Connect button has the details.

Where a photo goes when an engineer closes a Planon job

Checked against Planon's product documentation, September 2026.

Planon is an integrated workplace management system for real estate, facilities and maintenance, and the field half of it is the AppSuite app an engineer carries. According to Planon's help centre documentation (planoncloud.com), a job in My jobs opens as a set of information blocks, each summarising one part of the work. That layout is the reason a Planon photo is never orphaned: it arrives attached to an asset, a location and a time.

Questionnaires attached to a job appear as their own block, and the app's job icons separate a reactive work order from a planned maintenance order, a team order, a high-priority job and an appointment booking.

The filing underneath is careful. Planon's documentation states that photos, actions and signatures added to a job are stored in communication log records on the order, shown on the Order details level in Work Orders, and that photos added to a maintenance activity are stored on that activity instead, one level down under Orders, Maintenance activities and Order sub-details. Actions the engineer takes on the device, including start work, travel, wait, pause, resume, discontinue and a bar code scan, each write their own log line with the reason attached.

Does Planon record what the engineer decided?

Yes, precisely. On a planned maintenance order the engineer works through the checklist items on each maintenance activity and sets a result for each one, with a reason and a comment where the configuration asks for them.

• Not assessedThe default. The item has not been looked at yet.
• DoneCarried out. One word covering a job well done and a job done at speed at the end of a long shift.
• Assessed with observationLooked at, and something is not right. The reason field explains it in a sentence; the photo, if one was taken, sits in the communication log underneath.
• Unable to assessThe engineer could not get to it. A meaningful gap in a compliance record, and easy to miss in a portfolio-wide report.

So the record of condition in Planon is exact about who did what and when, and it hands the judgment of how the building actually looks to the person who was standing there. That is the right design for a system of record, and it leaves an estate manager with a quantity of correct, unread evidence that grows every week. RapidEye reads that evidence at portfolio scale and turns it into findings that carry the same building, space and asset codes Planon already uses.

Planon integration FAQ