Plan for the peak, not the average
A guest-to-bartender ratio skips the question that matters: how many orders arrive at once, and how long does this menu take to serve? A reception with one arrival wave can put more pressure on a bar than a longer event with the same attendance.
Break the event into windows: arrival, steady service, speeches, restart, and close. For each window, estimate beverage demand, distribution between stations, and the service method. Mark those estimates as planning assumptions. They are not measured facts until you have data from a comparable setup or a rehearsal.
Test the station you intend to run
Time complete service cycles with the proposed menu, glassware, garnish, and finishing method. Include order taking and handoff. A fast isolated pour is not the same as sustained guest service. Repeat the exercise and use a sustainable result, not the best attempt.
State what the test excludes. If someone else replenishes ice, clears glassware, and brings batch bottles, those tasks need separate capacity. If the bartender performs them, include that time in the test or provide relief. A throughput assumption is only useful when its conditions travel with it.
Show the headcount arithmetic
Fictional example: 12 peak serves/min ÷ 2 tested serves/min/bartender = 6 active bartenders. The inputs are illustrative, not industry benchmarks. This number excludes barbacks, runners, management, and relief.
Editable planning arithmetic. Zero demand yields zero active bartenders. Throughput must be greater than zero. The responsible operator must review the whole plan.
Round up because a fractional person cannot cover a station. Then check the physical layout: six bartenders are not useful if the bar only has safe working room for four. Rework station count, menu steps, service method, or arrival distribution instead of treating extra people as the only answer.
Separate service, support, and authority
| Role | Primary responsibility | Coverage question |
|---|---|---|
| Beverage lead | Approvals, quality, escalation | Who owns the floor while they resolve a problem? |
| Bartender | Guest service and recipe execution | Who covers each planned break? |
| Barback | Ice, batch, tools, and station reset | Can replenishment keep up at the peak? |
| Runner | Transfers between storage and stations | How long is the full delivery route? |
There is no automatic barback ratio here. Map support work by task and route. Identify the replenishment trigger, storage location, transport method, and person receiving the handoff. Keep guest access routes clear and confirm accommodations with the venue and team.
Build shifts around the work
Write call time, setup assignment, briefing, service position, break, relief person, and release condition for each role. Service hours are not shift hours. Receiving, station build, inventory counts, and rental return can sit outside the guest-facing window.
Separate planned, confirmed, and backup counts. Reconcile the role rows against actual named shifts before calling the plan staffed. A planned total of ten with no confirmed assignments is not ten people on the floor.
Review rest and meal breaks, accessibility, local labor requirements, training, and responsible-service duties with the accountable operator. A spreadsheet cannot determine legal staffing compliance or whether a crew member can safely complete a shift.
Before release, walk through a late arrival and an absent team member. Name the person who can move staff, simplify the menu, or pause a station. Put that decision authority in both the staffing sheet and the BEO so the team does not receive competing instructions.
Put the guide to work.
Get the blank BEO, staffing sheet, run of show, batch recipe, and production checklist in the editable kit.
Open the cocktail BEO builder ↗Connect the rest of the plan
How to write the beverage section of a BEO ↗How to build a cocktail-event run of show ↗
How to batch cocktails for an event ↗