Purpose: This article explains Event participation states in Administrate and how to interpret learner participation operationally.
Event participation is tracked through a learner’s Event-level participation record and its current state. These states help administrators understand whether a learner is waiting, confirmed, active, cancelled, or no longer valid for participation.
Participation states affect learner management, communications, capacity, attendance, reporting, and finance workflows.
In this article
Why participation states matter
Participation states are important because they affect:
- who is expected to attend an Event
- who appears in student management workflows
- which communications may be triggered
- how capacity and availability are interpreted
- how bookings are understood in reporting and finance
- whether attendance, results, or achievements should be reviewed
The key idea is that a person’s identity is separate from their participation. Participation is represented operationally through the learner’s Event-level participation record and its current state.
The participation model
The simplified model is:
Contact → Learner → Event participation record → Participation state
This means the Event is the unit of participation, and the participation state tells you where that learner stands in the Event lifecycle.
A learner may exist as a Contact or learner record without being an active participant in a specific Event.
Common participation states
Interested
Interested usually means the learner has expressed interest in the Event but is not yet fully confirmed.
Depending on your operating model, this may function similarly to a waitlist or early-stage registration state.
Use this state when:
- the learner is not yet guaranteed a place
- you are tracking demand before confirmation
- the learner still needs approval, payment, or another step before full participation
Reserved
Reserved usually means the learner has a place provisionally held on the Event, but participation may not yet be fully finalized.
This state is useful when:
- a seat is being held for the learner
- commercial or approval steps are still being completed
- you want visibility into likely attendance before final activation
Active
Active means the learner is fully confirmed as participating in the Event.
This is the main operational state for a confirmed attendee and is typically associated with:
- attendance tracking
- communications
- results and achievements
- capacity consumption
- learner-facing Event participation
Cancelled
Cancelled means the learner was previously participating or expected to participate, but that participation has been withdrawn.
This state preserves historical truth. It shows that the learner was once associated with the Event but is no longer expected to attend.
Cancellation may have downstream implications for:
- communications
- capacity
- linked bookings
- invoices, refunds, or payment corrections
- reporting and participation history
Expired
Expired means the learner’s participation is no longer valid because the opportunity to participate has passed or the required registration conditions were not completed in time.
This state is often used when a participation opportunity lapses before the learner becomes fully active.
Typical state progression
Participation states often represent a learner moving through the operational enrollment lifecycle for an Event.
A common progression is:
Interested → Reserved → Active → Completed or Cancelled
Not all learners move through every state. Some organizations enroll learners directly as Active, while others use reservation, approval, or payment workflows before confirming participation.
Once the Event has been delivered, attendance, results, and achievements become more important than the original enrollment state.
How to read these states operationally
A useful way to interpret the states is:
- Interested = demand or early intent
- Reserved = provisional place held
- Active = confirmed participation
- Cancelled = participation withdrawn after prior association
- Expired = participation no longer valid due to timing or completion conditions
The exact labels and workflow around these states may vary slightly by instance, but the operational meaning should remain consistent.
Participation states vs attendance
Participation states do not mean the same thing as attendance.
For example:
- A learner can be Active without yet being marked attended.
- Attendance is recorded during or after delivery.
- Participation state explains enrollment status, while attendance explains what actually happened during delivery.
This distinction is important because results, completion, and achievements often depend on attendance rather than only on enrollment.
Participation states vs bookings
Participation states are closely related to the learner’s booking, but they are best understood as the Event-facing view of that learner’s operational status.
When a learner’s status changes, review the linked booking and any commercial implications, especially if invoices, payments, credits, or refunds are involved.
Participation state changes may also trigger communications depending on your automation and trigger configuration.
Common uses
- reviewing the current expected roster for an Event
- understanding whether capacity is firm or still provisional
- determining which learners should receive participation-related communications
- reconciling learner operations with booking and finance workflows
- supporting reporting on learner movement through the Event lifecycle
- identifying which learners require attendance or result review
Common misunderstandings
- A Contact is not the same as an active participant. Identity and participation are separate.
- Active does not mean attended. It means confirmed participation.
- Cancelled does not mean deleted. It preserves history.
- Expired does not always mean cancelled. It usually means the participation opportunity lapsed.
- Participation state does not automatically prove completion. Completion usually depends on attendance, results, or achievement rules.
Best practices
- Use participation states consistently across your operational workflow.
- Review Active learners before sending Event communications.
- Confirm attendance separately from participation state.
- Review booking and finance implications before cancelling participation.
- Use transfer workflows instead of manually recreating learner participation.
- Review results and achievements after participation or attendance changes.