The BEO doesn’t lie. Three of them do.
The BEO (Banquet event order) at your venue doesn't lie. Three of them do.
It is 8am on a Saturday and the duty manager is holding three pieces of paper.
One was printed by banqueting on Thursday afternoon. One was emailed by the planner to the kitchen on Friday at 4pm and printed in the back office shortly after. The third one is the copy stuck to the side of the dishwasher, which is the one the chef has actually been working from since Wednesday because that is when the menu was finalised.
The pax count on the first one is 260. The pax count on the second one is 280. The pax count on the third one says 240, with the 4 crossed out and an 8 written in marker above it.
None of these BEOs are wrong. They were all right when they were printed. They are only wrong now.
Three BEOs in three hands is not a process failure
The first instinct, when you see three BEOs in three hands, is to say someone has not done their job properly. That is rarely the truth.
The truth is that the BEO is a static document trying to describe a moving event.
The moment a BEO is printed, a clock starts. The planner finalises a guarantee. The client decides they do want the chocolate dessert after all. The vegan count goes from four to six because a sponsor delegation added two people the morning of. The AV company adds a second wireless because the keynote refuses to wear a lavalier. The room flips from cabaret to rounds because the client walked in this morning and changed their mind.
None of these changes are unusual. All of them are normal. What is unusual is that anyone expected the printed BEO from Wednesday to still be telling the truth on Saturday morning.
Where staleness sneaks in
After enough events you start to see the same five things go stale, in the same five ways, every weekend.
Pax. The pax count drifts. Sometimes up, sometimes down, sometimes in the last hour because someone RSVP'd to the client directly and the client forgot to mention it. The kitchen plates what was on Wednesday's BEO. The banquet manager sets to Thursday's. Someone gets two of a course, someone gets none.
Dietaries. Two more vegans, one more gluten-free, the addition of an anaphylactic peanut allergy that needs to land with the chef right now. These changes almost never make it onto the printed BEO. They make it onto a text message, a sticky note, a phone call or scribble. They survive only if the right human is in the right place at the right minute to act on them.
Service style. The client changes their mind from plated to family-style two days out. The BEO still says plated. The chef has prepped plated. Someone is now making a call about which one happens in front of 300 people.
AV. The production company adds a sub-mixer. The venue's AV partner doesn't know. They arrive at the access window with the wrong rig. The BEO doesn't mention any of it because the change happened in an email thread the BEO author wasn't on.
Setup. Rounds of ten, theatre, cabaret, U-shape. These get changed late more often than anyone wants to admit. The banqueting team sets to whatever they saw last. The room is wrong by 4pm.
The mental shift
The thing every operations-heavy venue eventually arrives at is that the BEO is not a document. It is a snapshot of the state of the event at a particular moment.
If the state of the event changes (and the state of the event will change), the snapshot is now wrong. You have two options. You can re-print the snapshot every time something moves. Or you can stop printing the snapshot.
Most venues are very good at re-printing the snapshot. It is the small heroic act of every operations team: the BEO re-issued at 6pm on the night before, then again at 9am on the morning of, then again at 2pm with handwritten amendments, because by then the next print run is too slow and the duty manager has decided ink is fine.
The other option, the one almost nobody has, is to stop using a static BEO altogether. Make the BEO live. One source. Every department reads the same version. When the pax count changes at 11am, the kitchen, banqueting, AV, the duty manager, and the front desk all see the new number the next time they look. There is no "wait, are we on v3 or v4". There is only one version. The version on the screen.
What "live" actually means
A live BEO is not a Google Doc. A Google Doc is a shared document. People still print it. They still work from the version they printed at 4pm. Live needs to mean something stronger than shared.
Live means each department reads the BEO on a phone or a tablet, and the phone or tablet shows the current state. If the planner moves the pax to 285 at 11am, the chef opens the BEO at 11:01 and sees 285. The banqueting manager opens it at 11:15 and sees 285. The duty manager opens it at 4pm and sees 285. Nobody is looking at the version where it said 280.
Live also means the parts of the BEO that are also part of the ROS, the access time, the speeches, the band's set, the cake cutting, the room flip, are reading from the same place the ROS reads from. The ROS and the BEO are two views of the same event. If they disagree, one of them is lying.
This is the part the industry has not quite caught up to. Most of the tools venues use generate BEOs as PDFs. The PDF is created, emailed, printed, taped to the dishwasher. It is now a paper record of a moment in time. The next change happens in a different system, gets emailed separately, and the paper record drifts.
A live BEO is a different category of thing. It is the BEO and the ROS, together, on every phone in the building, all reading from the same place.
What this looks like on a Saturday
The duty manager opens their tablet at 4pm. The BEO is up. The ROS is up. Pax is 285. Dietaries say six vegan, four gluten-free, one anaphylactic peanut. Setup is rounds of ten, twenty-six tables. Access closed at 5pm. Vacate is 1am. The kitchen has the same view. The banqueting manager has the same view. AV has the same view, with their items highlighted in their own filter.
The planner makes a change at 4:15pm. By 4:16pm, every person above sees the change.
There is no email. There is no "FYI updated BEO attached". Nobody is printing v6 at the venue's front office on a printer the duty manager has not changed the toner in since 2019.
How to get closer to this from a PDF-BEO world
Most venues cannot rip out their event management software next week. That is fine. Some things to do in the meantime, while you are still living in the PDF-BEO world.
Print less. Every printed BEO is a future stale BEO. If you must print, print one canonical copy at one location (the duty desk), and treat every other copy as advisory.
Date and stamp every revision. v3 should look different from v4 at a glance. The change log on the BEO is sometimes more valuable than the BEO itself.
Tell every department to read on a phone. Not because phones are magical, but because the phone is always pulling the latest version, and paper is not.
Have one human who owns the BEO. One. Planner, venue coordinator, anyone. But one. Two BEO owners is three BEOs.
Where 1pm fits in
This is the part of the post where founders explain how their app solves the thing they have just spent eight paragraphs describing. Short version, because if you have read this far you already know.
1pm.app makes the BEO and the ROS the same thing. Every department reads from the same live page on their phone. The kitchen sees the dietaries. AV sees the access window and their own items. The duty manager sees the summary. The planner edits once. Everyone sees the change the next time they refresh.
It is the live BEO the industry has been re-printing for thirty years.
A quick note about words
Throughout this post I have used BEO (Banquet Event Order) and ROS (run of show). They are the same event seen from different angles. The BEO is the event's state today: pax, service style, dietaries, menu, setup, access, vacate. The ROS is the event's timeline today: when each thing happens, who is doing it, what is next. Same event. Same source. Two views.
Closing
There is a small part of me, after a lot of events, that still hopes one day to walk into a venue at 8am on a Saturday and not see anyone holding three pieces of paper.
We are working on it.
Chris
Founder, 1pm.app
