Banquet and F&B events — rooms stay in your hotel system
Treat the function as an event. Attach food, the run-of-show, tasks, and documents. Rooms, front desk, and reservations stay in the hotel system you already use.
Image to shoot
Empty for now. Product UI of a banquet or gala dinner event with F&B menu attached. Function room, not front desk. Do not show a room rack, occupancy calendar, or PMS.
Who this page is for
This page is for hotel teams who run functions: galas, meeting dinners, coffee breaks. Sales can keep booking the room in the hotel system. Food, timing, tasks, and documents live here as an event, so kitchen and banquet are not working from three different files.
How hotels use it
The function, not the room night
Treat the banquet, meeting dinner, or coffee break as an event. Attach F&B, tasks, and the run-of-show. Room blocks stay where they belong.
Kitchen and banquet on the same event
Menus generate shopping lists. Document templates fill from the event instead of a new BEO typed from scratch.
Staff see the function, not the rack
Share the timeline with the banquet team. Assign people to the event. They see the function — not rates, not the client file, not the room rack.
Image to shoot
Empty for now. Kitchen document or BEO-style output filled from event fields, beside a timeline. Caption energy: banquet F&B. Never a room block, group reservation, or front-office screen.