Why Protocols Beat Memory
Ask most small winemakers what they did differently in their best vintage, and they'll pause. "I think I pressed earlier... or maybe I added less SO₂ at crush?" When your process lives only in your head, you can't reproduce success — and you can't diagnose failure.
A written protocol solves this. It's not a rigid script — it's a baseline with decision points. Every vintage you either follow the protocol or consciously deviate from it and record why. Over time, you build a searchable history of what worked, what didn't, and what you'd do again.
What a Variety Protocol Covers
A complete protocol has six sections: harvest parameters, crush and prefermentation decisions, fermentation management, post-fermentation handling, aging milestones, and bottling criteria. Here's what belongs in each.
1. Harvest Parameters
Define your target ranges — not just a Brix number, but the full picture: Brix, pH, TA, and sensory cues (seed color, skin texture, flavor). For a Cabernet Sauvignon you might target 25–26 Brix, pH 3.55–3.65, TA 5.8–6.4 g/L, with seeds that are fully brown and flavors showing ripe dark fruit without green tannin.
Include your walk-away conditions too: what Brix or pH would cause you to pick earlier than ideal? What weather forecast triggers an emergency harvest call? Writing this in advance means you're not making panicked decisions in the field.
2. Crush and Prefermentation Decisions
Document your default settings: whole cluster percentage, destemming approach, cold soak duration and temperature, SO₂ dose at crush, and any enzymes added at this stage. Note the "why" next to each decision — "15% whole cluster for mid-palate texture; more than 20% gives a green note on this vineyard." That context is gold when you revisit the protocol next year.
3. Fermentation Management
This section is where most of the day-to-day action lives. Your protocol should specify:
- Yeast strain and inoculation timing — is this spontaneous, or do you pitch at a specific Brix? Which strain and why?
- YAN target and nutrient additions — initial YAN from YAN testing, your target, and whether you add Go-Ferm at rehydration plus Fermaid-O/K in stages.
- Temperature curve — starting temp, peak temp ceiling, and any deliberate cooling points.
- Cap management — punch-down vs. pump-over, frequency, and when you switch approaches as density drops.
- MLF inoculation — co-inoculation vs. sequential, which bacteria, and at what sugar level.
- Extended maceration decision criteria — how you decide whether to extend, and for how long.
4. Post-Fermentation Handling
Document your press timing criteria (density or dryness target), press fractions and how you handle them, first SO₂ addition post-press, and settling approach. This phase is often under-documented — winemakers write down fermentation details but get fuzzy on what happened between press and barrel.
5. Aging Milestones
Define your default aging vessel (new oak percentage, neutral oak, stainless, concrete), planned aging duration, racking schedule, SO₂ monitoring frequency and target free SO₂ by pH, and any topping schedule. Include your battonage protocol if you stir lees. Flag decision points: "at 6 months, bench trial blending components before finalizing cooperage split."
6. Bottling Criteria
What does "ready to bottle" actually mean for this variety? Write down the checklist: stability tests passed (protein, tartrate, microbial), free SO₂ at target, VA within acceptable range, sensory sign-off from at least two people, final blending decision documented. Don't rely on a calendar date — write the criteria the wine has to meet.
How to Create Your First Protocol
If you don't have documented protocols yet, start by reconstructing last vintage from memory and whatever notes you have. Fill in the six sections with what you actually did — even if some cells are "unknown" or "variable." That's your baseline.
Then annotate it: put a ✓ next to every decision you'd repeat, a ✗ next to anything you'd change, and a ? next to things you're unsure about. Those question marks become your experiments for next vintage.
Before harvest begins, review and update the protocol. What did you learn? What did the wine tell you? Revise the baseline and lock it in before the grapes come in — not during.
One Protocol Per Variety, Per Block
If you source from multiple vineyards, consider separate protocols for each block — even for the same variety. A Pinot Noir from a cool coastal site and a Pinot Noir from a warmer inland block may need different harvest windows, different cold soak durations, and different SO₂ management. Sharing a single protocol across them hides the information that would let you optimize each.
Living Documents, Not Archives
A protocol is only useful if you actually update it. After each vintage, run a brief retrospective: what deviated from protocol, what was the result, and what should the protocol say next time? Budget 30 minutes per variety after harvest ends. That time compounds — winemakers who do this for five vintages have something no amount of intuition can match: a documented map of cause and effect for their specific wines, their specific vineyards, their specific cellar.
Tracking It in WinemakerOS
WinemakerOS is built around exactly this workflow. Each lot gets a protocol attached at the start of the vintage. Lab entries, punch-down logs, SO₂ additions, and racking notes all connect back to the protocol so you can see, at a glance, where you followed the plan and where you improvised. At the end of the season, the system generates a vintage summary you can use as the starting point for next year's protocol.
If your winemaking notes are currently spread across clipboards, spreadsheets, and mental notes, book a demo to see how WinemakerOS brings it all into one place.