What is an Event?

An Event is the top-level thing you create in Eventene. It has a date, a location (physical or virtual), a list of participants, and one or more Activities that happen during it.

Most of what you do in Eventene happens inside an Event:

You build it (add Activities, configure registration, write content)
You publish it (make it visible to participants)
You run it (people register, attend, check in)
You track it (review attendance, responses, payments)

Event vs Program

You will see the word Program used throughout the Help Center alongside Event. They point to closely related things:

An Event is a single dated occurrence — for example, your March 2026 training session
A Program is the structure you build for that Event — the Activities, settings, communications, and registration setup

If you run the same kind of Event repeatedly (a monthly meetup, an annual conference, a quarterly training), you build the Program once and reuse it across many Events. The Help Center generally uses Program when describing setup and planning, and Event when describing the live, dated occurrence.

For everyday purposes, both words refer to the same thing in the app.

What an Event contains

An Event includes:

Activities — sessions, workshops, or registration steps that happen inside it (What is an Activity?)
Questions — what participants are asked during registration
Settings — how attendance is determined, who can see what, when responses are accepted
Products (optional) — items participants can pay for during registration

It also references one or more Groups — the persistent collections of people who participate. Groups are not contained inside an Event; they live independently and can be referenced by many Events over time. See What is a Group?.

Why Events and Groups are separate

A foundational design choice in Eventene is that Events reference Groups; Groups do not belong to Events.

This is different from many event-management tools, where attendees are uploaded into a specific event and the attendee list dies with the event. In Eventene:

A Main Group is a persistent, reusable collection of people
An Event references the Groups (or Subgroups) it needs
The same Group can be referenced by many Events over time
People accumulate history, payments, tags, and identity across Events — not just within one

This separation is what makes recurring programs, member management, and longitudinal participation tracking practical. It is the architectural reason Eventene supports ongoing program coordination, not just one-off events.

Event lifecycle

Events move through several phases:

Phase	What happens
Pending	You are building or scheduling; participants do not yet see it
Active	Published; registration may be open
Completed	The Event date has passed
Archived	Locked, but still viewable for reporting

You can change most settings up to (and during) the Active phase. Some settings lock once the Event completes.

A note on terminology

The platform's URL is app.eventene.com because the original primitive in the product was the Event. The "Program" framing is a more recent way to describe the broader, reusable structure — especially useful when you run the same kind of Event repeatedly.