Liability, DUI, and Incident Documentation

Alcohol-impaired driving can cause serious injury, death, property damage, arrest, license consequences, insurance consequences, job loss, and community harm. Servers are part of prevention because service decisions affect what happens after the guest leaves.

Washington DUI law includes per se alcohol limits and penalties. A guest does not need to look extreme to be unsafe. Judgment and reaction time can be impaired before a guest appears obviously drunk.

LCB and law-enforcement agencies may track DUI information connected to licensed premises. Responsible service, incident documentation, and cooperation with enforcement help show that the establishment took prevention seriously.

Washington's implied-consent framework means drivers can face consequences for refusing required breath or blood testing after a lawful DUI-related arrest process.

Servers do not explain legal rights to guests or provide legal advice. The training point is prevention: do not continue service when the guest's condition or consumption pattern makes driving risk foreseeable.

If a guest may drive after being refused service, use manager support, offer alternatives, document steps, and contact law enforcement when safety requires it.

Service decisions can affect people who were never inside the establishment: passengers, pedestrians, other drivers, families, coworkers, and licensees. Over-service and sales to minors create risk beyond the transaction.

A responsible server thinks ahead. If alcohol service contributes to a foreseeable injury, the permit holder, licensee, and employer may face consequences under Washington law, regulation, employment policy, insurance, or civil claims.

The best risk control is consistent practice: check ID, watch consumption, stop service early, communicate with staff, document incidents, and follow house policy every shift.

Incident logs should be factual, timely, and professional. Record what was observed, what was said, what actions staff took, who was involved, and whether transportation, medical help, law enforcement, or LCB contact occurred.

Document attempted minor purchases, questionable ID refusals, service refusals, disorderly conduct, threats, fights, injuries, ejections, calls for rides, and attempts by others to buy for a refused guest.

Daily notes are useful even when nothing major happens. A brief note that the shift had no refusals or incidents helps show routine attention and can help managers identify patterns over time.

Washington law includes Good Samaritan protection related to seeking medical assistance for alcohol poisoning in certain circumstances. The practical server rule is simple: call for help when a person may be in danger.

Do not let fear of discipline or embarrassment delay emergency care. Alcohol poisoning, serious injury, violence, or a credible threat to drive while impaired should be escalated immediately.

After the emergency is managed, document the observable facts and actions taken. Do not add gossip, guesses, medical diagnoses, or insulting language.

LCB's Last Call video reinforces the real-world consequences of DUI, over-service, and missed intervention opportunities. The prepared online workflow includes a Last Call viewing gate before permit processing.

Example 1: A guest consumes several strong cocktails quickly, becomes loud, and says they are driving. Staff slows service, refuses the next drink, gets the manager, offers food and a rideshare, and documents the refusal.

Example 2: A group passes drinks to a person who looks under 21. Staff checks ID, stops the shared-drink behavior, warns the table under policy, and documents the attempted furnishing to a minor.

Example 3: A regular guest seems fine because they tolerate alcohol well but has consumed enough to create risk. Staff does not rely on tolerance; they pace service, stop service when signs appear, and notify teammates.

RCW 46.61.502 currently describes DUI as driving with an alcohol concentration of 0.08 or higher within two hours after driving, a THC concentration of 5.00 or higher, driving while under the influence of or affected by intoxicating liquor, cannabis, or any drug, or driving while under combined influence. For server training, the most important point is that impairment is broader than one number.

RCW 46.61.5055 describes penalty schedules for alcohol and drug violators, including consequences that can increase with prior offenses, higher test results, refusal, and other aggravating facts. Servers are not expected to teach sentencing law, but they should understand that a bad exit plan can lead to serious public-safety and legal consequences.

RCW 46.20.308 is Washington's implied-consent statute. It addresses breath testing after DUI-related arrest and consequences for refusal or test results. A server should not give legal advice about testing; the server's role is to prevent an unsafe guest from reaching that point.

DUI prevention belongs in MAST because RCW 66.20.320 identifies driving while intoxicated and intervention with problem customers as required curriculum topics. A responsible server uses that knowledge before the guest leaves, not after a crash has happened.

Foreseeability is practical, not mystical. If a guest consumed several strong drinks, showed signs of impairment, said they were driving, refused a ride, or had keys in hand, the risk is foreseeable enough for staff action. Waiting for certainty can be waiting too long.

A responsible handoff means the person is connected to a safer exit option: sober friend, rideshare, taxi, public transportation, hotel, manager-approved waiting area, or emergency/law-enforcement support. Do not put an apparently intoxicated person in a situation that simply transfers risk to the parking lot.

If friends are involved, choose carefully. A friend who is also drinking may not be a safe driver. A friend who is angry or dismissive may not be a reliable helper. Ask simple, service-focused questions and involve a manager when the plan is unclear.

Documentation should show the chain of prevention: observed signs, refusal or pacing action, manager involvement, alternatives offered, guest response, final safe-exit plan or escalation, and staff who witnessed the event.

An incident report should read like a professional record. Use dates, times, locations, names or role descriptions, observable facts, exact refusal language when helpful, and actions taken. Avoid jokes, sarcasm, slang, insults, guesses about drugs, or medical diagnoses.

Good: 'At 10:15 p.m., guest at table 14 stumbled while standing, slurred words, and said they planned to drive. Server refused further alcohol, notified manager, offered water and rideshare, and guest left with sober friend Alex at 10:42 p.m.'

Weak: 'Customer was wasted and annoying, so we kicked him out.' That record is vague, insulting, and missing the safety steps. It does not show responsible service or give later reviewers enough detail.

Daily notes can supplement incident reports. A short shift-end note about refusals, ID issues, manager warnings, unusual events, and no-incident periods helps managers see patterns and shows that compliance is routine.

Case: A guest has consumed a high-ABV beer, two cocktails, and a shot bought by another table. They are loud, repeat the same story, drop a credit card, and say, 'I drive better after a few.' Staff refuses further alcohol and offers a rideshare.

The guest refuses the rideshare and says they will walk to the parking lot. The next step is manager involvement, another safe transportation offer, monitoring for keys or vehicle access when lawful and safe, and law-enforcement contact if the guest appears likely to drive while impaired.

The server's language should stay calm: 'I cannot serve more alcohol. We can help with a ride, call a sober friend, or let you wait with water while transportation arrives.' Do not bargain by offering one more drink if the guest agrees not to drive.

The report should include consumption known to staff, signs observed, refusal wording, alternatives offered, guest response, manager action, whether police were called, and the final known outcome. If the guest left before staff could complete the plan, document that too.