Room & Cleaning Automations
Automate room status changes and cleaning assignments with triggers and scheduled room jobs in HelloShift.
Automate room status changes and cleaning assignments in HelloShift. There are two types of automations:
Triggers - React to guest events (checkout, check-in, cancellation)
Room Automations - Run on a schedule to create cleaning tasks automatically
Overview
Part 1: Room Automations (Scheduled Automations)
Room Automations automatically create cleaning tasks based on schedules and guest stay patterns. They run daily at a configured time and apply to rooms matching specific conditions.
Accessing Room Automations
Go to AI & Automation > Scheduled Automations > Room
Click the Room Automations tab
You'll see a list of available room automations

Default Room Automations
HelloShift creates these room automations when you set up your site:
Daily Clean
Condition: Mid-stay guests (guests currently in-house, not arriving or departing)
Schedule: Daily at 6:00 AM
Action: Set a cleaning task (starts as "Clean"; pick one of your clean types)
Purpose: Ensures stayover rooms get daily cleaning tasks
Departure Clean
Condition: Guests departing today
Schedule: Daily at 6:00 AM
Action: Set a cleaning task (starts as "Clean"; pick your checkout clean type)
Purpose: Creates checkout cleaning tasks for departing guests
Day 3 Clean (Every 3 Days)
Condition: Mid-stay guests on day 3, 6, 9, etc. of their stay
Schedule: Daily at 6:00 AM
Action: One clean type on day 3, 6, 9… and another (or no task) on the other days. Starts as "Clean" / "Light Clean"
Purpose: Reduces daily cleaning for long-stay guests while ensuring periodic full cleans
Schedule-Based Clean
Condition: Rooms with custom schedules configured
Schedule: Daily at 6:00 AM
Action: Set a cleaning task (starts as "Clean") only if the room's schedule matches today
Purpose: Respects individual room cleaning schedules (e.g., "clean Mondays and Thursdays")
Check the clean types first. The four clean automations above start out setting "Clean" (and "Light Clean"). If your property's clean types have different names, for example "Check Out Clean" and "Service", these automations show an Invalid clean type badge and can't be switched on until you pick one of yours. See Choosing the Clean Type.
Import Room Data
Condition: All rooms
Schedule: Daily at 6:00 AM
Action: Pull room status from PMS
Purpose: Syncs room occupancy and status from your Property Management System
Room Automation Settings
Each room automation has these configurable options:
Available Checks
Custom Check Example
For properties with VIP-specific cleaning schedules:
{% if guest_stay.guest_type contains 'VIP' %}true{% else %}false{% endif %}Available Actions
The room-status actions need a guest condition (Departure Today, Arrival Today, etc.) - they are not available on the All Rooms condition.
Example: Flip Departing Rooms Dirty at 6 AM
Housekeeping wants departing rooms on the Dirty list at the start of the day, without waiting for the guest (or the PMS) to check out:
Condition: Departure Today
Run At: 6:00 AM, daily
Action: Set Room Vacant/Dirty
This works alongside the default Post-Checkout Room Update trigger: the 6 AM automation pre-marks rooms by departure date, and the trigger re-fires on the actual checkout event. Flipping an already-dirty room is a silent no-op, so having both never double-notifies.
Creating a Custom Room Automation
Beyond the default automations, you can create your own scheduled room automations — including automations that generate checklists and tasks. Click New Room Automation on the Room tab (AI & Automation > Scheduled Automations > Room; requires the Housekeeping plan).
A custom room automation combines:
For Guests: which stays to target by date — for example Departure Today matches every guest whose departure date is today, whether or not the PMS has checked them out. Use Departure Today (Not Checked Out) to target only guests still in-house.
Run At + Repeat: the time of day and recurrence — e.g., 6:00 AM daily.
Condition (optional): an additional check, including custom Liquid conditions.
Action: a cleaning task, or Create Checklist / Create Task with a picker for which template to use.
How generated checklists and tasks behave:
One per room per day: a reservation with several guests still produces exactly one checklist or task per room. Multi-room reservations get one per room.
Room-tagged and guest-linked: items land on the room page and housekeeping boards, linked to the guest.
No double-generation: if a Trigger already created the same checklist or task for that room today (or the automation is run twice), no second copy is created.
Checklist skip threshold: if the room’s recent copies of the same checklist are all still incomplete, a new one is skipped.
No room, no item: stays without a room assignment are skipped.
Safe template handling: if the selected template is later deleted or archived, the automation deactivates itself and warns once instead of failing silently.
Use Preview before activating: it lists exactly which rooms match today, what would be created for each, and flags rooms the live run would skip (with the reason).
Example — the most common setup: name it “Departure Checklists”, set For Guests to Departure Today, Run At 6:00 AM daily, Action Create Checklist with your checkout checklist. Every morning, each departing room gets its checklist — no PMS checkout event required.
Note: The Create Checklist action is available on the Staff plan.
Choosing the Clean Type
Room automations and triggers that set a cleaning task use your own clean types, the names you keep under Settings › Housekeeping › Custom Fields (for example Checkout, Stayover, Service). Open the automation and pick one:
Clean type to set: with no condition, the automation sets this clean type on every matching room.
When “<condition>” matches: with a condition (for example Stayover every 3 days), this is the clean type set on matching days. The hint under it says which days those are.
Otherwise: what to set on the other days: another clean type, or Do not set a task, which leaves the room as it is.
System automations (Daily Clean, Departure Clean, Day3-Clean-Repeat, Schedule-Based Clean) always set a cleaning task. You can change the clean type, the guests, the condition and when it runs, but not the kind of action.
If your site has no clean types yet, the picker says so. Admins get a link to add them.
Invalid clean type
An automation that points at a name that isn't one of your clean types (usually an old default such as "Clean", or a type that was renamed outside HelloShift) shows an Invalid clean type badge in the list and a banner on its page. Click the badge to open the form straight at the clean-type picker.
An automation with an invalid clean type can't be switched on. HelloShift says why and links to the fix.
If one is already on, its runs skip the rooms instead of creating a task nobody can complete. Run tells you how many rooms were set and how many were skipped, and the Last Run column shows the skip, for example “Skipped 4 rooms · 6:00 AM: “Clean” isn't a clean type”.
Triggers show the same badge and are refused in the same way.
Renaming and deleting clean types
Renaming a clean type in Settings › Housekeeping › Custom Fields updates every automation and trigger, room default task, open housekeeping task (from yesterday onwards), room credit, and the “<name>” / “<name> Inspection” checklists. Finished tasks keep the old name. The confirmation lists what was updated.
Deleting a clean type that an automation or a room's default task still uses is refused, with a list of what uses it. Change those first, then delete.
Two clean types can't share a name, even with different capitalisation.
Only admins can add, rename or delete clean types.
Enabling/Disabling Room Automations
Go to AI & Automation > Scheduled Automations > Rooms
Find the automation in the list
Click Off to switch it on, or On to switch it off (admins only)
Note: New automations start Off. Switch them on to start generating tasks. An automation with an invalid clean type can't be switched on until you pick one of your clean types.
Part 2: Triggers (Event-Based Automations)
Triggers respond to guest lifecycle events and execute actions immediately or after a delay.
Accessing Triggers
Go to AI & Automation > Triggers
You'll see a list of existing triggers
Click New Trigger to create an automation

