Events Calendar Pro registers events as tribe_events with recurring children, custom fields on each event, and RSVP rows in tribe_rsvp_attendees. Comments on the event page hold post-event opinions, the RSVP form often includes a topic question the team turns into a feedback prompt, and additional custom fields on the event sometimes carry post-session ratings. The default reading surface is the comments thread, the Attendees screen, and a custom field report.

SleekView Feedback brings those three sources onto a single board. It reads wp_comments joined to the event post, the answers from RSVP notes, and any post-session rating in a custom field. Each row renders as a card with a title, the running vote count from a counter meta, the author, a category pill for the topic, and a status pill bound to the organiser response field. The card front carries the event name, the series name when the event is recurring, and the RSVP status so a Going note reads differently from a Not going one.

Upvote writes the increment back to comment or RSVP meta. Submit lands a new topic request as a comment on the closest upcoming event with the category preset. The board export writes the top cards to CSV with category, status, series, and event so the next planning round reads off the same signal the audience just voted on.

A recurring meetup or a multi-track conference produces feedback every time it runs, and the patterns matter as much as any single response. Events Calendar Pro stores recurring children as their own posts with their own comments, RSVPs, and custom fields, which means the default reading workflow is one screen per occurrence and a planning meeting that tries to remember which request came up in which month. SleekView Feedback turns the whole series into one board with upvotes, categories, and statuses, and the card carries the series name so cards from January and June sit on the same page without losing their context.

A topic that climbs over six months gets a Planned pill and shows up on the next call for speakers. A bug that hit the Map view in one occurrence gets an Open pill until the team fixes it. The chapter stops doing per-meeting retros and starts reading a rolling board that the audience sorts in public.