Who Sleeps Where: The Room Block Problem

The PDF Arrives

Four months before the wedding, the hotel's reservations team sends you a PDF.

It is six pages long. It lists 82 rooms by wing, floor and bed type, in a font last seen on a fax machine. Attached is a polite sentence that will quietly run your life for the next month: "Kindly share the final rooming list at least 30 days prior to arrival."

A rooming list. Names against room numbers. Which specific human sleeps in which specific bed, for every night of a four-day wedding, for every guest who said yes.

You open a fresh spreadsheet. You feel briefly powerful. This feeling will not last.

A Bet You Placed Eight Months Ago

Here's the structural problem with a room block: you booked it long before you knew who was coming.

You signed for 80 rooms back when the guest list was a hopeful Google Sheet and everyone was "definitely coming, beta." Since then, reality has been trading against your position. A cousin got a new job and can't leave New York. An aunt who RSVP'd for two is now bringing three, because her son's girlfriend became a fiancée. Two singles became a couple. One couple became, awkwardly, two singles.

None of these people think they changed your wedding. Each of them changed the rooming list. The block is fixed; the list underneath it never stops moving. Every update arrives the same way — a WhatsApp forward from your mother at a time of night when you have no intention of opening a laptop.

If you've read about the 11 PM problem, this is where it lives.

The Constraints Nobody Writes Down

And matching bodies to beds isn't even the hard part. The hard part is that a rooming list is a diplomatic document, and the actual constraints are stored in your mother's head:

• Dadi logic. Grandparents go on the ground floor, near a lift, near the family, and nowhere near the sangeet speakers. This is non-negotiable and appears in no spreadsheet column.
• The feud. Two branches of the family who last spoke at a funeral in 2019 must not share a corridor. Everyone knows. No one will say it out loud, least of all in writing.
• The snorer. Every family has one uncle nobody will room with. He gets a king to himself and it costs you a room you needed.
• The bachelor floor. The cousins want to be together, far from parents, and ideally near the pool. Grant this and you buy yourself 40 fewer complaints.
• The reverse-destination guests. Your college friends flying in for their first Indian wedding need to be near someone who can explain why breakfast is at 7 and the baraat is at 9. Rooming them among strangers is how you end up doing guest support from the mandap.

A hotel sees 82 rooms. You're looking at a seating chart that people sleep in.

Why the Spreadsheet Loses

The spreadsheet fails for one reason: it's the fourth copy of the truth.

The hotel has its PDF. Your RSVP tracker has its numbers. The family WhatsApp has tonight's amendments. And your spreadsheet has whatever was true the last time you had ninety free minutes — which, this close to the wedding, was a while ago. Every change has to be noticed, believed, and hand-copied across all four before it's real. Miss one, and three weeks from now a cousin is standing in a lobby in Goa at midnight while a receptionist explains that room 214 already has people in it.

The fix isn't a better spreadsheet. It's not being the person who does the copying.

Forward the PDF

Phera's Planner — the chat agent that lives in your dashboard — treats the hotel's PDF as a thing to be read, not retyped. Forward it the way you'd forward it to a very capable friend:

PDF, a photo of the floor plan, or the Excel sheet the reservations desk actually uses — it parses any of them into a structured room list: numbers, wings, floors, bed types, capacity. The same rooms show up on your Room Assignments page as a table you can drag guests into, with a one-tap auto-assign that fills the block by family group and wedding side to give you a sane starting draft.

The Planner reads that same data, so from then on "who sleeps where" is a question, not a research project. Which rooms still have space? Where did we put the Boston cousins? How many beds do we have against confirmed guests? Each one gets an answer in seconds, pulled live — not from the version of the spreadsheet you last opened in March.

Tell It the Politics

Here's the part no software has ever handled: the constraints your mother keeps in her head. You state them in plain language, and they become part of how the block gets managed.

Notice the shape of that. Reading is unceremonious — the Planner looks at the block without asking your permission first. But moving people between rooms is a different class of action, so it stops, describes the move in plain English — who, from where, to where, who else is affected — and waits for you to tap Confirm.

That combination — act on a sentence, confirm before anything sensitive, undo anything — is what makes the moving guest list survivable. When masi adds her two sons at 11 PM, the update is one message, not an evening. The overflow gets noticed by the software, the reshuffle gets proposed, and you approve it from bed.

What It Won't Do

Some straight answers, because a rooming list is not a place for surprises:

The Night Before the List Is Due

There's a version of this month where you spend it in a spreadsheet, triangulating between the hotel's PDF, the RSVP tracker and the family group chat, and the rooming list goes out correct only because you personally checked all 82 rows at 1 AM.

And there's a version where the PDF got parsed in July, every change since then was one sentence in a chat, and the night before the deadline you ask "anything unassigned?" and get back a number. Ideally zero.

Same wedding. Same 82 rooms. Same masi, same sons. The only difference is who did the copying.

If you'd rather see a block that's already assigned, open the demo wedding and poke at its rooms.