Define the purpose before adding names
State the event objective and the role of each guest group: clients, partners, media, investors, speakers, hosts, production or personal guests. A person should not be included simply because they are prominent or known to the organiser. The list must serve the programme and the capacity available.
Set selection criteria that can be applied consistently. For a professional dinner, relevance to one business question may matter more than seniority. For a conference delegation, each participant should have a confirmed purpose such as speaking, meetings, representation or sector research.
Use one status vocabulary
Separate proposed, approved internally, invited, awaiting response, accepted, declined, wait-listed and cancelled. Registration submitted, organiser approval and admission confirmed are also different stages. Do not mark a guest as confirmed merely because a host intends to invite them.
Name the person who may change each status and keep a dated record. A shared vocabulary prevents an assistant, host and venue team from counting the same provisional guest differently.
Distinguish the host list from organiser-controlled access
A company may control invitations to its own dinner or meeting while the main fair, festival or conference controls accreditation, passes and admission. Record the two permissions separately.
Use the organiser's current categories and official route. Note whether a guest needs a ticket, professional pass, press accreditation, speaker credential or separate invitation. Admission decisions remain with the relevant organiser or host.
Record the invitation boundary
State whether the invitation is personal, transferable, valid for a companion or limited to a named session. Do not assume that a senior guest may bring an assistant, partner, security officer or photographer without prior confirmation.
If plus-ones are permitted, give them their own record and access status. A count of households or organisations is not sufficient for venue capacity, catering, security or arrival control.
Collect only the personal data required
Keep legal name, professional details, contact information, access status and arrival information only where each field has a defined purpose. The ICO describes data minimisation as limiting personal information to what is necessary. Passport data, dietary or accessibility information and private travel details need stricter handling than an ordinary contact list.
Limit access to the working record, define retention and avoid distributing complete spreadsheets to every supplier. The transport coordinator, venue desk and host may each need different parts of the information.
Reconcile the list with safe capacity
The venue's approved capacity, layout, exits, staffing and programme flow set the practical ceiling. HSE guidance asks organisers to assess how people assemble, enter, move and leave safely, and to monitor numbers so capacity is not exceeded.
Do not treat expected no-shows as additional capacity. If more people accept than can be hosted, use a transparent wait-list or an approved alternative session instead of hoping the arrival pattern will solve the problem.
Confirm the communication sequence
Plan the save-the-date, formal invitation, response deadline, access instructions, final confirmation and same-day contact. Each message should state the event name, date, local time, location, invitation boundary, response method and any separate organiser requirement.
Avoid sending operational details before they are stable. When a venue entrance or collection point changes, issue one corrected instruction and mark the earlier version as superseded.
Prepare the arrival list
Create a concise arrival record for the people working at the entrance: guest name, confirmed status, host, permitted companion, arrival window and authorised escalation contact. Keep sensitive notes out of the visible check-in view.
Arrange separate handling for speakers, mobility requirements, security teams, late arrivals or guests who must collect an organiser credential first. Arrival planning should follow designated entrances, screening and pedestrian routes rather than creating an unofficial shortcut.
Set a rule for changes and substitutions
Define the last point at which names, companions, dietary information or arrival times can be changed. After that point, route requests to the person authorised to decide and the venue or organiser where required.
A personal invitation does not automatically pass to a colleague. Check whether substitution is allowed, then update the invitation, access system, seating and arrival record together. A change in one spreadsheet alone is not operational confirmation.
Brief hosts without exposing the full list
Give each host the guests they are responsible for, the meeting purpose, confirmed introductions and an escalation contact. Avoid circulating private numbers or confidential notes unless the role genuinely requires them.
Agree how absences, unregistered arrivals and disputed invitations will be handled. Front-of-house staff should not have to negotiate exceptions with a guest while senior decision-makers remain unreachable.
Close and review the record
Reconcile invited, accepted, arrived, cancelled and absent guests after the event. Record access issues, queue delays and missed introductions, then remove personal information that no longer has a justified purpose.
Use the review to improve selection criteria, response timing, host assignments and venue communication. The aim is a more accurate next programme, not a permanently growing contact file.
Professional guest-list coordination
Access by ICON IMAGE can coordinate guest selection criteria, invitation status, organiser-controlled access records, arrival notes, host assignments and related executive schedules.
A useful starting brief includes the event, venue, purpose, capacity, guest categories, invitation owner, official access route and the programme each group is expected to attend. Admission and accreditation remain controlled by the relevant organiser or host.
Official sources
Information checked on 16 October 2026. Capacity, access, privacy and admission requirements must be confirmed for the specific event, venue and jurisdiction.