AI turnover inspection for Operto Teams

Overview

Operto Teams already makes your staff prove the work with a photo; what it does not do is look at the photo. A Task Rule generates the Task, the Task Form attached to it puts a checklist on the Staff Dashboard with Image Upload and Video Upload elements you can mark required, and the submission is saved with the Task, printable with images, shareable on the Owner Report. That is a better photo record than most operations platforms keep. But a required photo element is satisfied by any photo, and the Property Status flips to Clean because Complete was tapped, not because the photo showed a clean room. RapidEye reads those photos and videos, plus the property, the Task, its dates and the assigned staff, and returns one finding per problem: new damage, cleaning that was missed, an item that is gone, with the before and after photos side by side.

How it works with Operto Teams

Operto Teams builds the turnover from the booking: a Task Rule of type After Check Out or Change Over generates a Task per booking or vacancy, the Task lands on the Scheduling Calendar and the assigned staff member's Staff Dashboard, and the Task Form attached to the rule tells them what to do and what to photograph. RapidEye follows that shape. Each element type on the Task Form is a place a photo gets taken, and each photo is something RapidEye can read.

• Image Upload and Multiple Image Upload elements. These are the room-by-room evidence. RapidEye reads each photo against the last submission of the same spot at the same property, so a new burn on the counter, a cracked shower door or a stained sofa cushion is attributed to the booking that just checked out and not the one before. A hypothetical: a Check-out Clean at a 4-bedroom property might come back with one finding, a chip in the kitchen tile that was not in last Thursday's submission, before and after side by side, tied to the booking dates on the Task.
• Video Upload and Multiple Video Upload elements. Operto Teams accepts video from the Staff Dashboard once it is turned on in System Settings, and a walkthrough video covers far more of a room than a fixed photo. RapidEye reads video the same way: the shot of the hallway with the bulb still out, the bathroom bin with the liner not replaced, the bedroom the cleaner walked past without turning on the light.
• The Checked/See Notes/NA grid, radio buttons and dropdowns. These record what the cleaner attested. The checklist tick is a claim; the photo behind it is what RapidEye reads. Restock towels checked, plus a bathroom photo with two towels where this property keeps four, is a missing-item finding.
• Issues from the Staff Dashboard. When staff tap Issue Form, flag Damage or Maintenance and upload images, RapidEye reads those images too, so the Issue you manage on the Issues page arrives with the prior state of that spot and the booking that sat between. Most damage is never submitted as an Issue; it shows up in the routine Task Form photos, and that is where RapidEye finds it.
• Task Form Variations. A property with a hot tub gets the hot tub variation and the hot tub photo. RapidEye learns each property's standard from its own submissions, so the variation is the standard the photo is checked against, not a generic one.

Each finding names the property, the Task, the spot, the kind of problem, how serious it is, and shows the before and after photos with a suggested next step. Findings land in the RapidEye dashboard first, with Slack or email as optional copies. You decide what happens in Operto Teams: an Issue with a One-Off Task behind it, a note on the property, a word with the cleaner. These are examples, not the edges of what gets read. If your team documents differently, with a Quality Inspection Task Rule, a full video walkthrough, 3D scans, or a form of your own, that is something we set up with you.

How to connect Operto Teams to RapidEye

1. Task Rules with Task Forms that ask for photos. In Operto Teams, go to Setup, then Task Forms, and make sure the Task Form attached to your cleaning Task Rules (After Check Out, Change Over, Before Check-In) contains at least one Image Upload, Multiple Image Upload or Video Upload element, ideally one per room, marked required. Each Task those rules generate then carries the photos RapidEye reads.
2. Photos from the Staff Dashboard. Your staff keep working the Task on the Staff Dashboard: Start Task, fill in the Task Form, take or upload the photos, Complete. Those photos, and the images on any Issue they submit, are what RapidEye reads. If your Task Forms do not ask for photos yet, a RapidEye capture link goes in the Task Form instead: any phone, no app, a fixed set of angles per room, taken before Complete is tapped.
3. Add Rapid Eye as Staff. In Operto Teams, go to Setup, then Staff, then +Add Staff, and add Rapid Eye with the email support@rapideyeinspections.com. Tick Allow Administration Area Access with Reports selected, check all properties under Assign Properties, and tick Send Welcome Email on Save. Only the Main Administrator can grant administration access.

That is the whole setup. Staff change nothing, the Scheduling Calendar changes nothing, and the first findings arrive after the first Tasks are marked Complete.

How a Task Form photo works in Operto Teams, from Task Rule to Complete

Checked against Operto Teams' help centre, September 2026.

Operto Teams, formerly VRScheduler, is the scheduling and housekeeping half of the Operto suite, and its help centre is unusually thorough about the photo. According to Operto Teams' help centre documentation (operto.com), Task Forms are interactive guidelines shown on Staff Dashboards, attached to Task Rules so that when a rule auto-generates a Task such as a Check-out Clean, the form is already there for the assigned staff. A Task Form is a container; the work is done by its Elements, each of which can be marked required and shown on the Owner Report. The whole run, and where RapidEye reads in it, looks like this.

Stages and screens as documented by Operto Teams. The last line of each row is what RapidEye does there.

The element types, and what each can prove on its own

Operto Teams' Task Form Examples article lists the element types its customers actually use. Grouped by what they record, they fall into four kinds, and only one of them records the room rather than the cleaner.

Where a Task Form Submission can be seen

The help centre counts five, and it is worth knowing them because the answer to "who looked at that photo" is one of these.

All five are places a person goes to look. None is a place the photo gets looked at on its own.

Can Operto Teams tell you whether the clean was actually done?

Not from the Task. Every signal Operto Teams' documentation describes is set by the person doing the work: Complete and Done are tapped on the Staff Dashboard, the grid is ticked by whoever holds the phone, and the Property Status changes to whatever the Task Rule says when Complete is tapped. The help centre is candid about the last one: the status always shows the last event that changed it, so a property can read Clean while it is dirty, and the fix it offers is to update the status by hand. The image troubleshooting articles cover why a photo arrives as a strange icon or a zero-second video (device settings, the 1 GB limit, no uploads from the cloud), and the Task Form articles cover how to require a photo and where to print it. None of them describes anyone, or anything, reviewing what the photo shows, and the quality-tracking article's answer is a second Task for a human inspector with a rating dropdown. That is the gap this integration fills. Operto Teams already collects the one thing that can settle the question, a required photo on every Task, at every property; RapidEye is the part that looks at it, every time, and tells you what it shows.

Operto Teams integration FAQ