Cleaning and turnover on Nest: a practical guide — WEVONE

At 11:02 AM on a Sunday in Lyon, a guest closes the door behind them and taps checkout on Nest. The next guest is scheduled to arrive at 3:00 PM. In traditional short-term rental management, these four hours represent an operational hazard: the host sends an anxious message via WhatsApp to a freelance cleaner, prays no trash was left behind, and hopes the laundry finishes before the door code changes. When the cleaner cancels at 11:30 AM, the host either rushes over with a vacuum or faces a 1-star review and a refund claim.

Turnover is not a domestic chore; it is an industrial supply chain squeezed into a tight temporal window. WEVONE treats it as a programmatic sequence, bridging property management in Nest with service execution in Mission.

The Failure Modes of Legacy Turnover

Most short-term rental platforms disclaim operational responsibility the moment a booking is confirmed. They process payment, take a platform fee, and leave property maintenance to fragmented third-party channels. This decoupling creates three distinct structural failures:

Asymmetric Information: The host does not know the physical state of the apartment until the cleaner arrives. If the outgoing guest damaged a sofa or smoked indoors, the host discovers it long after the deposit retention window has closed.
Incentive Mismatch: Cleaners paid fixed flat rates off-platform are incentivized to complete jobs as quickly as possible, often overlooking invisible hygiene vectors like mattress protectors, filter grates, and cutlery drawers.
Uncoordinated Disruption: If a guest checks out forty minutes late, the cleaner’s schedule collapses, triggering a cascade of delayed check-ins across multiple properties.

To solve this, turnover cannot exist as an informal side agreement. It requires programmatic binding between the booking calendar and the service marketplace.

The Nest-Mission Interlock: How It Works

When a property is listed on Nest, the host specifies a turnover protocol. Rather than managing cleaning off-platform, the listing links directly to the Mission universe—WEVONE’s local service layer.

The moment a guest confirms checkout (or the calendar hits the mandatory checkout threshold), Nest emits a state change event. This event automatically generates a high-priority work order on Mission, routed to qualified service providers operating within a 3-kilometer radius.

The service provider accepts the job based on a standardized rate calculated by square meters, baseline cleaning scope, and turn window urgency. The payout for this task is pulled immediately from the property’s operating balance or the incoming turnover fee and placed into transactional escrow.

[ Guest Checkout ] ──> ( Nest Event ) ──> [ Mission Job Triggered ]
                                                    │
                                                    ▼
[ Escrow Locked ] <── ( Provider Accepts ) <── [ Local Provider ]

The provider does not simply receive an instruction to "clean the flat." They receive a dynamic, time-stamped task protocol anchored to the specific layout of the Nest listing.

A Worked Example: The 180-Minute Window

Consider a 52-square-meter apartment on Rue de la République in Lyon. The turnover protocol operates under strict parameters:

11:00 AM — Checkout & Routing: Guest checks out. Nest triggers a Mission work order for a standard 2-hour turnover. Provider Jean accepts the job via Mission.
11:15 AM — Arrival & Damage Inspection: Jean unlocks the door using a single-use access token generated by the Nest integration. Before touching a broom, Jean completes the 60-second inbound photo audit. He uploads four geo-located, time-stamped images through the app: living room, bedroom, kitchen sink, bathroom.
11:18 AM — Automated Flagging: Jean notes a heavy stain on the rug that was not present in the pre-check-in baseline log. He marks it in the audit tool. Nest instantly pauses the auto-release of the outgoing guest’s security deposit and notifies the host.
11:20 AM to 1:15 PM — Protocol Execution: Jean executes the standardized checklist: sheet swap, surface sanitization, trash extraction, restocking amenities, and HVAC filter check.
1:15 PM — Outbound Verification: Jean uploads six outbound verification photos covering the executed checklist points.
1:20 PM — Escrow Release: Mia cross-checks the outbound photo uploads against the property's baseline standard checklist. Upon successful verification, the transactional escrow releases funds directly to Jean’s WEVONE wallet. The door system re-arms for the incoming guest.

By formalizing every step, the host avoids manual oversight, the cleaner gets guaranteed instant payment upon job completion, and the incoming guest enters a verified environment.

The Technical Mechanisms Behind Nest Turnover

WEVONE’s architecture handles these operations through specific integrated infrastructure:

Transactional Escrow: Funds for the Mission turnover are held isolated from general platform revenue. Neither the host nor WEVONE can arbitrarily withhold payment once the time-stamped photo protocol is complete.
Dispute Windows: If an incoming guest claims improper cleaning within two hours of arrival, the platform opens a dispute window. The outbound photo log submitted by the Mission provider serves as the primary evidentiary record. If the provider omitted a required checklist photo (e.g., inside the microwave), the dispute defaults in favor of the guest.
Contribution Score Impact: Service providers who consistently complete turnovers on time and pass photo audits build a higher Contribution Score within Mission. Higher scores grant priority routing for high-value Nest properties and reduced escrow settlement delays.
Mia's Context Memory: Mia retains historic operational context across both Nest and Mission. If a particular unit consistently requires 30 minutes longer than average due to complex amenities (e.g., a wood-burning stove or high glass surfaces), Mia adjusts the automated Mission time estimate and pricing model for future listings.

Honesty Regarding Stage and Limitations

We must be precise about what is live versus what remains in development or testing.

Shipped and Live: Cross-universe job creation between Nest and Mission is operational. Transactional escrow locks and releases are fully functional. Time-stamped photo logging and mandatory arrival audits are live across all supported regions.
In Beta: Automated computer vision verification of photo logs is currently in beta testing in select markets. Right now, image validation relies on structured human verification logs and algorithmic completeness checks (verifying metadata, lighting, and presence of required targets) rather than AI-driven cleanliness grading.
Operational Limitations: Platform performance depends strictly on local Mission provider density. In high-density urban areas like Paris, Berlin, or Brussels, turnover fulfillment rates exceed 98%. In rural or low-density vacation markets, automated dispatch cannot guarantee immediate provider coverage. In those zones, hosts must assign dedicated fallback providers within the system.

Turnover should not rely on luck, frantic text messages, or unverified promises. By embedding service execution directly into rental infrastructure, Nest and Mission turn physical maintenance into a deterministic, verifiable process.