BirchPress Pro uses a mix of custom tables (wp_birchschedule_appointment, wp_birchschedule_service, wp_birchschedule_provider, wp_birchschedule_location) and standard WordPress posts/postmeta for some objects. Each addon (online payments, two-way Google Calendar, custom forms) widens the schema further.

The default admin presents each through fixed-column screens. Ops staff confirming tomorrow's appointments, finance reconciling online-payment charges, and providers managing their own schedule all swap between admin tabs because each piece of context lives on a separate page.

SleekView reads the BirchPress custom tables directly, joins on provider, location, and service IDs, and exposes calendar-sync status as a column. Status edits route through BirchPress's API so notification and Google Calendar sync logic fires. Saved views give each role the slice they need.

BirchPress Pro splits providers, locations, services, and appointments into custom tables for good reason: each is its own well-defined object. That same separation forces ops staff into multiple admin tabs to keep the day moving. Providers want to see only their own schedule, location managers want their site, finance wants the online-payments audit, and ops wants tomorrow's pending list confirmed before anyone calls.

SleekView reads the same wp_birchschedule_* tables BirchPress already maintains and joins them into a single editable grid. Status edits write through the BirchPress API so Google Calendar sync, notification emails, and payment-addon hooks continue to fire. Each role's view is a saved filter on the same underlying data, so adding a new provider or a new location doesn't add a new tab to navigate.

The default admin still works fine for one-off creation and configuration, but the operational rhythm runs much faster on a workspace that already knows how the BirchPress schema fits together.