Fundraiser event registration form
A fundraiser registration collects who is coming and what level they have chosen, not what they are paying — pricing and processing donations happen outside the form. This form records attendance and ticket type so the event team knows headcount and can plan seating and materials. The form stops at capacity so organizers do not accidentally overbook the venue.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
Ticket level as a select field, not a payment
The form asks which ticket level someone is registering at — gala tables, VIP seating, general admission — but does not collect payment. The registration records the choice so event organizers know headcount per level; payment is processed separately on a checkout page.
Headcount and dietary needs on one form, before the event
A number field for guest count and a textarea for dietary restrictions are both optional on a registration form, which lets attendees reserve early without nailing down every detail. The form is the place to record this, not an email thread or spreadsheet.
No card required.
Fundraiser Event Registration
Live previewHow to build this form
5 steps in the editor. Nothing here needs a paid plan.
- Add text and email fields for attendee name and contact information.
- Add a phone field, optional, for event logistics if coordination is needed later.
- Add a select field for ticket or sponsorship level, marked required so every attendee is categorized.
- Add a number field for guest count, optional, in case attendees bring others.
- Add an optional textarea for dietary restrictions, and set a response cap in Settings.
Fields in this form
6 fields, using 6 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Full name | Short text | Yes |
| Yes | ||
| Phone | Phone | Optional |
| Ticket level | Select | Yes |
| Number of guests (including you) | Number | Optional |
| Dietary restrictions | Long text | Optional |
What goes wrong with this form
Specific to a fundraiser event registration form, not general advice about forms.
Conflating registration with payment
This form records attendance; payment is a separate step. A form that tries to take payment is not doing the right job for either concern — registration loses the payment details and payment lacks the attendee logistics. Keep them separate.
A free-text ticket level instead of a dropdown
Put ticket types in a select field so attendees pick from options that exist, and you can count each level in the export. Free text produces "table", "table for two", "single seat" — none of which add up the same way.
No capacity check for the venue
Set a response cap in Settings once you have the venue limit. Without one, an over-booked event produces registrations nobody can accommodate, and following up to tell someone there is no space after they registered is the conversation you wanted to avoid.
Questions about this form
Does this form take payment?
No — it registers attendance and records the ticket level someone chose, but payment happens separately. Build this form to capture who is coming at what level, point it to an external checkout for donations or ticket purchases, then reconcile registrations against payments afterward.
How do I know how many meals to order for a fundraiser?
Export the responses to CSV and add up the guest count column for each ticket level. That gives you a real number to quote to your caterer, rather than a guess — and dietary restrictions are a separate column to walk through with the kitchen.
Can I tell which attendees are coming as a group?
Not from a single form response — this form registers one attendee at a time. If grouping matters for seating, handle that in a follow-up email or a separate form just for organizing tables, once you know who is coming.