How to Handle Event Cancellations and Refunds for a Nonprofit Fundraiser

The Armada Lions Club sold 140 tickets to their annual fish fry at $12 each — $1,680 in advance sales. Three days before the event, the venue called: a pipe burst and the building was closed for repairs. Now they had $1,680 in collected money, 140 people expecting dinner, and no venue. They found a church hall two miles away in 24 hours, posted on Facebook and sent texts, and ran the event a week late. Three people asked for refunds. The rest showed up.

That outcome is possible for most small nonprofit events — but only if you move fast, communicate honestly, and have a refund policy ready before people ask for their money back.

The Decision: Cancel, Postpone, or Relocate

When something goes wrong, you have three options.

Cancel entirely: issue refunds, absorb any non-refundable costs — venue deposit, food already purchased, printed materials. The money goes out and the event doesn't happen.

Postpone: same event, new date. You keep the ticket revenue, most ticket holders will still attend, and you avoid the full refund process. You will lose some attendees who can't make the new date, but in most cases that's five percent of your crowd, not fifty.

Relocate: same date, new venue. This is the fastest path if you can find space quickly — a clubhouse, a church hall, a VFW post, a school gym. It preserves the momentum of the event and avoids the calendar problem entirely.

Postponing is almost always better than canceling outright. Canceling should be the last resort — it's the only option that guarantees zero revenue for the night.

The decision process:

Can you find a backup venue in time? Call before you announce anything. Don't tell 140 people the fish fry is moving until you have confirmed space.
Is the problem temporary or permanent? A flooded venue is temporary. A venue that just shut down for good is not.
How much of your food is already purchased? If you bought 120 pounds of cod on Thursday for a Saturday event and the pipe burst Friday afternoon, "postpone two weeks" becomes complicated fast.

Communicate Immediately — Even Before You Have Answers

The moment you know there is a problem, post something. Not a full announcement — just acknowledgment.

What to post immediately:

"Our [event name] scheduled for [date] has been affected by [brief description of issue]. We are working on a solution and will update everyone within 24 hours."
Post it on Facebook. Text or email anyone whose contact information you collected at ticket purchase.
If you have a phone tree, use it.

What not to do:

Go silent for 48 hours while the board debates options
Post a vague "update coming soon" and then post nothing for three days
Wait until you have the perfect answer before saying anything

Silence creates rumors. "I heard the whole thing is canceled" spreads faster than anything you post, and it's a lot harder to walk back. One honest "we don't know yet but we're working on it" post prevents dozens of phone calls to your treasurer's personal cell.

Update as soon as you have new information. If the new venue is confirmed, say so. If the new date is set, announce it. Don't hold information until you have everything finalized.

Refund Policy: Decide This Before You Sell a Single Ticket

This is the step most small nonprofits skip until they're standing at the cash box with an angry ticket holder in front of them.

Your refund policy should be decided before ticket sales open, stated clearly on the ticket or in your confirmation message, and applied consistently — the same for everyone, no exceptions based on who's asking.

Common policies that work for small nonprofit events:

No refunds, all sales final: Acceptable for low-price events if stated explicitly at the point of sale. Risky if your organization cancels the event — stating "no refunds" and then canceling leads directly to chargebacks.
Refunds only if the org cancels; no refunds if the attendee cancels: The most common and the most defensible. It protects you from last-minute "I can't make it anymore" requests while giving ticket holders a fair guarantee.
Refunds within X days of purchase, then no refunds: Works for events with a long lead time where you need to lock in counts six weeks out.
Offer to convert the ticket to a donation: This is underused and surprisingly effective. When you have to cancel or postpone, give ticket holders the option to let their ticket price count as a donation to your org. Many people will take it, especially for events tied to causes they already support — food pantry fundraisers, youth sports, community organizations they actually care about.

Write the policy down. If it lives only in the treasurer's head, you will have a different policy for every person who asks.

Processing Refunds

If you have to issue refunds, process them within five to seven business days of the announcement. Waiting longer is the direct path to chargebacks.

Online payments (Stripe, PayPal, Square, or similar): Refund through the payment processor directly. The money goes back to the original payment method automatically, with no bank account or routing number required from the donor. Log the transaction.

If ticket payments went through Potluck, refunds process directly through the platform — no hunting through PayPal or Venmo to reverse individual transactions. Every transaction is recorded automatically.

Cash payments: Have the person bring their ticket stub. Pay them from the cash box. Get a signed and dated receipt with the amount and their name. The receipt goes in your treasurer's records.

Check payments: Write them a check back. Log every refund issued — amount, recipient, date, check number.

Keep a refund log regardless of payment type. You want a written record that shows who was refunded, how much, on what date, and by what method. If a question comes up six months later, you'll have the answer.

What a Chargeback Means

