The list is approved, doors are open, and a sponsor calls to replace two names. At the same time, an artist's guest arrives with an unapproved plus-one. These situations need decisions, but they should not stop every other guest from entering.
The guest-list management guide covers allocations and setup. This guide focuses on exceptions after the list closes: who decides, how staff record the change, and how the next entrance learns about it.
Name a guest-list lead and a backup for each shift. Tell sponsors, artist representatives, and internal staff where to send changes. A message to a friend working security should not become an unofficial admission instruction.
Define which changes the lead can approve and which need another decision-maker. Correcting a misspelled name may be routine. Adding an admission, changing access level, or reallocating a reserved seat affects inventory and needs the appropriate authority.
Keep the working list in a controlled system with a clear owner. If an approved change must be recorded manually, document it in one exception log and update the operational list before telling the guest it is ready.
Use a short record with the request time, guest name or ticket reference, requesting partner, current entitlement, requested change, approver, and outcome. Collect only the information the team needs to resolve the issue.
Separate a request from an approval. “Sponsor asked for two additional guests” should not look the same as “Two additional admissions approved and issued.” Record the actual ticket or entry reference when the change is completed.
For a name replacement, confirm whether the original ticket or credential needs to be canceled or otherwise handled through the supported workflow. Editing a name in a separate sheet does not necessarily invalidate a ticket already sent to someone else.
Give staff a courteous line they can use: “I can see there is a question about your entry. Our guest-list lead will check the approval with you here.” Direct the person to an appropriate help position while maintaining clear access routes.
Before adding an admission, check the relevant ticket inventory and operational capacity with the responsible team. A no-show on a guest list does not automatically make that person's issued ticket safe to resell or reallocate.
For reserved seating, identify the actual available seat before promising a replacement. For multi-day events, specify the day and access area. “Approved guest” is too vague when different credentials grant different privileges.
Suppose a sponsor has four admissions and asks to substitute two attendees. The lead should establish which admissions remain unused, apply the supported cancellation or replacement process, and communicate the updated entry instructions. This is an operational example, not a claim that every system automates those steps.
Confirm that the change is visible in the system the entry team actually uses. Avoid broadcasting personal guest details over an open radio channel. Share the minimum reference needed through the team's approved communication method.
At shift change, hand over unresolved requests and identify the current decision-maker. After the event, compare requested changes with issued admissions and check-in records. Investigate unmatched entries before treating the report as final.
Review recurring exceptions with the partners involved. Frequent late substitutions may call for an earlier reminder; repeated unapproved plus-ones may call for clearer confirmations. A reliable exception process gives staff a fair way to help guests while keeping the approved list meaningful.