Event agencies often coordinate several operational stages for the same client Event. Attendees submit information through a public form, the agency reviews who is eligible, the Guest List must be prepared, Invitations may need to be sent, and the onsite team must validate entry at the door. When those stages are separated across forms, spreadsheets and disconnected check-in tools, it becomes harder to know which people are merely registered, which are accepted Guests and which have actually entered.
QRGATE is event registration and QR check-in software for agencies that want these stages connected without collapsing them into one unclear status. Event Registration is an optional layer before the Guest List. After the documented verification and eligibility rules are met, an organizer can transfer attendees manually or enable automatic transfer for eligible registrations. The later Guest, Invitation, QR Ticket and Check-in workflow remains distinct and controlled.
The agency problem: registration is not the same as admission
A public Registration submission is useful attendee intake, but it is not automatically an accepted Guest and does not grant Event entry. This distinction matters when an agency is managing applications, client approvals, capacity limits or different attendee types. Without a connected workflow, teams may need to reconcile form responses against a spreadsheet, decide who should be accepted, create or update Guest records, issue entry credentials and prepare onsite operators separately. Common symptoms include duplicated attendee information, unclear approval status, capacity decisions that do not reach the entry team and uncertainty about whether an attendee has received the correct QR Ticket.
- Guests may be confused with people who have only submitted a Registration.
- Agency teams may re-enter custom answers or capacity decisions in downstream lists.
- A Registration QR code can be mistaken for an entry ticket.
- RSVP responses can be mistaken for actual attendance if the states are not kept separate.
- Different client Events can become difficult to compare operationally when every team uses a different handoff process.
Why manual workarounds often fall short
A separate form, spreadsheet and scanner can work for a simple one-off intake process, but the handoffs become harder to control as an agency repeats the workflow for different clients and Events. A spreadsheet may contain answers and approval notes while the check-in team works from a different list. Manual copying can also make it difficult to preserve one individual record for every attendee in a group Registration. QRGATE does not remove the organizer’s decision-making role. Instead, it gives each stage a defined place: Registration for public intake, Guest List for accepted Event participants, Invitation for communication, QR Ticket for identity and Check-in for recorded entry. That separation helps agencies understand what has happened to each person without presenting unsupported automation as a substitute for review.
- Use public Registration when the Event needs attendee applications or open intake.
- Use organizer-managed Guest List entry or supported Excel import when the agency already has a defined list.
- Combine both sources in one Event when some Guests are known in advance and others register publicly.
- Keep the Registration export separate from the Guest List export so each file represents the correct operational layer.
How QRGATE connects the registration-to-entry workflow
QRGATE keeps the workflow within the same Event context while preserving the boundaries between its modules. An agency can configure a separate Event for each client engagement, then manage that Event’s Registration settings, Guests, Invitations, QR Tickets and Check-in results from the same tenant-scoped account. Events remain separate lifecycles: Guests, Tickets, Invitation activity and Check-in results are not automatically merged across Events.
- Event Registration: publish an Event-specific Registration Page and configurable form.
- Registration verification: establish the documented basis for an attendee to become eligible for Guest List transfer.
- Guest List: hold accepted Event Guests, including manually created, imported and transferred records.
- Invitation: send supported personalized Event email after the Guest workflow is ready.
- QR Ticket: provide the Guest-facing QR identity used in the later entry workflow.
- Check-in: validate the QR Ticket against the Event and record the entry result.
- Excel: export supported Registration answers or operational Guest data for review and client coordination.
Manual and Automatic Guest List transfer
Manual transfer is the default and gives the agency direct control over the approval step. The organizer reviews Registration records, applies the appropriate status and selects eligible attendees for the Add selected to Guest List action. The system preserves the relationship between the original Registration and the resulting Guest. An organizer may enable Automatic Guest List transfer for an Event. Automatic transfer still begins with a Registration record and only applies when the documented eligibility and verification rules are satisfied. For example, a self-registrant may need to verify their own email, while an attendee added by a verified Registration Contact may be eligible on that contact-based verification basis. Registration Contact verification does not automatically verify every attendee’s own email address. In either mode, Guest List transfer is not an Invitation send and is not admission by itself. After transfer, the normal Guest lifecycle continues: Guest, Invitation, optional RSVP, QR Ticket and validated Check-in.
- Manual transfer is the default mode.
- Automatic transfer must be enabled by the organizer for the Event.
- Eligibility and duplicate-conversion protections are checked server-side.
- Public Registration editing locks after the attendee is added to the Guest List.
- An Invitation is not sent automatically merely because transfer has occurred.
A practical agency workflow for recurring client Events
The following workflow can be reused for a corporate conference, partner Event, product launch or another client engagement. The exact Event settings remain under the agency’s control.
- Create a separate QRGATE Event for the client engagement and configure its Event details and branding.
- Enable the optional Event Registration module when public attendee intake is required.
- Set Registration opening and closing times, maximum attendee capacity, public availability display and the Manual or Automatic transfer policy.
- Build the Registration Form with the required standard fields and any custom questions or capacity-limited options.
- Share the Public Registration URL, its Registration QR code or the supported website link/button HTML.
- Review Registration records, verification state, status, capacity information and any group-level information before transfer when using Manual mode.
- Transfer eligible attendees to the Guest List, or let the organizer-enabled Automatic policy handle eligible verified records.
- Review the resulting Guest List. Create additional organizer-managed Guests or import supported Excel data where required.
- Send the supported personalized Invitation workflow separately. Enable RSVP only when the client needs participation-intention tracking.
- Let each Guest access the individual QR Ticket. Do not treat the Registration QR code as the Guest QR Ticket.
- Prepare Entry Staff, Self Check-in or other documented onsite workflows and run validated QR Check-in at the Event.
- Use supported operational views and exports after the Event. RSVP remains participation intention; Check-in remains the recorded entry result.
Individual and multi-attendee Registration without losing records
A verified Registration Contact can register several attendees for the same Event when group Registration is enabled. This is useful when a company coordinator, agency contact or client representative submits a team list. Each person remains a separate Attendee Registration with their own answers, status, calculated price snapshot, conversion state and potential Guest, Invitation, QR Ticket and Check-in history. An attendee added by a Registration Contact may later use a secure self-claim workflow to verify their own email and manage their personal Registration data within the documented rules. This provides a more precise handoff than treating the whole group as one Guest record.
- The Event capacity counts attendees, not Registration Groups.
- Duplicate attendee email protection prevents a second attendee Registration for the same Event identity.
- A group can include attendees with different Registration statuses.
- A group-level central note is one Registration Group field, not a separate note copied to every attendee.
- A group status action updates each attendee’s existing Registration status; it does not create a separate independent Group status.
Forms, capacity, pricing and Excel export for client coordination
QRGATE’s Registration Form Builder supports structured collection instead of forcing every answer into a general comment field. Agencies can configure short text, long text, Yes/No, single choice, multiple choice, checkbox and attendee-level capacity choice questions. Standard identity fields remain active and required, while other supported fields can be configured for the Event. Capacity can operate at two levels. The Event can have a maximum attendee capacity, while a capacity choice can limit a specific option such as a workshop or time slot for individual attendees. These are separate constraints and are protected by server-side checks. Rejected or Waitlist registrations can release active capacity, while later approval requires the relevant capacity to be checked again. QRGATE can also calculate an informational Registration price from a base price and selected answer or option adjustments. This can help an agency display or export participation-fee information, but it is not attendee payment processing, ticket sales, settlement or donation collection. A client’s external payment instructions can be included in the organizer-defined information area where appropriate.
- Add structured custom questions and help text to collect consistent client-approved information.
- Use attendee-level capacity choices for limited workshops or selectable options.
- Show public availability only when the organizer chooses to display it.
- Export Registration answers, statuses, verification data, capacity choices and supported pricing snapshots to Excel.
- Use the Registration export for intake analysis and the Guest List export for downstream Guest operations.
- Do not describe QRGATE informational pricing as an attendee checkout or payment collection feature.
Repeatable operations across separate client Events
For agencies running recurring client work, the value of QRGATE is a repeatable operating model rather than a claim of unlimited usage, automatic discounts or a shared unrestricted marketing database. The agency can manage separate Event lifecycles from the same QRGATE account, keeping each client Event’s Guests, Invitations, Tickets, Registration records and Check-in results in their own Event context. Agencies can review the current QRGATE Event Credit packages and, where relevant, discuss the separately managed annual partnership option. Package prices, available volumes and commercial terms depend on current tenant and market data. Agency frequency alone does not create a guaranteed discount or unlimited entitlement. For agencies managing 10, 20 or more client events per year, QRGATE provides a repeatable workflow while keeping every event's guest data, invitations, QR tickets and check-in results separate.
- Standardize the registration-to-entry process while keeping each Event operationally separate.
- Reuse team knowledge about verification, transfer, Invitations and onsite Check-in.
- Combine public Registration with manually created or imported Guests when the client workflow requires both.
- Compare current Event Credit packages with an annual partnership only using current commercial information.
- Contact support@qrgate.org if a required agency workflow or commercial question is not documented.
Important prerequisites and product boundaries
QRGATE is an Event guest operations platform, not a CRM, public ticket marketplace, generic marketing automation system or attendee payment processor. Agencies should evaluate the workflow against the actual client requirement before committing to a process. Event Registration is optional and must be configured for the specific Event. A Registration submission is saved before verification, but only an eligible verified Registration can proceed through the applicable transfer policy. After transfer, the public Registration record is locked for editing and the Guest becomes the operational object for the Invitation, QR Ticket and Check-in stages. Supported QR Check-in operations can continue through the documented offline synchronization workflow during a temporary connection interruption, but offline support does not mean every QRGATE module works offline. If a requirement is not covered by the documented Product Brain, contact support@qrgate.org rather than assuming an integration, client portal, payment flow or automation exists.
- Registration is not RSVP, and RSVP is not Check-in.
- The Registration QR code points to the public Registration Page; it is not a Guest QR Ticket.
- A Wallet pass, where supported, represents an existing QR Ticket and is not a second Ticket or automatic entry authorization.
- Guest List transfer does not automatically send an Invitation.
- QRGATE does not provide an attendee payment processor through Registration pricing.
- Client Events should be configured and evaluated as separate Event lifecycles; an agency client portal or unrestricted account hierarchy should not be assumed.
Frequently asked questions
Is QRGATE Event Registration separate from the Guest List?
Yes. Event Registration is an optional public intake layer before the Guest List. A public submission is stored as a Registration first. A Guest is created only after the applicable verification, eligibility and Manual or organizer-enabled Automatic transfer rules are satisfied.
Does every public Registration submission immediately become a Guest?
No. Registration does not automatically grant Guest status or Event entry. Manual transfer is the default. Automatic transfer can be enabled by the organizer, but only eligible verified Registrations can be transferred.
What is the difference between Manual and Automatic Guest List transfer?
In Manual mode, the organizer reviews and selects eligible Registration records for transfer. In Automatic mode, the organizer has enabled a policy that allows eligible verified Registrations to be transferred by the documented workflow. Neither mode automatically sends an Invitation.
Can one Registration Contact register multiple attendees for a client Event?
Yes, when multi-attendee or group Registration is enabled for the Event. Each attendee remains a separate Registration record and can later have an individual Guest, Invitation, QR Ticket and Check-in history. Registration Contact verification is not the same as verifying every attendee’s own email.
Can agencies add custom questions and capacity limits?
Yes. The Form Builder supports structured question types including short text, long text, Yes/No, single choice, multiple choice, checkbox and capacity choice. Agencies can configure maximum Event attendee capacity and separate attendee-level option capacities.
Does QRGATE collect attendee Registration payments?
No. QRGATE can calculate and display informational pricing from a base price and selected adjustments, but this is not attendee card payment processing, ticket sales, settlement or donation collection. QRGATE’s own Event Credit purchase is a separate commercial workflow.
Is the Registration QR code the same as a Guest QR Ticket?
No. The Registration QR code directs people to the public Registration Page. A Guest QR Ticket belongs to a Guest after the Guest List workflow and is used in the later validated Check-in process.
Can agencies combine public Registration, Guest List and Excel workflows across recurring client Events?
Yes. Within a specific Event, the Guest List can contain organizer-created Guests, supported Excel-imported Guests and Guests created through eligible Registration transfer. Registration and operational Guest exports remain distinct. Separate client Events retain their own records and results while the agency manages them from the same QRGATE account.
Create an account and try the agency workflow
Set up a QRGATE account to evaluate the documented Event Registration, Guest List, QR Ticket and Check-in workflow. An eligible new customer may be able to activate the available Demo entitlement; current access and commercial conditions are verified by the platform.
Create your QRGATE account and try the demo