Nonprofit Event Website on WordPress: Run It All Year Round

A nonprofit event website on WordPress is the site that takes registrations for your events and keeps your people together in the weeks between them. Eventonomy handles the events, and the free plugin covers free RSVPs, capacity, waitlists and reminders. A member space, a forum and a partner directory are separate plugins you add as the group grows, and each one is optional.

Most nonprofit sites are built around event day. The sign-up form goes up two weeks before, everyone arrives, and then the page sits there until next year. This post follows the other approach: a site that stays useful all year. It walks through one year in the order you’d likely meet it, and it says clearly where the pieces connect and where they don’t.

Key points

• Free events, volunteer sign-ups, reminders and waitlists are in the free Eventonomy plugin.
• Paid tickets and door check-in are Pro. We take no share of what you raise.
• Eventonomy connects to the BuddyNext community through BuddyNext Pro. It has no data link to Jetonomy or Listora.
• It doesn’t issue donation receipts or assign volunteer shifts.

January: one site, one login

Start small. Install Eventonomy, and activation creates a Manage Events page, so a volunteer coordinator can work without ever opening wp-admin. That alone changes who can run your events. The person who organises the cleanup day doesn’t need to be the person who looks after the website.

Save your usual meeting places as venues, with the directions written in the description. Then pick one setting early, because it shapes everything after: the account policy. It’s a single choice called “Do attendees need an account?” You can create an account for each new email automatically, which is the default, take sign-ups as guests, or require a login. Test the one you pick as a logged-out visitor before anyone else sees it.

Guests who register without an account aren’t locked out. They change or cancel through a secure link in their confirmation email, valid for seven days by default. That link is why a guest sign-up works for the person who’ll never log in to anything.

March: the first volunteer day

Say you’re running a Saturday cleanup with forty people and a few set roles. This part is all in the free plugin.

Create the event and set the capacity to the number of people you can supervise. Turn on custom questions under Settings, Registration, where they ship switched off, and add a role dropdown, a t-shirt size and a phone number. Each question can be required or optional, and there are ten answer types to choose from.

Be careful what you ask. Dietary needs and shirt sizes are fine, and easy to explain on a form. Medical details, immigration status or anything about children don’t belong on a general RSVP form. Eventonomy has no background check or safeguarding workflow, so those stay in whatever process your organisation already uses.

When it fills, a waitlist takes over. On a free event, the next person on the list is promoted automatically when someone drops out. Our post on event waitlists explains how that differs on paid events.

Reminders go out a day and an hour before, with no setup. People forget Saturday mornings, so that matters more than it sounds.

For the longer walkthrough of running shifts, see volunteer shift sign-ups.

What it won’t do

Don’t promise your coordinator a rota. Eventonomy collects sign-ups, role answers and per-role counts, and you plan the schedule from the exported list. It doesn’t assign shifts, and it doesn’t track volunteer hours over time.

June: a monthly event with a crew list

Many nonprofits run something on repeat, such as a monthly meal. The free plugin repeats events daily, weekly or monthly, and you can cancel a single date and restore it later. Pro adds yearly repeats and patterns like the second Saturday of the month.

There’s one limit to plan around. A sign-up belongs to the event, not to one date, so a single RSVP covers the whole series and the capacity applies across all of it. That’s fine for a congregation that turns up every Sunday. It’s wrong for a food drive where each month needs its own crew.

For that, make each date its own event. Duplicating an event is built in, and each copy gets its own capacity, waitlist and attendee list. The recurring events post has the detail.

October: the gala

A first fundraising dinner is where Pro comes in. Taking money needs it. Paid tickets check out through Stripe, PayPal or WooCommerce, using whichever gateways you switch on. We take no commission, so what you pay is the gateway’s own fee, your hosting and the yearly licence.

Two ticket types are enough for a first dinner, a standard seat and a patron seat at a higher price. You can add a donation ticket for supporters who’d rather give an amount of their choice. In the free plugin, a donation ticket records a pledge and charges nothing. In Pro, with a gateway connected, the same ticket takes the payment.

On the night, check-in is also Pro. Each confirmed guest gets a QR code in their confirmation email. A signed-in organiser scans it with the phone’s camera app, which opens a check-in link and records the guest. A USB scanner works, and so does searching by name.

Plan your door around one rule: check-in works for the event’s owner or an administrator. Your door volunteers can’t check guests in from an ordinary member account.

What the gala still needs from elsewhere:

• A seating chart. There’s none, so keep tables in a spreadsheet and use the exported guest list.
• Donation receipts. Eventonomy doesn’t issue tax-deductible receipts or annual statements, so your accounting system does that.
• Badge printing.
• A volunteer rota.

November: keeping people between events

Here’s where most nonprofit sites stop, and where the rest of the stack starts.

