Skip to main content

Housekeeping Dashboard

Quick View

Most teams scan Condition, Room Status, and Do Not Disturb first. This takes about 2 minutes.

This guide helps you review room readiness, manage housekeeping status, and take rooms out of service from Housekeeping.

Quick Reference​

TaskWhere to clickResult
Search roomsSearch barList filters as you type
Sort the listColumn headerRooms reorder
Filter on mobileFilter chipsOnly matching rooms show
Update conditionCondition dropdownStatus updates
Toggle DNDDo Not Disturb switchDND updates
Take room out of serviceIn service badge, when supported by your PMSRoom is blocked from sale
Restore room to serviceOut of service badge, when supported by your PMSRoom returns to sellable inventory
Confirm cross-page updatesOpen Operations ViewMost PMS updates appear quickly; Furama conditions can take about 60 seconds
Slow Cloudbeds loadWait for the page to finish loadingAVA stops waiting after about 10 seconds

Dashboard Overview​

ColumnWhat it showsWhat you can do
RoomRoom number or nameClick header to sort
TypeRoom type from the PMSClick header to sort
ConditionClean, Dirty, or InspectedUpdate from dropdown
Room StatusOccupied or VacantRead-only (from PMS)
Do Not DisturbDND on/offToggle switch
Room Status is read-only

Room Status updates automatically after check-in or check-out in the PMS. You cannot edit it in AVA.

eZee room status

For eZee, Arrived and Dayuse mean Occupied in AVA. AVA uses eZee's hotel date, so check that date when a room status looks old.

eZee day-part placeholders

AVA omits eZee Morning and Night placeholder rows from Housekeeping. These rows use room ID 0 and do not represent physical rooms. Only physical housekeeping rooms can receive condition updates.

Opera room status loading

If you use Opera, AVA loads room-scoped status in grouped batches. This keeps large room lists faster and helps separate similar room numbers.

Cloudbeds room matching

If Cloudbeds uses different IDs for a reservation and its physical room, AVA matches the normalized room number. The correct physical room can still appear in Housekeeping.

Furama housekeeping timing

Furama accepts condition changes immediately, then applies them asynchronously. The room list, Operations View, and summary counts can show the old value for about 60 seconds.

Find a Room​

  1. On desktop, use the Search bar at the top of the list.

  2. On mobile, use the search field below the header.

  3. Type a room number, room type, or guest name.

    ✓ The list updates as you type.

Sort​

  1. Click any column header (e.g., Room, Type, Room Status).

  2. Click it again to reverse the order.

    ✓ The arrow beside the column shows the sort direction.

Mobile Filters​

  1. Tap a filter chip like Clean, Dirty, Inspected, Occupied, Vacant, or DND Active.

  2. Tap the same chip again to remove it.

  3. Tap Clear all to reset filters.

    ✓ Only matching rooms stay visible.

Active Filters Bar​

When filters or search are active, a bar appears above the list.

✓ It shows “Showing X rooms out of Y.”

Sorting is view-only

The list order resets after a refresh. Reapply your sort or filters if you navigate away.

Update Room Status​

Change a Room Condition​

  1. Find the room in the list.

  2. Open the Condition dropdown.

  3. Select Clean, Dirty, or Inspected.

    ✓ AVA shows a success message after the PMS accepts the change.

If you do not see Inspected

Your PMS may not support this status. You can still use Clean and Dirty.

Refresh after a Furama condition change

If you use Furama, wait about 60 seconds before checking another page. Then refresh Housekeeping and Operations View.

Same-day checkout prompt

If Settings → Check-In has Prompt housekeeping to confirm same-day checkout enabled, AVA shows a prompt when you mark a room Clean or Inspected on its checkout date. This prompt appears from Housekeeping and from Clean Room on reservation cards. Choose Check out reservation to check out first, then update the condition. Choose Update status without checkout to update only the condition. Close the prompt before choosing an option to cancel the condition update.

Updating banner

While updates sync, a banner says “Updating housekeeping status...”

Background sync to Operations

After condition or DND changes, AVA refreshes related room and reservation data in the background. For Furama, the PMS may finish applying the condition after AVA shows the success message.

Cloudbeds timeout behavior

Cloudbeds housekeeping reads now stop waiting after about 10 seconds. If Cloudbeds is slow, you may see the error sooner instead of a long spinner. AVA retries the request once before showing the error. Refresh after saving to see the latest version.

Toggle Do Not Disturb​

  1. In the Do Not Disturb column, toggle the switch.

  2. Confirm the action.

    ✓ The Do Not Disturb status updates and a success message appears.

Manage Out-of-Service Rooms​

Quick Update

Marking a room out of service usually takes about 1 minute.

Use this when a room needs maintenance, deep cleaning, or renovation. AVA keeps the room visible in the list, but assignment pickers disable it. When the PMS provides a block window, you see that date range on the badge. You can also restore blocks that the PMS created directly.

When multiple Opera blocks overlap, AVA chooses the displayed window by each field in order. A block without a start date is treated as the earliest block. AVA uses that complete window for the room's blocked dates and assignment checks. This keeps dates from being combined across separate blocks.

