How to Build — and Audit — a Hotel Rooming List

What goes on a hotel rooming list?

A rooming list is the roster you hand the hotel that turns your room block into named reservations. Until the hotel has it, your rooms are held but empty — reserved inventory with no guest attached. The rooming list is what the front desk checks people in against, so every column earns its place.

For each room, the hotel needs six things:

• Guest name — the full name as it appears on the ID the guest will present, with one lead name per room.
• Arrival and departure dates — the exact nights the room is occupied. This is what drives your room-night count and, in turn, your bill.
• Room type — king, double-double, suite, or whatever room categories your contract actually names.
• Occupancy and sharing — how many people, and who shares with whom. A single or double occupancy flag tells the hotel whether to set up one bed or two, and names the second guest when a room is shared.
• Billing instructions — who pays for what. Room-and-tax to a master account, incidentals to the guest’s own card, or the whole folio to the individual. Get this wrong and you will spend arrival week untangling charges.
• Special requests — accessibility needs, early check-in, connecting rooms, a high floor away from the elevator. The hotel cannot honor what it never sees.

The list is not a formality. It is the single document where a guest’s stay, your budget, and the hotel’s front desk all have to agree. A clean rooming list prevents the two most expensive arrival-day surprises: a guest with no room, and a room billed to the wrong account.

How do you collect guest names without chaos?

Run every name through one intake path, give each department or team lead ownership of their own slice, and set your internal deadline before the hotel’s cutoff — not on it.

The chaos in rooming lists is almost never the hotel’s fault. It comes from names arriving five different ways: a spreadsheet from one lead, a forwarded email from another, three names texted the night before. Pick one channel and hold the line. Each room request should enter through the same door, so you are never reconciling formats instead of building the list.

Push ownership down. If you are running a block for several departments, teams, or a sub-block per group, the person closest to each set of guests should enter their own names — they know who is actually coming. A department lead submitting through a private request link keeps you out of the transcription business and cuts the error rate at the source.

Set the internal deadline early. Your hotel cutoff date is a hard wall; treat it as the hotel’s deadline, not yours. Give your leads a due date a week or two ahead so you have room to chase the stragglers, fill gaps, and format the file before you submit.

And plan for the rooms you cannot name yet. A TBD room — allocated but unnamed — is still a guaranteed room night you are on the hook for. Do not drop it from the list because you lack a name; hold it as TBD, keep it visible, and swap in the real guest when you have one. Rooms that quietly fall off the list are how you end up under-submitting against a block you have already committed to pay for.

How should you format the rooming list for the hotel?

One row per room, dates in one unambiguous format, and after the first submission send changes only — never a fresh full list the hotel has to diff by hand.

One row per room is the golden rule. A guest staying four nights is still one row, not four. If two people share, that is one row with a primary and a secondary name, not two rows competing for the same bed. The moment your list has more rows than the hotel has rooms held, someone is going to double-book or drop a reservation.

Pick a date format and never vary it. “03/04” is March 4th to an American front desk and April 3rd to half the world; write “Mar 4, 2027” or “2027-03-04” and use it in every cell. Give arrival and departure, not “4 nights” — let the hotel see the exact dates so your room-night math and theirs line up.

Standardize the small stuff too: consistent room-type labels that match the contract, a billing code per row, one column for special requests. The cleaner the file, the fewer questions bounce back to you.

The part teams miss is the update discipline. Your first submission is the baseline. After that, send changes only — “add these three, cancel this one, move this arrival to Mar 5” — clearly marked. Re-sending the entire list every time you have an edit forces the hotel to re-key everything and reintroduces the errors you already fixed. A short, dated change log the hotel can apply in minutes beats a 200-row attachment they have to compare against last week’s version.

Why should you audit the hotel’s returned list before arrival week?

Because the hotel’s list and yours drift, and the cheapest time to catch a mismatch is while there is still time to fix it — not at the front desk on arrival day.

When you submit names, the hotel keys them into its own system and sends back a confirmed list, usually with a confirmation number for each reservation. That round trip is where errors creep in: a name gets transposed, a date shifts by a night, a room you submitted never made it in. A rooming-list audit is the line-by-line comparison of what came back against what you sent.

Match on the confirmation number first, then fall back to name. The confirmation number is the hotel’s unique key for a reservation, so it is the most reliable anchor; matching on name alone breaks the instant you have two guests with the same name or one name spelled two ways. Confirmation-number-first, name-second is how you line the two lists up without guessing.

Then look for the four discrepancy types:

• Name mismatches — a spelling change, a swapped first and last name, a maiden versus married name.
• Date drift — an arrival or departure that moved, quietly changing the room nights you will be billed for.
• Missing rooms — a reservation you submitted that the hotel has no record of.
• Extras — reservations on the hotel’s list that are not on yours: sometimes a duplicate, sometimes a guest who booked around your block.

Do this weeks out, not during arrival week. A name you fix in the system today is a smooth check-in; the same fix attempted at the desk while the guest waits is a bad first impression and, if it is a no-show or a missing room, a billing dispute. Auditing early converts arrival-day fire drills into a quiet email exchange.

What does a rooming-list audit actually look like?

Here is a small one. Say you are running a block at the fictional Meridian Harbor Hotel for a 40-room event, and the hotel returns its confirmed list. You match row by row — confirmation number first, then name — and three rows do not reconcile.

Discrepancy 1, date drift. You submitted Priya Nadar arriving Mar 4 and departing Mar 8: four nights. The hotel’s confirmed row shows arrival Mar 5 — three nights. Someone re-keyed the arrival a day late. Left alone, you would lose a night of pickup you are paying for, and Priya would find no room on the 4th. You flag it, and the correction goes back to the hotel: arrival Mar 4.

Discrepancy 2, name mismatch. Your list has “Jonathan Reyes”; the confirmed list reads “John Reyes.” The confirmation number is identical, so it is clearly the same reservation — just a shortened first name that will not match the ID he checks in with. A one-line correction fixes it before it becomes a front-desk argument.

Discrepancy 3, missing room. You submitted 40 rooms; the hotel’s list has 39. Matching by confirmation number, the TBD room you were holding for a late addition never got a confirmation — it dropped somewhere between your submission and their system. That is a room night you have committed to and a guest with nowhere to sleep. You surface it and ask the hotel to add it back.

Three rows, three different failure modes, all caught with time to spare. This is the loop Blocks runs for you: it audits the hotel’s returned list against yours, matched by confirmation number first, groups the discrepancies by type, and proposes each correction for you to confirm — nothing changes on a reservation until you say so.