All Collections
Events
Events
How enrollment statuses are reported
How enrollment statuses are reported

Learn how enrollment statuses are reported in dashboards, analytics, CVS exports, and so on.

Chris Ramlow avatar
Written by Chris Ramlow
Updated over a week ago

Scenario

As an admin or an event organizer, you want to understand how enrollment statuses are reported and what they mean.

Solution

Possible enrollment attendance statuses:

  • Cancelled - if the corresponding event has been cancelled

  • Checked-in - if not cancelled and the enrollment has been checked-in, regardless of who, when, or how checked in

  • No-show - if neither cancelled nor checked-in, the corresponding event is past its Self check-in closes cutoff, and the enrollee was registered as attending, regardless of their attendance method

  • Enrolled - if neither cancelled nor checked-in, the corresponding event is not past its Self check-in closes cutoff, and the enrollee was registered as attending, regardless of their attendance method

  • Waitlisted - if neither cancelled nor checked-in, and the enrollee was registered as wait-listed, regardless of their attendance method

  • Dropped - if neither cancelled nor checked-in, and the enrollment was explicitly dropped, regardless of their indicated attendance method

Furthermore, an enrollment attendance method is said to be:

  • In Person - if the enrollee was registered to attend in-person, regardless of their attendance status

  • Online - if the enrollee was registered to attend online, regardless of their attendance status

  • Unknown - if the person dropped their enrollment (this is a current limitation of the platform)

Go deeper

Uses

The enrollment attendance statuses and methods show up in several places:

  • Enrollment dashboard and reports

  • Enrollment exports

  • GraphQL API (as attendance_status and attendance_method filters/attributes)

Settings

Self check-in closes cutoff is a cascaded setting, which can be managed at different levels of the platform:

  • System (global policy)

  • Event type (all events of that type)

  • Event (just that event)

If this setting is disabled, then the corresponding enrollments are never considered No-show, even long past their events take place.

See also

Did this answer your question?