Administrate separates identity from participation. A person may exist in the system for years, but participation in training happens only when that person is booked onto a specific event or learning experience.
This article explains how Administrate models participation through bookings, attendance records, and outcomes such as achievements.
The participation model
The participation model connects identity, delivery, and outcomes.
The simplified relationship looks like this:
Contact → Learner → Booking → Event → Attendance → Achievement
In practical terms:
- A Contact represents the person over time.
- A Learner represents that person in a training context.
- A Booking represents that learner participating in a specific event.
- The Event is where delivery occurs.
- Attendance and progress record what actually happened.
- Achievements represent completion outcomes.
The important idea is that participation lives at the event level. A course template defines training design, but learners participate in events.
What a booking represents
A booking is the record of a learner’s participation in a specific event.
The booking connects several important parts of the system:
- the learner
- the event
- attendance records
- achievements
- communications
- financial transactions such as invoices
Because of this, the booking becomes the operational anchor for participation.
A person may attend many events over time. Each event participation is represented by its own booking record.
Booking lifecycle
Bookings move through a lifecycle as participation progresses.
Interested
The learner has expressed interest but is not yet confirmed on the event. This may function as a waitlist or early registration state depending on your operating model.
Reserved
The learner has been reserved for the event but the booking may not yet be fully confirmed or financially finalized.
Active
The learner is fully confirmed and participating in the event.
Cancelled
The learner was previously booked but the participation has been cancelled. This state preserves historical truth while removing the learner from the active roster.
Expired
The booking is no longer valid because the opportunity for participation has passed or the booking was not confirmed within required conditions.
How learners are added to events
Learners are typically added to events through one of several methods.
- manual enrollment by an administrator
- registration through a portal
- conversion from a booking workflow or opportunity
- automated enrollment based on program rules
Regardless of the entry method, the result is the same: a booking record connecting the learner to the event.
Attendance and participation tracking
Once an event is underway, attendance records describe the learner’s actual participation.
Attendance may include:
- present or absent status
- participation across multiple sessions
- completion milestones
- instructor evaluation or grading
Attendance information is important because many downstream outcomes depend on it.
Achievements and completion
Achievements represent successful completion of training requirements.
They are often awarded based on:
- attendance
- assessments
- instructor evaluation
- automated completion logic
When an achievement is awarded, it becomes part of the learner’s permanent training history.
Achievements may also trigger certificates or other completion artifacts.
Where learning paths fit
Learning Paths coordinate broader progression across multiple training requirements.
They typically aggregate outcomes such as achievements from multiple events or courses.
This means the hierarchy looks like this:
Event participation → Achievement → Learning Path progress
Learning paths organize training journeys, but events remain the delivery unit and bookings remain the participation record.
Why this model matters
- participation is tracked accurately at the event level
- historical records remain trustworthy
- attendance and outcomes reflect real delivery conditions
- reporting can distinguish design from execution
Without separating identity, participation, and delivery, it becomes difficult to track training outcomes accurately across time.
Common misunderstandings
- A contact is not the same as a participant.
- A course template does not contain participation records.
- Attendance belongs to the event, not the template.
- Achievements represent outcomes, not enrollment.