Forms & Registration
The form generator is the central tool for creating registration forms for your events. Instead of rigid, standard forms, you can drag and drop to create any number of custom fields, define if-then rules for conditional visibility, and everything is automatically validated—without writing a single line of code. This article covers the entire process, from form design and registration to automatic confirmation.
Overview
The visual editor in the studio lets you add, move, and configure fields. You'll always see a live preview of the form as it will appear to your participants. All entries are automatically and reliably validated during registration—both in the browser and on the server—ensuring that no erroneous or incomplete data is saved.
There is no limit to the number of fields. Whether you need three standard fields or thirty custom fields with nested logic—the generator supports both. All form data flows directly into the participant management system and is available there for searching, filtering, and exporting.
Field types
The form generator provides nine different field types, each suitable for different input scenarios. Each field type comes with its own validation rules and display options.
Text input
Text — A single-line text field for short information such as name, company, or position. You can set minimum and maximum lengths and define placeholder text.
Email — Text field with automatic email validation. The format is checked both in the browser and on the server. Invalid addresses are immediately marked with an error message.
Number — Numeric input field with optional minimum and maximum values. Suitable for information such as age, number of people, or budgets.
Textarea — Multi-line text field for longer entries such as comments, special requests, or dietary instructions.
Selection fields
Select — Dropdown list for individual selection from predefined options. Ideal for fields such as salutation, T-shirt size, or workshop selection.
Radio — Radio buttons where exactly one option can be selected. All options are visible simultaneously, which makes the decision easier when there are few choices.
Checkbox — Checkboxes for multiple selection. Participants can activate several options simultaneously — for example, for areas of interest or additional services.
Special fields
Date — Date field with calendar widget. For information such as birthday, arrival or departure date. The format is automatically validated.
Title — Not an input field, but a heading for the visual structuring of the form. Use title fields to group related fields into logical sections — for example, "Personal Data", "Booking Details", or "Special Requests".
Drag-and-drop arrangement
Fields can be rearranged using drag and drop. Simply grab a field by its handle and drag it to the new position. The other fields will adjust automatically. This allows you to change the form structure in seconds without having to delete and recreate fields.
When you move a field, you'll see a visual marker indicating where it will be inserted. This immediate feedback makes editing intuitive—you'll maintain an overview even with forms containing many fields.
Conditional logic
Conditional fields only appear if certain prerequisites are met. They define if-then rules based on the answers in other fields. This shortens the form for participants who haven't selected certain options and increases the completion rate.
A typical example: The "Company Data" field is only displayed if the participant has selected "Business" under "Registration Type". Or the "Allergies" field only appears if "Catering Required" is activated. Multiple conditions can be combined, allowing even complex branching to be implemented.
The logic is invisible to participants. They only see the fields relevant to their selection. This reduces confusion and leads to cleaner data.
Automatic validation of entries
Quick Event automatically checks all entries from your participants: errors are displayed immediately next to the relevant field—for example, if a required field is left blank, an email address is invalid, or a number is outside the allowed range. Participants see the feedback while entering their information, not only after submitting. As the organizer, you don't need to configure anything—the validation rules are automatically generated from your field configuration.
Mobile optimization
All forms are optimized from the ground up for mobile devices. The fields automatically adjust to the screen width, input fields are large enough for touchscreen use, and the validation messages are easily readable even on small displays.
Select fields on mobile devices utilize the operating system's native dropdown menu, enabling familiar and quick operation. Date fields open the native calendar. The form loads quickly and functions reliably even with a slow mobile connection.
Registration types
Not every event is the same. That's why Quick Event supports different registration types, which can be combined depending on the type of event.
Public registration
With public registration, any visitor to the event page can register directly. The landing page is SEO-optimized, so potential participants can also find the event via search engines. This mode is suitable for conferences, trade fairs, public lectures, and any event aiming for maximum reach.
Private registration (invite-only)
With private registration, only invited contacts can register. Access is controlled via the integrated contact management system : You invite people by email, and only they receive a personalized registration link. This mode is ideal for internal company events, exclusive gala evenings, or closed workshops.
password protection
For events that are intended to be publicly accessible but open only to a specific group of people, you can activate password protection. Participants will then have to enter a password before they see the registration form. This allows you to share the link, for example, via a newsletter or an internal portal, while simultaneously ensuring that only authorized individuals can register.
The registration process
The registration assistant divides the registration process into clearly separated steps. Participants only see the information that is currently relevant—this reduces the dropout rate and ensures intuitive user guidance. A progress indicator shows how far the registration has progressed at any given time.
Step 1: Select the number of people
In the first step, participants select how many people they want to register. As the organizer, you set the maximum number of people per registration in the studio. If only one person per registration is allowed, this step is automatically skipped, and the participant goes directly to the data entry page. If the event has a capacity limit, the remaining places will be displayed.
Step 2: Participant data and quota
The registration form is displayed individually for each person. The fields are configured using the form generator described above and can include standard fields (name, email, company) as well as any custom fields. Conditional fields only appear if certain prerequisites are met.
If quotas are configured, each participant selects their ticket type in this step. All available quotas are displayed with their title, description, and remaining capacity—fully booked quotas are automatically deactivated. For group bookings, multiple people can share a quota.
All entries are validated in real time. Required fields, email formats, and user-defined rules are checked immediately, so errors are detected as they are being entered. For multiple users, the assistant guides them through each form sequentially before proceeding to the summary.
Step 3: Summary and Conclusion
Before submitting, participants see a complete overview: the data entered by all individuals and the selected ticket quotas. After agreeing to the privacy policy , the booking is completed. Quick Event then automatically redirects participants to the success page, where they can download their tickets as a PDF. Simultaneously, all participants receive a confirmation email with their individual QR code.
Booking status
Each booking goes through a clearly defined status workflow. The current status determines which actions are available and which automated processes are triggered.
Pending
Once a participant submits the registration form, the booking is created with the status "Pending". An automatic confirmation of receipt informs the participant that their registration has been received. Depending on the configuration, the confirmation can be done manually by the organizer or automatically.
Confirmed
Confirmed bookings entitle the participant to attend and check in. Upon confirmation, an email containing event details, a QR code, and, if applicable, the PDF ticket or Apple Wallet pass will be sent automatically. The participant will then appear in the participant list .
Cancelled
Cancelled bookings automatically release the reserved space, making the allocated capacity available again. The participant receives a cancellation notification. Cancellations can be initiated by the organizer or—if configured—by the participant themselves.
Automatic confirmations
Quick Event automatically sends the appropriate email whenever the status changes. The email templates can be configured in the Studio under "Emails" and support placeholders for participant data, booking information, and event details.
The standard configuration includes an order confirmation for new registrations, a booking confirmation with a QR code when the status changes to "Confirmed," and a cancellation notification. Additionally, you can create your own email templates for reminders and follow-ups via email campaigns .
Registration without quota
For simple events without ticket categories, you can completely disable the quota selection . Participants will then proceed directly to data entry. This option is suitable for events where there is only one type of participation and no differentiation by ticket type is required.
Application examples
Depending on the event type, you will need different fields. Here are some typical configurations.
Corporate Events
For company events, in addition to standard data, you often collect information such as company name, position, department, cost center, and dietary requirements. Using conditional logic, you can ensure that the "Cost Center" field is only displayed if the participant has selected a specific company.
Training courses and seminars
For educational events, fields such as prior knowledge, learning objectives, certificate requirements, and whether participants will bring their own laptops are relevant. Radio buttons are suitable for assessing knowledge levels, while checkboxes allow for the selection of multiple areas of interest.
Networking Events
Community events benefit from fields such as LinkedIn profile, interests, "I'm looking for" and "I'm offering". This information helps participants find suitable conversation partners and gives you, as the organizer, valuable insights into the composition of your community.
Trade fairs and congresses
For large events with complex booking systems, fields such as booth number, product interest, budget, and meeting slot booking are used. Conditional logic is particularly helpful here: exhibitors see different fields than visitors, and VIP guests receive additional options.
Integration and Export
All collected form data is available via several methods. The CSV export lets you download every registration in an Excel-compatible format directly from the studio. A public event-creation endpoint already exists at POST /api/public/create-event; a full read REST API for programmatic access to form data and integration with external systems is on the roadmap.
Webhooks are also planned and will notify external systems in real time of every new registration. They will let you automatically create leads in your CRM, add participants to email marketing lists, or trigger internal workflows — all without manual effort.
The form data also flows directly into Quick Event's participant management system . There, all user-defined fields are searchable and filterable, just like the standard fields. A separate export and import process is not required.