Modern Events Calendar writes every booking as a post. Each row lives in mec-books with a post_status of publish, pending, or trash, plus meta keys like mec_verified, mec_confirmed, and mec_attendance that track verification and check-in. The default Bookings screen shows those rows as a table with the status as a column label, sorted by date, and verification spread across a separate confirmation screen.

SleekView Kanban reads the same mec-books posts and groups them by the combined booking state. The natural grouping is the lifecycle the plugin already encodes, so the board shows Pending, Confirmed, Attended, and Cancelled as separate columns. Each card carries the attendee name, the event title, the ticket variation, and the booking total from the linked WooCommerce order when MEC is wired to Woo, so the front of the card holds everything the organiser needs to move it forward.

Dragging a card writes back to the source row. Moving a card from Pending to Confirmed flips mec_confirmed to 1 and sends the confirmation email through the plugin hook, moving a card to Attended writes the attendance meta and the timestamp, and moving a card to Cancelled trashes the booking post and reverses the linked Woo order when one exists. Booking codes that need verification show a small flag so the organiser handles them before approval rather than after.

MEC already encodes a booking lifecycle: a row arrives in mec-books as pending, an organiser or the payment gateway flips mec_confirmed to one, the door scan writes mec_attendance, and a cancellation either trashes the row or reverses the linked WooCommerce order. The default Bookings screen still reads that lifecycle as a table sorted by date with the status as a column label and verification on a separate screen, so an organiser handling fifty pending bookings spends most of the time switching tabs. SleekView Kanban reads the same mec-books posts and lays them out as Pending, Confirmed, Attended, and Cancelled with a count at the top of each column and a card per booking.

Approving a batch means dragging cards in groups, not opening rows one at a time. The verification flag on the card is visible before the move, so the organiser does the checks once, before the booking turns confirmed and the email goes out. Cancellations move on the board and the linked Woo order updates through the same hook the orders screen would use, so the numbers in the plugin reports and the numbers on the board stay identical without manual reconciliation.