Solera Harvest Guide

Winery Harvest Planning: A Technical Crush Readiness SOP

By Kevin Nesgoda, winemaker and founder of Solera ·

Last verified: August 5, 2026
Scope: Commercial winery operations. U.S.-specific OSHA and TTB requirements are labeled as such.

Direct answer

A winery harvest plan is a controlled handoff from vineyard to cellar: each expected fruit lot should have a source identity, decision-ready chemistry, receiving window, processing path, available destination vessel, approved protocol, sanitation status, responsible operator, safety controls, and records that remain linked after the fruit is split, combined, pressed, fermented, transferred, or bottled.

Harvest planning is not a calendar exercise. It is a readiness system. The plan is ready when the winery can answer, for every load: What is coming, when is it coming, where will it go, what must happen to it, who owns each decision, what could stop the operation, and what record proves what happened?

This guide is written as an operating framework for commercial wineries. It deliberately does not prescribe a universal harvest Brix, YAN target, sulfite dose, fermentation temperature, sanitizer concentration, tank headspace percentage, or equipment setting. Those values are condition-dependent and belong in wine-specific protocols, product labels, manufacturer instructions, and site-validated SOPs.

Purpose and scope

Use this SOP to prepare the winery from late-season maturity sampling through stable fruit receiving and active fermentation tracking. It covers:

It is not a recipe for a particular wine style. A sparkling base wine, aromatic white, high-solids red ferment, carbonic lot, botrytis-affected fruit, smoke-exposed fruit, high-Brix must, or spontaneous fermentation can require materially different processing and analytical controls.

Preconditions: what must exist before the plan can go live

Assign one accountable owner for the harvest master plan. That person can delegate tasks, but changes to pick windows, destination vessels, lot identity, processing protocols, or safety holds need an explicit owner and a visible change record.

Before first fruit, confirm that the winery has current versions of:

  1. the expected fruit and receiving schedule;
  2. a vessel availability and working-capacity register;
  3. crush, press, transfer, inoculation, addition, sampling, sanitation, and emergency SOPs applicable to the planned work;
  4. current product labels and safety data sheets for hazardous chemicals used by the cellar;
  5. equipment manuals and site-specific lockout/tagout procedures where required;
  6. trained and authorized operators for covered equipment;
  7. lab methods, calibration records, standards, reagents, sample containers, and escalation thresholds;
  8. a lot-ID convention that survives splits, merges, press fractions, transfers, barrel downs, blending, and bottling;
  9. a process for recording deviations, holds, rework, loss, and disposition.

Iowa State University Extension recommends winery SOPs that make the responsible person, materials, procedure, and hazards clear. That is the standard this harvest plan should meet.

Safety gate: stop work before you improvise

Harvest pressure is not permission to bypass a safety control.

CO2 and fermentation atmospheres

Fermentation carbon dioxide is a serious cellar hazard because it is colorless and odorless. Smell is not an atmospheric test. Current OSHA chemical data for carbon dioxide list an OSHA permissible exposure limit of 5,000 ppm as an 8-hour time-weighted average. The same OSHA page reports the NIOSH recommended exposure limit of 5,000 ppm TWA, a NIOSH 30,000 ppm short-term exposure limit, and a NIOSH 40,000 ppm immediately dangerous to life or health (IDLH) concentration. NIOSH's Pocket Guide independently confirms those NIOSH values.

Those numbers are occupational exposure criteria with different meanings. They are not a DIY alarm-setting recipe. Ventilation design, detector placement, alarm logic, response procedures, state-plan rules, worker activity, cellar geometry, fermentation load, and rescue planning all require competent site-specific assessment.

Tanks and confined spaces

Under U.S. federal OSHA general-industry rules, a space can be a confined space when it is large enough to enter, has limited or restricted entry or exit, and is not designed for continuous occupancy. A space with the potential for a hazardous atmosphere can become permit-required. See 29 CFR 1910.146.

Oregon OSHA's winery-specific Confined Spaces - Winery Vessels hazard alert warns that simply blowing air into a tank is not enough to establish safety and that the atmosphere must be tested under the applicable confined-space procedure.

Stop-work rule: nobody places their head or body into a tank, vat, sump, pit, or similar space unless the winery has determined which confined-space procedures apply and the required controls are in place. Never attempt an improvised rescue into a hazardous atmosphere.

Machinery, forklifts, and chemicals

In U.S. general industry, 29 CFR 1910.147 covers servicing and maintenance when unexpected energization, startup, or stored-energy release could injure a worker. Do not clear, service, or disassemble crush equipment, presses, pumps, conveyors, or similar machinery by improvising around hazardous energy.

