Nonprofit Event Registration: How to Set It Up Well
Good nonprofit event registration comes down to one page, one short form and one checkout. People see what the event is, pick a ticket or RSVP, pay or donate, and get a confirmation email within seconds. Everything else, from dietary needs to check-in lists, is built around that path. This guide walks through how to design it, what to ask, how to take payments, and how to run event day without a clipboard.
TL;DR
- Keep the first form step to the essentials: name, email, ticket type and payment. Collect everything else after the person has registered.
- Show date, time, location, full price and refund terms above the form, and make the page work on a phone first.
- Let guests buy a ticket and add a donation in one checkout, and send a confirmation email immediately.
- Test every ticket type from start to finish before you announce the event, including on a phone and with a keyboard.
- Registration works best on your own website, where the page, the payments and your donor records stay under your control.
Table of Contents
- What event registration has to accomplish
- Put the answers above the form
- Build the form around the shortest path
- Make it work on a phone first
- Take payments and donations in one checkout
- The confirmation email is your most-read message
- Test before you announce
- Accessibility and privacy on the form
- Event day: check-in and follow-up
- Where registration should live
- Promo: registration built into a site we manage
- Perspective: why your event page should be the easy part
- A simple checklist for your next event
- FAQ
- Sources
What event registration has to accomplish
Registration is the first real interaction a supporter has with your event. It has three jobs: tell people clearly what they are signing up for, take their commitment (and money, if any) with as little friction as possible, and give your team the data needed to run the day and follow up afterward.
That third job is easy to forget. A registration list is also a record of who showed interest in your mission. Someone who buys a table or adds a donation at checkout is telling you something about their capacity to give. Someone who picks a hands-on workshop may be a future volunteer. A good process captures that without turning the form into a questionnaire.
The common failure is the opposite: a form built around what the staff might someday want to know. Every extra field is a place for someone to give up.
Put the answers above the form
Before anyone types a single character, the page should answer the questions they have. Event organizer guidance suggests showing these above the form:
- Date, start and end times, and the time zone for any online element
- Venue name, address and directions
- What a ticket includes
- The full price, including fees and taxes, or a clear note that they are added at checkout
- Refund, transfer and cancellation terms
- Accessibility information and a way to request access support
- A named contact person
For a gala, a fun run or a volunteer day, that is a few short blocks of text and a prominent button. Use plain calls to action such as “Register now” or “Save your spot” rather than a vague “Submit.”
Build the form around the shortest path
The research is consistent on this: long or overly detailed forms turn people away, and the shorter and simpler the form, the higher the completion rate. Ask only for name, contact details and ticket type up front, and keep the rest for later.
The fields most events need
Start with the basics and add a field only when you know exactly who will use the answer.
| Field | When to include it | Who uses it |
|---|---|---|
| First and last name | Always | Name badges, check-in list, receipts |
| Email address | Always | Confirmation, reminders, receipts |
| Ticket or registration type | Always | Pricing, attendee, sponsor or volunteer routing |
| Number of guests and guest names | Tables, family events | Seating, badges |
| Payment or donation add-on | Paid or fundraising events | Finance, donor records |
| Dietary needs | Meals served | Caterer |
| Accessibility request | Any in-person event | Event lead, handled privately |
| Phone number | Optional, for day-of logistics | Volunteer coordinator |
| How you heard about us | Optional | Marketing |
A workable target is five to eight fields in total. If you serve several kinds of registrants (attendees, sponsors, volunteers), use conditional logic so each person only sees the fields that apply to them. A sponsor needs a logo upload and a billing contact. A walk-a-thon participant needs a team name. Neither should see the other’s questions.
Split the form into two stages
One approach that works well for busy supporters is a two-step flow. The first step asks only what you need to create the registration. After they have confirmed, a short follow-up collects dietary requirements, session choices and other logistics. People who have already committed are far more willing to answer those questions.
Free events and RSVPs
For a free community event, the RSVP can be as light as a name and an email with one click to confirm. If you still want a gift, offer an optional donation after the confirmation rather than before it.
Make it work on a phone first
Most of your supporters will open your registration link from an email, a text or a social post on their phone. Treat the mobile page as the real page and the desktop version as the bonus.
That means legible text, large tap targets, a page that loads fast, and fields that autofill. Returning supporters should not retype their address. Offer a progress indicator if the form has more than one step, and let people edit or cancel their registration from the confirmation email so you are not fielding those requests by hand.
If you want to price for different audiences, simple options go a long way: early-bird pricing, group registration, member and non-member rates, or a sliding-scale or free ticket for people facing financial barriers.
Take payments and donations in one checkout
A supporter who has decided to attend is also the person most likely to give. Do not send them to a second form to do it. Offer a donation add-on with suggested amounts inside the same checkout as the ticket, with an option to give in honor or in memory of someone, if that fits your event.
A few practical points:
- Set up your payment processor once, at the organization level. Then every event on your site uses the same setup, and you are not reconfiguring for each gala.
- Offer the payment methods your audience uses. Cards and digital wallets cover most people. Some events, such as a church supper or a rural fundraiser, also need a way to register now and pay by check or cash at the door.
- Be transparent about fees. If you add a processing fee, say so before checkout. Surprise charges are the fastest way to lose a ticket buyer.
- Keep tax-deductible and non-deductible amounts clear. A ticket to a dinner usually includes goods or services, so your receipts should separate the ticket value from the donated portion. Ask your accountant how to word them.
- Send a receipt automatically. Donors expect it, and you will need it at year-end.
If you are choosing a processor, confirm the current nonprofit rates on the processor’s own pricing page, since they change and often require proof of 501©(3) status.
The confirmation email is your most-read message
The confirmation email is likely to be opened more than anything else you send for the event. Map D recommends sending it immediately, from a sender name people recognize, and including:
- What was bought and what was paid
- The ticket or a scannable code
- Date, time and venue, with a calendar file
- How to change or cancel the registration
- Who to contact with questions
Then schedule reminders. A reminder a day before and another an hour before cuts no-shows and gives you a natural place to repeat parking details or the schedule.
Test before you announce
Most registration problems come from rushed setups that were never tested end to end. Before you send the link to anyone:
- Register for every ticket type using a real email address.
- Confirm the payment goes through, and the donation add-on lands where it should.
- Check that the confirmation email arrives, looks right on a phone, and carries correct details.
- Make sure the registrant appears in your list with the right status.
- Complete a registration on a phone and again using only a keyboard.
That last step matters for accessibility. Organizer guidance on preparing for registration recommends confirming that the platform works with keyboards and assistive technology on desktop and mobile, with clear form fields, and testing a sample registration before opening.
Accessibility and privacy on the form
An accessible form is a better form for everyone. Use clear fonts, strong color contrast, labels attached to every field and error messages that say what went wrong. Test with a screen reader if you can.
When you ask about access needs, keep the question open. Ask how you can support someone’s participation, not for a medical diagnosis. The same guidance advises that the form should request only data that supports registration, event delivery or a specific planning decision, and that accommodation requests needing advance coordination should be planned for privately. Tell people who will see their answers and how long you will keep them.
If you have supporters who speak another language, a form in that language is a simple way to widen your reach.
Event day: check-in and follow-up
A clean registration list pays off at the door. Printed lists work for a small event, but a searchable digital list is faster: staff look up a guest by name or email, mark them in, and see attendance update as people arrive. A QR code on the confirmation email speeds this up for larger crowds, and lets several volunteers check people in at once. Plan for walk-ins and a waitlist if capacity is limited.
After the event, send thanks within a day or two. Segment the follow-up by what people did: donors get an impact update, first-time attendees get an invitation to learn more, and people who signed up for a workshop or shift get a volunteer invitation. If volunteers are central to your event, plan for volunteer scheduling and shift sign-ups alongside ticketing, since large volunteer-driven events need recruiting, scheduling and hours tracking.
Where registration should live
You have three broad options: a stand-alone ticketing service that hosts your event page, a donation or fundraising platform with event features, or registration built into your own website. Each can work. The deciding factors are how much of the experience you control and where your supporter data ends up.
When registration lives on your own site, supporters stay in your brand from the first click to the confirmation. Your event page can sit next to your donation page, volunteer sign-up and newsletter signup, and you decide which tools connect behind it. The trade-off is that someone has to build and maintain it, which is the part most small teams do not have time for.
Promo: registration built into a site we manage
If your team is small and nobody wants to own a website, that is the gap we fill. We build custom websites for nonprofits, churches and farms and orchards as a monthly subscription that covers design, hosting and updates handled by us, so you never have to log into a dashboard or make edits yourself.
Our sites can include donation forms, ticketing and registration, volunteer sign-up, and integrations with tools such as Stripe, Mailchimp and Planning Center.
Plans start at $29 per month for Launch, then $99 for Growth, $199 for Systems and $399 for Scale, with a one-off build fee of $799. Churches can also choose annual billing: Launch is $319 per year, Growth $1,089, Systems $2,189 and Scale $4,389. See the full plans on our pricing page, or book a call to talk through your next event.
Perspective: why your event page should be the easy part
We see the same pattern with the organizations we work with. The event is well planned, the volunteers are ready, and then registration lives in three places: a link to a third-party page, a spreadsheet, and an email inbox someone checks when they remember.
Our view is that registration belongs on your own website, next to the story of why you exist. A supporter reads about your mission, sees the upcoming event, registers, and gives, all without leaving a place that looks and sounds like you.
That is why we build around a subscription instead of a one-time project. A registration page is never finished. Dates change, ticket tiers change, a new event replaces last spring’s. Because we handle every update, your team sends us the details and the page is current, with no surprise bills and no dashboard to learn.
The same goes for the pieces around it. Donation forms, volunteer sign-up and the tools you already use, such as Mailchimp or Planning Center, should connect to the same site, so the data from one event helps with the next.
Grayson
A simple checklist for your next event
- Write the event page first: what, when, where, price, refund terms, contact.
- Choose your ticket types and any donation suggestions.
- Draft a form of five to eight fields, with conditional logic for each registrant type.
- Connect your payment processor and confirm the fee wording.
- Write the confirmation email and two reminders.
- Test every ticket type on a phone and with a keyboard.
- Prepare your check-in list, walk-in process and waitlist.
- Schedule the thank-you and follow-up messages before the event begins.
If you are planning a recurring event such as an annual gala or a seasonal festival, save this setup as a template so next year is a matter of changing dates and prices.
FAQ
How many fields should a nonprofit registration form have?
Aim for five to eight. Name, email and ticket type come first, with payment for paid events. Add dietary or accessibility questions only if you will act on the answers, and consider moving them to a short follow-up after registration.
Should we ask for a donation during registration?
Yes, as an optional add-on inside the same checkout. Supporters who have just decided to attend are the most willing to give, and a single checkout avoids sending them to a second form. Keep the amount optional and show suggested levels.
Can we accept registrations for a free event?
Yes. A name and email with a one-click confirmation is enough for most free events. Send a confirmation and reminders just as you would for a paid event, and offer a donation after the person has registered.
How do we handle people who cannot pay online?
Offer a registration option with payment by check or cash at the door, or a sliding-scale or free ticket for people with financial barriers. Record those registrations in the same list so check-in stays in one place.
What should we test before registration opens?
Register once for every ticket type with a real email address. Confirm payment, the donation add-on, the confirmation email and the entry in your attendee list. Then repeat it on a phone and with only a keyboard.
Sources
- How to Assess and Improve Your Event Registration Process, Nonprofit Learning Lab
- Preparing for event registration, World Information Architecture Association
- Event Registration Best Practices for Organizers, Map D
- Event Registration Software for Nonprofits: Choosing the Right Tool, Loopyah