Modern Events Calendar (MEC) registers events as a custom post type and attaches bookings, payments, and attendees through related records and rich post meta. The default admin handles the editing well but the bookings list — the one organizers actually live in — runs on fixed columns and limited filters, leaving cross-event lookups awkward and bulk operations cumbersome.

SleekView reads the MEC events CPT and the linked booking records into a single grid. Booking ID, attendee name, event, ticket type, amount, and status sit side by side. Custom event meta — capacity, location, organizer fields, recurrence pattern — promote to columns on demand. Inline edits write through the same meta keys MEC uses, so payment status changes, capacity updates, and bookings cancellations stay in sync with the front-end calendar.

The grid is built around the rituals event teams already run: confirm bookings, reconcile payments, watch capacity during a registration push, prepare check-in lists. Saved views replace the per-question filter rebuilding, and a CSV export of the active view hands finance or front-desk the exact column set they need.

Event operations is a tempo problem. A registration period opens and the team needs to know capacity per event by the end of each day; the day of the event arrives and front desk needs an attendee list grouped by ticket type with check-in status; refunds happen and finance needs a clean reconciliation against the gateway. MEC captures all of that data — events, bookings, attendees, payments, custom fields — but the default bookings list works against the workflow because it is paginated, fixed-column, and unaware of the event context that turns a booking row into a useful piece of operational information.

The cost is not technical but procedural: organizers fall back on spreadsheets that are stale within a day, finance reconciles in a separate tool, and last-minute changes propagate slowly because each one requires opening a record. Treating MEC data as a real grid keeps the team in wp-admin where the calendar templates and ticketing rules already live. Saved views become the rituals of the role, and inline edits cut the cycle time on a status change from minutes to seconds.