What goes on a BEO that the kitchen actually reads

A BEO fails in a very specific way. It is not usually wrong. It is usually complete, accurate, four pages long, and nobody reads it — so the chef asks what time the client wants the entrée, the captain asks where the gift table goes, and the answers were on page three all along.

The fix is not more detail. It is remembering who the document is for. A BEO is written for the crew at 4pm on the day. Every line either answers a question somebody will ask, or it is in the way of the lines that do.

The sections, and who each one is for

1. Identity block

Event name, date, day of the week, BEO number, revision number, and the date the revision was issued. Top right, large.

The day of the week matters more than it looks — 'Saturday 14 March' catches an error that '14/03' hides. And the revision number is the difference between a crew working from the current plan and a crew working from the one you printed on Tuesday.

2. Contacts

• Client name and mobile
• On-site day-of contact — often not the client, and this is the number that gets used
• Venue coordinator and their mobile
• Your captain and your chef
• The planner, if there is one, and what they are authorised to decide

That last line prevents a specific, expensive argument: a planner asking for a change nobody is going to pay for. Write down who can approve what.

3. Venue and access

The section that saves the day, and the one most often thin.

• Full address, plus the loading entrance if it differs — it usually does
• Parking: where, how many spaces, permits, whether the van fits
• Access route: stairs, lift dimensions, distance from van to kitchen
• Kitchen: what exists, what works, what you may use
• Power: how many circuits, where, and whether you need your own
• Water and waste, and where ice can be dumped
• Noise curfew and hard out time
• Venue restrictions: no open flame, no red wine, no confetti, no tape on walls

4. Timeline

Not the client's timeline. Yours. From leaving your kitchen to arriving back at it.

Include the staff meal and the briefing. If they are not on the timeline they do not happen, and a crew that has not eaten or been briefed is a crew that will improvise.

5. Counts

Three numbers, always: expected, guaranteed, and set-for. They are different numbers and confusing them is a whole class of mistake. 'Guaranteed 140, expected 150, set for 155' tells the kitchen what to cook, tells the client what they owe, and tells the captain how many chairs.

Kids and vendor meals get counted separately. A vendor meal is not a guest cover and should not be plated like one.

6. Menu, with exceptions attached

Course by course in service order, with the portion spec next to each item. Then, and this is the part that matters, the dietary exceptions listed as their own block:

Seat number, not just table. A server carrying two special plates to a table of ten and asking 'who had the vegan?' in the middle of the speeches is a small failure the client will remember for a year. And a severe allergy gets a name on the sheet and a person responsible for that plate from pass to table.

7. Beverage

• What is served, and who is paying — host bar, cash bar, or a tab with a ceiling
• The ceiling amount and what happens when it is reached
• Wine: which wines, poured or on table, how many bottles opened at once
• Toast: what, when, whether it is poured in advance
• Corkage arrangement if the client supplies alcohol
• Last call time, and who tells the client it is happening

8. Staffing with call times

Names, roles, call times, uniform, and where to park. Staggered call times save real money and only work if they are written down. See the staffing ratios post for the crew sizes themselves.

9. Floor plan and setup

Table count and shape, cover counts per table, linen colour and size, china and glass, centrepieces and who is bringing them, plus the specific placements people always ask about: gift table, cake table, place cards, bar position, buffet position, DJ, dance floor.

A sketch beats a paragraph. If your BEO carries one image, make it this one.

10. Rentals and equipment

What is coming from where, delivery and pickup windows, who receives it, and what is yours versus the rental company's — because at 23:00 in the dark, chafers all look the same and yours are the ones that do not come back.

11. Pack list

The section that decides whether the day is calm. It should be generated from the menu and the service style rather than typed from memory, because the thing you forget is never on the list you wrote from memory. Chafing fuel is the classic. So is the extension lead, the serving spoon for the one dish that needs a specific spoon, and a knife for the cake.

12. Billing summary

Contracted total, deposits received, balance due, when it is due, service charge and tax treatment, and what triggers an overage. One short block. The crew does not need it, but the person invoicing on Monday does, and they should not have to open a different document.

The four ways a BEO fails

1. 1Version drift. Three revisions exist and two of them are printed. Fix: revision number and date in the header, and one place the current version lives.
2. 2Written for the client. Prose, adjectives, marketing language. The crew needs a spec sheet, not a description of a lovely evening.
3. 3Missing the boring section. Access, power, parking and the hard out. Nobody enjoys writing these and every one of them ruins a day when it is wrong.
4. 4Not distributed. It exists in your email and nowhere else. If the captain cannot pull it up on a phone at 4pm, it does not exist.

Generate it, do not type it

Every field on a BEO already exists somewhere else: the menu is in the proposal, the counts are in the booking, the staffing is in the schedule, the rentals are on the order. Retyping all of it into a document is not just slow, it is how the fourth revision ends up disagreeing with the contract.

In Apron Desk the BEO is a view of the event rather than a document about it — change the guest count and the BEO, the pack list, the prep sheet and the invoice all move together, and the version on the captain's phone is the current one because there is only one.