For powered industrial trucks within 29 CFR 1910.178, operators must meet applicable training and evaluation requirements and the truck must be examined before being placed in service. A harvest staffing plan that assumes an unqualified intern can “just run the forklift” is not a valid plan.

For covered hazardous chemicals, the U.S. Hazard Communication standard requires hazard information, labels, safety data sheets, and worker training within its scope. Harvest chemical staging should therefore include the current SDS, correct labeling, PPE and handling controls defined by the product and site program, and a spill/exposure response path.

Build one harvest control table

The core planning artifact should be one operational table, not separate vineyard, lab, cellar, and logistics spreadsheets that disagree by the time the first truck arrives.

Field What it controls Required before release?
Source grower / estate block commercial and vineyard identity Yes
Variety / clone where relevant production plan and traceability Yes
Winery lot ID continuity through every operation Yes
Expected quantity receiving and vessel capacity Yes
Pick window and dispatch status labor, scale, crushpad sequencing Yes
Transport / bin or load identity chain of custody and receiving Yes
Latest representative sample pick decision context Yes
Required intake tests lab workload and hold points Yes
Fruit-condition risk sorting, microbial and processing plan Yes
Processing route destem/crush/whole cluster/press or other approved protocol Yes
Destination vessel capacity and cellar traffic Yes
Vessel sanitation state release to receive product Yes
Protocol / work-order set execution Yes
Winemaker approval decision accountability Yes
Exception owner recovery when reality changes Yes

The table should show both planned state and actual state. When a truck is late, a tank is not ready, fruit arrives outside specification, or the press goes down, the plan must preserve the original intent while recording the approved change.

Gate 1: fruit readiness

Do not pick from one number

Oregon State University Extension's peer-reviewed harvest chemistry guide identifies Brix, pH, and titratable acidity as standard grape compositional measurements and notes that YAN and malic acid can also be relevant near picking or once fruit is in tank. It also stresses that representative sampling is the first critical step.

That matters because Brix is not the same thing as fermentable glucose plus fructose, and pH is not interchangeable with TA. A technically defensible pick decision therefore records the data in context rather than treating a single Brix number as a universal harvest trigger.

At minimum, the decision record should capture:

Treat fruit condition as a process variable

UC Davis notes in its Harvesting Conditions guidance that greater fruit damage can support larger microbial populations before fermentation and that harvest temperature, oxygen exposure, rot, and holding conditions can influence the pre-fermentation flora.

So the harvest plan needs more than a chemistry column. Add a condition flag for rot, dehydration, damaged fruit, excessive MOG, smoke-exposure concern, extended transport, temperature concern, or another winery-defined risk. That flag should route the lot to a specific decision owner before routine protocol is applied.

Gate 2: capacity and throughput

Do not plan against a tank's nominal nameplate volume if the real process requires foam allowance, thermal expansion allowance, headspace, cap volume, fittings clearance, or another operating constraint. Store a validated working capacity by operation for each vessel.

Use these planning equations:

Available working capacity

validated working capacity for the planned operation - current occupied volume - committed incoming volume

Required average crushpad throughput

projected inbound tons / available processing hours

Projected material need

projected production quantity x validated historical usage per unit x winery-selected contingency factor

The equations are simple. The inputs are the hard part. The working capacity must come from the vessel/equipment specification and the winery's validated process, not an internet headspace percentage. Historical material usage should be normalized to the same production basis and reviewed for changes in fruit, protocol, packaging, supplier, or equipment.

Run a constraint review, not just an equipment count

Check the entire product path:

For every bottleneck, define the backup path before fruit is on the truck. A backup path is not “call someone.” It names the alternate equipment or vessel, who can authorize the switch, how lot identity survives the change, and what happens to the receiving schedule while the constraint is active.

Gate 3: cleaning and sanitation readiness

Cleaning removes soil and deposits. Sanitation controls microorganisms on an already cleaned surface. The sequence matters. AWRI's winery cleaning guidance explicitly states that cleaning must occur before sanitation so the sanitizer can contact the surface.

Before harvest, verify each product-contact system by cleanability and release status, not by appearance alone:

System Release evidence to define in the winery SOP
Receiving hopper / sorting equipment visibly clean, sanitation step complete where required, no chemical residue or foreign material
Crusher / destemmer guards and machine safety restored after cleaning, product-contact surfaces released
Press drains, screens, membrane/basket and transfer path inspected and released
Pumps / hoses / fittings correct cleaning circuit completed, connections protected from recontamination
Tanks / vessels cleaning and sanitation record complete, status visible, prior lot/material removed
Sampling tools clean/sanitized as method requires, dedicated storage prevents recontamination

