Attendees

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Records what happened rather than what was planned. Only this module knows the second number.

Distinguishes a no-show from a cancellation with notice, which are different problems with different fixes.

Per-session attendance is what billing-per-attendance and certification both need.

Late is a state, because for some businesses it matters and for others it does not.

How it works

1
A session is recorded and the expected attendees listed against it.
2
Status is set at or after the session, and the distinction between a no-show and a cancellation is preserved.
3
Attendance drives billing where sessions are billed per head.
4
Patterns across sessions surface a cohort with a problem rather than an individual with an excuse.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Attendeerequired	text	Who was expected, matched against Contacts where they exist.
Sessionrequired	text	Which occurrence. Attendance is per session, not per person.
Statusrequired	choice	Attended, No show, Attended late, or Cancelled with notice. Four states because they mean four different things.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Per session, so a course-level attendance rate has to be derived.
No check-in mechanism — somebody marks the register.
Notice periods are recorded in the status text rather than as a duration, so they cannot be summed.
No automatic follow-up on a no-show.

Before it works

What you have to provide, if anything.

Needs the sessions to exist, whether from Events, Bookings or by hand.
Decide whether late counts as attended before the first session, because changing it invalidates the history.

In practice

A training provider billing per session attended.

“Eleven turned up on Tuesday out of fourteen.”

What was said to the agent

What the agent built

Attendance per person: nine present, one late, one cancelled with two hours notice, one no-show.

What changed

Billing stopped being an argument. The no-show rate turned out to be concentrated in one cohort booked through a partner, which changed the partner terms.

Better with

These do a different job on the same data. An agent can have all of them.

GroupsLive

People are organised into standing sets that get addressed, scheduled or billed together.

EventsLive

The business puts on things people attend and needs the next few dates visible on the site without editing a page each time.

InvoicesLive

The agent bills clients or is billed by suppliers, and someone needs to see what is unpaid without opening the accounting tool.

Who uses this page

Event agency

Qualifies briefs, prices the obvious, and keeps every run-of-show and supplier straight.

Conference organiser

Handles attendee questions at scale and keeps the programme, speakers and venue straight.

Questions

What data does the Attendees page use?

It reads person records the agent has collected. People linked to an event (attendee edge). Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.