The evening this is about

An event that is agreed and not written down in one place is agreed with each person separately. The kitchen heard one thing, the floor heard another, the client remembers a third, and all three are discovered at once on the day.

The couple changed the starter in an email six weeks ago and the kitchen never saw it.
The bar staff learn the timing when the timing arrives.
The client says the room was to be set by four, and nobody can find where that was said.
Three versions of the running order exist and none is marked final.

What it actually does

Puts the whole event on one sheet: menu, timings, numbers, room layout, who is doing what.
Keeps one version, with changes dated and visible, so "final" means something.
Gives each department the part it needs — kitchen times, bar stock, floor layout — from the same sheet.
Turns the agreed sheet into the invoice at the end, without anybody re-entering it.

The detail that matters

This is the document the whole trade calls a BEO, and it exists for one reason: an event has too many moving pieces for anyone to hold the whole thing. When it is one sheet with one version, the argument on the day is about something real, and usually there is no argument.

What it does not do

It does not sign the contract. The commercial agreement is a separate document and should be.
It does not stop a client changing their mind at the last minute. It makes the change visible to everyone at once instead of to one person.

We would rather you read this before the call than find out after.

Where it sits

A wedding quoted in seconds, counted to the last plate. Event Orders is one of six tools in Events & Banquets, and it runs on the same guest, booking and menu data as the rest of the Suite — so nothing is typed in twice.

Fifteen minutes, no slides.

Tell us how your venue runs and we will say plainly whether Event Orders helps — and which two or three tools to start with.

Talk to us See the whole Suite