Event Organiser registers events as the event post type with dates and venues stored in eo_events. Bookings from Event Organiser Pro live in eo_bookings with a status column, and post-event ratings often arrive as comments on the event post or as custom rows when the organiser bolted on a survey shortcode. The default reading surfaces are the bookings table, the comments thread on each event, and the survey CSV, three places to read three slices of the same conversation.

SleekView Feedback collapses those into one board. It reads the event comments joined to their event post, the booking rows from eo_bookings when the organiser asked for a rating at the booking step, and any survey custom post the team is already using. Each row becomes a card with a title, a running vote count, the author, a category pill for the topic, and a status pill bound to the organiser field. The card font carries the event name so cards from different events sit on the same board without losing context.

Upvote writes back to a counter meta on the row. A new topic request submitted from the board lands as a comment on the relevant event post with the category preset, and the board re-sorts so the most-asked topic always sits at the top. Programme teams read the board the same way attendees do, and the export drops the top cards into the next planning round.

A good conference programme listens to the audience between the closing keynote and the call for speakers. Event Organiser captures the raw signal already, partly as comments on each event post and partly as booking notes when the organiser asked for a topic at the booking step. The problem is not missing data, it is missing alignment, because the programme team reads the comments thread on one screen, the booking notes on another, and the survey CSV on a third.

SleekView Feedback turns those three sources into one board with upvotes, categories, and statuses, so attendees rank the requests in public and the programme team reads them in the same order. A speaker who got rave reviews has a Shipped pill within minutes of being rebooked, a logistics issue gets an Open pill until someone fixes it, and a topic that the audience keeps asking for climbs to the top whether it landed as a comment, a booking note, or a fresh submission from the board itself. The next year is planned out loud rather than in a planning meeting reading old emails.