Skip to content

Build the registration form for an event

This guide shows you how to add questions to the registration form that members complete when they sign up for an event.

Who can do this: Organization admins with event management permissions.

  • Open the event and select the Registration form tab to reach the form builder.
  • Each field saves individually — there is no single save button for the whole form.
  • The questions you build here belong to the event you are editing. Another event’s questions are separate, so the same question can exist on both, and an “already used” error means the name or key is already used on this event — not anywhere else in your organization.
  • Changes take effect for new registrations immediately. Existing registrations are not affected.
  1. In the Questions section, select Add question.
  2. Choose a Field type: Short text, Long text, Single choice, Multiple choice, Checkbox, File upload, Waiver, or Extra-charge.
  3. Enter the question Label. This is required.
  4. To make the question required, check Required.
  5. To show the question only when an earlier question has a specific answer, use the Conditional visibility (optional) section: choose the question in Show if, then pick an Operator and a Show if value. Only questions above this one can be chosen; if none can, the section says “No earlier question can control this one.” If saving would make two questions depend on each other, the question isn’t saved and you see “Circular condition detected — this question and another depend on each other.”
  6. To limit the question to registrants who bought a specific ticket type, select the ticket types under Ticket-type scope. Leave it blank to show the question for all tickets.
  7. Select Save question.

New questions are added at the bottom of the list. Reordering questions and choosing whether answers are written back to the member profile aren’t available yet.

A waiver is required by default — the Required checkbox starts checked. Leave it checked when registrants must accept the waiver to register; clear it to make the waiver optional. A waiver is always answered by the registrant, and it shows only its text — you can’t attach a document link to it.

  1. In the Questions section, select Add question.
  2. Choose Waiver as the field type.
  3. Enter the waiver text in the Label field.
  4. Select Save question.

During registration, members must check a required waiver before they can complete registration. Once a registrant has answered a waiver, their answer can’t be changed when you edit the registration.

Sessions (parallel tracks or time slots registrants pick from) and add-ons (optional extras such as a dinner ticket or parking pass) aren’t available yet. The registration form has a Questions section only. To charge for an optional extra today, add an Extra-charge question.

To reuse questions from a previous event:

  1. Select Copy questions from another event.
  2. Search for and select the source event.
  3. Select Copy questions.

The event’s questions are copied across. If a question’s name or key is already in use on this event, that one is skipped and the rest still copy — the confirmation tells you how many were copied and how many were skipped.

Copied questions appear at the bottom of the question list, and they belong to the event you are editing — the source event’s questions are unchanged, and editing or deleting a copy here never affects the event you copied from.

Each copy keeps its label, key, type, required setting, order, sensitivity, choices, extra charge and access control.

Conditions and ticket scope are matched to this event. A “show if” condition points at the copy of the question it used. If that question was skipped because this event already has it, the condition points at the question already here — as long as that question can still be used in the condition. A ticket scope moves to the ticket type here with the same name. If something has no match, it is removed. The confirmation tells you how many were removed, so check those questions before you publish.

Removing a condition or a ticket scope never hides a question — it shows it to more people. A question that loses its condition always shows to the ticket types it is limited to. A question that loses all of its ticket scope is shown to every ticket type. The confirmation lists both kinds of question.

Select Preview form to turn on preview mode. The note “Preview mode — read only. This is how members see the form.” appears above the question list. Select Preview form again to turn it off.

After saving each question, it appears in the Questions list with its type and label, a Required badge if it is required, and a chip for each ticket type it is limited to.

  • Conditional visibility shows an error — the condition creates a circular dependency. Change the source or target field to break the loop.
  • A question stopped showing after you changed another question — its condition depended on the question you changed, and the change broke it. The builder warns you before saving such a change and marks the question Condition needs fixing. Open that question and fix or remove its condition.
  • A question does not appear for some ticket types — check the Ticket-type scope setting on that question. If a ticket type is not selected, holders of that ticket type do not see the question.