Skip to content
EventProgrammer

What Is a Rooming List? A Planner’s Guide

What a rooming list is, what goes in it and when the hotel needs it. Rooming list vs booking link, room types, several hotels and common mistakes.

Updated 4 October 20267 min read

What is a rooming list?

A rooming list is the list a planner sends a hotel showing which guests stay in which rooms, and for which dates. The hotel uses it to name the rooms held for the group, prepare check-in and, in the end, raise the invoice.

Congress, dealer meeting, incentive trip or launch: whenever the organiser takes care of the guests’ accommodation, the rooming list is the shared language with the hotel. For the hotel it fills in a block of rooms set aside for the group; for the planner it is the slice of the guest list that belongs to that hotel.

What goes in a rooming list

Hotels ask for different formats, but nearly every hotel rooming list includes:

  • Guest name, spelled as on the ID
  • Room type (Single, Double, Twin, Triple, Suite)
  • Who shares the room
  • Check-in and check-out dates
  • Billing: master account or paid by the guest
  • Special requests: accessible room, cot, connecting rooms
  • Arrival details: flight and landing time, early check-in needs

The most practical layout is one row per room, with the second guest of a shared room on the same row. Then your row count equals the hotel’s room count. For a ready-made layout, use the free rooming list template.

When does the hotel need it?

Group contracts usually set a cut-off date. The hotel wants the list by then; after it, unnamed rooms in the block may be released or the group rate may no longer be guaranteed. Dates and terms differ by contract, so note them per hotel.

In practice the list is never final in one go: the first full list goes at cut-off, corrections follow until arrival, and the last week brings small changes almost daily. What matters is that every change reaches the hotel and the hotel works from the latest list.

Room types, decoded

Single (SGL)
One guest. The room itself may have a large bed; what counts is one occupant.
Double (DBL)
Two guests, one large bed. For couples.
Twin (TWN)
Two guests, two separate beds. For colleagues sharing.
Triple (TRP)
Three guests, often with an extra bed.

Running rooming lists for several hotels

Past a few hundred guests one hotel is rarely enough, and that is where it gets hard. Each hotel should see only its own guests, so you produce one list per hotel from one master list.

  • Keep one source. Hotel, room and dates for each guest live in one place, and the hotel lists come from it. If one guest has different dates in two files, nobody knows which is right.
  • Version every send. Call them v1, v2, v3 and list the changed rows.
  • Follow flight changes. A late flight means a late check-in; a cancelled one means a no-show. The hotel should hear it from you.
  • Compare room nights with the block. Put the rooms you hold each night next to the contracted block; under-filling can turn into a charge, depending on the contract.

Common mistakes

  1. Mixing up double and twin. A couple in two beds, two colleagues in one.
  2. Names that don’t match the ID. The front desk can’t find the guest and the queue grows.
  3. Counting the departure day as a night. 11–14 March is three nights, not four.
  4. Sending the whole list to every hotel. Confusing, and personal data shared for no reason.
  5. Changes made by phone that never reach the list. Your list and the hotel’s drift apart, and it shows up on the invoice.

After the event

When the hotel invoice arrives, check it against what was actually stayed, not against the rooming list. Planned nights (on the list), actual nights (what the guest really stayed) and billable nights (what the contract makes payable) are three different numbers. No-shows, early departures and late arrivals pull them apart.

Keeping those three numbers room by room turns the end-of-event reconciliation with the hotel from an argument into a checklist.

Keep the list live, not in a spreadsheet.

In EventProgrammer each hotel sees only its own guests on a live link, so changes reach it without sending a new version. After the event, planned, actual and billable nights come out separately.