Event Tickets layers on top of The Events Calendar by writing attendees and tickets as posts linked to each event, with order records bridged into WooCommerce when paid tickets are involved. The default attendee list is per-event — a sensible default until the day of a multi-event run when door staff need to find an attendee without knowing which event they bought into.

SleekView reads the attendee CPT and the linked event, ticket type, and order ID into a single cross-event grid. Custom registration fields — meal preference, t-shirt size, accessibility note — promote from attendee meta into named columns. The check-in cell is editable, so staff can mark attendance from a phone or tablet and the timestamp is recorded against the same meta key the plugin uses internally.

The practical impact is the door workflow that Event Tickets does not ship: a phone-friendly grid filtered to today's events, with a one-tap check-in column and a search by name or email. Saved views split the work between door staff, accounting, and customer support so each role sees the columns they need without learning the attendee CPT structure.

On the day of an event the data quality of the attendee list determines whether the line moves or stalls. Event Tickets captures attendee data well — the per-event list, the order link, the registration fields — but its admin design assumes the operator knows which event they are working in. That assumption breaks the moment a venue runs back-to-back events, a conference splits into tracks, or a buyer holds tickets across multiple events.

Door staff need to find Marcus Lee without first knowing whether he is going to the Annual Conference or the Summer Workshop. Customer support needs to see every ticket attached to one email when a buyer writes in. Finance needs paid versus refunded across events for the weekly reconciliation.

Treating attendees as a real cross-event grid solves all three at once: a single grid with the right columns, role-based saved views, and an editable check-in cell that works on the phone the staff member is already holding. The data is the same; the workflow finally matches the role.