AI inspections for RDPWin

Overview

A clean status in RDPWin records a decision, not a condition. The Rooms Status screen counts your units by occupancy and clean state, the boards hand each attendant a list with a clean type and a clean time, and an inspector approves what they can reach before the next arrival. What none of it holds is a picture of the unit. RapidEye supplies that half: it reads the room masters and reservation dates from RDPWin and the photos your team takes in each unit, then returns a finding per unit, matched to the stay it belongs to.

How it works with RDPWin

RDPWin already sorts the day for you by occupancy status, so the checks follow the same cut. What differs per row is which stay the photos sit between, and therefore what a difference means.

• Checkout units. A departing guest sits between the last set of photos and today's. A chipped counter edge, a missing bar stool or a scorched duvet comes back as a finding with both photos and the reservation dates in between, which is the form an owner charge has to take.
• Stayover units. The unit is occupied and being serviced on the pattern its clean type sets. RapidEye reads the service photos and flags the untouched bathroom, the bin nobody emptied and the dead bulb while the guest is still there to fix it for.
• Vacant units with an arrival today. Units sitting empty in a shoulder season lose things: a slow cooker borrowed for another unit, the second remote, linens stripped and never replaced. RapidEye names what is in the baseline for that unit and not in today's photos.
• Maintenance holds and work orders. A maintenance reservation holds a unit out of inventory while work happens, and the work order module tracks the asset that got replaced. RapidEye keeps the photo from before the hold and the photo after, so a replaced coffee maker or a repainted wall has a dated visual record next to the billing record.
• Room moves and sleepers. When a guest changes rooms, the unit left behind is picked up as a tidy. Both units get read, so the one abandoned mid-stay does not go back into sale on nobody's word.

Each finding names the unit, the spot in the room, the type of problem, how serious it is, the two photos, and a suggested next step. It lands in the RapidEye dashboard and, if you want it there, a Slack channel or the housekeeping inbox. Your head of housekeeping decides what happens next in RDPWin. Photos are the common case and not the limit: video walkthroughs, 3D scans and an inspection format of your own are all things RapidEye reads, so a check that matters at your properties and is not listed here is something we set up with you.

How to connect RDPWin to RapidEye

1. Your RDPWin room masters. The rental units you clean, with the housekeeping zones and clean types you already run. Non-rental room masters, the lobby and the laundry among them, stay out of it.
2. Where the room photos come from. If your housekeepers or inspectors already photograph units in another app, RapidEye reads those. If they do not, RapidEye sends a capture link that opens in any phone browser with nothing to install: a fixed set of angles per unit, lights on, taken before the room is set to Ready to Inspect.
3. Add RapidEye as a user. In RDPWin, users are added from the System menu under Manage Users. The Connect RDPWin panel has the name and email to use, and we take it from there.

How RDPWin housekeeping works today

Checked against Resort Data Processing's support documentation, September 2026.

RDPWin is the property management system from Resort Data Processing, a Vail, Colorado company whose software runs resorts, condo hotels, vacation rentals, timeshares and campgrounds, with reservations, front desk, housekeeping, work orders and back office in one system. Housekeeping is built on two objects: the board, which is a day's worth of cleans handed to one attendant, and the clean status, which is what the front desk reads before it lets a guest into a unit.

According to Resort Data Processing's support documentation (resortdata.com), the schedule is generated for a date and distributed either by the number of attendants working or by hours per board, with units grouped by maid zone, room number or a defined room sequence. Each board carries the next arrival date, the zone, the assigned housekeeper, the assigned inspector and the housekeeping comments from both the room master and the reservation. Clean types are yours to define, with a clean time per unit per type: the documentation's own examples are a daily clean, a checkout clean, a room move and a no clean, arranged into patterns such as a no clean every day except the third, with a checkout clean at departure.

The three clean statuses

The default clean statuses are Dirty, Inspect and Clean. Ready to Inspect is switched on in housekeeping configuration and, per the documentation, exists so a housekeeper using the maid phone interface can hand a finished unit up rather than declaring it ready themselves.

A fourth column, Tidy, appears when the switch governing room moves is set to it: the old unit is checked as needing a tidy automatically when a guest changes rooms, and clears once the row is marked Inspect or Clean.

The Rooms Status screen, and the button worth knowing about

Rooms Status summarises every unit, maintenance rooms included, by occupancy: Stayover for in-house reservations departing later, Checkout for those leaving today, Sleeper for a reservation whose departure date has already passed, Vacant, Maintenance for units held out of inventory so work can be done, and Non-Rental for lobbies, laundries and storage. It refreshes on a configurable interval, five minutes by default.

The screen also lets a manager change every unit currently displayed in the grid to Clean, to Dirty or to Ready to Inspect in one action. RDP's own documentation is blunt about it: confirmation is required, the change is written to the RDPWin log file for history, and there is no button to put the grid back, so the feature should be used carefully. That is the honest shape of the problem. A status that can be applied to a whole filtered grid at once is a record of an intention, and the unit it describes may or may not match.

Does RDPWin hold housekeeping photos?

No, and its documentation does not claim to. The Rooms Status pages, the housekeeping configuration and procedures training material, and the mobile device pages describe boards, zones, clean types, clean times, housekeepers, inspectors, fixed-cost tracking and status changes written to a log, with no photo attached to a unit or a clean anywhere in them. Mobile housekeeping is a set of browser pages served from your own web server, reached with a mobile password set in Manage Users, with housekeeper and inspector initials matched to the staff tab in housekeeping configuration and access governed by power levels and menu security fence levels. It is a good way to move a status from a phone. It is not a record of what the phone was looking at. That gap is why this page exists: RapidEye holds the visual history for each unit and reads new photos against it, while RDPWin keeps doing what it does well, which is knowing who is in which unit and who is cleaning it.

RDPWin integration FAQ