The Events Calendar already tracks every RSVP and ticket as a row. RSVP responses land as tribe_rsvp_attendees posts with _tribe_rsvp_status set to yes or no, ticket attendees from Event Tickets sit in tribe_tpp_attendees with an order status, and check-in writes _tribe_qr_status and _tribe_qr_ticket_checkedin against the same row. The default Attendees screen lists those records as a long table sorted by purchase date, with the status visible only as a small label per row.

SleekView Kanban reads the same attendee posts and groups them into columns by status. The natural grouping field is the combined RSVP and check-in state, so the board shows Going, Not going, Checked in, and Refunded as separate stacks. Each card shows the attendee name, the event title, the ticket type, and the order total when one exists, so the front of the card carries the data the door staff and the organiser actually need.

Dragging a card writes the new status back to the source row. Moving a Going card into Checked in updates the check-in meta and stamps the time, moving a card into Refunded triggers the refund flow on the linked WooCommerce order when Event Tickets Plus is active, and moving an RSVP between Going and Not going flips _tribe_rsvp_status. SleekView keeps an audit log per card so changes made on the board are traceable back to the user who made them.

An event has stages and people move through them. RSVPs come in, then convert to ticket purchases when the event sells tickets, then get scanned at the door, then sometimes turn into refunds when the event is postponed. The Events Calendar stores all of that already, just spread across two attendee post types, a few meta keys, and the linked WooCommerce order when Event Tickets Plus is active.

The default reading surface is still a long table sorted by purchase date, so seeing how many Going RSVPs are still unscanned an hour into the event takes a filter, a sort, and a count in your head. SleekView Kanban turns that same data into a board with Going, Checked in, Not going, and Refunded as columns, a count per column at the top, and a card per attendee with the fields door staff and the organiser actually need. Drag a card to flip the status and the meta updates on the row.

The Attendees screen, the check-in report, and the order in WooCommerce all read the new value because SleekView writes to the source row, not to a parallel table.