Harvest Timing Decisions and PHI Record Keeping in Vineyards

By VitiScribe Editorial·March 15, 2025·Updated April 18, 2025

Spray records must be verified against PHI before harvest to avoid product rejection. That sounds obvious, but in the pressure of harvest season, with multiple blocks ripening at different rates and a winery pushing for delivery dates, it's exactly the kind of check that gets skipped.

TL;DR

Harvesting within a product's PHI is an illegal application under federal FIFRA and California law -- the consequence is not just a fine but potential fruit rejection, regulatory investigation, and recall liability if residue is discovered in processed wine
The PHI review process has five steps: pull the block spray log, check PHI for every product applied (tank mixes are governed by the longest PHI in the mix), cross-reference against the winery's requested pick date, document the review with a dated note, and plan late-season sprays around remaining harvest windows
For multi-block operations, blocks included in the same spray event but scheduled to harvest on different dates each need individual PHI calculations -- the clearance date for Block 2 harvesting September 1 is different from Block 7 harvesting September 20 even if they received the same spray
Field-level records lumping multiple blocks together ("applied to east blocks") are legally insufficient for PHI compliance if one of those blocks was harvested within PHI -- block-level records are required
For organic operations, late-season PHI review must simultaneously confirm both PHI clearance and OMRI listing status -- both conditions must be met, not just one
VitiScribe displays the earliest harvest date for each block automatically from your logged application dates and product PHIs, updating each time you log a new application

VitiScribe automatically calculates the earliest safe harvest date from your last application and PHI. That automation isn't a convenience feature. It's the thing that keeps a late-season fungicide application from becoming a rejection and a regulatory violation.

What's at Stake With PHI Compliance

The pre-harvest interval is a label requirement, not a suggestion. Applying a pesticide within its PHI of harvest is an illegal application under federal FIFRA and California law. The consequences go beyond a fine.

If fruit is harvested with pesticide residues exceeding tolerance levels, because PHI wasn't respected, the winery can reject the load. If the residue shows up in wine that's already been processed, the recall and liability costs are substantial. CDFA can assess civil penalties, and in some cases the DPR investigates as a misuse case.

The documentation problem compounds the legal one. If you can't produce spray records showing PHI was respected, you have no defense. The absence of records is treated as non-compliance.

How to Verify PHI Compliance Before Harvest

Step 1: Pull the Spray Log for Each Block

Before committing to a harvest date for any block, pull the complete spray log for that block for the current season. You need the date of the last application of each product applied.

If you're managing 10+ blocks, do this systematically, not from memory. A single missed product, especially a late-season fungicide applied to suppress botrytis, can put you in violation.

Step 2: Check PHI for Every Product Applied

For each product in the spray log, look up the PHI and calculate the earliest safe harvest date from the last application. For multi-component tank mixes, the longest PHI in the mix governs.

VitiScribe displays the earliest harvest date for each block automatically, calculated from your logged application dates and each product's current registered PHI. This calculation updates every time you log a new application.

Step 3: Cross-Reference Your Winery Pick Date

If the winery has requested a specific pick date, verify it against your PHI-calculated earliest safe harvest date for every block being harvested. If there's a conflict, the PHI wins. You'll need to push the pick date or discuss alternatives with the winery.

Step 4: Document the PHI Review

The review itself should be documented. Note in your spray log or harvest planning record that you performed a PHI review on a specific date, who conducted it, and what the earliest safe harvest date was for each block. This creates an audit trail showing due diligence.

Step 5: Plan Late-Season Sprays Around Harvest

For any late-season applications, especially botrytis fungicides near harvest, confirm the harvest window before applying. If Block 5 is expected to pick in 21 days and you're considering a fungicide with a 30-day PHI, that's a conflict. VitiScribe flags these conflicts in your spray calendar before you schedule the application.

See the harvest block spray clearance guide for the complete harvest clearance report process, including timing for multi-block operations and sequential pick situations.

The Multi-Block Challenge

The PHI problem gets complex fast when you're managing multiple blocks with staggered pick dates. Block 2 might harvest a full two weeks before Block 7, but if Block 2 is included in the same spray event as Block 7 and that spray has a 21-day PHI, you have a problem with Block 2 even if Block 7 is fine.

Multi-block spray records in VitiScribe handle this automatically. When you log a spray across multiple blocks, each block gets an individual PHI calculation based on its own planned harvest date. If any block shows a conflict, you see it before the application goes in.

Tracking by Block Is Non-Negotiable

