Choosing the wrong attendee intake route can create avoidable work before an Event has even started. An organizer-managed Excel Guest List import and a public Event Registration form are not interchangeable: one starts with records your team already controls, while the other collects Registration submissions that must remain separate until they meet the rules for Guest List transfer. This guide explains the practical differences, the consequences for guests and event teams, and how to decide between the two routes.
The operational problem: two intake routes with different starting points
The first question is not which form or spreadsheet is easier to use. It is whether your team already knows who should be on the Event Guest List. If the invitees are predefined, the organizer may need a controlled Guest workflow from the beginning. If the attendee population is not fully known, a public Registration Page may be more suitable for collecting individual or group submissions.
- Use an Excel Guest List import when the organizer already holds a list of intended Guests and wants to manage those Event-specific records directly.
- Use public Event Registration when people need to submit their own details, or when a verified Registration Contact needs to register several attendees.
- Consider both routes when some attendees are known in advance while others need to be collected through a public Registration Page.
- Do not treat a public Registration submission as an immediate Guest, QR Ticket holder, or person authorized to enter the Event.
What happens when the wrong route is chosen
The intake decision affects both the guest experience and the work required from the event team. For example, a corporate team with a confirmed list of invitees may create unnecessary public-registration steps for people who were already selected. Conversely, an agency promoting an open registration page may create manual rework if staff ask every attendee to send details by email and then re-enter them into a separate operational list.
- Guests may be unsure whether submitting a form means they are accepted, invited, or authorized to enter.
- Event teams may need to copy information between email, spreadsheets, registration records, and an operational Guest List.
- A single contact registering several people can be represented poorly if the process keeps only one group-level row instead of preserving each attendee as an individual record.
- Assuming that Registration equals Guest status can cause the team to send invitations or prepare entry operations before the eligibility and transfer steps are complete.
- Using a spreadsheet as an informal public form does not provide the same documented Registration, verification, group-attendee, and transfer model.
A practical decision rule: import, register publicly, or combine both
Choose the route according to the source of attendee identity and the amount of organizer control required. The decision is about where the Guest workflow begins, not about which route sounds more modern.
- Choose Excel Guest List import if the organizer has a predefined invitee list, controls who should become a Guest, and does not need a public intake page for the main audience.
- Choose public Event Registration if attendees need to submit their own details, if the Event needs a public Registration Page, or if one verified Registration Contact may register multiple attendees.
- Choose both if the Event has an existing organizer-managed list plus a separate public intake audience. The resulting Guest List can contain imported, manually created, and transferred Guests.
- Keep Registration and Guest List stages separate when acceptance, verification, or organizer review matters before the Invitation and entry workflow begins.
When Excel Guest List import is the better fit
Excel Guest List import is suited to organizer-managed intake. A conference team might receive a confirmed attendee list from an internal department, while an event agency might receive an approved invitee spreadsheet from its client. In these cases, the organizer starts with the people who should be managed as Event Guests rather than asking them to submit a public form first.
- The invitee list is already known and approved by the organizer or Event team.
- The Event is invitation-led and the team wants to create or import Guest records directly.
- The organizer wants to decide when each person enters the Guest List before sending a personalized Invitation.
- Attendee details are managed as Event-specific Guest records rather than as a general CRM contact database.
- The team wants to continue from the Guest List into Invitation, optional RSVP, QR Ticket, and validated Check-in workflows.
When public Event Registration is the better fit
Public Event Registration is useful when the organizer needs a structured way to collect attendee information before the Guest workflow. QRGATE can provide an Event-level public Registration Page and an editable Registration Form. The form can support individual Registration or a group process in which one verified Registration Contact records multiple attendees.
- The Event needs a public link that people can use to submit their own Registration.
- The final attendee list is not known at the start of planning.
- A company coordinator, assistant, HR representative, or other verified Registration Contact needs to register several people.
- Each attendee must remain a separate Attendee Registration so that the person can later have an individual Guest, Invitation, RSVP, QR Ticket, and Check-in history.
- The organizer needs documented Registration states, e-mail verification, custom questions, capacity settings, or an attendee-level Registration export.
- The Event needs informational pricing or calculated participation amounts, while payment collection remains outside QRGATE.
Can one Event use both routes? Yes, but do not assume automatic merging
An Event Registration does not replace the existing Guest List workflow. QRGATE supports organizer-created Guests, supported Excel-imported Guests, and Guests created from eligible Registration transfers in the same Event Guest List. This makes a combined intake model possible when the Event has different attendee sources.
- Import the predefined invitee group through the supported Excel Guest List import route.
- Keep public submissions in the separate Registration layer until the documented eligibility and verification basis is satisfied.
- Transfer eligible Registration records to the Guest List manually, or use Automatic transfer only after the organizer enables that Event-level mode.
- Do not assume that QRGATE automatically merges imported Guest records with Registration records. The system preserves the relationship between a converted Registration and its resulting Guest instead.
- Use the Registration conversion state to distinguish records that have not been added from those already added to the Guest List.
How QRGATE connects the intake routes
QRGATE keeps the two intake paths in one Event-centred workflow while preserving their different business meanings. The Event is the shared context. The Registration module collects and verifies submissions; the Guest List becomes the operational source for the downstream Invitation and entry process after a person has been added as a Guest.
- Organizer-managed route: Event → supported Excel import or manual Guest creation → Guest List → Invitation → optional RSVP → QR Ticket → validated Check-in.
- Individual Registration route: Event → Public Registration Page → Attendee Registration submission → the attendee verifies their own e-mail → eligible Registration → Manual or organizer-enabled Automatic Guest List transfer → Guest.
- Multi-attendee route: a verified Registration Contact adds multiple attendees, with each attendee stored as a separate Attendee Registration before any Guest List transfer.
- Manual transfer is the default. The organizer reviews eligible Registration records and can use the documented Guest List conversion workflow.
- Automatic transfer requires organizer enablement and a documented verification basis. It does not turn an unchecked public submission into an uncontrolled Guest or entry authorization.
- After transfer, the Registration remains linked to the Guest, public Registration editing is locked, and the normal Guest workflow continues.
- Transfer does not automatically send an Invitation. The organizer still manages the separate Invitation workflow.
- A Registration QR code points people to the public Registration Page; it is not the same as the individual QR Ticket used in the later Guest workflow.
The practical benefits of keeping the stages distinct
Separating intake from Guest operations gives the event team a clearer decision boundary. The team can collect information publicly without confusing a submission with an accepted Event Guest, while an invitation-only team can bypass unnecessary public intake and work directly from its controlled list.
- Guests receive clearer expectations because Registration, Invitation, RSVP, QR Ticket, and Check-in represent different stages.
- Organizers retain control over which eligible Registration records enter the operational Guest List when Manual transfer is used.
- Group Registration does not have to collapse several people into one contact: every attendee can continue as an individual record.
- The Guest List remains a practical operating view for Invitations, RSVP status, Guest/Ticket information, and downstream entry preparation.
- Validated Check-in applies the Event’s business rules after the Guest and QR Ticket workflow, rather than treating a form submission or QR image as entry permission.
- A combined Event can support different intake sources without forcing every attendee through the same route.
Prerequisites, limitations, and when to contact support
Before selecting a route, confirm the operating policy for the Event. Excel import is documented as a supported Guest List capability, but the Product Brain does not define every possible spreadsheet structure, column mapping, cleaning process, or import limit. For a specific file or implementation question, contact support@qrgate.org rather than assuming compatibility.
- For public Registration, decide whether the Event should use Manual transfer or organizer-enabled Automatic transfer. Manual is the default.
- Define the verification basis required for eligibility. Self-registration uses the attendee’s own verified e-mail; an attendee added by a verified Registration Contact can be eligible on that contact basis, but contact verification does not verify every attendee’s own e-mail.
- Do not describe QRGATE Event Registration as public ticket sales, payment processing, or automatic entry authorization. Calculated pricing is informational.
- Do not assume automatic waitlisting, iframe form embedding, automatic Invitations, or automatic RSVP reminders; these are not documented capabilities in the supplied Product Brain.
- Remember that Registration and RSVP are separate. Registration comes before the Guest workflow, while RSVP records the current participation intention of an existing Guest.
- If your required file format, eligibility rule, transfer scenario, or integration is not covered here, ask support@qrgate.org for a confirmed answer.
よくあるご質問
What is the difference between Excel Guest List import and Event Registration in QRGATE?
Excel Guest List import is an organizer-managed route for creating Event-specific Guest records from a supported Excel import. Event Registration is an optional public intake layer. A public submission is first stored as a Registration and can become a Guest only after the documented eligibility and verification rules allow Manual or organizer-enabled Automatic transfer.
When should an organizer use Excel Guest List import?
Use it when the invitee list is already known and the organizer wants to control the Guest List directly. It fits invitation-led Events where the team can import or create Guests first, then manage Invitations, optional RSVP, QR Tickets, and validated Check-in.
When is public Event Registration the better intake route?
Public Event Registration is a better fit when attendees need to submit their details through a public Registration Page, when the final list is not known in advance, or when a verified Registration Contact needs to register several people. It is also useful when the organizer needs structured questions, capacity settings, verification, or informational pricing.
Can an Event use both Excel-imported Guests and Event Registrations?
Yes. An Event Guest List can contain manually created Guests, supported Excel-imported Guests, and Guests transferred from eligible Event Registrations. QRGATE does not automatically merge imported Guest records with Registration records, so the team should manage each source according to its documented workflow.
Does a public Registration submission immediately become a Guest?
No. The submission first remains an Attendee Registration. For self-registration, the attendee must verify their own e-mail; for an attendee added by a group Registration Contact, eligibility can be based on that contact’s verification. The organizer then uses Manual transfer by default or enables Automatic transfer for eligible Registrations.
Can a verified Registration Contact register multiple attendees?
Yes. A verified Registration Contact can register multiple attendees for the same Event. Each person remains a separate Attendee Registration and can later have an individual Guest, Invitation, RSVP, QR Ticket, and Check-in history. Contact verification does not by itself verify every attendee’s own e-mail address.
Does transferring a Registration to the Guest List automatically send an Invitation?
No. Transfer creates and links the Guest record, preserves the Registration relationship, and locks public Registration editing. Invitation remains a separate organizer workflow.
Is QRGATE Event Registration a ticket sales or payment-processing system?
No. QRGATE can support informational base pricing, currency, price suffixes, answer or option adjustments, and calculated Registration price snapshots. It does not process payments, provide public ticket sales, or grant entry based on a Registration or calculated price.
Choose your intake route and test the workflow
Create your QRGATE account and try the demo to see how an organizer-managed Guest List and public Event Registration can fit your Event operations. If you need confirmation about a specific import structure or unsupported requirement, contact support@qrgate.org.
Create a QRGATE account and try the demo