Part of the Relax Global Group
Cleaner-first operations for short-term rentals
RelaxOps schedules the cleans your calendars create, puts them in the right cleaner's day in the right order, and keeps the property knowledge, the accountability and the audit trail in one system — instead of spread across spreadsheets and group chats.
Already set up? Signing in takes you straight to your dashboard.
14 Hill St
Departure · 150m
12 Hill St
10:00 – 12:00
8 Bay Rd
12:00 – 14:00
3 Vista Ct
10:00 – 11:30
The dispatch board: unassigned work on the left, each cleaner's day beside it.
One system, four views of the same day
Operators do not need another dashboard. They need the schedule, the properties, the table they actually work from, and a record of what happened — all agreeing with each other.
Property schedule
Stays banded behind the cleans they create, a week at a time.
Operations table
Dense and filterable: every job, cleaner, tag and status in one place.
Cleaner dispatch
14 Hill St
Departure · 150m
12 Hill St
10:00 – 12:00
8 Bay Rd
12:00 – 14:00
3 Vista Ct
10:00 – 11:30
Drag to assign; the server picks the time so routes stay in order.
Governance
Coordinator assigned 12 Hill St to Carla Chen
10:04Dispatch route reordered · 1 later task moved
10:06iCal sync checkout changed · clean rescheduled
09:12
Versioned knowledge, acknowledgements, and an append-only audit trail.
What it actually does
Scheduling and dispatch
Reservations arrive from the property calendars and become cleans on their checkout date. Assign by dragging a job into a cleaner’s column; the server decides the time — service default, inserted into the route, or appended after the last job — so ordinary drops never collide.
Property visibility
A week per property, with stays banded behind the cleans they generate, so a back-to-back changeover is obvious before it becomes urgent. Access notes, service type and history stay with the property.
Cleaner accountability
Cleaners work from their own day: start and finish times, checklists, photos and comments against the job itself. Coordinators watch progress instead of chasing messages.
Knowledge and governance
Client and property rules live as versioned knowledge with acknowledgement, and every operational change lands in an append-only audit trail recording who did it and what caused it.
A changeover day, start to finish
This is the loop RelaxOps was built around — the real one, with moved checkouts, reshuffled routes and jobs nobody has picked up yet.
- 1
Calendars sync
Airbnb and channel calendars feed reservations in continuously. A checkout creates the changeover clean; a moved checkout cancels the old job and creates the new one, with the reason recorded against both.
- 2
The unassigned queue clears
Everything without a cleaner sits in one column. Drag a job to a cleaner and it lands at the operational start time — 10:00 for a checkout clean — or slots into their route without overlapping the work already there.
- 3
The day runs
Routes reorder as reality changes and breaks stay put. Cleaners mark jobs started and finished, add comments and attach photos, and the board reflects it without anyone refreshing.
- 4
The record stands
Who assigned what, which sync moved a clean, when a rule was acknowledged — captured as immutable events you can answer questions from weeks later.
Coordinator assigned 12 Hill St to Carla Chen
10:04Dispatch route reordered · 1 later task moved
10:06iCal sync checkout changed · clean rescheduled
09:12
Built for the awkward cases
- Back-to-back changeovers flagged before the day starts
- Cleaner breaks treated as immovable when routes shuffle
- An exact-time override for when the operator knows better
- Comments and photos attached to the job, not lost in a chat thread
Run today's cleans in RelaxOps
Sign in to pick up your board, or join the waitlist if you would like RelaxOps set up for your properties.