A pipe bursts in the classroom wing, or the presenter for Saturday’s family workshop calls in sick, and suddenly a scheduled program event with thirty tickets already sold has to come off the calendar. Anyone who has canceled a group reservation in Altru tends to expect a similar, guided process for a public program. In practice, canceling a scheduled program event usually takes more manual work, and it helps to know where the gaps are before you need to do it under pressure.
Why it feels different from a group reservation
A group reservation is one record tied to one organizer. When you cancel it, everything you need (the itinerary, the deposit, the balance, the contact) lives in one place, and Altru is built around that single-record workflow.
A scheduled program event is different. It’s one event with many separate orders attached: some sold online, some at the desk in daily sales, some in advance sales, some possibly comped or redeemed by members. Canceling the event itself doesn’t automatically unwind each of those orders, refund each buyer, and notify each guest. Exactly how much Altru handles for you depends on your version, your configuration, and whether tickets have already been sold, so test the process in a sandbox or confirm with Blackbaud support before you rely on it. Assume the order-level cleanup is yours unless you’ve seen otherwise.
Before you touch the event: get the list
The single most useful step is to pull a complete list of who’s affected while the event still exists in its normal state. Changing or removing the event first can make that list harder to build.
- Build or run a ticket/order query filtered to that program and event date and time. Include the order number, sales channel, payment method, amount, constituent name, email, and phone.
- Export it and save a copy with the event name and date in the file name. This becomes your refund and outreach checklist.
- Note the anonymous sales. Walk-up daily sales often have no constituent attached. Those buyers can’t be contacted, so decide now how you’ll honor them if they show up.
Stop new sales
Close the door before you start refunding, or you’ll be refunding new orders all afternoon.
- Remove the event from online sales so your web forms and any embedded calendar stop offering it.
- Make sure it’s no longer available in daily sales and advance sales. Depending on your setup, that may mean editing the event’s capacity or availability rather than deleting it.
- Avoid deleting the event outright if any orders exist. Altru may block it, and even where it doesn’t, you lose the clean history that reports and auditors will want later. Most admins keep the record and change its name or description to show it was canceled (for example, adding “CANCELED” to the start of the name) so staff spot it immediately.
Refund, exchange, or credit each order
Work through your exported list one order at a time. Decide your policy first so staff aren’t improvising:
- Full refund to the original payment method. This is the cleanest option for online card payments. Check how far back your payment processor allows refunds against the original transaction.
- Exchange to a rescheduled date of the same program, if you’re running it again. This keeps revenue on the books and is often what guests prefer.
- Cash and check sales need a separate path, usually a refund check or in-person cash refund, so flag those on the list.
- Member or comp tickets may have no money to refund, but the guest still needs to hear from you.
Mark each line on your spreadsheet as you go (refunded, exchanged, unreachable). If more than one person is processing refunds, split the list rather than sharing it, so no order gets refunded twice.
Tell people, quickly and once
Use the emails from your query to send a single, clear cancellation message: what was canceled, what you’ve already done (refunded, or the new date you’ve moved them to), when the refund should appear, and who to call with questions. If you’re offering a choice between refund and exchange, give a deadline and a default so you aren’t chasing replies for weeks. Call the buyers who have only a phone number on file.
Post a short notice on the program’s web page and brief the front desk. Some people won’t read their email, and the desk should know exactly what to tell anyone who arrives.
Clean up afterward
- Reconcile. Rerun your query and confirm every order now shows as refunded or exchanged. Compare refund totals against your deposit and batch reports so finance isn’t surprised.
- Check program reports. Attendance and revenue reports for that program will now show a canceled date. Make sure your naming convention makes that obvious to anyone reading them next year.
- Write down what you did. A one-page internal procedure (who pulls the list, who stops sales, who refunds, who emails) turns the next cancellation into a 30-minute task instead of a scramble.
Quick answers
Will canceling the event automatically refund ticket buyers?
Don’t count on it. Treat refunds as a separate, order-by-order step unless you’ve confirmed otherwise in a test environment.
Should I delete the event or keep it?
Keep it and relabel it as canceled. Deleting an event with sales history causes more problems than it solves.
What if I’m only canceling one time slot of a recurring program?
The same steps apply, but filter your query to that specific date and time so you don’t pull in guests from slots that are still running.
