HBook Hotel Booking stores every reservation as a row in hbook_reservations with a status column whose values are pending, valid, cancelled, expired, or on-hold. The default Reservations screen lists those rows in a long table sorted by reservation ID with the status as a small column per row, which is fine for a small guesthouse and breaks down for properties handling weekly arrivals.

SleekView Kanban reads the same hbook_reservations table and treats the status column as the natural axis to group by. Each card surfaces the guest name, the accommodation type, the check-in and check-out dates, the nights count, and the total. Columns mirror your real HBook statuses, so a glance tells you how many reservations are pending payment, how many are valid for next week, and how many have expired without paying.

Drag a card from Pending to Valid and SleekView calls the same HBook update path the admin uses, which fires the validation email, marks the accommodation as booked on the front-end calendar, and triggers any payment hook you have configured. Drag to Cancelled and the refund and notification flows run through HBook so any payment gateway integration handles the money side consistently.

An accommodation site sells nights, not products, and nights run out whether you act on them or not. HBook Hotel Booking captures reservations cleanly in hbook_reservations, but the default admin gives you a list sorted by reservation ID, which is the order they came in, not the order they need attention. That works for a quiet B and B and falls apart the moment you have a phone ringing, a deposit window closing, and a guest asking why nobody validated their stay three days ago.

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 reservations are pending validation, how many are valid for next week, and how many cancellations still need a refund. Cards make individual reservations legible at the level of guest, accommodation, dates, and money.

Drag is the natural verb for moving a reservation from one stage to the next, and because SleekView writes through HBook's own functions, every drag still triggers the validation emails, the availability changes, and the deposit captures you already configured. List view and board view stop being a tradeoff and start being two reading surfaces over the same data.