How Eventene Works
Overview
Eventene helps you plan, run, and repeat structured programs — training cohorts, recurring conferences, member events, volunteer activations, and similar. Instead of treating each event as a one-off, Eventene is built around the idea that most programs happen more than once, involve many people, and benefit from a consistent structure.
This article explains the core building blocks and how they fit together. Once you have these in mind, the rest of the help center will make more sense.
The Core Concepts
Eventene is built around a small set of concepts. Most of what you do in the system is combining them in different ways.
Program
A Program is the thing you are organizing. It is the container for everything else: who is involved, what happens, when, and where.
A Program might be a one-time conference, a recurring monthly meetup, an annual fundraiser, or a season of volunteer events. The Program holds the plan.
Event
An Event is the actual run of a Program. When you publish a Program and people start registering and showing up, you are running an event.
For Programs you repeat, each occurrence is a new event — but you do not rebuild from scratch. You copy the previous Program and shift the dates.
Activity
An Activity is a specific thing that happens inside a Program — a session, a workshop, a meal, or a registration step. A Program is built out of Activities.
Activities are also how you control what participants see. When you assign a group of people to an Activity, only those people see and respond to it.
Participants
Participants are the people involved — registrants, attendees, members, staff, volunteers, speakers, or guests. Participants live in Groups, and Groups are connected to Activities. A participant’s experience is shaped by which Activities apply to them.
Products
If your Program collects payments, you create Products — tickets, fees, meals, or merchandise — that participants select (and pay for, if applicable) during registration. Products are optional; many Programs run entirely free.
For more, see Payments Overview.
These concepts work together: participants register for events, events are made up of activities, and products define what participants may need to pay for.
Example
A training organization might run the same leadership program every quarter. Instead of rebuilding everything each time, they reuse the same structure — activities, pricing, and communication — and only update the schedule and participant list.
The Lifecycle
Most Programs move through four phases. The help center is organized to follow this same flow.
| Phase | What happens | Where in the help center |
|---|---|---|
| Plan | Build the Program: structure, activities, registration flow | Plan Your Program |
| Manage | Invite participants, send communications, assign people | Manage Your Program |
| Run | Execute the event: attendance, walk-ins, day-of communication | During Your Event |
| Track | Monitor responses and follow up afterward | Track & Adjust |
You will spend time in each phase, but they are not strictly sequential. You might return to Plan to add an Activity even after registration has opened.
Why It Works This Way
A few design choices explain why Eventene behaves the way it does.
Repeatable, not one-off
Many event tools assume you run one event and move on. Eventene assumes you are likely to run the same Program again — next month, next quarter, or next year. That is why copying, reusable templates, and consistent structure are central.
Structure beats spreadsheets
Storing people in one tool, schedules in another, and registration in a third makes coordination expensive. Eventene puts Groups, Activities, registration, and tracking in one place so the same person, the same activity, and the same response do not have to be reconciled across systems.
Coordination across teams
Most Programs involve more than one person running them — organizers, communications leads, finance, on-site staff. The same Program can be worked on by all of them, with each person seeing what is relevant to their role.
Where to Go Next
Once you have a feel for the model, useful next steps are:
- See what participants experience — Ways Participants Access Your Event
- Build your first Program — Create a Program
- Understand registration — How Registration Works