Furama service blocks

Furama iPMS v2 supports Take out of service and Restore to service when the capability is enabled. The PMS may take about 60 seconds to show a new block in AVA.

Take a Room Out of Service​

  1. Find the room in the list.

  2. Click the room's In service badge.

  3. Choose a Reason.

  4. Set the Start date.

  5. Add an End date if the block is temporary.

  6. Add Notes if you want to explain the block.

  7. Click Take out of service.

    ✓ AVA confirms that Furama accepted the block. ✓ The room stays visible, but staff cannot assign it for the blocked dates.

Furama block timing

Furama stores the block when it accepts the request. The badge may take about 60 seconds to update. Future blocks become active only when their start date opens in Furama. Do not repeat a successful request while the badge is still updating.

PMS capability varies

These actions appear only when your PMS supports room service-status updates. If the actions are unavailable, manage the block in your PMS.

Restore a Room to Service​

  1. Find the room marked Out of service.

  2. Click the Out of service badge.

  3. Review the dates shown in the modal.

  4. Click Restore to service.

    ✓ AVA confirms that Furama accepted the release. ✓ AVA checks the PMS again after removing the active block. ✓ If another overlapping PMS block still exists, the room can stay out of service.

Assignment behavior

Rooms blocked for the selected stay still appear in room assignment and room change pickers. They are disabled, and AVA shows the PMS reason when available. The same rule applies when you assign a room during reservation creation.

Plan Your Cleaning Order​

Quick Plan

Start with Vacant rooms marked Dirty—these are the fastest to turn.

PriorityWhy it matters
Vacant + DirtyFastest rooms to turn for new arrivals
Vacant + CleanReady for early arrivals—verify DND is off
OccupiedCoordinate before entry
DND ActiveDo not enter until DND is cleared

Recommended workflow:

  1. Sort by Room Status to group Vacant rooms first.
  2. Then sort by Condition to see Dirty rooms at the top.
  3. Update each room to Clean or Inspected after finishing.

Troubleshooting​

Housekeeping status unavailable banner​

What you see: A yellow banner that says housekeeping status is unavailable.

Fix:

  1. Refresh the page.
  2. Ask an admin to verify Settings → Essentials → PMS Integration.
Limited data

When this banner appears, AVA shows basic room details only.

Error loading housekeeping data​

What you see: An error message with a Retry button.

Fix:

  1. Click Retry.
  2. If the error repeats, refresh the page.

Opera housekeeping request returns 502​

What you see: A 502 error appears when you save a room condition or reload housekeeping data.

Why this happens: Opera dropped the connection while AVA was reading or writing housekeeping data. AVA now returns 502 for this kind of retryable connection failure.

Fix:

  1. Refresh the page once.

  2. Try the same action again.

  3. If it keeps happening, check the PMS connection.

  4. Contact support if the same room keeps failing.

    ✓ One-off 502 errors should clear after a retry.

Cloudbeds housekeeping loads slowly​

What you see: The page keeps loading, then shows an error or rate-limit message.

Fix:

  1. Click Retry once.

  2. If a retry time appears, wait for it.

  3. Refresh the page after the retry time passes.

  4. If you just changed room status, wait a few seconds and refresh again.

  5. If the issue repeats, wait a few minutes before trying again.

  6. Ask an admin to check the Cloudbeds PMS connection.

    ✓ Slow Cloudbeds responses should fail faster, and rate-limit messages should show a retry time when available.

A Cloudbeds room is missing​

What you see: A Cloudbeds reservation's assigned room does not appear in Housekeeping.

Why this happens: Cloudbeds can use different IDs for a reservation and its physical room. AVA normally matches the room number after it loads and normalizes housekeeping data.

Fix:

  1. Confirm the assigned room number in Cloudbeds.

  2. Compare it with the room number shown in AVA.

  3. Refresh Housekeeping.

  4. If the room remains missing, ask an admin to verify the room mapping in Cloudbeds.

    ✓ The physical room should appear when its normalized room number matches.

Condition changes do not save​

What you see: The update shows an error, or the condition returns to its previous value without a success message.

Fix:

  1. If you use Furama and saw a success message, follow Furama condition update is delayed.
  2. Otherwise, wait a few seconds and try again.
  3. Refresh the page.
  4. Ask an admin to confirm Settings → Essentials → PMS Integration is connected.

PMS refuses a condition change​

What you see: AVA shows a PMS explanation instead of only "Failed to update room condition."

Why this happens: The PMS found a room rule that prevents the change. For example, a room may be out of service for maintenance.

Fix:

  1. Read the full reason in the AVA message.

  2. Open the affected room in your PMS.

  3. Resolve the issue described, such as releasing an active service block.

  4. Refresh Housekeeping.

  5. Select the required room condition again.

    ✓ The condition should update after the PMS accepts the request.

Furama example

If Furama says a room is out of service, release its active service block first. Then retry the Condition change in AVA.

Cloudbeds rejects a housekeeping update​

What you see: AVA shows PMS_VENDOR_REJECTED_HOUSEKEEPING_UPDATE and a Cloudbeds reason.

