Private dining and in-house events, on one booking
Birthdays, corporate dinners, and other restaurant events. Put the menu, timeline, tasks, and documents on the event so office, kitchen, and floor are looking at the same plan.
Image to shoot
Empty for now. Product UI: one restaurant event with client and date prominent; menu, timeline, and documents attached. Private-dining context — tables, not a hotel ballroom. Desktop, light UI.
Who this page is for
This page is for restaurant teams who run events in their own dining room. If the office has the email, the kitchen has a spreadsheet, and the floor has a chat screenshot, those pieces can sit on one event instead of three versions of the same night.
How restaurants use it
One event for office, kitchen, and floor
Client, date, and status live on the event. You attach menus, timelines, tasks, and documents when the booking needs them.
A shopping list from the menu you already built
Meals and drinks sit on the event menu. Ingredients roll into a shopping list, so the order is not a second spreadsheet.
Guest paper and kitchen paper from the same fields
Templates fill from the event and the client. The packet for the floor and the packet for the kitchen stay in step.
A staff login that is not the office file
Kitchen and floor open the event from a staff login. They get the menu and the timing. They do not get the client or the prices.
Image to shoot
Empty for now. Split frame: left = guest-facing menu or timeline; right = kitchen shopping list or kitchen document. Same event title in both headers. Restaurant service, not a hall wedding.