Event reception and registration: visitor flow and incident handling
Plan posts, operating permissions and referrals for welcoming attendees without improvising access decisions. A briefing guide with three planning scenarios.
1. Map the arrival route and separate decisions
The process starts before the desk: identify where registered or expected attendees are welcomed, where initial enquiries are directed and who handles an issue. Circulation and waiting areas need to fit the venue plan and conditions without blocking access or exits.
Separate checking a registration from deciding an exception. A staff member may guide and verify using the agreed tool; new registrations, category changes or access outside the assigned scope belong to the designated decision-maker. Printing a badge does not mean it grants entry to every area.
The photograph is an archive image of event staff. It is not presented as a registration assignment or evidence of a registration system operated by Wira.
2. Agree roles and referral responsibilities
Welcome
Identifies the reason for arrival and directs the attendee to the correct point.
Refers to: Registration or the incident lead, depending on the enquiry.
Registration
Checks the authorised tool and issues credentials under the agreed procedure.
Refers to: Organiser representative for additions, categories or exceptions.
Incident handling
Takes the minimum information and updates the attendee without announcing details to the queue.
Refers to: Organiser for decisions; support for tool faults.
Coordination and handover
Checks post coverage, contacts, programme changes and outstanding tasks.
Refers to: Event and venue leads for decisions outside the assignment.
The names and permissions behind these functions are specified in the briefing. This matrix does not establish a fixed headcount: simultaneous tasks, breaks, languages or several areas may need a different staffing plan.
3. Define the tool, permissions and list handling
Agree who supplies the system, user accounts, devices, printers, consumables and connectivity. Each role needs to know what it can view, change, reprint or export and whom to ask for help. Do not assume staff bring an included platform, licences or equipment.
The party responsible for data processing defines instructions, attendee information, access and retention conditions. Avoid photographs of lists, uncontrolled shared accounts or copies on private phones as an improvised workaround. Take only what is needed for the assigned function.
Spain’s AEPD explains data minimisation and limiting access and retention, and distinguishes informing people from obtaining consent where that is the relevant basis. These are references for operations subject to the GDPR; the organiser must confirm the applicable framework. Registration does not itself mean agreement to marketing messages.
References: AEPD: principles · information and consent.
4. Rehearse opening with scenarios, not real data
Before attendees arrive, review an expected arrival, an issue and the decision-making contact. Use fictional data for training tests. Check that every post knows the current procedure and how to notify others without leaving a task that still needs coverage.
The handover should cover supplies, replenishment, languages by post, hours and breaks. Any system-outage fallback must be approved and prepared by the responsible parties: permitted actions, where they are recorded and how they are reconciled afterwards. A connection failure is not a reason to invent a parallel list.
5. Three issues for rehearsing referrals
The following are fictional planning scenarios, not delivered Wira assignments or verified results. Use them to rehearse who communicates, who decides and what remains pending.
Name not found: reception requests only the information specified for checking registration and refers to the organiser contact. It neither announces the name to the queue nor grants access independently. The responsible person provides the next step.
Unreadable code or reprint: follow the agreed verification and support procedure. Before another credential is issued, the authorised post confirms what happens to the previous one and its permissions. The decision is not made simply because the printer is working again.
Room or agenda change: coordination receives a confirmed version, informs affected posts and checks who is responsible for directions. Staff do not confirm a room, access category or meeting that has not yet been validated.
6. Hand over the post and close the assignment
The incoming person receives the role, hours, operational contact, programme version and necessary pending items. Identify who covers attendee service during the handover and who takes open issues; leaving an unlocked screen is not a handover.
At close-out, return equipment, materials and records through the agreed channel. Assign who revokes access, reconciles duplicates or pending items, and follows retention or deletion instructions. Distinguish registrations, credentials issued and incidents: these counts are not sales or proof of satisfaction.
Prepare the proposal
To request a team, provide the event, city, venue, hours, simultaneous posts, languages, estimated volume and arrival peaks, available system and resources, decision-maker and support contact. A named attendee list is not needed for the first enquiry. Scope is defined in the proposal.
Before reception opens
Can reception admit someone who is not on the list?
Only within expressly assigned authority. Additions, categories and exceptions are referred to the organiser representative under the agreed procedure.
Are a platform, printers or licences included?
These are not assumed. The brief and proposal identify who supplies each resource, permissions, support and consumables, as well as staff duties.
What should be prepared for a connection failure?
A fallback approved by the system and event leads, with permitted tasks, controlled recording and later reconciliation. Not improvised copies on private phones.
Are the examples delivered Wira assignments?
No. They are fictional scenarios for preparing the briefing and incident referrals, not Wira cases, testimonials or results.
Tell us the staff roles and running order