Restaurant Reservations Pro stores every booking as a nd_booking custom post with a post_status like nd_pending, nd_confirmed, nd_arrived, nd_cancelled, or nd_closed. The default Bookings screen lists those posts in a long table sorted by reservation time with the status as a small column per row, which is fine for a quiet shift and fails on Friday night when every table is turning.

SleekView Kanban reads the same nd_booking posts and treats post_status as the natural axis to group by. Each card surfaces the guest name, the party size, the requested time, the table assignment, and the deposit status. Columns mirror your real Restaurant Reservations Pro statuses, so the pending stack and the arrived stack each read as a single number rather than as labels scattered across rows.

Drag a card from Confirmed to Arrived when the guest walks in and SleekView calls the same Restaurant Reservations Pro update path the admin uses, which marks the table as occupied and stops the public booking form from offering the same time. Drag to Cancelled to release the slot and trigger the configured email. Per-shift boards keep the floor manager focused on tonight's service.

A restaurant floor is a real-time system: confirmations come in, parties arrive, tables turn, no-shows free up seats for walk-ins. Restaurant Reservations Pro captures all of that already in nd_booking posts, but the default admin lists reservations in time order with status as a small label, which is the wrong axis for the question hosts actually ask, which is who is seated right now and which tables are about to turn. The board view fixes this by making the only state that matters, the reservation status, the primary axis of the screen.

You can see at a glance how many tables are confirmed for the next slot, how many parties have arrived, and how many cancellations have just released tables back to the pool. Cards make individual bookings legible at the level of guest, party size, time, table, and any allergy or anniversary note. Drag is the natural verb for marking a table arrived when a party walks in, and because SleekView writes through Restaurant Reservations Pro's own update path, every drag still triggers the confirmation emails, the table availability changes, and the SMS hooks you already configured.

The list view stays available for the back office while the host stand finally has a board for service.