Approve a BEO, email it and track changes
Set the BEO status to Approved, or print or email it once it is past Draft, and the BEO is released to the team. After that, a change to the menu, bar, timing, guest count, room, staffing or notes alerts the kitchen, bar and floor. Each person marks the change seen.
Release a BEO to the team
- Open the BEO, set BEO status to Approved (or Completed) and press Save BEO. The approved version becomes the baseline that later changes are measured against.
- Or press Print BEO, Download PDF, Kitchen copy (no prices) or Email BEO on a BEO that is past Draft. The first time, that releases it with the printed version as the baseline. A BEO in Draft is not released by printing.
- Printing or emailing an already released BEO does not move the baseline.
Choose who hears about changes
- Open Settings, then Members under People & access.
- On each member’s row, set BEO alerts for name to Kitchen, Bar or Floor. No BEO alerts takes them off.
- Alerts also go to the event’s assigned manager, and to people on the event’s staff list whose name or email matches a member. If nobody is marked, everyone with the Staff role hears. Clients never do, and neither does the person who made the change.
Email a BEO to staff
- Save the BEO, then press the envelope, Email BEO.
- Under Send to type up to 10 email addresses, separated by commas.
- Under Which copy choose Kitchen copy, no prices or Full copy, with prices. The kitchen copy is the default.
- Press Send. A message says “Sent to N people”, or names who it could not reach.
What staff receive
One email for each address, so recipients do not see each other. It carries a link that opens the BEO read-only with no login. The link always shows the latest version, works for 90 days, and names one BEO and one copy, so it cannot be edited to show prices or another BEO. Anyone with the link can open it, so keep it within your team. Replies go to your venue’s reply address.
What a change alert watches
| Group | Fields | Comes from |
|---|---|---|
| Guest count | Guest count | The BEO, the event, the client’s final count |
| Timing | Date, start time, schedule | The BEO or the event’s timeline |
| Room and floor plan | Location, room (layout), setup instructions, the floor plan itself | The BEO, the event, a floor plan redrawn in the builder |
| Menu | Menu lines | The BEO |
| Bar | Drinks, bar service type, bar notes | The BEO |
| Staffing | Staffing requirements | The BEO |
| Notes and dietary needs | Special requests | The BEO or the event’s notes |
What happens when something changes
The first change after release opens an alert and raises the version number. Changes within the next 10 minutes join the same alert, so five saves in a row send one. Each person who needs to know gets a bell notice, and one email goes out when the 10 minutes end with every change in it. The client’s name, email, phone and the BEO title are not watched.
On the BEO, staff see a panel titled Changed since approval, or Changed since it was printed for the team when it was released by printing. It shows the version, the date, each change as a line such as “Guest count: 120 to 140”, who made it and when, a Seen by list and a Not seen yet list. A section that changed carries a Changed tag. A banner, Changes since you last viewed, shows once per change and has Hide.
Each person presses Mark as seen. The panel then says “You marked version N as seen.” On the BEOs list a strip reads “N BEOs changed after approval” and opens each one. The printed BEO says “Version N” and “Changed since approval” on the sections that changed.
Redrawing the room’s floor plan raises an alert on every released BEO for an event still to come that uses the plan, up to 50, with the line “Floor plan redrawn”.
If something is not working
| What you see | Why | What to do |
|---|---|---|
| No change panel on the BEO | The BEO is still in Draft and was never printed or emailed, or you are signed in as a client. | Set the status to Approved or print it once past Draft. |
| Nobody got an alert | The change was to the title or client details, which are not watched, or the only person who could hear made the change. | Check Settings, Members for who is marked Kitchen, Bar or Floor. |
| “Enter at least one email address.” | Send to is empty. | Type an address. |
| “name is not a valid email address.” | One entry is not an address. | Correct it and press Send. |
| “You can send to 10 addresses at most.” | More than ten were typed. | Send in two goes. |
| “We couldn’t send the email. Try again.” | The send failed for every address. | Wait a moment and try again. You can send 30 times an hour. |
| The emailed link says not found | It expired after 90 days, or was changed. | Press Email BEO again. |
What it does not do
- Approved does not lock the BEO. Staff can still edit it, and the change alert is how the team finds out.
- Every saved version is kept in the History button on the BEO tab, with what changed.
- Change alerts reach staff and above. A client never sees the alerts or who has seen them.
- A personal BEO, outside a venue, has no team to alert.
- Email BEO sends read-only links to up to 10 addresses at a time, and 30 sends an hour for each person.
- The alert email is sent about 10 minutes after the first change and is replaced if more changes join before then.
Common questions
Does approving a BEO lock it?
No. Approving releases the BEO to the team and records the baseline. Staff can still edit it, and every change after that raises an alert.
How does the kitchen find out the guest count changed?
A change to the guest count on the BEO, the event or the client’s final count raises an alert for the people marked Kitchen, Bar and Floor, and the BEO shows the old and new number.
Can I send a BEO to the chef without prices?
Yes. Press Email BEO, choose Kitchen copy, no prices, and send it to their address.