Where a fundraising night actually breaks: a walkthrough from ticket page to the front door

Nonprofit event threads are some of the most honest ones we read. Nobody is selling anything. A development director, a volunteer coordinator or a board member who got handed "the website bit" describes what went wrong at last year's dinner and asks how not to repeat it.

We've collected a lot of these from across the communities we follow: galas with a line out the door, first fundraisers stuck between a free invite and a ticketed dinner, golf days with an auction bolted on, organisers waiting on payouts from a ticketing platform, and small teams trying to staff a Sunday event with volunteers who can't commit to weekends.

What stands out is that almost none of these events failed on the big decisions. The venue was fine. The cause was clear. Things broke at the handoffs, the places where one person's spreadsheet becomes another person's clipboard. So instead of a feature list, here's a walk through one composite fundraising night, stage by stage, with what people told us went wrong and what they changed.

Stage 1: Deciding what you're actually selling

The first fork comes before any ticket page exists. Is this an open event where you hope people give on the night, or a ticketed dinner where the ticket is the donation?

People who ran their first fundraiser described this as the decision they wished they'd made on purpose. Open invites bring a bigger crowd but make headcount a guess, which hurts when catering is per plate. Ticketed dinners give you a number to plan around but can shut out the supporters who would have given more once they were in the room.

A middle path that came up more than once: a free RSVP for supporters and volunteers, paid tickets or tables for everyone else, and a clear "give on the night" option for people who registered free. The important part is that free and paid sit in the same list. If they live in two tools, nobody knows the real headcount until the night.

Stage 2: Table captains and give-get goals

Many galas don't sell most tickets through a public page at all. They sell them through table captains or board members with a goal: fill a table, or bring in a set amount.

This is where reporting quietly breaks. The ticketing tool knows which tickets sold. The development team's spreadsheet knows which captain promised what. Nobody can answer "how close is each captain to their goal?" without a manual merge, usually the week before, when there's no time.

What helped: give every captain their own link or code so sales attribute themselves, and decide early whether a captain's comped seats count toward their goal. That second question sounds small. It turned into a real argument in more than one organisation.

Stage 3: Comps, sponsors and the leaky guest list

Comped seats for sponsors, speakers, honourees and volunteers are normal. The trouble starts when they're handed out by email, text and conversation, and never land in the same list as paid tickets.

People described comp leakage as a slow drip: a sponsor's table of ten becomes twelve, a speaker brings a partner, a board member "just adds a couple". None of it is wrong on its own. But catering, seating and the door list all assume one number, and nobody owns it.

The fix people landed on was boring and effective. Every seat, paid or comped, goes in one guest list with a type attached, and only one or two people can add comps. If someone wants an extra seat, it goes through them.

Stage 4: Add-ons that slow the door

Drink tickets, raffle entries, parking passes, dinner choices and auction paddles are all reasonable to sell ahead. The surprise is how much they slow down check-in when the door team has to hand out the right extras to each guest.

One pattern that came up: add-ons sold to people who never bought a ticket, which leaves the door team with someone who has a drink voucher and no seat. Another was a single check-in line where every guest needs three different things handed over.

What helped:

• Only sell add-ons attached to a ticket, never on their own.
• Pre-pack extras per guest or per table before doors open.
• Keep a separate desk for problems (walk-ins, wrong names, payment issues) so the main line keeps moving.

Stage 5: The check-in line itself

The most vivid story we saw was a dinner for a few hundred guests with two volunteers holding printed lists, and a half-hour line in evening wear. That's not a volunteer failure. Printed lists don't scale past a certain number of guests, and that number is lower than people expect.

What people changed afterwards:

• More stations than seemed necessary, split by surname or table number.
• QR codes on confirmation emails, scanned on phones or tablets the team already owns.
• A list that syncs, so two stations can't check in the same guest twice.
• A paper backup anyway, because venue wifi is never as good as promised.

Stage 6: Volunteers and shifts

Behind the door team is a volunteer schedule, and that's often a spreadsheet plus a group chat. Small teams told us the hardest part isn't finding volunteers. It's group sign-ups (a company or a church group bringing several people), knowing who's actually confirmed, and filling gaps when partners can't do weekends.

Fixed shifts with a set number of slots, a captain who can sign up a whole group, and a waitlist when a shift fills all came up as things people wished they'd had from the start.

Stage 7: After the night: payouts, refunds and the report

The last handoff is money. Organisers on hosted ticketing platforms described payouts that arrived later than expected, lump-sum deposits with little detail, and refund requests they couldn't control themselves. For a nonprofit that needs to reconcile every gift for the board and for donors' tax receipts, unclear payouts turn a good night into weeks of admin.

Questions worth asking before you pick any tool:

• Does the money land in our own payment account, or does the platform hold it first?
• Who decides refunds, and how fast can we issue one?
• Can we export a guest list with ticket type, comps, add-ons and check-in status in one file?

Where tools fit

There's no single right stack here. Some teams use a dedicated fundraising platform for the auction and keep simple tickets elsewhere. Others run tickets, RSVPs and check-in on their own website and keep the auction in a specialist tool. Smaller events do fine with a form, a spreadsheet and a disciplined door team.

If you run your site on WordPress, event plugins like The Events Calendar, Events Manager or our own Eventonomy cover tickets, RSVPs and QR check-in on your own site. Disclosure: we build Eventonomy. It doesn't run auctions, so a gala with a big silent auction would still pair it with an auction tool.

The tool matters less than the rule underneath it: one guest list, one owner for comps, and a door plan built for the real headcount.

Your turn

• Where did your last fundraiser actually break: tickets, comps, add-ons, the door or the payout?
• How do you track table captains against their goals without a last-minute spreadsheet merge?
• Do comped seats count toward a captain's goal in your organisation, and how did you decide?
• What's the one change that made your check-in line noticeably shorter?