One living Banquet Event Order per event — the version the kitchen, the floor, and the planner all trust.
1-month free trial · No credit card required
Where event teams break down today
The sales manager emails a BEO, the chef edits it, the planner edits it again — nobody knows which is current.
A dietary change made at 4pm never makes it to the line. The wrong headcount goes out.
The BEO is a Word doc. The contract is a PDF. The payment is a spreadsheet. Three sources, all out of sync.
Every BEO is built from scratch. Items, prices, and timing retyped every time.
How Irisen solves it
A single BEO that updates in real time. Everyone reads the version that is current — no more chasing PDFs.
Every edit is tracked with who changed what and when. Revert to a prior version in one click if a client changes their mind.
Build BEOs from your saved items — menus, bar packages, rentals — with prices that stay in sync across documents.
Set start and end times per item so the kitchen and floor know exactly when each course hits the pass.
Send the kitchen a read-only BEO link, or print a clean copy for the back of house. No login required.
BEO items flow from the signed contract. One change, one place — the contract and BEO never disagree.
Why teams switch
A Banquet Event Order — the document that tells the kitchen, floor, and planner exactly what is being served, when, and to how many. Irisen keeps one living version per event.
Yes. Share a read-only link, or print a clean copy for the back of house. The link always shows the current version.
Yes. When a contract is signed, its items flow into the BEO. Change an item once and both stay in sync.
Every edit is versioned. Open the history, see who changed what, and revert to any prior version in one click.

Start your free trial today. Your first proposal is minutes away.