FooEvents Multi-Day is a clever extension to FooEvents: instead of one ticket per day, each attendee has a single event_magic_tickets post with per-day flags written into wp_postmeta like WooCommerceEventsAttendeeCheckedIn_Day1, _Day2, and so on. The data model is compact, but the default attendee list cannot surface per-day attendance side by side, so a three-day conference becomes three separate admin trips.

SleekView reads the attendee CPT and pivots each per-day check-in flag into a column or, with a per-day expansion view, into its own row. Day 1 status, Day 2 status, Day 3 status, and the cumulative attendance count all promote out of wp_postmeta. The check-in cell for the active day is editable, writing back through the same meta key the FooEvents check-in modal uses internally.

The operational impact is a multi-day conference that runs like a single-day event: open the grid filtered to today's day flag, hand a phone to the door team, and stop maintaining a parallel spreadsheet to track which attendees skipped Day 2.

Multi-day conferences live or die by Day 2 attendance, and the team that runs them needs to see Day 2 in context, not in isolation. FooEvents Multi-Day captures the data correctly: a per-day meta key on each attendee record, one row per ticket, no extra tables needed. The default admin then hides those flags inside the attendee edit screen, which forces organizers to either click through every record or build a parallel spreadsheet to track drop-offs.

Treating each day as a column rebuilds the operational picture in the place the data already lives. Door staff see today's day flag and a single editable cell, sponsors get clean per-day exports for the lounges they paid for, and the post-event analysis stops being a data archeology exercise. The data structure was right; the workflow was missing.