WP Symposium Events extends the WP Symposium community plugin with event RSVPs stored in wp_symposium_events and wp_symposium_events_rsvp. Each RSVP row links a community member's uid to a specific event, with status (Going, Maybe, Not going) and an optional guest count. The default admin gives a per-event RSVP list, but no cross-event view, no member history, and no inline RSVP status edit.

SleekView reads wp_symposium_events_rsvp as the row source, joins wp_symposium_events for event title and date, and joins wp_users for member display name and email. RSVP status, guest count, and the event's date become first-class columns. Inline edits route RSVP status through the same column the plugin reads on the event page, so an organiser who changes a Maybe to a Going in the grid updates the member's public RSVP too.

The result is the cross-event organiser workflow Symposium doesn't ship: filter to upcoming events, group by member to see who keeps RSVPing but skipping, and export the Going list per event for the room layout. Saved views replace the per-event drilldowns that turn community work into busywork.

Community work is repeat work, and Symposium organisers know it: the same forty members RSVP for every monthly meetup, with a long tail of newcomers who try one event and either return or don't. The data to spot those patterns lives in wp_symposium_events_rsvp, but the default admin presents it event by event, which makes patterns invisible. A member who RSVPed Going for three events and showed up to one is the same row, three times over, in three separate admin screens.

Treating RSVPs as a real grid changes that: the regulars are visible at a glance, the persistent maybes are filterable, and the export per event finally produces the Going list the room organiser actually needs. Community managers spend their time on outreach instead of admin clicks, and the next event starts with a real picture of who is coming.