Imagine it’s the month after the gala. The people who came are still interested, and nothing on your site gives them a reason to return. This is the job of a community layer, and it’s a separate plugin from Eventonomy.

A member space with BuddyNext

BuddyNext gives you member profiles, an activity feed and notifications. The link to Eventonomy lives in BuddyNext Pro, not in Eventonomy, so it’s BuddyNext Pro you need. Here’s what the bridge does, according to its code:

• A published event becomes a card in the community feed and is added to community search.
• When a member says they’re going, a card shows that they’re attending, and it’s removed if they cancel.
• An Events hub appears in the navigation, and a member’s profile has an Events tab.
• Eventonomy’s own pages stay as they are. The community links out to them.

The bridge doesn’t send email. Eventonomy owns the reminders and confirmations, and the community never sends a second copy. One more point worth knowing: you don’t need Eventonomy Pro for any of this. The bridge works with the free plugin.

A forum for between-event talk

Volunteers ask the same questions every time. Where do we park? Who’s bringing the tables? A forum answers them once, in public, and keeps the answer. Jetonomy is our forum plugin, and we wrote about starting a forum you fully own separately.

Be straight about the connection. Jetonomy and Eventonomy share your site and your login, and that’s all. There’s no code that links them. What does connect is Jetonomy and BuddyNext, so with all three active, a forum discussion can appear in the community feed. Eventonomy events appear there too, through BuddyNext Pro.

A directory of partners

A nonprofit usually relies on other organisations: venues, sponsors, caterers and local businesses that donate. Listora is our directory plugin, and it suits a partner directory. Each partner gets a listing with a map pin, and a business owner can claim a listing you created for them.

The same honesty applies. Listora and Eventonomy run side by side and share nothing. A partner listing won’t automatically appear on an event page. If you want a venue linked to an event, you do it by hand in the event description.

The message the day before

Sooner or later you need to tell everyone who registered something. The hall is closed, the weather turned, the car park moved. The attendee panel lets an organiser email everyone registered for one event, and it’s the quickest way to reach forty volunteers without opening anyone’s address book.

It has limits worth knowing. An organiser can send five of these per event in an hour, the subject is capped at 200 characters and the message at 5,000, and people who have opted out of emails are skipped. Only someone with permission to manage that event’s registrations can send one. That rules out most of your volunteers, which is what you want.

Write it like a person. A subject that says what changed (“Saturday’s cleanup moves to the north gate”) gets opened. One that says “Important update” gets ignored by anyone who’s had a lot of those.

Letting supporters take the dates with them

People rarely check a website for the next date. They check their calendar. Eventonomy publishes a calendar feed and an add-to-calendar option in the free plugin, so a supporter can subscribe once and see your dates alongside everything else in their week.

Cancelled dates drop out of the feed when a subscribed calendar next refreshes, though the refresh timing is up to each calendar app, so don’t promise instant updates. A date can be cancelled but not moved, so if the cleanup shifts to Sunday, cancel Saturday’s date and create a new event for Sunday.

Privacy, because you’re holding people’s details

Registrations live in your own database, and nobody else holds a copy. Organisers can export their own events, and the site owner can export everything. If someone asks what you hold on them, the WordPress personal data export returns their RSVPs and orders by email address. Erasing anonymises their RSVP and keeps the seat count correct, though paid order records are kept.

You can also email everyone registered for one event from the attendee panel, which is how you send a last-minute weather update.

What a year looks like, as a plan

1. January: install, set the account policy, add venues.
2. March: run the first volunteer day on the free plugin.
3. June: set up the monthly event, with a separate event for each crew.
4. October: add Pro for the gala, with check-in at the door.
5. November: add the member space, then a forum if people want one.
6. Next year: a partner directory, once you have partners to list.

Add each piece when someone asks for it. A site with five plugins and no members is worse than one plugin and a good event.

When a hosted tool is the better call

If you run one fundraiser a year and nobody on your team can look after plugin updates, a hosted fundraising platform takes that job away. Some groups use one for the yearly gala and Eventonomy for everything else. Our nonprofit page compares the two honestly.

Questions people ask

Is Eventonomy free for a nonprofit? The free plugin handles free events, RSVPs, volunteer sign-ups, waitlists and reminders. Paid tickets and check-in are Pro, and the free vs Pro page lists the rest.

Can volunteers sign up without an account? Yes. Set the account policy to guest sign-ups, and people change their answer through a link in their email.

Do I need BuddyNext? No. Events work on their own. Add BuddyNext Pro when you want events in a community feed and on member profiles.

Does it work with the other plugins automatically? Only BuddyNext Pro connects to it. Jetonomy and Listora share the site and the login, nothing more.

Does it issue donation receipts? No. Use your accounting system for those, and check what your country requires.