Event Organiser registers event as a custom post type, models venues as the event-venue custom taxonomy, and stores recurring instances as their own posts pointing at a parent. Start and end times, recurrence rules, and venue terms live in the standard WordPress places, which is exactly why power users have been writing custom WP_List_Table extensions for it since the plugin shipped.

SleekView reads the events CPT and the venue taxonomy together. Title, start, end, venue, category, and recurrence rule promote to columns. Each recurring instance appears under its parent through a filter or expansion, with the parent's recurrence rule visible as context. Inline edits to start time and venue write to the same Event Organiser meta keys the plugin uses internally, which means the front-end calendar widget continues to render the updated values without any code changes.

For event teams the result is a planning surface that matches the role: a saved view for the next two weeks of events sorted by start, a venue filter that catches double bookings before they reach a customer, a category group that pulls a clean list for newsletters. Bulk operations cover the messy days — a venue cancels, a series moves online, a category needs a rename — without opening each event in the editor.

Event Organiser has always treated WordPress conventions seriously: events are a custom post type, venues are a taxonomy, recurring instances are real posts that point at a parent. The data model is among the cleanest in the WordPress events space, and that cleanliness is exactly why the default admin can feel so thin. The data is structured perfectly; the surface that exposes it is a posts list with a couple of extra columns.

Organizers, venue staff, and marketers each have a planning rhythm — a horizon, a category, a venue — and the rhythm needs a saved view, an inline edit, and a venue filter that does not feel bolted on. Treating Event Organiser data as a grid completes the workflow without changing the plugin. Saved views become the meetings: the Monday roster, the Friday venue check, the end-of-quarter category cleanup.

The front-end calendar continues to render the same data because every write goes through the same meta keys it already reads. The only thing that changes is how much time the team spends in the editor instead of with attendees.