Event setup

Manage event attendees and check-in

Use the event attendee list to review registrations, selected times, notes, ticket quantities, check-in state, and day-of event attendance.

Updated 2026-07-02

The attendee list is the day-of workspace for a CoverCount Event. It shows who registered, how many tickets they reserved, which time they selected, any guest notes, and whether the registration has checked in.

Use the attendee list for event arrivals. Do not look for event attendees on the reservation floor unless you also created a separate reservation for operational seating.

Open The Correct Event Time

For events with more than one time, each time has its own attendee list, capacity, and check-in state. Confirm you are viewing the correct time before check-in begins.

Check:

  • Event name
  • Event date
  • Start time
  • Ticket capacity
  • Tickets sold
  • Registration count

This matters when the same event has an 11:00 a.m. group and a 2:00 p.m. group, or when the event spans multiple days.

Review The Attendee List

Before doors open, review:

  • Guest names
  • Ticket quantities
  • Phone numbers
  • Email addresses
  • Guest notes
  • Payment or registration status
  • Check-in state

Use notes to spot dietary restrictions, accessibility requests, club-member context, seating needs, or arrival details that should be shared with staff.

Check In Guests

When a guest arrives:

  1. Find the registration by guest name, email, phone, or registration details.
  2. Confirm the ticket quantity.
  3. Confirm the guest is at the correct event time.
  4. Mark the registration checked in.

If one registration covers multiple people, check in the registration when the group arrives according to your venue's process.

Use QR Codes Or Confirmation Emails

Guests may bring their confirmation email or manage-registration link. If your team uses QR scanning, make sure the scan opens the correct registration before marking the guest checked in.

For door scanning, install CoverCount Check-In from the App Store on the staff iPhone used at the event.

Even with QR codes, staff should still verify obvious mismatches:

  • Wrong event
  • Wrong time
  • Cancelled registration
  • Duplicate screenshot
  • Guest trying to use a registration that has already checked in

Handle Wrong-Time Arrivals

If a guest arrives for the wrong time, do not silently move the registration. A registration has a ticket code, confirmation email, capacity count, payment state, and check-in state tied to the selected time.

For now, use the venue's policy:

  • If the correct time still has room, cancel or refund/no-refund the original registration and have the guest re-register for the right time.
  • If the guest can be admitted anyway, make the decision operationally and keep the original registration tied to its purchased time.
  • If the desired time is sold out, explain that capacity is managed per time and the sold-out time cannot accept more tickets through normal registration.

Moving a registration between times is planned for a future workflow, but it needs ticket-code and confirmation-email handling before it should be used live.

Undo Check-In Carefully

Only undo check-in when staff made a mistake.

Examples:

  • Staff checked in the wrong guest.
  • Staff checked in a duplicate registration.
  • The guest left before entry was finalized.

Avoid toggling check-in repeatedly as a note-taking tool. Use notes or staff communication for anything that is not attendance state.

Handle Walk-Ups Consistently

If the venue accepts walk-up event registrations, use the staff event workflow instead of adding guests to the reservation floor. Walk-up tickets should still count against event capacity and appear in the attendee list.

For paid walk-ups, confirm the venue's payment process before letting the guest enter.

After The Event

After the event, review:

  • Tickets sold
  • Tickets checked in
  • No-shows
  • Refunds or cancellations
  • Guest notes worth following up on
  • Any payment or refund issues

This gives the team a clean record for reporting and for planning the next event.

For launch testing, see Test an Event before publishing.