AI turnover inspection for Lodgable

Overview

Lodgable holds the booking, not the clean. A Lodgable listing carries the content, the rates and availability, the policies including the check-in window, and an active or inactive switch that decides whether the property is on sale across the booking sites. Its help centre documents all of that in detail, and documents no cleaning task, housekeeping schedule or inspection record. So the turn happens somewhere else, and the photos from it end up in a chat thread or a camera roll that nobody opens. RapidEye takes the property and the stay dates from Lodgable and reads those photos against them, returning a finding per problem: what is newly damaged, what was not cleaned, and what is missing from the room.

How it works with Lodgable

Lodgable's own structure gives the integration three things: the listing, the reservation, and the policies that fix the shape of a turnaround day. Everything else comes from the photos. Here is what each part contributes.

• The listing. Every finding is filed against a Lodgable listing rather than against a photo folder, which is what makes the record readable months later when an owner asks what happened in their house in July. Because a listing in Lodgable can be switched between active and inactive, a property that quietly went off sale after a bad turn is visible in the history rather than lost in it.
• The reservation. Stay dates decide attribution. A cracked splashback that shows up in the photos after one guest and not before is that guest's; a scuff that has been in the frame for six weeks is the property's, and reporting it as new would cost you a claim and a relationship. RapidEye reads each turn against the last known state of the same spot for that reason.
• The check-in window under Policies. Lodgable lets you set the time a guest can check in on each listing. That time is the deadline the clean is really running against, so it is what separates a finding you can still act on from one that becomes an apology.
• The photos from the clean. This is where the substance is. Streaked glass, a bin that was not emptied, hair left in a drain, a bulb out in a hallway that nobody switched on, bedding remade over a stain, a room that has no photo in the set at all. That last one matters more than it sounds: the easiest way for a room to go unchecked is for it never to be photographed.
• The system behind Lodgable, if you run one. Lodgable documents connecting an Escapia account through Account Settings and its App Directory, and mapping RNS properties into Lodgable. Where that is your stack, the housekeeping record lives on that side and RapidEye can read a single photo set against both the Lodgable stay and the record behind it.

A finding names the property and the room, the kind of problem, how serious it is, the frames it was found in with their times, and a suggested next step. Read each finding in the RapidEye dashboard, or have it posted to Slack or sent to an inbox. What you do with one, whether that is holding the property back, sending the cleaner in again or opening a claim, stays with your team. And photos are the common input rather than the only one: teams that film a walkthrough on the way out, teams with a Matterport scan of each house, and teams who want findings scored against an inspection form of their own get that configured with us at setup, so if your input is not listed here, ask.

How to connect Lodgable to RapidEye

1. Your listings and the check-in window. In Lodgable, open the Listings view and check that every property you want covered is active, and that the check-in window under Policies is the one you actually run. That window is the deadline a turnover is racing, and it is what tells RapidEye which findings still matter for the next arrival.
2. Where the turnover photos live. Tell us where the photos from a clean end up today: a group chat, a shared album, a camera roll, or a cleaning app your team runs beside Lodgable. If nobody photographs the turn yet, a RapidEye capture link goes to the cleaner's phone instead: no install, a fixed set of angles per room, taken before the property goes back on sale.
3. Invite RapidEye as a team member. In Lodgable, click Team members in the left navigation of the main dashboard, or the plus symbol at the top right and then Add team member. Enter the first name Rapid, the last name Eye and the email support@rapideyeinspections.com, then click Send invite. We accept the invitation from the email and finish the setup from our side.

Nothing about how your cleaners work has to change for this. The listings, rates, availability and payouts you have configured stay exactly as they are.

What a Lodgable listing records, and what it leaves to you

Checked against Lodgable's help centre, September 2026.

According to Lodgable's help centre documentation (lodgable.com), a listing is a distribution record. You create it, meet the minimum content requirements to activate it, set rates and availability, edit policies including the window a guest can check in, and flip a status switch in the Listings view that is blue when the property is active and grey when it is not. An inactive property comes off the travel agencies it is listed with while its data stays in Lodgable for easy reactivation. Reservations arrive from the connected sites with the guest's contact details and encrypted card data saved against them, and payouts and guest payments are configured under Account Settings. It is a tightly drawn scope, and Lodgable is explicit that it is aimed at hosts with five or more listings billing in US dollars. What that scope does not include is anything about the condition of the house.

Left column as documented by Lodgable. Right column is what an operator still has to establish some other way.

Does Lodgable have a housekeeping or cleaning module?

No, and its documentation does not suggest one. The help centre is organised into collections for getting started, managing your properties, Airbnb, Vrbo and the other booking sites, getting paid, cancellations, onboarding, tech support, and two collections for hosts connected through RNS or Escapia. Across all of them there is no cleaning task, no housekeeping schedule, no checklist and no inspection record. That is a design decision rather than an omission: Lodgable's job is to get the listing onto the channels and the booking into your account, and it does that job without pretending to run your field team. The consequence for the operator is simply that the turnover lives outside the software, which is why the photos from it are usually the only evidence that exists.

What this means if you run Escapia or RNS behind Lodgable

Two of Lodgable's help centre collections exist for hosts whose property management system sits behind it. The Escapia path runs through enabling Lodgable as a network partner, selecting units for distribution, and connecting the account from Lodgable's App Directory before mapping each property; the RNS path is a similar mapping of properties and bookings between the two. If that is your setup, the housekeeping record you care about is on the other system and the stay is in Lodgable, which is a common shape and one RapidEye reads across. One photo set, checked against the property in Lodgable and the work record behind it, with the finding filed once.

Three shapes a Lodgable turnover takes

• The message threadThe cleaner sends photos when the house is done, and the thread is the only record. RapidEye reads the same photos and turns them into findings filed against the listing and the stay.
• A cleaning app beside LodgableTurnovers are scheduled and marked done in a separate tool. The photos are already collected there and only need reading.
• Nobody photographs the turnThe most common shape, and the easiest to fix. A capture link opens on the cleaner's phone with nothing to install and asks for the same angles every time.

Lodgable integration FAQ