Assigning rooms before arrival: rules for blocking, upgrades and special requests

Hotel room assignment is the act of attaching a specific room to a reservation before the guest arrives. Done the evening before, it lets housekeeping plan its routes and lets the desk honor connecting rooms, accessibility needs and repeat-guest preferences, using one written order of priority that every shift follows.

A family of four checks in at 22:00 and is split across two floors. The connecting pair was free all evening. Nothing in the system was broken and nobody decided wrongly on purpose: the assignment was simply left to whoever had time the night before. After reading this guide you will be able to run one evening assignment pass with a fixed order of priority, use upgrades to free sellable room types, block groups and long stays as units, and control day-of changes with one named decision-maker per shift.

Why does assigning rooms the evening before matter?#

Because the arrival list turns into the housekeeping plan and the desk's script at the same moment, and both are far cheaper to change the night before than at 14:00 with a guest standing at the counter.

First, separate the words. A block is a hold on a specific room number against a reservation. An assignment is the decision that this guest sleeps in that room. Both belong on the reservation itself, not in a notebook, a sticky note or a chat message, because anything that lives outside the reservation is invisible to the next shift.

Housekeeping builds its route from departures and the arrival list. Which rooms must be ready first, such as early arrivals, VIP amenity setups and long-stay changeovers, is decided by the assignment, not by the order rooms happen to be cleaned. The morning shift then inherits the previous evening's decisions. If nothing was decided, the first agent to check someone in takes the best room of that type, and the second agent cannot undo it without a move.

Pre-assignment also surfaces conflicts while they are still cheap: two reservations blocked into the same room, a blocked room that has gone out of order, a connecting pair where one half was sold to a solo traveler. Each of these costs minutes the night before and an apology the next afternoon.

The work itself is small in one pass. Sort the arrival list by room type, place the constrained reservations first, then fill the remaining rooms in arrival-time order. Mind the trade-off, though. Assigning every room weeks ahead creates rework each time a stay is extended or a room is taken out of service, so assign constrained arrivals early and ordinary ones the evening before.

Room status, meaning whether a room is clean and inspected, dirty, or out of order, is the other half of this picture. If the terms are unfamiliar, read our guide to room status codes such as VC, VD and OOO before the next pass.

What order of priority should the whole desk use?#

One fixed order, written down and used by reservations, the desk and the night shift, so that the same request gets the same answer whoever is on duty.

Priority follows constraints, not importance. A guest who needs a step-free bathroom outranks a VIP, because only one of those two problems can be solved with an apology. Record the reason next to the block: a held room with no note is released by the next shift, and the constraint is lost silently.

Keep preferences in a different field from constraints, so the desk can see at a glance what it must honor and what it should try to honor. Place the constrained reservations first and let the unconstrained ones fill the gaps; doing it the other way round means moving people afterwards. The list has to be the same list everywhere: at the desk, in reservations, and in the report the night shift reads before it closes the business day.

Which requests must be honored, and which are best effort?#

Honor anything the room physically has to be for the guest to use it. Treat everything else as a preference and say so at the time of booking.

The must list is short: accessibility needs, a cot or extra bed the hotel has confirmed, connecting rooms the hotel has confirmed in writing, and the room type the guest paid for. The best-effort list is longer: floor, view, distance from the lift, quiet side, early check-in. These are honored when the inventory allows and never promised as certainties.

The difference is not politeness, it is what the hotel can actually deliver. A confirmed connecting pair is a promise; a high floor if possible is not. Write the confirmation where the desk will see it, on the reservation. A confirmation buried in an email thread is not a confirmation.

Do not improvise room suitability at the counter. Accessibility details belong to a separate checklist, and the desk should work from what that checklist established; our accessible hotel checklist for rooms and routes covers what to verify. If a must-have cannot be met, tell the guest before arrival and offer the alternative the hotel can genuinely deliver that day.

How do upgrades free the room types you need to sell?#

An upgrade moves a guest up a room type and puts a lower type back on sale, so it is an inventory decision taken during the assignment pass, not a gift handed out at the counter.

The mechanism is simple. If the standard rooms are oversold and the suites are not, moving one reservation up releases one standard room that can still be sold at the standard price. For example, if a hotel has sold 41 of its 40 standard rooms and has suites open, one upgrade turns an oversell into a sale.

Upgrade only when the higher room type is otherwise unsold for the whole length of the stay. Otherwise the hotel gives away a room it could have sold. Never break a connecting pair, an accessibility room or a group block to make an upgrade; those are constraints, and an upgrade is not.

Decide upgrades at assignment time, before arrival, so housekeeping, the room plan and the bill are correct from the first minute. Tell the guest at check-in rather than days in advance, because an upgrade announced early becomes a promise that a later change may break. Note the reason on the reservation, for example "upgraded to release a standard room". A free upgrade with no note looks like an error to the next shift and to the auditor.

How should groups and long stays be blocked?#

Block a group as a unit on as few floors as possible, and block a long stay into one room for its entire length.

Block groups by floor and corridor so that noise, breakfast timing and the housekeeping route stay together, and keep the block's room type counts matching the rooming list. Rooming lists often arrive late, so block the shape first, meaning the counts by room type and floor, then put names on rooms when the list lands. Our guide to group bookings, blocks and rooming lists covers the full workflow.

Assign a long stay to one room for the whole stay at once, and prefer a room whose type is not in short supply on the busiest night of that stay. Do not move a long-stay guest mid-stay to satisfy a short booking: the move is paid twice, once in housekeeping time and once in trust.

Keep the group block visible to housekeeping so the floor is cleaned in one pass instead of three. When the block changes, change the note on the reservation in the same action, so the desk and housekeeping read the same plan. On the systems side, AI Otel's hotel operating system keeps reservations, groups and room assignment in one system, protected against selling the same room twice; it is built and working, ahead of launch.

What changes on the day, and who may override the plan?#

Early arrivals, late checkouts and rooms going out of order rewrite the plan, so the plan is re-checked at the start of every shift and only one named role may override a block.

Re-check at handover: which blocked rooms are still dirty, which have gone out of order, which guests have already arrived, which departures are running late. An early arrival can only be answered by looking at the specific blocked room; a clean room held for a later VIP should not be handed over without the supervisor's decision. Our guide to early check-in and late checkout policy sets the rules for both sides of the day.

A late checkout extends a room's unavailability, so check it against today's arrivals of the same room type before agreeing, not after. A room taken out of order must be removed from the block in the same step, and the guest moved before arrival wherever possible.

Name one role per shift that can break a block, and require a note on the reservation saying why. An override without a reason is indistinguishable from a mistake. Keep the guest informed throughout: a room change before arrival is a message; a room change at the counter is a complaint.

What to do next#

Write the priority order on one page, use it in the next assignment pass, and re-check it at every handover. The pieces fit together in one direction: constraints are placed first, upgrades release the room types you can still sell, groups and long stays are blocked as units, and the day-of changes are handled by one named person with a note. That is the whole method, and it costs one evening pass rather than a morning of moves. If you want to see how these rules land in software, request a briefing at https://ai-otel.com/contact.