5.1 House Policies, Team Roles, and Shift Handoffs

Translate rules into daily actions

House policies are the venue's instructions for how staff carry out responsible service. Law establishes obligations and limits; policy specifies who checks, how staff communicate, which tools are used, and who responds when a problem develops. A policy can be more protective than the legal minimum but cannot make prohibited service lawful.

For example, a venue may require checking everyone under a stated apparent-age threshold or everyone entering a particular event. That threshold is an operational instruction, not a claim that the legal purchase age changed. Staff should know which rule is law and which is house policy so they can explain decisions accurately.

Write procedures that someone can execute

A usable policy answers concrete questions. Where is the ID reference? What happens if the reader fails? Who covers the service well while the bartender handles a refusal? Which manager can request emergency assistance? Avoid a policy that simply says “be responsible” without assigning work.

Staff need training before they are expected to perform these tasks independently. Confirm any legally required course or permit for each role. A general training certificate does not automatically fulfill a jurisdiction-specific requirement, and course completion alone does not prove that an employee knows the venue's actual procedure.

Portion control supports observation

Use measured recipes and suitable tools to keep pours consistent. A jigger or calibrated system helps staff understand what was served. Beer and wine also need attention to actual serving size and ABV; a standard glass does not make every product one standard drink.

A recipe specification should identify all alcoholic ingredients and their measures. Avoid defining a universal cocktail by one spirit volume while ignoring liqueurs or stronger substitutions. If the recipe changes, communicate the change to servers who describe and track it.

A house drink limit can be an additional boundary. It is never a promise that every guest may safely receive that amount. Do not infer that two drinks per hour is medically safe for everyone or that a manager can approve another drink despite a required refusal. Assess each transaction and stop earlier when circumstances warrant.

Management support makes enforcement practical

An employee who expects punishment for a safety refusal may hesitate during the next incident. Managers should support good-faith refusals, take over difficult interactions when needed, and ensure the same boundary applies at other stations. A guest's spending, status, or threat to complain should not create an exception to an unlawful sale.

Support includes practical work: covering the employee's section, coordinating a safe ride, notifying security, or documenting the event. Do not treat support as simply telling the employee to handle the guest alone. If a refusal raises a question about discrimination or a misunderstood credential, investigate respectfully and improve training without casually overriding a justified intoxication cutoff.

Make the pre-shift briefing useful

A short briefing should cover current risks and assignments, not repeat the entire handbook. Identify the manager on duty, event conditions, staffing gaps, unusual service areas, and any approved promotion. Confirm that staff know which contact method to use when a guest is refused service.

Check that equipment is available and the age-calculation reference uses the correct date. Verify that staff can find emergency contacts and the venue's address. A tool locked in an office may be functionally unavailable during a rushed transaction. Fix that access problem before the doors open.

Handoffs protect continuity

An incoming server should receive relevant information about the guests they inherit. This includes known consumption, current refusals, unresolved ID questions, and transportation arrangements still in progress. Use factual descriptions and limit personal information to what staff need for safe service.

Suppose an outgoing bartender refused a guest on the patio, but the guest moves indoors just as the shift changes. A tab note is useful only if incoming staff see and understand it. Combine available system alerts with direct communication and confirmation. Do not rely on the guest to explain that they were refused elsewhere.

Review practice, not just paperwork

After an incident, ask whether procedures were followed and whether they were workable. Did the message reach every station? Was someone assigned to meet responders? Could the guest obtain alcohol through a companion? Use the answers to improve staffing, tools, or instruction.

Keep training and policy records accurate. Do not claim policies guarantee dismissal of a lawsuit or a specific insurance discount. Their primary value is consistent safe conduct. Records can help explain that conduct, including where a process failed and what changed afterward.

Worked management example

A server notices slurred speech and refuses another cocktail. The guest demands the general manager. The manager supports the refusal, asks a colleague to cover the server's tables, and arranges assistance. The incoming shift receives the refusal information. This response connects written policy to staff roles and follow-through rather than making the server choose between safety and abandoning their section.

Sources checked October 16, 2026: TIPS measured-service and coworker-handoff guidance and TABC example of written policies within conditional safe harbor.