Default Triggers
HelloShift creates these system triggers when you set up your site:
Post-Checkout Room Update
Event: Guest Checked Out
Action: Set Room Vacant/Dirty
Purpose: Automatically marks room as dirty when guest departs
Post-Booking Room Assignment
Event: Guest Booking Confirmed
Action: Set Default Cleaning Task
Purpose: Pre-assign cleaning task based on room's default
Post-Cancel Room Update
Event: Booking Cancelled
Action: Remove room assignment if applicable
Creating a Trigger
Step 1: Choose the Event
Select when the automation should trigger:
Step 2: Set a Condition (Optional)
Add conditions to limit when the automation runs:
Step 3: Choose the Action
Select what happens when the trigger fires:
Step 4: Set Delay (Optional)
Add a delay before the action executes:
0 seconds (default) = Immediate
300 seconds = 5 minutes after event
3600 seconds = 1 hour after event
Delays are useful for:
Giving front desk time to complete checkout
Allowing for late checkouts
Staggering cleaner notifications

Common Automation Scenarios
Scenario 1: Auto-Mark Dirty on Checkout
Goal: When guest checks out, automatically mark room dirty
Setup:
Event: Guest Checked Out
Condition: Always
Action: Set Room Vacant/Dirty
Delay: 0 (immediate)
Scenario 2: Assign Cleaner on Checkout
Goal: When guest checks out, assign the room's default cleaner
Setup:
Event: Guest Checked Out
Condition: Guests Departing Today
Action: Assign Default Cleaner
Delay: 300 (5 minutes)
Scenario 3: Set Checkout Task for Departures
Goal: Set cleaning task to "Checkout" for departing guests
Setup:
Event: Guest Checked Out
Condition: Always
Action: Set Cleaning Task: Checkout (your checkout clean type)
Delay: 0
Note: If there is no "Checkout" clean type yet, an admin can add it under Settings › Housekeeping › Custom Fields.
Scenario 4: Notify Housekeeping Lead
Goal: Alert housekeeping supervisor when VIP checks out
Setup:
Event: Guest Checked Out
Condition: Custom (check for VIP tag)
Action: Notify Cleaner on Checkout
Delay: 0
Custom Conditions
For advanced scenarios, write custom Liquid templates that return "true" or "false".
Available Variables
Example: VIP Guests Only
{% if guest_stay.guest_type contains 'VIP' %}true{% else %}false{% endif %}Example: Long Stays
{% assign nights = guest_stay.nights | plus: 0 %}{% if nights > 7 %}true{% else %}false{% endif %}Managing Automations
Enabling/Disabling
Go to Admin > Settings > Automations
Find the trigger in the list
Click the status toggle to enable or disable
Disabled triggers remain configured but don't execute.
Editing a Trigger
Click Edit next to the trigger
Modify delay or condition as needed. On your own triggers you can also pick a different clean type for a Set Cleaning Task action
Note: Event and Action cannot be changed after creation
Click Update Trigger
Deleting a Trigger
Click Delete next to the trigger
Confirm deletion
System triggers (Post-Checkout-Room, etc.) cannot be deleted
Integration with PMS
Automations work with your PMS integration:
From PMS to HelloShift
PMS sends checkout event
HelloShift marks guest as checked out
Checkout automation triggers
Room condition updates to Dirty
From HelloShift to PMS
When enabled in Cleaning settings:
Cleaner marks room Clean
HelloShift syncs status to PMS
Front desk sees updated room status
Automation Flow Example
Here's how automations work together for a typical checkout:
Guest checks out at front desk (PMS event)
PMS syncs checkout status to HelloShift
Post-Checkout automation fires:
Sets room to Vacant/Dirty
Assigns default cleaner
Cleaner receives notification on mobile
Cleaner starts room and timer begins
Cleaner completes room
Room status syncs back to PMS (if enabled)
Best Practices
Keep It Simple
Start with essential automations (checkout → dirty)
Add complexity gradually as needed
Test each automation before enabling others
Use Delays Wisely
Immediate (0) for status changes
Short delay (5-10 min) for notifications
Longer delay if allowing for late checkouts
Monitor and Adjust
Check that automations fire as expected
Review room status after checkouts
Adjust conditions if too many false positives
Combine with Manual Oversight
Automations handle the common case
Staff can always override manually
Use automations to speed up, not replace judgment
Troubleshooting
Automation not firing
Verify the trigger is enabled (active status)
Check that the event matches (Guest Checked Out vs. Guest Checked In)
Confirm PMS integration is working
Review condition - it may be blocking execution
Room status not changing
Check if another automation might be overriding
For a scheduled Set Room action, confirm the automation is On and its run time has passed today
Verify room exists and is active
Look for delays that haven't elapsed yet
Rooms not getting a cleaning task
Look for an Invalid clean type badge on the automation or trigger, and pick one of your clean types
Check the Last Run column: it says when rooms were skipped and why
With a condition, check the Otherwise choice: Do not set a task leaves non-matching rooms as they are
Wrong cleaner assigned
Check room's default cleaner setting
Verify cleaner is active in Housekeeping department
Review if cleaner was changed manually after automation
Notifications not received
Verify cleaner has notifications enabled
Check mobile device push notification settings
Ensure cleaner is assigned to the room
Choosing Between Room Automations and Triggers
Key Differences
Best Practice: Combine Both
For comprehensive automation:
Enable Triggers for immediate room status changes (checkout → dirty)
Enable Room Automations for scheduled task creation and day-start status flips (daily at 6 AM)
Use Credits to balance workload when tasks are created
Review Assignments before cleaners start their shift
Schedule Projection
Room automations can be projected forward to generate cleaning assignments for upcoming days automatically. This gives your housekeeping team visibility into future workload without waiting for each day's automations to run.
How It Works
HelloShift evaluates all active room automations nightly and creates assignments for the next N days (configurable, default 7)
Room schedules, stay-based conditions, and day-of-week rules are all respected
The system reconciles each night — adding new assignments, removing stale ones, and preserving manual overrides
Optionally, cleaners can be auto-assigned to projected tasks
Configuration
Go to Admin > Settings > Housekeeping > General and adjust:

For more details on how projected assignments appear on the assignment page, see Room Assignment System > Schedule Projection.
Related Articles
Room Assignment System - Manual and auto assignment options
All About Housekeeping - Complete housekeeping overview
Housekeeping Credit System - Credit-based workload balancing
Pre-cleaning (Strip) Phase - The create_pre_cleaning_task room job and the strip phase
Was this helpful?
More in Housekeeping
All About HousekeepingRoom Inventory ManagementHousekeeping Time TrackingPre-cleaning (Strip) PhaseStill need help? Ask the team