Why this happens: Cloudbeds accepted the request, but rejected the requested room update. An unsupported condition or an update with no condition or DND change is rejected before submission.

Fix:

  1. Read the Cloudbeds reason shown by AVA.

  2. Select Clean, Dirty, or Inspected in Condition.

  3. Toggle Do Not Disturb when you need to change DND.

  4. Check the room's rules and status in Cloudbeds.

  5. Refresh Housekeeping, then submit the valid change once.

    ✓ AVA sends the update only when it includes a supported change.

Do not keep retrying the same rejected update.

Furama condition update is delayed​

What you see: Furama shows a success message, but AVA still shows the old condition.

Why this happens: Furama applies accepted condition changes asynchronously. The room list and summary counts can take about 60 seconds to catch up.

Fix:

  1. Wait about 60 seconds.
  2. Refresh Housekeeping.
  3. Refresh Operations View and check the room again.
  4. Contact support if the old value remains after the wait.

Do not send repeated updates while the first request is still processing.

eZee says a housekeeping unit was not found​

What you see: An eZee condition update shows Fail or Unit Id(s) not found in the system.

Why this happens: eZee does not track that room as a housekeeping unit. AVA shows the reason returned by eZee when available.

Fix:

  1. Note the affected room number.

  2. Confirm the room is configured as a housekeeping unit in eZee.

  3. Correct the eZee room mapping, or update another tracked room.

  4. Return to Housekeeping and refresh the room list.

    ✓ The condition update should work for a tracked housekeeping unit.

Inspected option is missing​

What you see: Only Clean and Dirty appear in the dropdown.

Fix:

  1. Confirm your PMS supports Inspected.
  2. If it does, ask support to review the PMS mapping.

Room shows occupied after guest left​

What you see: Room Status stays Occupied.

Fix:

  1. Complete the check-out in the PMS or AVA.
  2. Refresh Housekeeping after check-out.

Opera room status looks mixed​

What you see: A room with a similar number appears, or a room looks repeated.

Fix:

  1. Refresh Housekeeping.
  2. Confirm the room number is mapped correctly in your PMS.
  3. Ask support to review the room mapping if it happens again.

Opera out-of-service dates look wrong​

What you see: An Opera room badge shows an unexpected out-of-service date range.

Why this happens: Opera can return several overlapping blocks for one room. AVA selects one complete block window instead of combining dates from different blocks.

Fix:

  1. Open the room's out-of-service records in Opera.
  2. Check for overlapping blocks or a block without a start date.
  3. Refresh Housekeeping.
  4. Contact support if the badge still differs from Opera.

Operations still shows the old room condition​

What you see: You changed Condition or Do Not Disturb, but Operations View still looks old.

Fix:

  1. If you use Furama, wait about 60 seconds after the success message.
  2. Open Operations View and click Refresh.
  3. Reopen the reservation details and check Room Information.
  4. Clear any active room filter and check again.
  5. If it still looks old, ask an admin to verify Settings → Essentials → PMS Integration.

Search returns no rooms​

What you see: Empty list after searching.

Fix:

  1. Remove extra characters like # or -.
  2. Try a shorter room number or partial match.

Sorting looks unchanged​

What you see: The arrow changes, but rooms appear in the same order.

Fix:

  1. Clear any active search terms.
  2. Click the column header again to flip the sort direction.

No rooms found matching filters​

What you see: “No rooms found matching your filters.”

Fix:

  1. Tap Clear all.
  2. Remove any search term.
  3. Try a wider filter, like Vacant.

Room stays out of service after restore​

What you see: You clicked Restore to service, but the room still shows Out of service.

Fix:

  1. Refresh the page.
  2. Open the room again and try Restore to service once more.
  3. Check whether another overlapping PMS block still exists in the PMS.
  4. Ask an admin to review the PMS room block window.

Restore only partly succeeds​

What you see: AVA restores some blocks, then reports that matching blocks remain.

Fix:

  1. Refresh the page.
  2. Open the room again.
  3. Try Restore to service once more.
  4. Ask an admin to check for overlapping PMS blocks.
  5. Share the removed targets and remaining count with support if the issue repeats.

Furama service block is not active​

What you see: Furama refuses Restore to service, or the block does not appear immediately.

Why this happens: Furama only releases a block that is active at the current PMS business date. Future and expired blocks cannot be released through AVA.

Fix:

  1. For a new block, wait about 60 seconds after the success message, then refresh Housekeeping.
  2. Check the block start and end dates in Furama.
  3. Release the block in Furama if its window is future-dated or already expired.
  4. Use Clean, Dirty, or Inspected only for housekeeping conditions.
  5. Contact support if an active block still cannot be released.

Still Stuck?​

Contact success@vouch-technologies.com if:

  • ❌ The dashboard stays empty after a refresh
  • ❌ Room updates fail more than twice
  • ❌ The PMS connection shows offline
  • ❌ Room Status never changes after check-out

Helpful to include:

  • Screenshot of the banner or error
  • Room numbers affected
  • Time the issue started