Five Star Restaurant Reservations stores every booking as the rtb-booking custom post type. Date, time, party size, table assignment, location, and Pro custom fields (allergies, occasion, dietary requirements) live in postmeta on each record, and Ultimate adds deposit data in the same way. The default admin shows a per-day list, useful for confirming today and clumsy for everything else.

SleekView Charts treats rtb-booking as the base of a dataset and pivots the postmeta into proper columns. Number cards count tonight's pending bookings. Donut cards split party size or location share. Bar cards rank table utilisation across a service window. Area cards plot daily covers over the active range, with service-window filters built into the date dimension.

Inline edits from the linked table view route through wp_update_post(), so Five Star's confirmation emails fire and table-availability logic stays consistent. The chart layer adds the dashboard half a busy restaurant runs by, beside the per-day admin Five Star already ships.

Restaurants think in services, not single days. Lunch is one operational unit, dinner is another, weekend brunch is a third, and each one has its own rhythm of pending bookings, party-size distribution, and table utilisation. Five Star's per-day admin works for a single-shift venue and feels clumsy when a restaurant runs three services or operates across several locations.

The data is rich enough already: rtb-booking stores everything an operator needs in postmeta, including Pro custom fields and Ultimate deposit data. The missing piece is a configurable chart layer that turns the booking corpus into a service-night dashboard. SleekView Charts adds that layer.

The host runs tonight's dinner from a saved dashboard, the owner reviews weekly covers from another, and the multi-location operator pins one dashboard per branch plus a chain rollup. Same rtb-booking dataset, different filter and chart configuration per role.