Do not copy a sanitizer concentration, contact time, temperature, or rinse rule from a generic checklist. Proprietary products vary in active ingredient concentration and instructions, surfaces differ, water chemistry matters, and soil load changes the job. Use the current manufacturer label/SDS and the winery's validated sanitation SOP. If the winery changes product, concentration, equipment, water source, or process, review the validation before assuming the old procedure still applies.

Gate 4: lab readiness and fermentation control

The harvest lab fails operationally when a result exists but cannot be trusted, linked to the right lot, or acted on in time.

Before first fruit, create a method matrix:

Test Sample point Method/version Calibration/QC Decision supported Escalation owner
Brix or density method vineyard/intake/ferment as appropriate winery method instrument-specific maturity or fermentation trend winemaker
pH grape/must/wine as appropriate winery method current buffers/QC acid and microbial-risk context enologist/winemaker
TA grape/must/wine as appropriate winery method titrant/QC defined acidity and sensory context enologist/winemaker
YAN must/juice when relevant validated method/external lab method-specific nutrient plan winemaker
Malic acid as required by wine plan validated method/external lab method-specific MLF and acid planning winemaker
Temperature vessel/process point calibrated device device check kinetics/process safety/quality cellar lead

Do not turn the matrix into a universal target table. OSU specifically notes that YAN needs depend on must composition and yeast demand and that pH behavior depends on grape and wine chemistry. The right harvest plan therefore stores the winery-approved target or action threshold for that lot, together with who approved it and which method generated the measurement.

If a measurement changes a cellar action, the measurement, decision, and resulting work order should remain connected.

Gate 5: grape receipt and lot continuity

A receiving record should be designed so the lot can still be reconstructed months or years later, after it has been split across tanks, combined with another source, pressed into fractions, barreled down, blended, or bottled.

For U.S. bonded wine premises, this is more than an efficiency preference. TTB's current What Happens After Qualification page explains that required records include winemaking materials received and used, bulk wine records, bottling records, transfers in bond, and taxpaid removals. 27 CFR Part 24 Subpart O contains the controlling record provisions.

For basic winemaking materials, 27 CFR 24.315 requires records including the date received, quantity received, source, and date of use or other disposition. The same Subpart O requires records sufficient to verify wine label information from source material through removal for consumption or sale.

For the downstream reporting bridge, see Solera's TTB Form 5120.17 line-by-line guide. California bonded wineries can also cross-check the broader California winery compliance guide for state and federal obligations outside this operational SOP.

Minimum operational intake record

Capture:

The regulation does not require that those fields live in one software screen. TTB states that required records may be kept in any format that accurately reflects operations. The operational goal is stronger: one identifier should let a winemaker traverse the chain without reconstructing it from memory.

First-load procedure

Treat the first fruit of the season as a controlled commissioning run, even when the equipment worked perfectly in a water test.

  1. Confirm identity before movement. Match the arriving load to the expected source and lot. If identity is uncertain, hold the load under a temporary receiving identifier instead of guessing.
  2. Capture receiving quantity. Record the applicable scale/weight information and source documents.
  3. Create or confirm the winery lot. Make the link between source material and cellar lot before the load is split or combined.
  4. Pull the required intake sample. Use the winery's sampling SOP and preserve sample-to-lot identity.
  5. Assess fruit condition. Record condition flags that can change sorting, processing, microbial strategy, press decisions, or lab testing.
  6. Verify the destination. Confirm the vessel ID, current contents, validated working capacity for this operation, sanitation release, valve/path configuration, and lot compatibility.
  7. Run the approved processing protocol. Operators should see the current protocol and any lot-specific deviations.
  8. Record actual movement. Capture source, destination, measured quantity, time, operator, and equipment/work-order references.
  9. Close the loop. Update vessel state, lot state, lab queue, downstream task queue, and exception log before the crew mentally moves on to the next truck.

If any hold point fails, stop the normal flow and route the issue to the named decision owner. The safest time to resolve an identity or vessel error is before product moves.

End-of-shift reconciliation

Do not wait until the end of harvest to discover that the plan and cellar diverged.

At each shift handoff, reconcile:

The purpose is not to force every physical quantity to match perfectly in real time. It is to expose unexplained differences while the people, equipment, and source documents are still available to resolve them.

Troubleshooting and decision table

