Alcohol Server common mistakes
Alcohol Server · Understand the traps and how to avoid them.
Offering coffee, food, or a cold shower to a guest who has had too much, and telling them it will 'sober them up' before they drive.
These are culturally repeated myths that get memorized instead of the actual pharmacology; caffeine and cold water only change how alert someone feels, not how impaired they are.
What to do instead
Memorize the single fact the exam tests: only time clears alcohol, at roughly one standard drink per hour for the average adult, and nothing speeds that up. Caffeine, food, and cold all change how the guest acts, not their BAC.
Deciding a guest is fine at the moment they order because 'they've only had two,' without re-checking them 30 to 60 minutes later.
Alcohol absorption lags behind drinking, so BAC keeps rising after the last sip, especially on an empty stomach or with fast consumption; servers judge the present moment and assume it is the peak.
What to do instead
Plan a check-back instead of a single judgment: note the time of the last drink and reassess after 30 to 60 minutes, since BAC typically peaks in that window and a guest can look steady at order time and be visibly impaired later.
Accepting the guest's own account of how much they've had ('I'm fine, this is my second') and pouring based on that number.
Guests under-report, drinks vary in strength, and the server may not have seen every drink; self-report feels polite and avoids conflict.
What to do instead
Track standard drinks yourself (including what colleagues served) and let observed behaviour override the guest's number. Counting is a tool for pacing, never proof of sobriety.
Serving a high-tolerance regular who is talking normally but has glassy eyes, is fumbling with their wallet, and is repeating themselves, because they 'hold it well.'
Tolerance suppresses the loud, obvious signs, so servers anchor on slurred speech as the only real cue and miss the subtler cluster.
What to do instead
Use a fixed cue checklist every time: speech, balance and gait, coordination with money and phone, eye appearance, and any change from the guest's normal behaviour. Two or more cues means stop serving, regardless of how well the guest is talking.
Glancing only at the date of birth on an ID and handing it back, without checking the expiration date, the photo match, or signs of tampering.
The DOB is the only field servers are trained to compute, and under time pressure the rest of the check gets skipped.
What to do instead
Run a fixed four-point check out loud in your head: photo matches the person, DOB math puts them over 21, ID is not expired, and the physical document shows no tampering (holograms, font, edge, feel). Any failed point is a refusal.
Carding only the person paying for a pitcher or a round, and serving the rest of the table without ID.
The transaction is treated as belonging to one customer, and carding a whole group feels awkward or insulting.
What to do instead
Card every person who will drink from the order, not just the buyer. If one person at the table cannot produce acceptable ID, no alcohol goes to that table.
Continuing to serve a guest who is visibly intoxicated because 'it's their choice' or 'they're an adult and they have a ride.'
Servers picture responsibility as resting entirely with the drinker and underestimate how far the establishment's exposure reaches.
What to do instead
Learn the liability rule the exam wants: the server and the establishment can share civil and criminal liability for over-service, including injuries the guest causes after leaving, and a 'designated driver' claim is worthless unless you have confirmed that person is sober.
Cutting one guest off without telling the other bartender, the floor staff, or the next shift, so the guest simply orders from someone else.
There is no formal handoff mechanism and shifts are busy, so each server believes they are the only one watching that guest.
What to do instead
Make the cutoff a communicated event: tell the colleague directly, flag the tab or table in the POS, and hand it over verbally at shift change. Refusal is a team action, not a private decision.
Announcing loudly in front of the guest's friends that they are drunk and cannot be served, and then arguing when the guest disputes it.
The confrontation feels like a personal challenge, so the server defends the judgment instead of managing the situation; embarrassment in front of peers also escalates the guest.
What to do instead
Use a short, neutral script that states the decision and not a diagnosis: 'I'm not able to serve you any more alcohol tonight.' Do not debate whether they are intoxicated. Move the conversation away from the group, offer water, food, and a ride, and involve the manager or security if it escalates.
Writing an incident note as conclusions - 'guest was drunk and aggressive, we cut him off' - with no times, drinks served, exact words, or actions taken.
People write reports the way they would tell the story to a colleague, compressing observations into judgments and leaving out the details that make a record usable later.
What to do instead
Write only what a camera would have recorded: clock times, each drink served and by whom, specific observed behaviours ('could not stand without holding the bar, speech slow, spilled water twice'), exact quotes, the refusal, alternatives offered, and who was notified. Keep opinions out of the record.