A vineyard doesn't ripen all at once, and it doesn't get sprayed all at once either. Different blocks — different varieties, different exposures, different disease pressure — run their own spray schedules across a season, and each one runs its own countdown to a harvest date the winery, not the grower alone, ultimately calls. By the weeks before pick, a working vineyard can have several blocks each carrying a different open window, on a different clock, headed toward a different truck.
That structure is what makes vineyard spray records a distinct problem from a single-block row crop, even though the underlying discipline — active ingredient, rate, lot, two intervals, two end dates — is identical. What's different is the number of blocks running independently, the sensitivity of the buyer at the end of the chain, and a harvest window that is set by ripeness and a winery's schedule rather than by the grower's own convenience. This page is about keeping a multi-block season straight when the fruit's fate is decided by someone downstream.
The label is the authority. Nothing here states a re-entry interval or pre-harvest interval for any product used in winegrapes, and you should distrust anything that does. Those intervals are set by the product label and by the regulator and certifier that govern your operation, and they vary by product, variety, and jurisdiction. What follows describes the process of recording a vineyard spray program. For the intervals themselves, the label is the source, not this page.
The block is the unit that matters, not the vineyard
A vineyard's blocks are rarely sprayed in lockstep. A block with heavier canopy or a history of mildew pressure might get an extra pass a neighboring block doesn't need. A block earmarked for an earlier-picking variety might be finishing its spray program while another, later-ripening block is still mid-season. Treating the whole vineyard as one spray record erases exactly the distinction that matters on the day someone asks whether a specific block is ready to pick.
This is the same principle described at greater length for orchard block records, applied to a crop where the stakes at the end are, if anything, higher — because the buyer at the far end of a vineyard's harvest is often running its own residue testing before the fruit is accepted.
The harvest date isn't yours to move
A row crop grower who has a pre-harvest interval running close to a planned harvest date has some room to adjust — delay the pick a few days, if the crop and the market allow it. A vineyard has much less of that room. Grapes are picked at a specific ripeness window the winery has determined from sugar and acid testing, sometimes called on short notice once conditions hit the target, and that call is frequently the winery's to make, not the grower's alone.
This means a late-season application's pre-harvest interval has to be checked against the harvest plan well before picking day arrives, not discovered as a conflict once the winery has already called for fruit. A block sprayed too late in the season, without checking the interval against the realistic harvest window, can end up with no good options — pick early and violate the interval, or hold the fruit and risk losing the ripeness window the winery wants.
The buyer at the end of the chain is unusually exacting
Wine, more than most crops, tends to be produced for buyers who audit closely — wineries with quality programs, and especially those selling into export markets with their own residue-testing requirements. Many wineries ask growers for block-level spray records ahead of harvest: product, active ingredient, rate, and pre-harvest interval for every application made to the fruit they're buying, not a general assurance that the vineyard was farmed responsibly.
A grower who can produce that record per block, on request, without having to reconstruct it from memory or scattered receipts, is in a fundamentally stronger position with that buyer than one who can't — and that record is exactly the same one described in what belongs in a spray record, kept per block instead of per farm.
Custom applicators are common, and the record still travels with the block
Many vineyards, especially smaller ones, hire a custom applicator for at least some of the season's passes, and the same obligation described for any custom-applied pass applies here without modification: the record belongs with the block it was applied to, in your files, not only in the applicator's. Ask for the block-level detail before the applicator leaves — product, active ingredient, rate, lot number, date and time, and both intervals with their end dates — and reconcile it against your own block identifiers if the applicator uses a different naming scheme. A winery asking for a block's history a season later does not care whose sprayer applied the product; it cares whether the record exists and can be produced.
Weather still matters, block by block
Vineyards are often planted on slopes and near other agricultural or residential uses, and a drift complaint about a specific block's application is investigated the same way it would be for any crop: wind speed and direction, temperature, and humidity at the moment of that specific pass. Recording weather at the block level, alongside the product and rate, is not an additional burden so much as the same field already required, kept with the same precision the rest of a vineyard's records need.
Keeping a season of blocks straight
Farm40 lets you log an application record per block, with the active ingredient, rate, lot number, and both intervals as first-class fields, and it computes each block's end dates from the interval and date you enter — so a question about one specific block's status is a lookup rather than a reconstruction across a season of passes. Its limit is the one that applies everywhere on this site: it computes from what's entered and does not verify the interval against the label itself, so an interval typed in wrong produces an end date that's wrong with the same confidence as a correct one.
What makes a vineyard's records defensible to a winery, months later, is the discipline of keeping every pass attached to its specific block, with both intervals and both end dates written down the day of the application — so that when a buyer with a residue testing program asks for one block's history, the answer already exists rather than needing to be assembled under a harvest deadline. None of it requires software, and all of it requires the same underlying habit: write the block, the product, the rate, and both interval end dates down at the sprayer, the day of the pass, before the season's next block is already asking for the same attention.