Play the lesson aloud and follow the highlighted text. You can pause, replay, and adjust the speed.
This lesson teaches visible signs of intoxication, early prevention, pacing, water and food strategies, manager involvement, and responsible marketing boundaries.
Common signs include slurred speech, poor coordination, slowed reaction, confusion, aggressive behavior, sleepiness, spilled drinks, and impaired judgment.
A single sign may not prove intoxication, but patterns and escalation require a safer service response.
Prevention starts before refusal: observe pace, check group dynamics, offer food and nonalcoholic options, and communicate with coworkers.
Responsible service includes standard-drink awareness and avoiding service patterns that encourage rapid or excessive consumption.
Servers should involve a manager before a situation becomes confrontational or unsafe.
Escalation protects the guest, other patrons, staff, the licensee, and the public.
Signs of intoxication can appear in speech, balance, coordination, attention, mood, judgment, appearance, and interaction with others. No single sign proves every case, but a pattern should trigger action.
Examples include slurred speech, glassy or bloodshot eyes, stumbling, spilling drinks, trouble counting money, repeated questions, mood swings, aggression, drowsiness, or difficulty following conversation.
Servers should compare current behavior to earlier behavior. A guest who becomes louder, less coordinated, more argumentative, or less aware of surroundings may need slowed or stopped service.
Preventing over-service is easier than refusing service after the guest is visibly intoxicated. Early steps include pacing, offering water, suggesting food, checking in with coworkers, and slowing the next drink.
High-risk patterns include rapid ordering, rounds of shots, drinking games, large groups, special events, emotional distress, and movement between bar, table, patio, or event stations.
Servers should communicate across service areas so one guest is not served repeatedly by different staff members who each see only part of the pattern.
A manager should be involved when the server sees intoxication signs, anticipates conflict, needs backup for a refusal, or is unsure how to apply policy.
Manager support can include confirming the decision, speaking with the guest, notifying security, arranging safe transportation options, documenting the incident, or limiting service to the group.
The server should not carry a difficult decision alone when the business has a policy for support. Shared decisions help protect staff, guests, and the licensee.
Incident notes should be factual and free of exaggeration. Useful details include observed signs, drinks known to staff, time of refusal, manager involvement, witness names, and steps taken to reduce harm.
Documentation can help identify repeated risk patterns, such as certain promotions, staffing gaps, event layouts, or service practices that make over-service more likely.
Good records also support later questions from management, regulators, law enforcement, or the guest. The goal is a clear account of responsible decisions made in real time.
Before moving forward, choose one concrete action that lowers risk and respects the course completion controls.
Each module includes an interactive check before moving forward. This view lets reviewers test the pattern without a student account.