If a rooming list from Blocks just landed in your email, this is the system behind it. Blocks is the platform your group clients use to run their room blocks — and when a group runs its block on Blocks, your team gets one structured list before cutoff, explicit change requests instead of new spreadsheet versions, and one conversation per event.
The better the group runs its block, the less work lands on your desk at the last minute.
“The final list arrived in three versions across five email threads — and none of them matched the block.”
Groups on Blocks send one list, in one format, from one system — guest names, dates, room types, and confirmation numbers in columns your team can load without re-keying.
“Names came in after cutoff, then kept changing the week of arrival.”
Blocks tracks the group’s cutoff dates and chases their guest names internally, so the list reaches you when the contract says it should. Later changes arrive as explicit change requests — this reservation, this field — not another attachment to diff by hand.
“A wrong check-out date turned into a walked guest on our busiest night.”
Every reservation’s dates are checked against the contracted block before the list goes out. And when the list you return differs from the group’s, the difference is matched by confirmation number and comes back as a specific question — settled before arrival, not at the front desk.
“Reconciliation took two weeks of forwarded spreadsheets and ended in a disputed invoice.”
Both sides work from the same record all season. Differences surface row by row while the block is live, so the final invoice confirms what everyone already knows.
Blocks runs the group’s work so your team receives the information it needs, when it needs it.
The rooming list is sent from Blocks on the coordinator’s click — consistent columns, versioned, with confirmation numbers once you’ve assigned them. Your team returns its version on the hotel’s private page or simply by replying with your file. Nothing to install, no login to manage.
Every send, reply, and change request stays with the event it belongs to. When the group is waiting on you, they know exactly what for — and when you’ve answered, it’s on the record. Fewer duplicate chases; fewer “per my last email” threads.
Cutoffs, list due dates, and release dates live in the group’s operating plan with reminders attached. You get names before your cutoff, and rooms come back as dated, written release requests instead of quiet attrition and end-of-block surprises.
One consistent format, sent when the coordinator sends it, versioned when it changes.
A browser link to view the current list and return yours — no account, no password to reset.
This reservation, this field, this new value — never “see attached, some things moved.”
Dated and in writing, so your revenue team can resell the rooms instead of guessing.
Answer by reply email like you always have; your response files with the right event on the group’s side.
The hotel side of Blocks
Blocks is bought by the group, not the hotel. There’s no hotel account to create, no seat to license, no software to install. Your team receives cleaner inputs — that’s the whole arrangement.
You see more group blocks in a season than most organizers see in a career — and you know exactly which ones arrive as chaos. Introduce them to Blocks. Every group starts with a working session and white-glove import of their existing spreadsheets, and the next list that reaches your desk is clean.
Write to hello@blocks.travel, or point them at www.blocks.travel.
The group runs Blocks. Your team gets a cleaner, clearer handoff.
Have more questions? Check our glossary of terms or get in touch.