Registration

Optional assisted registration for eligible Events

Registration Forms

Prepare hosted or embedded registration forms with custom questions and explicit publication. Keep draft changes, participant consent and saved versions clear.

Ask about eligibility

Interactive preview

See Registration Forms in action

Illustrative example with fictional data, not live customer records. Silent and local to this page.

SHarbour Design Week

First name

Last name

SForm fieldsOrganiser view

First nameRequired

Last nameRequired

EmailRequired

CompanyOptional

Published

Registration form builder: Form fields configured

How organisers set it up

1
Create the form
Choose a clear name and configure the supported participant fields. Collect first and last names separately and ask only for information the event actually needs.
2
Configure questions and requirements
Set supported choice options, required fields and applicable conditions. Review labels, consent wording and capacity-related choices together.
3
Save, preview and publish
Save a draft version and inspect the participant preview. Publish the intended saved version explicitly; existing registrations retain their original version context.

What participants experience

Participants see the published form rather than the organiser's unsaved editor state. They complete the relevant questions and follow the supported submission flow, which may include capacity, invitation or payment steps. An embedded presentation should lead to the same intended registration outcome.

Settings and controls

Draft and published versions

Editing is not publication. Review which version is public before announcing a registration link.

Hosted and embedded access

Use the generated destination or supported embed. Test it in the actual host page, including small-screen layout and the next step after submission.

Illustrative guided walkthrough

See how Registration Forms could play out

Sample scenario for explanation only. This is not live product data, a screenshot, or a real registration or draw.

Scenario: An organiser revises a registration question while registration is open.

Step 1 of 3

Edit the draft

They update the question and save a new draft version.

Reporting

Saved answers belong to the registration and its version context. Registration reports are separate from station-survey reporting, even when both contain similarly named questions. Check access permissions before exporting identifiable answers.

Limitations and boundaries

A form should not imply confirmed entry when a submission is waitlisted or awaiting payment.
Consent fields require clear purpose and suitable wording; participation must not silently authorise marketing.

FAQ

Frequently asked questions

Eligible registration setups support hosted or embedded forms. Test the supported embed in the destination site.

No. The public version is separate, and existing registrations keep their original version context.

Keep reading

Related features

Event Registration

Explore optional StampRise Event registration: forms, invitations, payments, admission, badges and Passport access, with assisted availability explained.

Invitations, Categories & Waitlists

Manage invitation-based registration, categories and capacity limits. Explain explicit waitlist opt-in and the difference between waiting and confirmation.

Paid Registration

Connect eligible registration to Stripe payment. Distinguish submitted forms, pending payment and confirmed registration throughout the participant journey.

Branding & Languages

Adapt the Passport to your event identity and supported participant languages. Review translated content, fallback behaviour and package-dependent branding.

Talk to us about Registration Forms

This capability is set up with the StampRise team for eligible events.

Contact the team All features