How to Train Staff on Craft Beer and Taproom Knowledge

Here's what actually happens. You get a fresh keg of something local on a Tuesday. Your sales rep is excited about it. You're excited about it. You write it on the chalkboard. And then a guest at table six asks your server what it tastes like, whether it's hoppy, whether there's wheat in it, and your server says "I think it's pretty good" and walks away. That guest ordered water.

You paid for that keg. You paid for the chalkboard art. You didn't pay for training.

The problem isn't that your staff is bad at their jobs. The problem is that craft beer knowledge is genuinely technical and it changes constantly. An IPA tastes nothing like a gose. A New England-style IPA is a completely different drink than a West Coast IPA, even though they share four letters. Sours can range from barely tart to face-puckering. Stouts can be bone dry or taste like a dessert. Staff can't fake their way through those distinctions the way they might with a wine they've never tasted. Beer guests ask specific questions. They know what they know.

So if you're rotating your taps every couple weeks, you're also rotating your training problem. Every new keg is a new knowledge gap until you close it.

Let me tell you what actually matters when you're building out beer training for a rotating list.

Start with the framework, not the individual beers. If your staff understands the basic style categories and what they mean, a new IPA on the list isn't a mystery. They already have the bucket. The bucket just has a new can in it. West Coast IPAs: clear, bitter, piney or citrusy, dry finish. New England IPAs: hazy, low bitterness, stone fruit and tropical, soft mouthfeel. Sours: produced with wild yeast or bacteria, tart, often fruity, sometimes funky. Wheat beers: hefeweizens, witbiers, Berliner weisses. This last category matters because wheat is an allergen, and it shows up in more beers than guests realize.

That allergen angle is where I get genuinely serious with staff at both of my places. Hefeweizens are made with wheat. Witbiers, same. Some white IPAs, same. A lot of craft breweries don't filter their beers, which complicates things further. A guest with celiac disease or a serious gluten sensitivity isn't asking about wheat because they're curious about the grain bill. They're asking because they'll get sick. Your staff needs to know which beers on your current list contain wheat and which are either gluten-free or brewed from gluten-free grains like sorghum or millet. Not a rough guess. The actual answer, for the actual beers on tap right now.

This is where the rotating list becomes genuinely dangerous if you're not keeping training current. A beer that was on tap six weeks ago was wheat-free. The one that replaced it is a hefeweizen. If your staff is still working off the knowledge from the previous keg, you've got a problem sitting in that glass.

The old way to handle this was a printed beer menu update, maybe a quick pre-shift rundown if the manager remembered, and then crossing your fingers that servers retained it. That's not a system. That's hoping.

What actually works is getting the new information into staff heads fast, confirmed, not just assumed. When a new keg comes on, someone needs to build a short set of questions around it. What style is it? How does it taste? Who made it? Is there wheat in it? Is it gluten-free? What food on your menu does it pair with? Staff answers those questions on their phones before service, not the next time they happen to notice the chalkboard. That's the gap you're closing. Not the knowing, the confirming.

At Black Barrel Tavern we don't wait for staff to osmose beer knowledge through shift experience. We push it to them when the information is new, which is when it matters. That's what the platform I built does, and it works exactly the same for a new tap as it does for a seasonal menu item. Upload the info, questions get generated, staff gets quizzed. The whole thing takes minutes to set up on our end.

But even without any platform, the discipline matters. The question you're asking yourself isn't "did I tell them about the new keg?" It's "can they answer a guest's question about it right now?" Those are two different questions. Telling is not training.

One more thing worth saying. Beer-knowledgeable staff sell more beer. This is just true. A server who can say "it pours hazy, it smells like mango and peach, it's smooth with almost no bitterness, honestly if you like wheat beers you'll love it" is going to move that keg. A server who says "it's an IPA" is going to get a lot of "I'll just have a Modelo." Your tap program is a revenue line. The training that supports it is not optional overhead. It's part of what you paid for when you signed that distributor invoice.

Keep the style framework in their heads. Keep the allergen list current every time a keg rotates. Confirm they know it, don't just assume they heard it. That's the whole system.

Have a great day! — Terry Psaltakis
Your AI Restaurant Guy