Venue Ops Vault

Included with BEO Studio. Seven templates and standards from a working venue operation. Print to PDF, or copy what you need. Every template ends with a "why" — the failure it exists to prevent.

1. Blank BEO template

Event		Date
Client		Contact
Guests (final)		Room / layout
Start / end		Bar policy

Run of show

Time	Item	Owner

Menu & beverages

Dietary

Halal ☐ · Kosher ☐ · Vegetarian ___ · Vegan ___ · Allergies:

Staffing

Waiters ___ · Bar ___ · Supervisors ___ · Setup crew ___ · Kitchen: per caterer

Setup notes

Sign-off

Client ____________ · Venue ____________ · Kitchen ____________ · Version ___ · Date ___

Why: the function brief that "exists nowhere" is the root of most event failures — the kitchen hears one version, the floor another, the client a third. One living sheet everyone runs from.

2. BEO operating standard ("No BEO, no event")

Every booking gets a BEO the day it is confirmed. Draft is fine; existing is mandatory.
21-day gap check. Once per shift, list every event in the next 21 days without a BEO. Target: zero.
48-hour rule. A BEO is confirmed (menu, timeline, staffing, final numbers) no later than 48 hours before the event. Anything unconfirmed at 48h is an exception the manager sees that morning.
Version on every change. Numbers change 48h out; everyone who needs to know is on a named list on the BEO, and the version number goes up.
One owner. A named person owns the BEO from draft to debrief. Ownership can be handed over, never shared.
Checklist ticks are stamped. Who ticked it, when. A tick without a name is not a tick.

Why: BEOs did not get written when writing them was a task with no reward. The standard makes a missing BEO visible to the manager every morning — the visibility is the enforcement.

3. Kitchen prep sheet

Event / date		Total covers
Service style	Plated ☐ Buffet ☐ Canapés ☐ Family ☐	Service times	Starters ___ Mains ___ Dessert ___

Courses

Course	Dish	Qty	Notes

Dietary board (post in kitchen)

Vegetarian ___ · Vegan ___ · Halal ☐ · Kosher ☐ · Allergies: · Table numbers for special plates:

Handover

Prep confirmed by ____________ at ____ · Dietary board posted ☐ · Plate count checked against final pax ☐

Why: the kitchen finds out about the coeliac guest at table 4 during service. The board on the wall, posted at handover, is the fix.

4. Event-day supervisor run-sheet

T-3h (T-4h at 400+, T-5h at 800+)	Setup crew call — floor plan built per BEO, walked against the sheet	☐
T-2h	Power, HVAC and facilities run-up (backup power tested under load; condensate/drip check over guest areas); bathrooms stocked	☐
T-90m	Kitchen handover — prep confirmed, dietary board posted	☐
T-45m	Supervisor final walk — cleanliness zones, pest check, sound test from the client's position	☐
T-30m	Doors — service staff posted, welcome drinks ready, shift lead named to the client contact	☐
During	Service beats per BEO; changes logged on the BEO with time and who told whom	☐
End	Teardown; equipment count-back against packing list; damage logged	☐
End +90m	Returns checked in, venue locked, debrief note: what broke, what the client said, what to fix before the next one	☐

Why: the same five failures recur at every venue — power, air-con drips, cleanliness, sound, and a kitchen surprised by numbers. Each line here is one of them, timed before it can happen.

5. Pre-event standards checklist (13 points, with the reason for each)

Final guest count confirmed with client (72h out) — every count downstream (plates, chairs, staff) hangs on this one number.
Balance payment confirmed before event day — chasing money during service loses both the money and the client.
Power / backup generator load-tested under full load (48h out) — a generator that starts is not a generator that holds 1,000 guests' worth of load.
Backup power fuel + changeover checked — the failure is usually the changeover, not the machine.
HVAC run 2h + condensate/drip check over guest areas — a drip on a guest's table is the story they tell about your venue.
Pest check — hall, kitchen, bins — flies at dessert erase everything that went right before.
Cleanliness zones signed off — "clean" is not a state; a named zone with a signature is.
Bathrooms stocked + checked — the one room every guest visits and nobody on the team does.
Floor plan set per BEO + walked — a plan on paper and a floor as built are two different rooms until someone walks it.
Sound/mic tested from client position — it works at the desk and not at the top table.
Kitchen has prep sheet + dietary board posted — see template 3.
Packing list dispatched + returns scheduled — unscheduled returns are how stock disappears.
Shift lead named + crew briefed — a room with no named lead escalates everything to the owner.

6. Site-visit discovery checklist (for venue managers assessing a new client or partner venue)

Before

Confirm who will be present — the decision-maker and the person who runs the day
Ask to see a working period, not a quiet one
List every revenue line and booking channel from their website

On the day — talk 20%, ask and write 80%

Walk me through a booking from first enquiry to invoice — who touches it, where does it live?
What runs on a system, and what runs on spreadsheets or WhatsApp?
What went wrong most recently? What breaks repeatedly that everyone has accepted?
What do you find out too late to fix?
When a client changes numbers 48 hours out, how many people have to be told, and who tells them?
How does the kitchen learn what a function needs, and when?

Observe without asking

Printed sheets taped to walls — paper on a wall is a system that failed
How often someone says "let me check with…"
The same information written in two places

Within 72 hours

A two-page findings note in their language: what you saw · what's working · where it leaks (3–5 items, each with the cost) · what to fix first.

Why: whoever names the client's problem back to them most accurately wins.

7. Deposit, balance and final-numbers policy (template wording)

Deposit. A non-refundable deposit of ___% (minimum ___) secures the date. The date is not held until the deposit reflects.

Balance. The balance is due ___ days before the event. Events with an outstanding balance 48 hours before the date may be cancelled at the venue's discretion.

Final numbers. Final guest numbers are confirmed in writing ___ hours before the event (we recommend 72). Numbers may increase after this point subject to availability; they may not decrease. Charges are based on the confirmed number or the number attending, whichever is higher.

Changes. Changes to menu, timing or layout after the BEO is confirmed (48 hours before the event) are accepted only in writing and may carry a change fee of ___.

Dietary. Dietary requirements and allergies must be supplied in writing with the final numbers. The venue cannot guarantee dietary needs notified after this point.

Why: every one of these lines is a conversation that otherwise happens on the night, with the client, in front of the guests.