An assignment rule is only useful if it still works when the first cleaner says no. Sending a notification is easy. Recovering from silence, a cancellation or a changed booking requires a defined sequence with a deadline and someone responsible for the outcome.
This guide describes a workflow to design and test with your team. The timings are examples, not platform defaults. Use your actual service durations and coverage arrangements to decide how long each step can wait.
Separate eligibility from preference
First decide who can do the job. Check the cleaner's working hours, existing assignments, travel time, access arrangements and any property-specific requirements. Only then rank the eligible people by familiarity, preferred zone or another agreed criterion.
A preferred cleaner who cannot arrive in time is not a viable candidate. Equally, a free slot on a calendar does not prove that the person has the right equipment or can collect the linen. Make those requirements part of the property brief.
Define the assignment states
Keep the difference between offered and accepted visible. An offer needs a response deadline; an acceptance needs a record of who accepted and which version of the job they saw. If the scope or time window changes materially, seek confirmation again.
| Event | Next action |
|---|---|
| Offer declined | Offer to the next eligible cleaner |
| Offer expires | Close the offer before moving to the next candidate |
| Accepted cleaner cancels | Recheck the remaining time and backup availability |
| No viable cleaner remains | Alert the coordinator with the latest viable start |
Keep one authoritative assignment. If multiple people receive an offer, the first valid acceptance must close the other offers. An expired link should not allow a second cleaner to accept a job that has already been reassigned.
Make the rules understandable to the team
Write each rule as a decision someone could explain without the software. For example: first check whether the preferred cleaner can complete the service before the review deadline; if not, offer it to another eligible cleaner in the same area; if nobody accepts before the escalation point, assign the coordinator to arrange cover. The order and time limits should be visible to whoever handles exceptions.
Avoid ranking people on a single signal such as proximity. A cleaner who is close but already committed, lacks access or cannot collect linen may be a worse choice than someone farther away. If a coordinator overrides the ranking, record the reason. That feedback helps improve the rule without hiding a decision inside a notification history.
Work out the fallback deadline
Calculate the latest viable start from the required finish, the expected service duration and the review buffer. The time left before that start determines whether you can wait for another response or need a coordinator to intervene.
Do not reuse the same response window for a booking next week and a job due this afternoon. Urgency should change the workflow, including when a person takes over. Record the reason for escalation so the coordinator does not have to reconstruct the situation from notifications.
Handle booking changes without duplicate work
Use a stable booking reference to connect calendar updates to the existing turnover. A changed checkout should update the job and prompt a feasibility check, rather than silently creating another clean. A cancelled booking also needs a clear rule for any service already arranged.
Before sending an offer, check that the booking is still current and that the job is not already covered. After acceptance, show the cleaner the latest scope and time window. These checks matter when updates arrive close together or someone edits the schedule manually.
Give every booking update a visible outcome: unchanged assignment, reconfirmation requested, reassignment started or manual review required. If a calendar feed delivers an update late, do not assume the newest message is the newest state. Compare the booking reference and effective times before changing an accepted job. The coordinator should be able to see why an offer was withdrawn.
Test the awkward cases first
- The first cleaner declines and the backup accepts.
- No one responds before the offer deadline.
- Two cleaners try to accept the same job.
- A booking changes after a cleaner has accepted.
- A cancellation leaves too little time for a normal fallback.
- A notification fails, or a cleaner has no connection.
Run these scenarios with test jobs before using the rules on guest arrivals. Check the final assignment, the visible status and the messages received by each person. A test passes when the next action is clear, not simply when a notification was sent.
Keep a human recovery path
Automation needs an owner when it reaches the end of its candidate list, loses a notification channel or encounters conflicting booking details. Define the escalation point from the guest arrival deadline, not from an arbitrary number of retries. Give the coordinator the booking, last accepted assignment, offers already sent and time remaining in one view.
If no viable cover exists, stop sending offers that cannot realistically be fulfilled. The property manager can then decide whether to arrange an alternative service or contact the guest. Record the resolution, including who made the decision, so the team can inspect failures and adjust coverage before the next busy day.
Measure whether coverage improves
Track how long jobs remain unaccepted, how often a coordinator intervenes and how often an accepted job still starts late. Review those measures alongside the reasons for declines. They can reveal an unrealistic time window or a thin backup pool that faster messaging will not fix.
Start with one area and keep a manual recovery path available. Expand the automation after the team can explain its decisions and reliably recover from an exception. That is the point at which assignment rules become an operational aid rather than another system to watch.
