Tables and guest-list manual
Keep every type of admission connected to the right capacity and scanner mode.
A ticket, a table package and a guest-list place represent different promises. Combining them informally can overfill a venue or confuse the entrance. This manual shows how to configure each allocation, communicate it to guests and check it with the correct workflow on event day.
Separate the capacity pools
Decide how many people may enter through regular tickets, tables and guest list. A table package can cover several guests, so count people rather than packages when reconciling the venue limit.
What to do
- Record every allocation in people.
- Keep an operational reserve explicit.
- Prevent two teams from selling the same capacity.
Describe table packages precisely
State the number of guests, included service, price and entry conditions. Do not imply an item or service that the package does not include. Make the named purchaser and arrival process clear to the reservation team.
What to do
- Set capacity per table and available quantity.
- Write inclusions and exclusions plainly.
- Confirm the entrance contact and arrival rule.
Create controlled guest-list entries
Use the guest-list workflow for invited names instead of treating chat messages as the final list. Record the intended number of places and avoid unnecessary personal details. Close or update entries when invitations change.
What to do
- Add the guest under the correct event.
- Record only information needed for admission.
- Remove cancelled or duplicate invitations.
Prepare separate entrance stations
Ticket QR, table admission and guest list use different scanner or lookup modes. Brief staff before doors open and give each station only the permissions and information it needs.
What to do
- Assign a mode and queue to each station.
- Test one example from every admission type.
- Name a supervisor for conflicting records.
Admit the correct number of people
For a table, confirm the package and permitted group size before recording admission. For guest list, use the named entry and its remaining places. A reward QR is not an entrance credential.
What to do
- Read the result before admitting the group.
- Record partial group arrival correctly.
- Send mismatches to manual review.
Reconcile after the entrance peak
Compare admitted tickets, table guests and guest-list arrivals with the planned capacity. Record unresolved exceptions without exporting unnecessary guest data. Remove temporary staff access after the event.
What to do
- Compare totals across admission modes.
- Document unresolved cases for the manager.
- Close temporary scanner and list permissions.
Before doors open
0 of 5 completed
The checklist remembers your progress in this browser.
Tables and guest-list manual
Common admission questions
Does one table package count as one guest?
No. Reconcile the number of people included in the package against venue capacity and record the actual admission according to the table workflow.
Can a social message replace the guest list entry?
Use the controlled guest-list record as the source. A message can be reviewed by the supervisor but should not silently create admission.
Can staff scan a reward QR as a ticket?
No. Rewards use their own scanner mode and rules. They do not grant entry unless a separate valid admission credential exists.