AI turnover inspection for RueBaRue

Overview

The RueBaRue Inspection Board is where somebody declares a property ready; it is not where anybody checks that it is. Every arrival in the window gets a row, and a manager clicks a status on that row. Behind the row sit the tasks that did the work, and those tasks do carry photos: Attachments is a documented task field, beside the checklist, the assignees and the notes. What RueBaRue has no feature for is opening them. RapidEye is that half. It reads the images on your cleaning, inspection and maintenance tasks along with the property, the guest stay and the date, and returns one finding per problem, with the frame from last time next to the frame from today.

How it works with RueBaRue

RueBaRue is built as a chain: a message becomes a task, the task carries a standard, the standard leaves a record, and the record decides an arrival. RapidEye plugs into the middle of that chain, at the point where a photo exists and nobody is going to look at it.

• A guest or owner message turns into a taskThe complaint arrives already attached to the property and the reservation. When the task closes with a photo of the repaired shower door, RapidEye reads whether the thing complained about is the thing that got fixed, and whether anything beside it moved.
• A recurring rule fires the turnover cleanRueBaRue can anchor a recurring task a set number of days after checkout, with assignees and a checklist template already on it. Every one of those generated tasks is a turnover, so every one gets read: the burn on the worktop that is new since the last set of frames, the bulb still out in the hallway, the second bath towel that never came back.
• A required checklist item asks for proofRueBaRue lets a template mark items required so completion stays tied to the standard. A required item with a photo beside it is exactly the pair RapidEye scores: reset the kitchen and restock amenities, ticked, with an after frame showing a coffee tray holding two pods where your standard is six.
• Attachments pile up on completed tasksEvery task that closed this season left images in RueBaRue that nobody reopened. On the first connection RapidEye reads that history and builds a baseline of what each room looks like when it is right, which is what makes a two-pod coffee tray a finding instead of a photo.
• The arrival lands on the Inspection BoardThe board is the last checkpoint before a guest walks in, and RueBaRue tells you to start the morning by triaging every arrival with no status. RapidEye gives that triage a starting position: the arrivals where the photos disagree with the work, ranked, so the ones you walk are the ones worth walking.

A finding names the property, the room, the spot, the kind of problem, how serious it is, the two frames, and a suggested next step. It arrives in the RapidEye dashboard and, if you want it there, in a Slack channel or an inbox. What happens back in RueBaRue is yours: a new maintenance task, a note on the board row, a red status on the arrival, a charge against the guest. And a photo on a task is the most common input, not the boundary. Teams that film a walkthrough, that hold 3D scans of each home, or that want findings scored against an inspection form they wrote themselves get that set up with us at the start.

How to connect RueBaRue to RapidEye

1. The tasks that carry the turnover. In RueBaRue, open Operations and then Tasks, and tell us which task types cover your turnovers. Cleaning and inspection are the usual pair, and the recurring rules anchored after checkout or before check-in are the ones tied to a stay.
2. Photos on the task. Your team adds photos in the Attachments field on the task, and those are what RapidEye reads. If photos are not part of the routine yet, a RapidEye capture link goes on the task instead: any phone, no app, a fixed set of angles per room, taken before the task is marked Completed.
3. Add RapidEye on the Team page. Go to the Team page, click Add a Person, enter Rapid Eye with the email support@rapideyeinspections.com, save, then click Invite to RueBaRue under Actions. The modal has it in the same words.

Nothing changes for the people doing the work. Same tasks, same checklists, same board.

The Inspection Board, and what a readiness status actually asserts

Checked against RueBaRue's product pages and help centre, September 2026.

According to RueBaRue's help centre documentation (intercom.help), the Inspection Board lists every reservation arriving in the window you have selected, guest stays, owner stays and maintenance blocks alike, in a daily or weekly view, with the property and reservation number, the check-in and check-out dates, the guest name and phone, the assigned status, and any notes. You step forward and back a day or a week at a time, filter by status or by property tag, and set a status from a selector on the row. There are six of them, and each is a different sentence about the property.

Statuses, colours and stated uses as documented by RueBaRue; the third column is ours. RueBaRue also documents that one status is active per row at a time, that a status saves automatically, that the row picks up a coloured accent bar so the day can be scanned, and that a status can be cleared back to no status. Its product pages list further readiness states beyond these six, including No Early Check-in Allowed and Stale Clean.

Does RueBaRue hold photos of the work?

Yes, and operators get this wrong in both directions. RueBaRue's help centre documents Attachments as a task field, described as photos or supporting files, sitting alongside the summary, type, property, guest, status, priority, category, manager, assignees, checklist and tags. Its product pages describe turning an issue into a task and adding a checklist or photos, and keeping notes, comments, photos and costs on the same record. So the images exist, dated, on the right property, next to the right reservation. What no page in RueBaRue's documentation describes is anything that looks at them: no comparison with how the room looked last week, no flag when a required item is ticked and the photo disagrees, no way to ask which of today's twelve arrivals is the one to walk. That is a reading problem rather than a storage problem, and it is the half RapidEye supplies.

Where the board sits in the day

RueBaRue's own advice is to open the Daily view each morning, filter to No Status, and give every arrival a status; to use Out and In through the day for the turnovers that need priority; and to leave a note whenever there is context the next person should have. That routine is sound, and it is also where the ceiling is: a person is assigning a condition to a property they have not seen, from tasks they have not opened. Hand the same routine a set of findings ranked by severity and the triage becomes a reading exercise instead of a guessing one, with the notes column carrying something a colleague can act on.

RueBaRue integration FAQ