Field-level records that lump multiple blocks together create ambiguity. "Applied to east blocks" is legally insufficient if one of those blocks was harvested within PHI and you need to prove compliance. Block-level records with GPS verification remove that ambiguity.

See the PHI and REI guide for viticulture for more on how PHI is calculated and what regulators look for in records.

PHI Records and the Winery Relationship

Increasingly, wineries are asking for spray records before accepting fruit. Large buyers, particularly those with branded wines or export markets, have pesticide residue management programs that require grower documentation.

Your PHI-verified spray log is the core document in that relationship. A clean, complete record showing every application and the corresponding PHI clearance date is what a winery's quality manager needs to sign off on incoming fruit.

VitiScribe's block spray history report exports as a PDF or CSV formatted for winery buyer review. See the vineyard spray log compliance hub for the full picture of what compliance-ready spray records look like.

Harvest Timing in the Context of Organic Certification

For organic operations, PHI compliance overlaps with organic material compliance. Every product applied near harvest needs to be OMRI-listed or otherwise approved, in addition to having its PHI cleared. VitiScribe's organic material flag works alongside PHI tracking, so you're verifying both material compliance and timing compliance in the same record.

Vineyard Irrigation Scheduling and Record Keeping

FAQ

How do I verify PHI compliance before vineyard harvest?

Pull the complete spray log for each block being harvested. For every product applied during the season, identify the date of the last application and the product's current registered PHI. Calculate the earliest safe harvest date and compare it to your planned pick date. If any product's PHI extends past the planned harvest date, you need to delay harvest for that block. Document the review with a note in your records showing it was conducted and who performed it.

What spray records do I need to review before harvest?

Review every application recorded for the block during the current growing season, with particular attention to the most recent applications. For each application, you need the product name, application date, and current labeled PHI. Tank mixes require reviewing every component, the longest PHI in the mix governs the entire application. Pay special attention to late-season botrytis fungicides, which often have PHIs of 7-30 days and are applied close to the harvest window.

How does VitiScribe alert me to PHI conflicts with planned harvest dates?

VitiScribe calculates the earliest safe harvest date for each block by looking at every application logged and applying the current registered PHI for each product. That date is visible on the block record at all times. When you plan a new spray event, VitiScribe checks whether the application date plus PHI would conflict with the block's planned harvest date and flags any conflicts before you save the record. For multi-block spray events, each block gets its own PHI calculation based on its individual harvest date.

What documentation do I provide to the winery to confirm PHI compliance at delivery?

The block spray history report for the harvested block, showing all applications from the current season with dates, products, and PHI clearance dates, is the standard documentation provided to winery receiving teams. Some wineries request this in a specific format -- VitiScribe generates block spray history reports as PDF, which is the most widely accepted format. If the winery has a vendor compliance form that asks about last application date, last restricted-use pesticide application, or PHI clearance date for specific products, those answers come from the same spray log. For wineries with formal grower qualification programs, the spray records may be reviewed annually rather than at each delivery.

What happens if I discover a PHI conflict the morning of harvest after picking crews are already deployed?

Stop picking immediately in the affected block. A PHI violation that has already occurred -- where fruit was picked before the PHI cleared -- is a more serious situation than a conflict discovered before picking begins. Contact your PCA and winery receiving contact to explain the situation. Do not deliver the fruit from the affected block until you've assessed whether the PHI clearance date passes before the fruit deteriorates and whether the winery will accept a delayed delivery. If the fruit cannot wait and is delivered anyway, the winery may conduct residue testing. Document everything that happened, including the time of discovery and who was notified. Going forward, the morning-of harvest clearance check is the control that prevents this scenario.

What is Harvest Timing Decisions and PHI Record Keeping in Vineyards?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Harvest Timing Decisions and PHI Record Keeping in Vineyards. Target 50-150 words.]

How much does Harvest Timing Decisions and PHI Record Keeping in Vineyards cost?

How does Harvest Timing Decisions and PHI Record Keeping in Vineyards work?

Sources

California Department of Pesticide Regulation (CDPR)
UC Cooperative Extension Viticulture
Wine Institute
American Vineyard Foundation
American Society for Enology and Viticulture (ASEV)

Get Started with VitiScribe

PHI compliance at harvest is a documentation problem before it becomes a regulatory or commercial one -- and complete, current spray records are the only way to confirm clearance with confidence under harvest-season pressure. VitiScribe's automatic earliest-harvest-date calculation by block, pre-application PHI conflict flagging, and one-click harvest clearance reports give vineyard managers the tools to verify compliance before pick decisions are made. Try VitiScribe free and set up your first block with automatic PHI tracking today.