If someone paid by card and requests a refund that doesn't happen quickly, they may dispute the charge directly with their bank. That is called a chargeback, and it is significantly worse than simply issuing a refund.

The bank pulls the money from your account immediately while the dispute is under review — you don't get to hold it while you make your case
There is a chargeback fee of roughly $15 to $25 per dispute, regardless of whether you win or lose
If you lose the dispute, you keep neither the original payment nor the fee
Losing multiple chargebacks can affect your ability to use certain payment processors going forward

The best defense against chargebacks is not an argument to the bank — it's a clear refund policy communicated before the sale, a prompt refund when you cancel, and a paper trail showing the refund was issued. Banks side with cardholders by default. Documentation is the only thing that changes that.

Non-Refundable Costs

When you cancel, some costs are gone. That is not mismanagement — it is the financial reality of event cancellation.

Costs you commonly cannot recover:

Venue deposit (often 25 to 50 percent of the rental cost — read the contract clause on cancellation before you sign, not after you need to cancel)
Perishable food already purchased
Printed materials, banners, signage, flyers
Advertising costs — Facebook ads that already ran, newspaper listings, printing
Raffle license fees that are non-refundable once issued

Document these losses in your treasurer's records as legitimate organizational expenses. If ticket revenue partially covers them, record that offset too. Your annual report or 990-N filing may need to account for the event's net financial outcome, even if the event didn't happen as planned.

If your treasurer is new or this is the first time your org has dealt with a cancellation, a line item in the meeting minutes that explains the unrecoverable costs is worth the five minutes it takes to write.

Rescheduling: How to Do It Right

If you are postponing rather than canceling, a few specifics matter.

Announce the new date at the same time as the postponement notice when possible. "We're postponing — stay tuned for a new date" is less reassuring than "We're moving to June 14 at St. Michael's Hall." One announcement does both jobs.
Confirm the new venue before you say anything publicly. Announcing a postponement and then having to announce that the backup venue fell through is worse than the original problem.
Tell ticket holders their tickets are automatically valid for the new date. Do not make them re-register, re-purchase, or call anyone to confirm. The default assumption should be: you bought a ticket, you have a ticket.
Set a clear deadline for refund requests from people who cannot attend the new date — two weeks is typically enough. State it in the announcement.
Re-promote the event on Facebook and email as if it were new. Some people never saw the original announcement. The new date is a second chance to fill seats.

One thing that trips up small orgs: announcing a postponement without a firm new date, then going quiet for three weeks while the board finds a venue, and then announcing a date that conflicts with three other community events nobody checked. Do the venue work before you post.

Prevention: What to Do Differently Before the Next Event

None of this is complicated in hindsight. It is just easier to skip until you have 140 people expecting a fish fry and a burst pipe.

Before you sell the first ticket:

Identify a backup venue before ticket sales open. It doesn't need to be reserved — just confirmed as a possibility. A phone call to your church hall or the VFW post is enough: "If we ever had an emergency, could we potentially use your space with a week's notice?" Most places say yes to that question.
Read your venue contract's cancellation and force majeure clauses. If the venue cancels on you, do you get the deposit back? The contract has the answer. Not finding out until after is a very expensive time to learn.
Write your refund policy and put it on the ticket or confirmation. Two sentences is enough: "Tickets are non-refundable unless the event is canceled by the organization. If the event is canceled, full refunds will be issued within seven days."
Collect contact information for every ticket buyer. Name and phone number or email. Facebook is not a reliable communications channel for urgent announcements — not everyone sees posts, the algorithm buries things, and accounts get deactivated. A direct text or email reaches people that Facebook doesn't.
Consider event cancellation insurance for events with significant pre-purchased inventory. If you're buying $800 in food and paying a $300 venue deposit upfront, a one-time insurance policy that covers cancellation for weather or venue failure is worth pricing out. It is not always expensive for small nonprofit events.

The Short Version

If something goes wrong with your event, this is the sequence:

Move fast on the decision — cancel, postpone, or relocate. Every hour of delay is an hour of rumors.
Post something immediately, even if the answer isn't finalized yet.
Have your refund policy written down before anyone asks.
Process refunds within five to seven days of the announcement — not two weeks, not "when we get to it."
Document non-refundable losses as organizational expenses in the treasurer's records.
For next time: backup venue, written refund policy, ticket buyer contact list. Those three things eliminate most of the chaos.

The Lions Club that ran their fish fry a week late and kept 137 out of 140 ticket holders did not do anything remarkable. They made a decision fast, told people the truth, and found a church hall. That is the whole playbook.

Handling ticket sales through Potluck means you have a record of every buyer and a way to process refunds in one place. Free to start.

Looking for more ideas? See the full list: Fundraising Ideas for Small Nonprofits and Community Clubs.