A parent wants to sign two kids up for four Saturday workshops. In many Altru setups that turns into eight separate selections, eight sets of registrant details, and a good chance one of the kids ends up on the wrong date. The registrations go through, but the experience is slow for the family and messy for the education team that has to clean up afterward.
Registering for several program events at once is mostly a question of how you’ve built the offering in Altru, plus some discipline about how registrant information gets collected. The right setup depends on what kind of multi-event registration you’re dealing with.
Start with the real question: is it one thing or many?
Before changing anything, decide what the guest is actually buying. Multi-event registrations usually fall into one of three patterns, and each one points to a different setup:
- A series that only makes sense as a whole. A five-day camp, a four-week class, a lecture series sold as a package. People rarely want “just Wednesday.”
- A menu of independent events. Monthly family programs, member tours, workshops a guest can mix and match.
- One event, several people. A family registering multiple children for the same session, each with their own name, age, or allergy notes.
Teams often try to solve all three with the same structure, which is where the repetition comes from.
Series: sell it as one registration
If attendees are expected to come to every session, the cleanest fix is usually to stop selling the sessions separately. Build the series as a single program offering with one price and one registration, and track the individual session dates for staff scheduling rather than for sale.
How you model this depends on your Altru configuration and on how you report attendance. Some organizations set up the series as one program event with a longer duration; others keep separate events for capacity and staffing but only expose one combined option to the public. Test both in a sandbox or with a dummy program before you commit, and check what your reports and queries show afterward. If you’re unsure whether a particular structure is supported in your version, Blackbaud support can confirm before you rebuild a season’s worth of programs.
The tradeoff: a single registration makes drop-in or partial attendance harder to sell. If a meaningful share of people want only some sessions, keep the sessions separate and use the approach below.
Independent events: one order, many items
For mix-and-match programs, the goal is getting several events into one transaction instead of several checkouts. At the desk or on the phone, staff can usually add multiple program events to the same order through advance sales, which keeps payment and confirmation in one place. Train staff to build the whole order before taking payment; it sounds obvious, but split orders are a common source of duplicate fees and confusing receipts.
Online, it depends on how your web forms are configured. Check whether your current form lets a guest add more than one event to a cart in a single visit, or whether they have to start over for each date. Go through it yourself on a phone, start to finish, booking three events. Count how many times you re-enter the same information. That number is usually the clearest argument for whatever change you make next.
Several attendees: collect details once, cleanly
When one buyer registers several people, the friction is usually the registrant questions rather than the event selection. A few things help regardless of the tools you use:
- Trim the questions. Ask only for what you’ll actually use on the day: attendee name, age or grade if the program needs it, and medical or accessibility notes. Everything else can come from the buyer’s constituent record.
- Separate buyer and attendee. Payment and contact info belong to the parent or organizer; per-person questions belong to each attendee. Mixing them is what makes forms feel twice as long as they need to be.
- Watch for duplicates. Multi-attendee registrations are a frequent source of new constituent records for children or guests who already exist in Altru. Decide whether attendees need their own records at all, and if so, review new records from registrations regularly so the household relationships stay correct.
- Confirm the list back. The confirmation should show each attendee next to each event date. That one detail catches most “I meant the other Saturday” mistakes before the program day.
Check your reporting before and after
Whatever structure you pick, run a query on a test registration and make sure you can still answer the questions your education team gets asked: who is attending each session, how many seats remain, and what each registration brought in as revenue. A setup that’s easy for families but makes the roster hard to pull will just move the work from the guest to your staff.
When the web form is the bottleneck
Sometimes the program structure is fine and the real problem is the online purchase flow itself. Social Good’s Checkouts is a branded, mobile-friendly checkout that replaces Altru web forms for tickets, memberships, and donations, with the transaction data written back to Altru. It’s built around tickets, memberships, and donations, so if program registration is your main concern, bring your multi-event and multi-attendee scenarios to a demo and confirm which ones it covers before you plan around it.
Quick answers
Can one person register for several program events in a single transaction?
At the desk, staff can generally combine multiple events in one advance sales order. Online, it depends on how your web forms are set up, so test the full flow yourself before assuming.
Should a multi-week class be one event or several?
If people must attend every session, one registration is usually simpler for everyone. If partial attendance is common, keep separate events and make multi-event ordering easy.
