Documenting Bartenders

What's different about documenting a bartender

A bartender's record is distinct because one person holds the inventory, the register, and the alcohol service decision for an entire shift with no manager behind the bar — which means their evidence trail is denser than any other role and almost none of it is generated by anyone else. A server's work is visible from the floor. A cook's is visible at the pass. A bartender's is visible only in the reports.

That has a specific consequence for documentation. Everything that matters about a bar shift — what was poured, what was rung, what was comped, who was refused — exists as data or as nothing. If your bar does not count inventory, does not export void detail, and does not write down refusals, then a bartender who is doing everything right and a bartender who is not look identical in the file.

The standards worth documenting

Standard	How it is measured	Where the number lives
Pour cost by category	Variance against target, by liquor / beer / wine, over a counted period	Inventory count plus POS sales by category
Inventory variance on named items	Bottles depleted vs bottles sold, on the items worth counting	Weekly or biweekly count sheet
Comps issued	Count, amount, and whether a reason was recorded	POS comp detail by employee ID
Post-payment voids	Count and amount, separated from pre-payment	POS void detail — see void and comp abuse
House till variance	Count to the cent, two counters, against the issued bank	Till count sheet, cash-out report
ID check practice	Whether checked, when, and by whom, on the tabs that require it	Bar log, POS age-verification prompt where enabled
Alcohol service decisions	Every refusal, and any incident, written the same night	Incident records — see overservice documentation
Certification currency	Server training certificate on file and in date	Personnel record
Bar open and close standards	Par stock, garnish, glassware, dating and rotation, keg lines, station clean	Signed bar checklist
Speed and consistency	Ticket times on bar drinks during defined windows, and spec adherence	POS bar ticket timing, spec book, taste checks

Two of these are unique to the bar and do most of the work. Pour cost is the only standard in the building where the measurement itself requires a process you may not have. Documented refusals are the only standard where the absence of records is the finding.

Evidence this role generates

• Inventory count sheets — the count, the counter, and the date. A pour cost figure with no count sheet behind it is a rumor with a percent sign.
• POS sales by category for the same period as the count. The two only mean something together.
• Void and comp detail by employee ID, split pre- and post-payment, with reason codes and the approving manager. Note whether your approval code is shared; many bars run one, and it breaks attribution.
• House till count sheet — issued amount, counted at issue, close-out variance, two counters.
• Bar log or manager log for refusals, incidents, ID issues, and anything a liquor authority might ask about later.
• Signed bar checklist at open and close.
• Camera over the well, the register, and the back bar. The highest-value footage in the building and the fastest to overwrite. Export the day it matters.
• Keg and draft records — line cleaning dates, keg yields, foam-out logs. Draft variance is frequently equipment, not people.
• Certification records with expiry dates.

Pull the POS detail the same night and photograph the paper count sheet. Bar paperwork lives on a clipboard by a sink; assume it will not survive the month.

Recurring situations

Situation	What it usually becomes
Pour cost outside target across a counted period	A coaching conversation with the count and conditions in front of the employee first; discipline only if the spec was retaught and the variance persists
Post-payment voids outside the bar's normal range	A procedure write-up, per void and comp abuse
Refusing service to a guest	A four-line incident record, every time, including the ones that go smoothly
A service decision that becomes an incident	A full incident record the same night, per overservice documentation
Till variance at close	A cash record built from the count and the access list, per cash drawer shortage
A confrontation at the bar	Statements collected individually the same shift, per documenting an altercation
Bar left unbroken-down, no dating, dirty lines	A verbal warning against the posted checklist, per documenting a verbal warning
Buyback culture running past policy	A conversation about the policy first — this is usually a management standard nobody wrote down

Coaching before discipline

Pour cost is where bar managers most often skip the coaching layer and go straight to accusation, and it is the one number where that is least justified.

A usable bartender coaching note looks like this:

