Every kitchen knows the shape of it. A twelve-top lands at eight, the order arrives at twenty past, and for the next forty minutes every other table in the room quietly pays for it. The fryer backs up, the pass jams, and the couple on table five wonder why their mains are slow when the room is half empty.
The problem is not the party, it is the surprise
A big table is only disruptive because the kitchen learns what it wants at the worst possible moment. The same twelve covers, known at lunchtime, are a gift: the section can be prepped, the sauces portioned, the timings staggered against the rest of the book.
Which is why the pre-order is one of the oldest tricks in banqueting, and one of the least used in ordinary restaurants. Somewhere along the way it came to mean a fax back from a wedding coordinator, and everyone quietly agreed it was too much fuss for a birthday dinner.
Make ordering ahead the path of least resistance
The fuss was never the idea, it was the mechanics: a PDF menu, an email thread, someone retyping choices into a notepad that the kitchen cannot read. Strip that out and a pre-order is just a menu and a form, attached to a booking.
- Put the live menu inside the booking flow, so choosing dishes happens at the moment of highest intent
- Let the organiser share a link with their party instead of chasing choices themselves
- Send the kitchen one tidy list per booking, named per guest, not a thread of screenshots
A pre-ordered twelve-top is not a problem table. It is the easiest service of the night, booked in advance.
None of this needs to feel corporate. The menu the party orders from is the same menu on your website tonight, at the same prices, with the same specials. If it changes before they arrive, their choices follow it. That is the whole trick: one menu, everywhere, including inside the booking.