We’re running into the same issue almost daily. A guest checks into a room, stays only a few minutes or an hour, then switches to another room. Mews immediately flips that first room back to “Dirty,” even though it was fully cleaned and inspected earlier that day.

Housekeeping ends up wondering why a clean room suddenly looks like it needs a full turnover when, in reality, it only needs a quick touch-up. It slows the team down and creates unnecessary backtracking.

What we really need are two things:

1. Automatic “Pickup” logic for short occupancy
In another PMS, this would fall under a Pickup status, meaning the room was used lightly and only needs a refresh, not a full clean.
Mews could handle this with:
• a “Pickup” status, or
• an automated rule triggered when the guest stays in the room less than X hours, or
• any system tag that prevents a fully cleaned room from coming back as “Dirty” when the use was minimal.

2. A report showing all room changes for a selected period
To better understand patterns and support housekeeping, we need a simple audit that shows:
• every room change
• timestamps
• who triggered the change
• original room → new room

This would help us catch problem patterns, reduce confusion for the team, and avoid double work.

Both improvements would make day-to-day operations smoother and give housekeeping a clearer picture of what actually happened during the shift.