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.