One hall, many bookings, a separate record for each event
Weddings, corporate functions, and private parties in a dedicated room. The booking is what kitchen and floor work from — not last month’s Word file with the names swapped.
Image to shoot
Empty for now. Product UI: a list or calendar of hall bookings (many dated events, one venue). Not a restaurant homepage hero. Optional lifestyle: empty hall set for a function, no hotel lobby.
Who this page is for
This page is for banquet halls and event rooms that host many bookings in the same space. Each reservation becomes its own event, so the menu, run-of-show, and paperwork belong to that night instead of a packet you rebuild every time.
How venues use it
The booking is the packet
Client, date, menu, timeline, and tasks live on the event. Copy what you reuse. You do not start from a blank file for every wedding.
Kitchen and floor read the same hall
Shopping lists come from the menu. The run-of-show is shareable. Nobody is working off Tuesday’s printout.
Paperwork that matches production
Document templates pull event and client fields so the hall packet matches what the kitchen already sees.
Many bookings, many people, the same hall
The hall stays one place. Each booking is its own event. Schedules put people on that night without cloning the room.
Image to shoot
Empty for now. Event packet for a hall booking: timeline with ceremony/dinner times plus a document preview. Venue context (one room), not restaurant storefront branding.