TL;DR: Classics training fails in almost every bar, and the list is rarely the problem. The program is the problem. Build a short scoped list, run weekly micro-sessions, lock down one recipe standard, and measure competency in a way your team can actually pass.
Every bar owner nods when you say "we should be doing more classics training." Then Tuesday happens. The shipment is wrong, the walk-in is down two degrees, someone called out, and the Monday training sheet is sitting face-down on the prep counter.
I've watched this play out in around 40 bars. The owners genuinely want it. The staff genuinely wants it. And then week two arrives and it's gone, buried under the operational weight of actually running a bar.
The bars where it stuck didn't have better lists or extra hours. They had a better program. Five things, specifically. Those five things are the whole article.
This is not about memorizing recipes. The staff you hired are adults who can read and build drinks. This is about the operational structure that turns knowledge into consistent execution, and consistent execution into something measurable.
The failure usually starts before the first session. Here's what it actually looks like in practice:
The program is the problem. Not the people.
The 80/20 rule applies here as much as anywhere. Your guests order a relatively small range of classics with regularity. A well-scoped core list covers the drinks that actually move, the drinks that communicate craft to a knowledgeable guest, and the drinks that your bar specifically wants to be known for.
Six drinks per major category is a workable ceiling for the core list. That's enough to cover the territory without being paralyzing. Build out from there once the core is solid.
Chris Lowder put out a 2016 list called "The 178 Classics to Know" that's still a great starting template for figuring out which drinks belong in scope. It's thoughtfully organized and gives you a map of the territory. Don't make your team learn all 178 at once, but it's a smart reference for building your own short list. Worth the shoutout.
The goal is not to know everything. The goal is to know the right things cold.
Every bar with more than three bartenders has the "my old bar did it this way" problem. It's not a character flaw. People bring their training with them and that training varies. The problem is structural.
Fix it structurally. Pick one version of every drink on the core list. Document it. That's the bar's version. Full stop.
Your lead bartender or beverage director owns that document. They're responsible for resolving disagreements before they reach the floor. If two bartenders have a legitimate debate about a recipe, that's a great conversation to have at a tasting. Settle it, document the outcome, and move on. The guest does not experience the debate. They experience the drink.
When the standard changes, the document changes. One person updates it. Everyone else uses the updated version. The system doesn't depend on institutional memory or word of mouth.
A three-hour Sunday training seminar feels productive. By Wednesday, most of it is gone.
Fifteen minutes, three times a week, is a different experience entirely. You're tasting one drink. You're building it two ways, maybe with a small variation in technique or ratio, to understand why the standard is what it is. You're having a real conversation about it. And you're done before the shift starts.
This format fits inside a real bar week without requiring a scheduling miracle. It also compounds. Three sessions a week over a month covers twelve drinks in a way that actually sticks, because each one gets repeated exposure and real context.
The session leader rotates. Not every week, but enough to force deeper preparation and build ownership across the team. Keep brief notes on what was tasted, when, and who attended. That becomes your training record without extra administrative lift.
Quarterly. Quiet. Five drinks, pulled randomly from the core list, built from memory. The evaluator isn't looking for perfection. They're looking for consistency with the standard.
Pass means a bonus or a training stipend. Name the number and pay it. Fifty dollars, a hundred dollars, whatever your margin allows. The amount matters less than the fact that you put real money behind it, because that tells the staff that competency is worth something to the bar and not an unfunded mandate.
Fail means two weeks to retake. No penalty beyond that. The goal is not to catch people out. The goal is to give the program a measurable endpoint and reward the staff who invest in it.
Tone matters more than the mechanics here. If this feels like surveillance, it will be resented and gamed. If it feels like a milestone, most of your staff will take it seriously. Frame it as a milestone. Pay out when they pass.
The binder doesn't work as onboarding. The new hire is already managing a new environment, new colleagues, new POS, new layout, and new expectations. A three-inch binder of recipes is not going to land in week one.
Here's what works: in the first two weeks, the new hire tastes every drink on the core list with the lead bartender. Together. During prep, not as homework. The lead bartender builds the drink, talks through why it's made this way, and the new hire tastes it. The new hire asks questions. The lead bartender answers them.
This takes maybe thirty minutes across several prep shifts. It is also the most efficient onboarding a bar can run, because the new hire learns the bar's standard from the person who owns it, before they're on the floor trying to figure it out under pressure.
It also tells the new hire immediately that the bar takes this seriously. That signal matters for retention.
Don't measure trivia. Measure behavior.
Time-to-competency for new hires. How long from first shift to passing the quarterly competency check? A well-run program should get a new hire there in under 30 days. If it's taking 90, the onboarding isn't working.
Guest return rate on signature orders. Guests ordering your signature classics and coming back is the signal. One-time orders with no repeat means the drink isn't landing the same way twice.
Staff retention past 90 days. A bar where staff feel competent and invested in retains better. Track the 90-day number. If it's low, training program design is one place to look.
None of these require a software build. A spreadsheet and honest attention to your own floor will get you there.
Most programs that survive the first three months die quietly in month fourteen. Here's the pattern:
The program stops being refreshed. The core list from year one is fine for year one. By year two, your menu has evolved, your guest base has shifted, and the program is teaching drinks that don't match the bar anymore. Someone needs to own the annual review of the list. Put it on the calendar now.
New recipes don't go through the standard process. The bar adds a new drink. The bartender who developed it teaches it informally to whoever asks. Three months later there are four versions on the floor and nobody knows which is right. Every addition to the core list goes through the same recipe standard process. No exceptions.
Leadership stops attending tastings. When the owner or GM stops showing up to micro-sessions, the message is that this doesn't matter anymore. It doesn't have to be every session. But visible leadership participation is what keeps the program from becoming an afterthought.
The lead bartender leaves and the standard goes with them. This is the most common failure and the most preventable. The standard lives in the document, not in one person's head. If your recipe standard document is thorough enough that someone new could own it on day one, you've built the thing correctly. If it's not, fix it before the lead bartender gives notice.
How long should the core list be?
Start with 30 to 40 drinks. That's enough to build real fluency without making the program feel infinite. Organize by category and make sure the list covers the range of your actual menu and the classics your guests order. Once the team has genuine competency across the core, you can build out from there.
What if my bar already has a different list?
Use it. The list is the least important part. Audit it for scope, make sure each drink has a documented standard, and build the program structure around what you already have. You don't need a new list. You need a program.
Do I really need a paid competency check?
You don't need to pay for it. But you'll get better results if you do. Paying out for passing tells the team that competency has real value to the business. It also makes the check feel earned rather than punitive. If your margins genuinely can't support it, a non-monetary reward (a shift trade, a bottle, public recognition) works better than nothing. But the paid version produces better engagement, and the cost is modest.
Who owns the recipe standard when the lead bartender leaves?
The person who steps into the lead role takes ownership. This is only a crisis if the standard document is incomplete or lives inside one person's memory. A good recipe standard document should be transferable. The departing lead bartender should walk their replacement through it before they leave. Make that handoff part of the offboarding process.
How do I get buy-in from a team that's been "training" for years and isn't excited about another one?
Don't tell them it's a training program. Tell them you're standardizing the bar's recipes and you want their input on how the drinks should be made. Run the first tasting as a collaborative session. Let the team argue about ratios and techniques and resolve it together. The standard you land on will be better for it, and the team will have ownership of it. People defend things they helped build.
If you're running a bar program and want help building the operational backbone behind this kind of training system, ASM Command is built for exactly that. Start at jlittrell.com.
If you run a service business and want the operational system behind programs like this, the same architecture applies. kmsops.com/connect is the place to start.
More playbooks like this one come out regularly in The Ops Wire. You can find it at theopswire.substack.com.
Jason Littrell spent 10 years behind the bar in NYC, including Death & Co, and served as USBG NYC president. He now runs his hospitality consulting firm entirely on AI. He hosts the Hospitality Strategy Lab podcast and writes The Ops Wire newsletter.
Jason