Track attendance on the day

POM Events records registrations, not door attendance. There is no check-in control in the event editor. This page covers the supported ways to run a door list and record who actually came.

What the product gives you

  • Three registration states: Confirmed, Waiting list, Cancelled.
  • A Confirmed count on the events list.
  • Exports to CSV and XLS containing every registration with its status.

The export is the door list. Everything in this page is built on it.

Prepare the door list

The day before the event:

  1. Open the event.
  2. Review the three sections and resolve anything pending — promote waiting-list people, cancel withdrawals.
  3. Read the comments; some of them affect the door.
  4. Select Export to CSV, or Export to XLS if the door team works in a spreadsheet.
  5. Sort the file by name.
  6. Add an empty Attended column.
  7. Print it, or open it on a tablet.

Export after the last changes, not before. The file is a snapshot.

At the door

Tick names on the printed list, or fill the Attended column on the tablet. That record lives in your file, not in WordPress.

Practical notes:

  • Take the file offline. Do not rely on the venue's network.
  • Take the waiting-list section too. If confirmed people do not arrive, you can admit from it.
  • Take the comments with you. Accessibility and dietary notes are needed at the door, not in the office.

After the event

Bring the attendance back into your own records — a spreadsheet, a CRM, an attendance file per event. POM Events has no field for it.

If you need the information visible inside WordPress, two supported options:

  • keep the exported file with the event's own documentation;
  • have a developer add a column to the attendee table through the supported extension point — see Attendee table columns.

Using the statuses as attendance

Some teams reuse the three states after the event: move no-shows to Cancelled so the confirmed list becomes the attended list.

It works, and it has a cost: you lose the distinction between "cancelled in advance" and "did not turn up", which are very different things for planning the next edition.

If you do it, decide it as a policy and write it down, so the lists mean the same thing to everyone.

What the exports contain

The export includes a Confirmed column alongside the registration status, plus the name, email, telephone, comments and country. Read it as the registration record it is, and keep your attendance marks in your own column.

Repeat attendees

Because registrations are tied to user accounts, the same person registering for several events is the same user. Nothing in the interface aggregates their history, but exports from several events can be compared on the email column.

For a season of events, a simple habit pays off: keep every export in one folder, named by event and date.

Verify

  1. Export the list and confirm every confirmed registration is in it.
  2. Confirm the status column distinguishes the three sections.
  3. Confirm comments are readable in the file.
  4. Confirm the file opens on the device the door team will use.
  5. Confirm someone owns the file after the event.