AI turnover inspection for Lavanda

Overview

The Lavanda Room rack tells you what somebody said about a unit, not what the unit looks like. It holds four cleanliness states, quick views that turn a building into a housekeeping queue, and counts for arrivals, departures and units still dirty with a guest due. The status itself is set by a person selecting Mark clean, and Lavanda's own documentation says the cleaning task and the cleanliness status are separate records: closing the task does not make the unit clean, and marking the unit clean does not close a task. RapidEye sits across that gap. It reads your buildings, units and booking dates from Lavanda together with the pictures attached to each cleaning or check-in task, and returns one finding per problem, with the picture from the last clean beside the picture from this one.

How it works with Lavanda

Lavanda runs operations as two halves that never quite meet: the tasks your workforce is allocated, and the cleanliness state on the rack. RapidEye follows the task, because that is where the pictures are, and reports against the unit, because that is where you look.

• The cleaning task on a changeover. A resident or guest leaves, a task is generated for the unit, and somebody works it. The pictures taken there are the first sight of how the last stay ended. RapidEye compares them with the pictures from the previous clean of the same unit, so a scorched worktop, a cracked shower screen or a bedside lamp that is no longer there is attributed to the booking that sat between the two, not to the one before it.
• The check-in task before an arrival. A unit that has stood empty collects dust, a dead bulb and a kettle somebody borrowed for the flat upstairs. RapidEye reads the check-in pictures against what the unit held when it was last signed off, and names what is missing.
• The units the rack counts as arrivals at risk. Those are the ones still marked dirty with a guest due the same day, and they are where the operations desk is already looking. A finding on one of them says which unit and what to fix, instead of sending somebody up to look.
• Tickets with several tasks behind them. In Lavanda a ticket collects related tasks, so a broken sink becomes a valve order, a maintenance visit and an access code. RapidEye keeps the picture from before the ticket and the picture after the last task closes, which is the dated record of the repair that the ticket itself does not hold.
• Units set out of order. Out of order is a state of its own, counted apart from dirty. RapidEye holds the last known condition of a unit going into a closure and reads what comes back, so what the contractor found is a matter of record rather than of memory.

A finding names the building and the unit, the spot, the type of problem, how serious it is, the picture from last time next to this one, the time it was taken, and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox for the operations desk if you want it there. Nothing is written back: whether the unit goes to Dirty, whether a ticket is raised, whether a charge follows, stays your call inside Lavanda. Pictures are the common case, not the boundary. Teams who film a walkthrough instead of shooting stills, who hold scans of each unit type, or who want findings scored against an inspection form of their own get that set up with us on the first call.

How to connect Lavanda to RapidEye

1. The buildings and units you clean. In Lavanda, go to Inventory, then Buildings, and confirm the buildings whose units you want checked. Every unit on the Room rack for those buildings is in scope, with its zone if you use zones, and units set out of order are left out until they come back.
2. Where the cleaning pictures come from. If your cleaners already add pictures to the cleaning or check-in task, RapidEye reads those. If they do not, a RapidEye capture link goes out instead: any phone, no app to install, a fixed set of angles per room, taken before anyone marks the unit clean.
3. The invite. Lavanda invitations are sent by a user with the Admin role. Ask your Admin to invite Rapid Eye with the email support@rapideyeinspections.com, and we take it from there.

Nothing changes for the people doing the work. The same allocations, the same tasks, the same rack.

The Lavanda Room rack, and what it can and cannot tell you

Checked against Lavanda's help centre, September 2026.

The Room rack is where a Lavanda operator finds out whether a unit is ready. According to Lavanda's help centre documentation (lavanda.app), you open it from Operations, choose a building and a date, and read the position for that day; a Zoom control moves between Building, Floor, Zone and Unit, and the filter field searches by unit and by booking. Cleanliness is one of four states, and only two of them are ones a person can set.

Above the rack sit the counts for the selected date, and beside it the quick views that turn a building into a working list. Each answers a scheduling question well. None of them answers a quality question at all.

The counts follow the same shape: Arrivals, Departures, Occupied, Vacant clean, Vacant dirty, Out of order, and the one every operations desk watches, Arrivals at risk, which is units still marked dirty with a guest due the same day. Changing a status needs the housekeeping permission, and without it Lavanda answers that you do not have permission to update housekeeping status. Bulk actions stop at 25 units at a time, so a large building takes several passes.

Can Lavanda tell you a unit was actually cleaned?

It cannot, and it says so plainly. Lavanda's help centre states that cleaning tasks and cleanliness status are separate records, that completing a cleaning task does not by itself change a unit to Clean, and that no setting in the PMS changes the clean or dirty status on a schedule, so every change is made by a person on the Room rack. The task side is real work: Lavanda's operations pages describe auto-generated or manually created tasks, a central allocations view, tickets that collect related tasks, and external contractors receiving and completing assigned tasks in a mobile web app without needing a user account. The help centre even documents how to add pictures to a cleaning or check-in task, described there as attaching photographs as evidence to a task. What no page in either place describes is anything that opens those pictures and checks them. That is the whole of the integration: the evidence already exists, and RapidEye is the reader.

Lavanda integration FAQ