The rooming list changed tonight. How do you prepare for arrival?
The group is due tomorrow morning. A revised rooming list arrives after the evening handover, and the old copy is already in use. The useful question is not how to process a group faster; it is how to identify what changed, confirm what matters, and give the arriving shift a dependable working list.
Stop the silent version swap
Save the incoming file with its arrival time and keep the previous copy available for comparison. Tell the people preparing the arrival that a revision is under review. Do not let a filename such as final or latest decide which file is authoritative. Ask the sender to identify the revision or confirm that this is the version to use. If the source cannot confirm, mark the list as unconfirmed and keep the question visible for the group contact.
Compare the two copies by the fields that affect a real arrival: guest name, room assignment if supplied, arrival date, occupancy, accessibility or bedding request, and any note the team has agreed to act on. A spreadsheet sort can make rows move, so compare records by a stable identifier where one exists, then inspect changed values. A missing row may mean a cancellation, a moved guest, or simply a formatting change; it is a question to resolve, not an instruction to guess.
Turn differences into named questions
Create a short exception list rather than asking colleagues to reread every row. For each difference, write what changed, what still needs confirmation, who owns the follow-up, and when the answer is needed for preparation. Keep operational observations separate from requests to the organizer. For example, a room preference can be recorded as received while its fulfillment remains unconfirmed. That distinction prevents an unverified note from turning into a promise.
Check whether the change affects a room already assigned, a special setup, or a message the guest has received. Route each item to the person who can verify it: reservations or the group contact for identity and dates, front office for arrival preparation, and the relevant service team for a setup request. Share only the details each colleague needs to do that work.
Give the next shift a clear handover
Publish one working copy with a clear revision label and time, and mark superseded copies so they are not picked up by mistake. The handover should state which version is current, which exceptions remain open, who is following each one, and what the team should say if a guest arrives before an answer is confirmed. When a question is resolved, update the list and close the exception in the same place the team checks.
Before the first arrival, have one colleague sample the changed records against the source confirmation. If the list still contains uncertainty, say so plainly and keep the affected item out of any definitive guest-facing promise. The practical result is modest but valuable: the morning team can see what changed and what is still unknown.