Events Made Easy (EME) is one of the few WordPress event plugins that uses its own custom tables instead of bending the post type system. Events sit in wp_eme_events, bookings in wp_eme_bookings, people in wp_eme_people, payments in wp_eme_payments. The schema is clean; the admin built on top of it is functional but per-screen and hard to use across the lifecycle of a single event.

SleekView reads wp_eme_bookings as the row source and joins wp_eme_events for event name and start, and wp_eme_people for attendee name and email. Booking status, seats, total, payment status, and event date all promote into named columns. Inline edits route to the same EME columns the front-end booking page reads, so a status change in the grid is consistent with what attendees see.

The day-to-day workflow becomes a single grid: filter to upcoming events, group by event, sort by booking date. Saved views split door staff, finance, and event manager roles. EME's own front-end flow remains the customer interface; SleekView is the admin operations surface.

Events Made Easy is one of the better-architected event plugins because it owns its data model: wp_eme_events, wp_eme_bookings, wp_eme_people, wp_eme_payments. That choice keeps the schema clean and the queries fast, but it also means the data lives outside the post type system, which is where most WordPress admin tools focus. The result is a plugin with great data and a per-screen admin built on top of it.

Treating those four tables as a joined grid in WordPress admin recovers the operational picture that the schema already supports: one row per booking, with event, attendee, and payment context inline, and inline edits that route through the same columns the customer-facing pages read. The plugin's data choices were the right ones; the admin layer just needed to catch up.