The choice between Excel guest list import vs event registration determines where your attendee workflow begins. A supported Excel import starts with people the organizer already knows and manages as Event-specific Guests. Public Event Registration starts with submissions that remain in a separate Registration layer until the documented eligibility and verification rules allow transfer to the Guest List. This guide explains the consequences, failed workarounds, and QRGATE workflow so you can choose the right route without confusing Registration with Guest status or entry authorization.
The problem: two intake routes with different starting points
Excel Guest List import and public Event Registration can both help build an Event audience, but they solve different intake problems. The first question is whether the organizer already controls the intended attendee list. If invitees are predefined, direct Guest List management is usually the clearer route. If people need to submit their own details, or one verified Registration Contact needs to register several attendees, public Registration provides a structured intake layer before Guest operations begin.
- Use supported Excel Guest List import when the organizer already has a predefined list of intended Guests.
- Use public Event Registration when attendees or a verified Registration Contact need to submit attendee information through a public Registration Page.
- Use both when some attendees are known in advance and another audience must apply or register publicly.
- Do not treat a public Registration submission as an immediate Guest, QR Ticket holder, or person authorized to enter the Event.
What goes wrong when the route is mismatched
Choosing the wrong route creates uncertainty for attendees and additional work for organizers. An invitation-led corporate Event may already have an approved list, yet still force selected guests through an unnecessary public form. Conversely, an Event that needs structured public intake may rely on email replies or spreadsheet edits, leaving staff to copy information into the operational Guest List later.
- Attendees may not know whether submitting a form means they are registered, accepted, invited, or allowed to enter.
- Organizers may duplicate data between email, spreadsheets, Registration records, and Guest records.
- A group coordinator may be represented by one row even though every attendee needs an individual operational record.
- The team may send Invitations or prepare entry operations before a Registration has met the eligibility and transfer requirements.
- A spreadsheet used as an informal public form does not provide the documented Registration, verification, group-attendee, and transfer model.
Failed workarounds to avoid
Several shortcuts appear to combine the two routes but create unclear ownership and status. Treating an Excel file as a public form makes it difficult to control submissions, validation, and individual attendee records. Treating every Registration as a Guest skips the distinction between intake and controlled Event operations. Keeping only a Registration Contact row can also lose the identity of the people who will need separate Invitations, QR Tickets, and Check-in records.
- Do not use a shared spreadsheet as a substitute for the public Registration workflow.
- Do not manually copy every public submission into a separate Guest List as an assumed requirement; use the documented Manual or organizer-enabled Automatic transfer path.
- Do not collapse several attendees into one group-level Guest record.
- Do not assume that transferring a Registration automatically sends an Invitation.
- Do not use a Registration QR code as if it were an individual QR Ticket or entry credential.
The decision rule: import, register publicly, or combine both
Choose the route based on the source of attendee identity and the level of organizer control required. The decision is not about whether a spreadsheet or form looks easier. It is about whether the Guest workflow should start with an organizer-controlled record or with a participant submission that must first be verified and evaluated.
- Choose Excel Guest List import when the invitee list is predefined and the organizer wants direct control of Event-specific Guest records.
- Choose public Event Registration when people need to submit their details, the final audience is not known in advance, or a verified Registration Contact may register multiple attendees.
- Choose both when the Event has a controlled invitee group plus a separate public intake audience.
- Keep Registration and Guest List stages separate when verification, acceptance, or organizer review matters before Invitations and entry operations.
When Excel Guest List import is the better fit
The organizer-managed route is designed for invitation-led Events. For example, a company may receive an approved attendee list from an internal department, or an agency may receive a client-approved spreadsheet. The organizer can use the supported Excel Guest List import capability to create Event-specific Guest records, review the list, and continue with the normal Guest workflow.
- The intended invitees are already known and approved.
- The Event is invitation-based and does not need public intake for its main audience.
- The organizer wants to decide when people enter the Guest List before sending Invitations.
- Attendee information belongs to the Event-specific Guest workflow rather than a general CRM database.
- The team wants to continue from Guest List to Invitation, optional RSVP, QR Ticket, and validated Check-in.
When public Event Registration is the better fit
Public Event Registration is suitable when the organizer needs to collect attendee information through an Event-specific public page. QRGATE supports an editable Registration Form, verification, structured questions, capacity settings, and individual or multi-attendee Registration. A verified Registration Contact can register several attendees, while each person remains a separate Attendee Registration.
- The Event needs a public Registration Page that people can access directly.
- The final attendee population is not fully known when planning begins.
- A company coordinator, assistant, HR representative, or other verified Registration Contact needs to register multiple people.
- Each attendee needs an individual Registration record that can later become an individual Guest.
- The organizer needs structured Registration data, custom questions, capacity controls, verification, or a Registration export.
- The Event needs informational pricing or calculated participation amounts, while payment collection remains outside QRGATE.
Can one Event use both routes? Yes, without automatic merging
One Event Guest List can contain manually created Guests, supported Excel-imported Guests, and Guests created from eligible Registration transfers. This makes a combined intake model possible, but QRGATE does not automatically merge imported Guest records with Registration records. Each source should follow its documented workflow.
- Import the predefined invitee group through the supported Excel Guest List route.
- Keep public submissions in the separate Registration layer until the documented verification and eligibility basis is satisfied.
- Use Manual transfer by default, or enable Automatic transfer at Event level for eligible Registrations when appropriate.
- Review duplicate and conversion states rather than assuming that records from different sources have been merged.
- After transfer, the Registration remains linked to its Guest and public Registration editing is locked.
The QRGATE workflow from intake to Check-in
QRGATE keeps both intake routes within the same Event context while preserving their different meanings. Registration collects and verifies submissions. The Guest List becomes the operational source for Invitations and the later entry workflow only after an attendee 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 → attendee verifies their own e-mail → eligible Registration → Manual or organizer-enabled Automatic transfer → Guest.
- Multi-attendee route: a verified Registration Contact adds multiple attendees, with each attendee stored as a separate Attendee Registration.
- Manual Guest List transfer is the default. Automatic transfer requires organizer enablement and a documented verification basis.
- Registration Contact verification can provide the basis for contact-added attendees, but it does not verify every attendee’s own e-mail address.
- Transfer does not automatically send an Invitation. Invitation remains a separate organizer workflow.
- A Registration QR code points to the public Registration Page; it is not the individual QR Ticket used in the Guest workflow.
Benefits and limitations of keeping the stages distinct
Separating Registration from Guest operations gives the Event team a clear control point. Public intake can collect information without implying acceptance or entry, while an invitation-only team can bypass unnecessary public intake and work directly from its controlled Guest List.
- Attendees can distinguish Registration, Invitation, RSVP, QR Ticket, and Check-in as separate stages.
- Organizers retain control over which eligible Registration records enter the Guest List when Manual transfer is used.
- Group Registration preserves individual attendee records instead of reducing several people to one contact.
- The Guest List provides the operational view for Invitations, RSVP status, Guest information, and downstream entry preparation.
- Validated Check-in applies Event business rules; a form submission, Registration QR code, or QR image does not independently authorize entry.
- Excel import is supported, but the Product Brain does not define every possible spreadsheet structure, mapping, cleaning process, or import limit.
- Event Registration is not public ticket sales or attendee payment processing. Calculated participation pricing is informational.
What to confirm before choosing a route
Before configuring the Event, agree on who controls attendee identity, whether public submissions need review, and when records should become Guests. For Registration, decide whether Manual transfer is sufficient or whether the organizer should enable Automatic transfer for eligible submissions. For Excel, confirm that the intended file and workflow fit the supported import capability rather than assuming every spreadsheet structure is accepted.
- Define whether the Event is invitation-led, public-registration-led, or a combination.
- For public Registration, document the verification basis required before transfer.
- Remember that self-registration uses the attendee’s own verified e-mail, while a contact-added attendee may be eligible on the verified Registration Contact basis.
- Do not assume automatic waitlisting, automatic Invitations, automatic RSVP reminders, iframe form embedding, or other undocumented capabilities.
- If you need confirmation about a particular import structure, transfer scenario, integration, or product requirement, contact support@qrgate.org.
Frequently asked questions
What is the difference between Excel Guest List import and Event Registration in QRGATE?
Supported Excel Guest List import is an organizer-managed route for creating Event-specific Guest records from a controlled list. Event Registration is a separate public intake layer. A submission remains a Registration until the documented eligibility and verification rules allow Manual or organizer-enabled Automatic transfer to the Guest List.
When should an organizer use Excel Guest List import?
Use it when the invitee list is already known and the organizer wants direct control of the Event Guest List. It fits invitation-led Events that move from imported or manually created Guests to Invitations, optional RSVP, QR Tickets, and validated Check-in.
When is public Event Registration the better intake route?
Use public Event Registration when attendees need to submit their own information, the final audience is not known in advance, or a verified Registration Contact needs to register multiple attendees. It also fits Events that need structured questions, verification, capacity settings, or informational pricing.
Can an Event use both Excel-imported Guests and Event Registrations?
Yes. The same Event Guest List can contain manually created Guests, supported Excel-imported Guests, and Guests transferred from eligible Registrations. QRGATE does not automatically merge imported Guest records with Registration records, so each source should follow its documented workflow.
Does a public Registration submission immediately become a Guest?
No. It first remains an Attendee Registration. The required verification basis must be satisfied, after which the organizer can use Manual transfer by default or enable Automatic transfer for eligible Registrations. Registration alone does not authorize entry.
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 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 and locks public Registration editing. Invitation remains a separate organizer-controlled workflow.
Is QRGATE Event Registration a ticket sales or payment-processing system?
No. QRGATE can calculate and display informational Registration pricing, including a base price and documented answer or option adjustments. It does not process attendee payments, operate a public ticket marketplace, or grant entry based on a Registration or calculated price.
Choose the intake route that fits your Event
Create your QRGATE account and test how an organizer-managed Guest List, public Event Registration, or a combination of both can support your Event workflow. For a specific import structure or unresolved product question, contact support@qrgate.org.
Create your QRGATE account