I’m refreshing our pre-shift wine education to tie pairings to what’s on the shelf right now, not idealized bottles. Thinking a 20-minute weekly lab: one menu item, two SKUs we have in adjacent bins, blind side-by-side, then track Coravin day 0/48/72 to talk oxidation, pour yield, and when to pivot a pairing as vintages turn — anyone tried this and have tips for making FOH and BOH both engage?
We’ve been running a 15–20 min “speed dating for SKUs” and the biggest unlock was a laminated card: menu item, two bins, day 0/48/72, and a single line to note “pivot if aromatics flatten or acid spikes at 48h.” Assign one server as scribe and pour the blind with the fast Coravin needle but log yields with the standard needle so cost and oxidation are apples-to-apples; small caveat, swap in one slow-mover each week so FOH practices selling through laggards. If you track last-glass sales after the drill, you can show the pairing’s real lift the next shift.
Quick tip: we added a single “say this at the table” line to the card — after the blind, each server writes a 10-word pivot script (e.g., “more acid? shift to Bin 12 Verdicchio”) so FOH uses the change; small caveat: we cap Coravin checks to two days to keep capsule cost sane, @myoung.
Run one SKU at cellar temp and the other about 10°F colder during the same 20-minute lab; we’ve salvaged pairings that way without changing bins. Building on @myoung’s card, add a temp line and a simple rule like “pivot if still muted at 50°F.” For speed, use the Coravin Fast Pour needle in drills — just know it chews through gas.
the Coravin Fast Pour needle in drills — just know it chews through gas. Agreed — we swap to the Standard needle for trainings. We also keep a gram scale by the bins; @OP we weigh bottles pre/post and use about 150 g ≈ one 5‑oz pour to forecast yield and decide when to pivot, but wipe the neck on older reds or the numbers drift.
My take: I’d lean toward the simplest next step and see if it changes anything this week — if not, you’ve got a clear case to escalate. What would block you from trying that?