Group rooming lists: how to build, submit and manage changes

In our view, a rooming list for a group hotel booking takes an afternoon to build and weeks to keep accurate. Start by pulling the deadlines from the signed contract. Submit the list before the hotel's due date. Then log every add, drop and name change against the room block until the last guest checks in.

Most published guides stop at the moment the list goes to the hotel. We think agencies lose margin in the weeks after that, so most of the detail below is about changes.

How do you create and submit a rooming list for a group hotel booking?

Five steps, in this order:

1. Read the signed contract for the rooming list due date, the cut-off date and the rules for changes. Do this before you collect a single name.
2. Get the booking or registration method to attendees early, so names arrive while you still have time to adjust.
3. Build the list against the block, night by night and room type by room type.
4. Submit it before the due date and get written confirmation from the hotel.
5. Manage every change until arrival, and confirm each one with the hotel in writing.

Engine's guide to room blocks puts the same job in one line: get the booking method to your travelers early, track pickup against the cutoff date, and submit the rooming list on time. We agree with all of it, and it is roughly where most published advice ends.

We think step three is the easy one. Free templates from Jotform and RoomMaster handle the build well enough. Step five is the one that costs money. Once the list is with the hotel, it keeps moving: someone drops out, someone swaps in, a senior manager decides to arrive a day late. Each change touches the block, runs up against a contract date and shows up on the invoice weeks later.

What does a hotel need on a rooming list?

There is no single industry format. The fields below are our view of good operational practice. The hotel needs enough to check each guest in, put them in the right bed and bill the right party:

• Guest name exactly as it appears on their ID
• Arrival and departure date for each guest, even if most match the group dates
• Room type
• Bed configuration, such as double, twin or king
• Sharers paired on the same line
• Billing instruction: master account or individual payment
• Special requests such as accessibility needs or dietary notes

If the contract asks for a specific format, use it. Sample contract language collected by Law Insider requires the list to be completed in accordance with any instructions given by the Organiser. Send a list in the wrong shape and the hotel has a reason to send it back.

Give the billing instruction extra care, because it decides who pays when something goes wrong. Another sample clause states that if guests on the rooming list do not check in, the Group's Master Account will be charged for the guest's entire lodging stay. You can mark a guest as paying individually on your list and still see the charge land on the master account under the contract, so check that the two documents agree.

We also think agencies should send only what the hotel needs to check guests in and bill them. Every extra field is personal data your agency is responsible for: passport numbers and home addresses sitting in a spreadsheet forwarded across several inboxes. A lean list is easier for the hotel to read and carries less risk for you.

Which contract dates control the rooming list?

Four or five dates in the contract govern the rooming list. They rarely sit in the same clause.

The cut-off date comes first. Stova defines it as the date when all your room reservations must be made, and adds that any rooms left unused in your block after this date are returned to the hotel inventory and put up for general sale.

The rooming list due date can match the cut-off or fall on a different day. One sample clause says the list must be submitted no later than 28 days before the date of the Event. Windows vary by hotel, brand and market, so treat 28 days as one example rather than a norm.

Some contracts add a change-fee window and charge for late edits. Sample language reads: any changes to the rooming list after 2 weeks prior to arrival may be subject to an administrative fee of $5 per change.

A name-change deadline may sit somewhere else again. Roomblocks notes that name changes may need to go through the hotel's group sales team and follow a set deadline, and that deadline may not match either of the dates above.

Late reservation terms cover names that arrive after the due date. One sample clause accepts them on a space available basis, at the higher of the contract rate or rate available at that time.

Each date carries a different consequence: released rooms, a fee, a refused name change or a higher rate. In our view, the first job with any signed group contract is to pull these dates into one place for that booking, on the day of signature, so nobody finds the change-fee clause two days before arrival.

When should you send the rooming list to the hotel?

Our position is to send the first full list well ahead of the contractual due date. If you send it on the deadline, the hotel has no time to query a mismatched room type or a missing departure date, and you have no time to fix those gaps before the terms tighten.

Track pickup against the cut-off while registrations come in, as Engine recommends. If pickup is running below what you committed, the same guide is direct: if you are trending under your commitment, talk to the hotel before cutoff. We think a hotel that hears about a shortfall weeks ahead has more ways to help, such as reselling rooms or adjusting the block, than one that hears after cut-off. PCMA makes a related point in a piece on contract disputes: as a first instance, don't call the lawyer. Call the hotel and talk to the meeting coordinator or director of sales.

After the first list, our view on cadence is to send change-only updates, each with a version number and a date. If you resend the whole spreadsheet every time, the hotel has to compare two files line by line, and someone will miss a change in that comparison. A short message that says "version 4, 12 March: two drops, one name change" is much harder to misread.

What happens if you miss the rooming list cut-off?

The contract language here is blunt. One sample clause states that if a rooming list is not provided by the cutoff date, all rooms on hold will be released for general sale. Stova describes the same mechanism, and Engine calls cut-off the deadline in the contract when unclaimed rooms are released back to the hotel.

After that point, a new name has no guaranteed room at the group rate. Under the late reservation clause quoted above, the hotel accepts late names only if it has space, at the higher of the contract rate or the rate on the day. During a busy week in a city centre, that gap can be large, and it lands on either the client's budget or your margin.

In our view, the released rooms are the smaller risk. The larger one is assuming your commitment shrank along with the held inventory. Depending on the wording, rooms released at cut-off may still count against your attrition commitment. Before you tell a client that a missed cut-off means fewer rooms and nothing more, read how the contract treats released rooms in the final bill.

Why is managing changes harder than building the list?

Every change after submission touches the block, and each type touches it differently.