Condition Immediate control Decision owner must resolve
Fruit arrives before planned window keep source identity intact; verify receiving and destination capacity accept, hold, divert, or reschedule process
Fruit condition differs from plan flag lot and pull required sample before routine treatment sorting, processing, analysis, microbial and disposition plan
Destination vessel unavailable do not silently substitute alternate vessel, capacity, sanitation, compatibility, lot record change
Lab backlog blocks decision prioritize decision-critical tests; document temporary hold whether processing can proceed without the result
Press/crusher/pump unavailable apply safe shutdown and equipment-specific energy-control procedure where required approved backup path and schedule impact
Sanitation release fails place equipment/vessel on hold reclean/resanitize, investigate failure, authorize release
Lot identity is missing or ambiguous quarantine the identity problem before blending or transfer source verification and documented correction
CO2/atmosphere alarm or unsafe reading follow site emergency/evacuation procedure; prevent entry competent safety response and re-entry criteria

Records to capture and retain

The harvest package should leave a durable trail of:

For U.S. bonded wine premises, 27 CFR 24.300(d) within Subpart O generally requires covered records to be retained for at least three years from the record date or the date of the last required entry, whichever is later, and authorizes TTB to require up to three additional years when necessary. Other legal, contractual, certification, insurance, or quality-system requirements may require longer retention.

A practical harvest readiness checklist

Fruit and schedule

Cellar and equipment

Sanitation and chemicals

Lab and fermentation

Traceability and records

Safety

Frequently asked questions

What should be in a winery harvest plan?

At minimum: source lots, expected quantities, pick and receiving status, representative chemistry, fruit-condition risks, processing route, destination vessel, validated working capacity, sanitation release, required lab work, responsible decision owners, cellar work orders, safety controls, and traceability records from source through every split or merge.

Does Brix determine the harvest date?

No. Brix is useful, but it is not the same thing as fermentable glucose plus fructose and it does not capture pH, TA, YAN, malic acid, fruit condition, sensory maturity, weather risk, logistics, or wine style. OSU Extension recommends representative sampling and interpreting grape chemistry in context.

How much headspace should a fermenter have?

There is no universal percentage that belongs in a general harvest guide. Required working space depends on vessel geometry, must type, cap behavior, fermentation kinetics, temperature, process, gas management, fittings, and manufacturer limits. Use the vessel/equipment documentation and a winery-validated working capacity for the specific operation.

Can one sanitation recipe be used for every tank, hose, barrel, and bottling component?

No. Cleaning method, sanitizer, active concentration, contact conditions, compatibility, soil load, and rinse requirements differ by product and surface. Use the current product label/SDS, equipment compatibility information, and a validated winery sanitation SOP. Cleaning should precede sanitation when soil must be removed for sanitizer contact.

What happens if fruit arrives and the planned tank is not ready?

Treat that as a controlled deviation. Preserve the fruit's identity, stop the automatic routing, verify an alternate vessel's working capacity, sanitation status and compatibility, obtain the required approval, then record the actual destination. Never fix a capacity problem by creating a traceability problem.

How often should the harvest plan be updated?

Update it whenever new information changes a real decision: pick timing, quantity, fruit condition, arrival sequence, vessel availability, equipment state, lab hold, staffing, safety status, or processing protocol. During active crush, reconcile and hand off unresolved exceptions at every shift change.

How Solera can support the workflow

Solera's current product specification marks lab logging, fermentation vessel tracking, closed-loop cellar work orders, sanitation/CIP workflow, weigh-tag recording, crushpad intake management, and a harvest logistics dashboard as live capabilities. Used correctly, those tools can keep the receiving record, vessel state, lab result, work order, and lot history connected instead of recreating the harvest after the fact.

The operating principle is more important than the software: record the event when it happens, preserve the lot relationship, and make the next decision from the current state.

See Solera's winery operations features.

References

Enology and winery operations

U.S. safety

U.S. wine records

Limitations and disclaimer

This guide summarizes technical and official information available as of August 5, 2026. Winery conditions, equipment, products, wine styles, jurisdictions, permits, labor rules, food-safety programs, and state OSHA plans vary. Confirm safety-critical work with your site's qualified safety personnel and current authority requirements. Confirm material regulatory decisions with TTB, the responsible regulator, or a qualified adviser.

This page intentionally does not substitute generalized online ranges for a winery's validated process, a chemical label/SDS, an equipment manual, a laboratory method, or a site-specific safety program.

Version history

Start your 30-day free trial

Disclaimer: This guide is for informational purposes only and is not legal, tax, or compliance advice. Verify all requirements with the relevant regulatory agency.