You imported a guest list into the wrong event. Or a test registration run left forty fake names on next month’s gala. Or an event was rescheduled and half the registrants need to come off the original date. Whatever the cause, you now have a lot of participants to remove, and clicking delete forty times is not how anyone wants to spend an afternoon.
The short version: Altru’s event tools are built around managing registrants one at a time, and a true “select all and delete” for event participants is not something you should assume exists in your database. Before you plan around it, confirm what your version offers. In the meantime, there are faster and safer ways to get the result you actually need.
First, decide whether you really need to delete
Deleting a registrant removes the record of their participation. That is the right call for junk data: test entries, a duplicated import, names attached to the wrong event by mistake. It is usually the wrong call for real people whose plans changed.
- Bad data that never should have existed (tests, import errors): deletion is appropriate.
- Real guests who cancelled: mark them as not attending or cancel the registration instead. You keep the history, and your attendance and cancellation numbers stay honest.
- Guests moving to another date: they need to be registered on the new event, and the old registration cancelled or removed. Do the add first so nobody falls through the cracks.
If most of your list falls into the second or third group, a bulk delete would actually cost you information you will want later.
Check what your Altru database supports
Altru includes global changes for some record types, and organizations sometimes have custom ones added over the years. Whether there is one that removes event registrants in bulk is something to verify rather than guess:
- Look through the global changes available in your administration area and search for anything mentioning events or registrants.
- If you find one, run it first against a single test event in a sandbox, or against one throwaway registrant, and confirm what it touches.
- If you find nothing, open a case with Blackbaud support and ask directly whether bulk removal of event registrants is possible in your environment. Ask whether the answer changes if the registrations have payments attached.
That last point matters. A registration tied to revenue is not just a name on a list. Expect Altru to protect paid registrations, and plan to handle refunds or revenue adjustments through your normal finance process before the participant record can come off cleanly.
Making the manual route less painful
When one-at-a-time is the only option, a little setup turns a slog into a short, accurate job.
Build the exact list first
Write a query of registrants for the event in question, filtered to precisely the people who should be removed: a specific import date, a test name pattern, a registration option, whatever identifies them. Export it. This becomes your checklist and your audit trail, and it prevents the classic mistake of deleting a real guest who happened to sit next to a test entry on screen.
Separate paid from unpaid
Sort the list by whether any payment is attached. Clear the unpaid ones first; they are quick. Hand the paid ones to whoever handles refunds so revenue is sorted out before anyone touches the registration.
Split the work
Forty registrants across two staff members with the same exported list is a fifteen-minute job. Have each person mark off names on the shared sheet as they go.
Re-run the query when you are done
The same query should now return zero rows, or only the paid records still waiting on finance. That is your confirmation.
When the whole event is the problem
If every participant on an event is junk, for example a test event built during training, it may be simpler to deal with the event itself than with each registrant. Whether Altru will let you delete an event that still has registrants, and what it requires first, depends on what is attached to it. Try it on a copy in a sandbox, or ask support, before doing it in production. For a real event that simply got cancelled, keep the event and its history and mark registrations accordingly.
Preventing the next cleanup
- Test in a sandbox or on a clearly named test event, never on the live event your guests will register for.
- Double-check the target event before any import. Most bulk-removal jobs start with a list loaded into the wrong event.
- Keep a saved registrant query per recurring event type so the next time you need to review or clean up a list, the filter is already built.
Quick answers
Can I delete a registrant who has paid?
Plan on resolving the payment first through a refund or revenue adjustment. Confirm the exact requirement with Blackbaud support, since it depends on how the registration and payment were recorded.
Will removing registrants affect my event reports?
Yes. Deleted registrants disappear from counts entirely, while cancelled ones can still be reported on. That difference is the main reason to cancel real guests rather than delete them.