An add may need a room the hotel has already released, so it falls under the late reservation terms. A drop reduces pickup and moves the group closer to its attrition threshold. A name change keeps the block intact if the hotel handles it as a replacement on the same reservation. If the hotel processes it as a cancellation plus a new booking, it can count as a drop.

Drops turn into money through attrition. ContractNerds gives an example on a 100-room commitment: if the hotel allows for 75% attrition, you can supply 75 guests and you won't have an issue. The same piece warns that your attrition percentage may be higher (e.g., 85%). Crewfare, a vendor, describes a generic contract where if room pickup falls below 80% of the committed block, the organizer will owe a percentage of the lost room revenue. It also mentions that some agreements allow a cushion, often 10% to 20%, before penalties apply. Treat these figures as illustrations and work from the percentage in your own contract.

Our view is that most attrition bills build up from small changes rather than one dramatic cancellation. Take a hypothetical 30-room block for three nights, with an 80% threshold. That is 90 room nights, so the group needs at least 72. Five full-stay drops bring pickup to 75, which still looks safe. Then four guests each leave a night early and pickup falls to 71. Each change looked harmless on its own, and if nobody keeps a running total, the coordinator first sees the shortfall on the hotel's final invoice.

How do you track adds, drops and name changes without breaking the room block?

The process we recommend works in a spreadsheet, provided one person keeps to it:

1. Keep one master list. Every other copy is a view of it, and nobody edits the copies.
2. Log every change with the date, the person who asked for it and the type: add, drop, name change or date change.
3. Recalculate pickup in room nights after every drop or date change, and compare it with the attrition threshold.
4. Where the client allows it, replace a name instead of cancelling and rebooking, so the room stays in the block.
5. Send changes to the hotel as a dated, numbered update that lists only what changed since the last version.
6. Get written confirmation from the hotel for each change and file it next to the log entry.

Find out early who at the hotel accepts changes. Name changes may need to go through group sales against a set deadline, as Roomblocks notes, so the reservations desk may not be able to help when you call. Ask for the right contact's name when you sign the contract.

Give date changes and early departures their own line in the log. In our view they are the changes coordinators miss most, because the headcount stays the same while the room nights fall. A guest who leaves a night early still appears on the list, and a coordinator scanning names will not see the gap.

If the log shows pickup sliding toward the threshold, follow Engine's advice and talk to the hotel before cut-off, while it still has time to resell the rooms.

Who pays for no-shows and late changes?

The contract usually answers this, and the default rarely favours the group. Under the sample no-show clause quoted earlier, the hotel charges a guest who does not check in to the group's master account for the guest's entire lodging stay. Late change fees are smaller. The sample clause allows an administrative fee of $5 per change within two weeks of arrival, and other contracts set other amounts. Five dollars sounds trivial until a group with dozens of late edits produces an invoice line someone has to explain to the client.

Our view is that you should settle who absorbs these costs with the client before the list goes out, and write it into your client terms. State whether you pass no-show charges and change fees through at cost or absorb them. If you buy on a net rate and add your own margin, a no-show charged to the master account comes straight out of that margin unless your terms say otherwise. The principle is the same as in keeping hidden costs out of your group rates: every cost should be visible to someone who agreed to pay it.

What should room block management software do for rooming lists?

The existing tools deserve some credit. The Jotform and RoomMaster templates are fine for the first build, and Eventpipe and Mews both publish guides to rooming lists worth a read. In our view, none of them covers managing changes once the list is with the hotel, and that is where a tool has to earn its place.

Our criteria for room block management software, as far as rooming lists go:

• It reads the key dates from the signed contract: due date, cut-off, change-fee window and name-change deadline.
• It holds one master list matched to the block by night and room type.
• It logs every change with the date, the requester and the change type.
• It shows pickup in room nights against the attrition threshold after every change.
• It sends change-only updates to the hotel and records each confirmation.

We also think the rooming list should connect in both directions. It should link back to the offer and contract it came from, so nobody types the block and dates in twice. And it should link forward to deposits and balances, so nobody re-keys a change in headcount in three places. Our view is that many sourcing tools, including most hotel RFP software, stop at the signed contract. Check for that when you compare purpose-built alternatives for group hotel sourcing, because the rooming list sits after the signature.

Here is how a hypothetical booking would run in GatheroniX, which covers the full group booking lifecycle: Requests, Offers, Contracts, Attendees and Payments. The example starts once the hotel is chosen.

A DMC has contracted 40 rooms for three nights at one hotel for an incentive group, which comes to 120 room nights. When the coordinator uploads the signed contract into Contracts, the module pulls out the rooming list due date, the cut-off, the change-fee window and an 80% attrition allowance. It checks them against the accepted offer and flags any date that changed between offer and contract before anyone relies on it. In Attendees, the coordinator builds the list from registrations, matched to the block by night and room type, and sends version 1 to the hotel ahead of the due date.

Nine days before arrival, two attendees drop out for the full stay and a colleague replaces a third. These changes are automatically logged by the system and all the coordinator has to do is approve them. The replacement goes to the hotel as a name change, so that room stays in the block. The two drops take pickup from 120 to 114 room nights, which is 95% against the 80% allowance, and the log shows no attrition exposure. Nine days falls inside the change-fee window, so Attendees module marks the changes as billable. The hotel receives one message, marked version 2, listing only the three changes where they confirm receipt, and the coordinator files its confirmation against each one. Payments then works from the final count when the balance falls due.

---

Rooming lists are one link in a chain that runs from the first RFP to the final balance. GatheroniX keeps that whole chain in one place for groups of 10 to 100 people, and you can book a demo to try it during the beta.