3/19, 2:30 p.m., before open. K. Alvarez, bar. Reviewed the 3/1–3/15 count with her. Well spirits depleted 41 bottles against 33 bottles' worth of sales, pour cost 31% against a 22% target. Beer and wine within target. Conditions: no menu change in the period, no spec change, one comped private party on 3/9 (14 covers, comped by GM, recorded). Poured four wells with her against the 1.5 oz spec using the jigger and then free-hand: free-hand pours measured 1.9, 2.1, 1.8, and 2.0 oz. She said the bar switched to free pour "sometime last year" and she was never re-specced. Agreed: jiggers on all wells through the next count, and a re-taste at pre-shift on 3/26. Follow-up 4/2 with the next count.

That note is not discipline and it produces the outcome discipline would not: a measured cause, a stated fix, and a date. It also records something the operation owns — nobody re-specced the bar after a change in method. The note format is on restaurant employee coaching; the coaching note generator writes it in a minute.

Examples

Documented refusal, the routine kind. "Friday 3/14, 10:20 p.m. Bar seat 2, tab #1102. I observed the guest repeat an order twice and set a card down twice within about a minute. Service refused by K. Alvarez at 10:22 p.m.; she said 'I'm going to switch you to water and get you some food.' Guest accepted water, declined food, settled at 10:31 p.m. and left with two companions from tab #1104 at 10:35 p.m. No incident. Noted in the bar log." Four lines, one minute, and a file that shows the standard is live.

Inventory variance with the conditions. "Count 3/1–3/15, tequila category. Depleted 19 bottles; sales support 14. Variance 5 bottles, approx. $310 at cost. Conditions: the new margarita program launched 3/3 with a 2 oz spec against the previous 1.5 oz, and the recipe card was updated 3/8 — five days after launch. Bartenders on shift during that window: K. Alvarez, T. Nguyen, R. Diallo. Finding recorded as a spec rollout gap, not an individual record. Recipe cards printed and posted 3/16; re-count scheduled 3/31."

Post-payment adjustments. "Void detail 3/1–3/14, K. Alvarez, Terminal 3, sole sign-in. 9 post-payment voids totaling $196.15 against a bar average of 2 for the period. 8 of the 9 carry no reason code; policy requires one (Handbook §6.3, acknowledged 8/9). All 9 approved under the shared code MGR-BAR, which four managers use — the system cannot attribute those approvals. Report shown to employee 3/16; she stated she voids and re-rings when a guest changes a split after paying. Action: written warning for the missing reason codes. Control action: shared manager approval code retired 3/17, individual codes issued."

Not one of those examples would make sense on the page about servers or the page about line cooks. That is the test a role page has to pass.

Consistency across shifts

Bar standards drift by manager more than any other station, because the bar is where the exceptions live. One MOD approves a buyback round without a thought; another writes up the same round as an unrecorded comp. One counts the till at issue; another hands it over. Then a bartender is disciplined against a standard that only exists on some nights.

Four things hold it:

1. Write the numbers down. Pour cost target by category, comp allowance per shift, buyback policy, void approval rules. A standard nobody has published is not enforceable and should not appear in a write-up.
2. Count the bank at issue, every shift, both signatures. Without this, no till variance is attributable to anyone.
3. Individual manager approval codes. A shared code makes every approval unattributable and every post-payment void argument unwinnable.
4. Count inventory on a fixed cycle with the same method. An irregular count produces variance that is mostly noise, and noise in a personnel file is worse than nothing.

The FOH and BOH counterparts, with entirely different measures, are documenting servers and documenting line cooks. The full set of records a restaurant file needs is on the pillar guide.

Conclusion

Document the bar from the reports, with the conditions attached, and write down every refusal. Pour cost against a counted period and a stated target, adjustments split pre- and post-payment, a till counted at issue and at close, and service decisions recorded the night they happen.

Turn the facts into a document with the write-up generator, or capture the conversation first with the coaching note generator. The eleven fields are on restaurant employee write-up.

Docu-Coach™ keeps the counts, the refusals, the coaching, and the discipline in one dated history so a bar shift leaves a record behind it — better documentation and more consistent records, not legal advice. Liquor law and service liability questions belong with your own counsel.

See it against a real bar shift at /demo.