The Events Calendar Pro builds on the core schema: tribe_events for events, tribe_venue for venues, tribe_organizer for organizers, plus Pro-only types like tribe_event_series and the Custom Tables migration that introduces tec_occurrences for recurrence indexing. Meta keys like _EventStartDate, _EventEndDate, _EventVenueID, and _EventOrganizerID link the records together.

SleekView reads tribe_events and joins venue, organizer, and series fields onto each event row through the linked post IDs. When the Custom Tables migration is active, the recurrence-aware tec_occurrences table joins back so each occurrence appears as its own filterable row. Additional Fields (Pro's custom fields) promote to columns automatically once detected.

Inline edits write to the same _Event* meta keys Pro reads internally and use Pro's CRUD layer for series-level changes. A rescheduled occurrence updates the front-end calendar, an Additional Field change reflects on the public template, and a series-level reschedule cascades through the plugin's own recurrence handling. The grid never tries to outsmart the Pro pipeline; it joins it.

The Events Calendar Pro layers serious capability onto the core plugin: recurrence, series, additional fields, custom tables. Each of those features improves the public-side experience and adds a new admin screen that the planning team has to remember exists. A coordinator running a season of workshops with three series, six venues, and four organizers is now toggling between five Pro screens to answer one question.

The data is already there in tribe_events, tribe_event_series, tribe_venue, and the optional tec_occurrences table; it just is not joined on one screen. Treating those records as a real grid that joins on the keys Pro already maintains turns the admin into a planning surface. Saved views capture the rituals of the role, additional fields become real columns and filters, and inline edits route through the same meta keys and CRUD layer Pro uses internally.

The Pro features feel like one product again, not five tabs that happen to share a parent calendar.