Vine Disease Spray Records: Documentation Requirements for Every Major Vineyard Disease

By VitiScribe Editorial·December 1, 2025·Updated February 2, 2026

California wine grapes receive an average of 11 disease-targeted spray applications per season. That's 11 opportunities for a record-keeping error that could trigger a DPR citation, fail a third-party audit, or cost you a winery contract. Keeping those records straight -- by disease, by product, by block -- requires a system that understands the difference between a botrytis fungicide at harvest and a powdery mildew spray at bloom.

Most spray log templates treat all fungicide applications the same way. They capture the date, the product, the rate, and the block. That works fine for basic compliance, but it misses the details that matter when a certifier asks whether you rotated FRAC groups for powdery mildew, or whether your botrytis applications were timed to the correct phenological window. VitiScribe organizes spray records by disease target, pre-loading the correct FRAC group, PHI, and REI data for every registered product in your program.

TL;DR

California wine grapes average 11 disease-targeted spray applications per season; every application needs the standard compliance fields plus growth stage, FRAC group, and weather conditions to document an IPM program rather than just a spray calendar
FRAC Group 17 (anilinopyrimidines -- Scala, Vangard) resistance is documented in high-use California botrytis programs; Group 4 (phenylamide -- Ridomil) resistance in downy mildew; QoI resistance in black rot in eastern regions -- rotation records are not optional in any disease category
Botrytis PHI conflicts in pre-harvest tank mixes are one of the highest-risk compliance failures: a Pristine (0-day) plus Scala (7-day) mix applied 5 days before target pick creates a harvest delay that spray records need to flag before the application, not after
Pruning wound protection records must tie the application date to the pruning date -- a 5-day gap between cut and protectant application defeats efficacy and may show up as higher Eutypa incidence three to five years later when block history is reviewed
Mancozeb is a restricted-use pesticide in California; Phomopsis applications using mancozeb require certified applicator documentation and county filing within 24 hours in most California counties
Tank mixes targeting multiple diseases simultaneously require recording the most restrictive PHI across all products; VitiScribe computes this automatically from product selection

Powdery Mildew Spray Records

Powdery mildew (Erysiphe necator) is the most sprayed disease in California, Oregon, Washington, and most other US wine regions. A typical program runs from early budbreak through veraison -- sometimes 10 to 14 applications in a wet year. For compliance purposes, every application needs the standard fields: date, block, product, EPA registration number, rate, volume applied, applicator name and license number.

But for a well-documented IPM program, you need more. You need the FRAC group recorded for every application so you can demonstrate rotation. You need the weather conditions at application time, especially wind speed and direction for drift-sensitive materials like sulfur. You need the growth stage at application so your records show that you were hitting critical infection windows rather than just spraying on a calendar.

VitiScribe's powdery mildew spray template pre-loads FRAC group from your product selection, pulls the current growth stage from your phenology calendar, and captures the weather data from your connected station. You don't have to look anything up.

For resistance management documentation, the FRAC group history by block is the key report. If a certifier or a PCA asks why you stayed off QoI (Group 11) products for three consecutive applications, your VitiScribe FRAC rotation log answers the question in seconds. Learn more about FRAC rotation tracking in VitiScribe.

Botrytis Spray Records

Botrytis (Botrytis cinerea) management generates some of the most compliance-critical spray records in the vineyard season because most programs are concentrated in the 4-6 weeks before harvest. PHI matters enormously here. A botrytis fungicide applied on the wrong day can put your fruit into harvest with a residue issue, or force you to wait past your intended pick date.

VitiScribe calculates botrytis fungicide PHI automatically from the moment you log each application. As you add applications to a block, the harvest clearance date updates in real time. If you apply Pristine (0-day PHI) and then apply Scala (7-day PHI) five days before your target pick, VitiScribe will flag the conflict before you go to the field.

Beyond PHI, botrytis programs require FRAC rotation documentation because resistance is widespread. FRAC Group 17 (anilinopyrimidines -- Scala, Vangard) resistance is documented in high-use California vineyards. Group 2 (MBC fungicides -- Rovral) is similarly compromised in some regions. Your records should show that you're rotating among Groups 7, 11, 12, 17, and others rather than defaulting to the same chemistry every application.

Botrytis spray timing relative to canopy management events is also worth documenting. An application the day after bunch zone leaf removal creates a different efficacy profile than one made to a dense canopy. VitiScribe lets you log canopy work dates in the block record, so your spray history and cultural practice history are in the same place. See how scouting records connect to spray decisions in VitiScribe.

Downy Mildew Spray Records

Downy mildew (Plasmopara viticola) is predominantly an eastern US problem, but coastal California, Oregon, and the wet regions of Washington also deal with it. The infection model for downy mildew -- the "10-10-24" rule (10mm rain, 10°C minimum temp, 24-hour incubation) -- means that spray timing is tied to weather events, not calendar intervals. Your spray records should reflect that connection.

When a downy mildew spray is logged after a wetting event that met infection criteria, your documentation tells the story of a threshold-based program. That's what a sustainable viticulture certifier wants to see. It's also what a PCA needs if a question arises about why you sprayed when you did.

Downy mildew programs carry their own FRAC resistance concerns. Phenylamide (Group 4 -- Ridomil) resistance has been documented in several US wine regions. Your spray records should show that Group 4 products are used in mixtures with contact materials, not as standalones, and that you're rotating off them when infection pressure is low.

For organic programs, copper is the primary tool and it carries additional record-keeping requirements. Many organic certifications now track cumulative copper inputs per season and per year, with EU-derived rate limits becoming more common in domestic certification standards. VitiScribe tracks cumulative copper applications automatically, so your organic certifier can see that you stayed within program limits across all blocks.

Trunk Disease Spray Records

Trunk diseases -- Eutypa dieback (Eutypa lata), Botryosphaeria dieback, Esca, and related canker pathogens -- are managed primarily through pruning wound protection. That means the most important spray records in your trunk disease program are tied to pruning dates, not weather events.

The critical window for pruning wound protection is within 24 hours of the cut. If you're applying Topsin, Rally, or biological wound protectants, your records need to show the application date relative to the pruning date for each block. A 5-day gap between pruning completion and wound protectant application is a problem your records will either document or hide.

VitiScribe's block record links pruning dates to wound protection spray applications, so the timeline is visible when you pull a block history. If you're managing Eutypa in established blocks and tracking the spread of symptoms over time, you can log disease incidence observations in the scouting record and compare them to your wound protection history. Blocks with gaps in protection coverage often show higher disease incidence three to five years later.

Registered fungicides for pruning wound protection include thiophanate-methyl (Topsin-M), myclobutanil (Rally), and several biological products including Trichoderma-based formulations. PHI varies by product -- confirm current label PHI before applying late in the season. Your spray record should capture the pruning date, the application date, the product and rate, and the number of vines or linear footage treated if you're applying to individual cuts rather than broadcast.

Leafroll Virus Management Records

Grapevine leafroll disease is managed through vector control -- primarily mealybug in the western US -- rather than direct antifungal applications. But the spray records for mealybug management in leafroll-positive blocks carry specific documentation needs that differ from general insecticide records.

When you're spraying for mealybugs as leafroll vectors, your records should document the scouting observations that triggered the application. What was the mealybug population count? What growth stage were you treating? Was this a first- or second-generation crawler spray? Timing matters enormously for crawler management, and your records should show that you hit the window rather than simply sprayed on a schedule.

PHI for mealybug insecticides varies widely. Admire Pro (imidacloprid) carries a 21-day PHI in grapes. Movento (spirotetramat) is labeled at 7 days. Closer (sulfoxaflor) at 7 days. If you're making late-season mealybug applications for leafroll vector management, PHI tracking is critical and your records need to reflect it. VitiScribe populates PHI from your product selection and updates harvest clearance dates accordingly.

Organic programs managing leafroll vectors can use kaolin clay applications or mite-destroyer releases, which have their own record-keeping requirements for certified organic operations. OMRI listing status should be documented on every organic-approved input record.

Phomopsis and Early Season Disease Records

Phomopsis cane and leaf spot (Phomopsis viticola) is the first disease management priority in wet-spring regions. The critical window runs from budbreak through 4-inch shoot growth -- typically a 2-3 week window in early April or May depending on region. Miss it and you lose the season for that pest.

Because Phomopsis programs are compressed into early season, the spray records are few but time-sensitive. Your documentation should capture the phenological stage at application (budbreak, 1-inch shoot, 2-inch shoot) and the weather conditions that preceded the application -- specifically the wetting events that created infection risk. This ties your timing to agronomic rationale rather than calendar habit.

Registered materials include mancozeb, captan, ziram, and several DMI fungicides. Note that mancozeb is a restricted-use pesticide in California, requiring certified applicator documentation. If you're using mancozeb for Phomopsis, your spray record needs the applicator's CA license number and must be filed with the County Agricultural Commissioner within 7 days (or within 24 hours for some counties under the expedited reporting rule). VitiScribe's California profile applies these requirements automatically.

Black Rot Records in Eastern Vineyards

Black rot (Guignardia bidwellii) is the dominant disease concern in humid eastern vineyards -- Virginia, New York, North Carolina, Tennessee, Missouri. The spray program runs from early season through berry development, and timing is governed by the Mills infection model, which combines temperature and wetness duration to predict infection events.

Documenting black rot sprays against weather-triggered infection events is what separates a defensible IPM program from a calendar-based one. When your records show "applied Mancozeb on May 15 following a 14-hour wetting period with temps above 60°F," you're demonstrating threshold-based decision-making. That documentation matters for sustainable certification and for any extension or industry audit of your IPM practices.

Black rot materials include mancozeb, captan, myclobutanil, DMI fungicides, and strobilurins. FRAC rotation applies here too -- QoI resistance in black rot is documented in some eastern regions, similar to powdery mildew. Your spray records should show the FRAC group for every application, not just the product name.

Organizing Records by Disease Target

The practical challenge is that most vineyards are managing multiple diseases simultaneously through the season. A spray made in late May might target powdery mildew, downy mildew, and Phomopsis in a single tank mix. Your record needs to capture all three target pests, the mode of action for each component, and the specific PHI for the most restrictive product in the mix.

VitiScribe handles tank mixes by calculating the most restrictive PHI across all products in the application and displaying it as the harvest clearance date for that spray event. You select each product in the mix, and the system computes the overlap automatically. If one product in your tank mix has a 21-day PHI and the others are 7 days, your harvest clearance date reflects the 21-day requirement.

Disease-specific spray templates in VitiScribe pre-load the FRAC group, the typical target pests, and the standard compliance fields for each product. When you start a new spray record and select your product, the template knows whether you're applying a QoI fungicide for powdery mildew or a phenylamide for downy mildew, and it records the relevant classification without you having to look it up.

Building a Defensible Disease Management Record

Auditors -- whether from DPR, your certification body, or your winery buyer -- aren't just checking whether you have records. They're checking whether your records tell a coherent story. A good disease management record shows that you observed conditions warranting a spray, selected appropriate chemistry with resistance management in mind, applied within the correct window, and stayed within PHI constraints.

That story requires more fields than the bare minimum for compliance. It requires growth stage, weather conditions, FRAC group, tank mix components, and PHI-driven harvest clearance dates -- all of which VitiScribe captures as part of the standard spray entry workflow, not as an add-on burden on top of basic record keeping.

When your season is done, VitiScribe's disease-specific spray reports let you review your program by target pest, by block, by FRAC group, and by cost. You can see exactly how many times you applied Group 11 chemistry to your Chardonnay blocks, whether your PHI clearances were met, and how your pesticide spending broke down by disease category. That's the kind of management intelligence that helps you design a better program next season.

Frequently Asked Questions

What spray records are required for vineyard disease management programs?

Every vineyard disease spray requires at minimum: date and time of application, product name and EPA registration number, application rate and volume, block or acreage treated, weather conditions (wind speed and direction, temperature), applicator name and license number, and the target pest. For California DPR restricted-use pesticides, records must be filed with the County Agricultural Commissioner within 7 days, or within 24 hours in most counties under current expedited reporting requirements. For organic programs, additional fields document OMRI-listed status and application justification. Certifiers like SIP Certified and CCOF add further requirements including FRAC group rotation documentation and threshold-based decision records.

How does VitiScribe organize spray records by disease target?

VitiScribe's spray log uses disease-specific templates that pre-load the correct FRAC group, registered PHI, and REI data when you select a product. When you start a spray entry, you select the target pest -- powdery mildew, botrytis, downy mildew, trunk disease -- and the template pre-fills the compliance fields specific to that disease category. Tank mixes that target multiple diseases simultaneously calculate the most restrictive PHI across all selected products. Block-level disease history reports let you review spray frequency, FRAC rotation, and product spending by disease category for any date range.

Do different diseases require different spray record formats for DPR compliance?

California DPR uses the same core record format for all pesticide applications -- there's no separate form for powdery mildew vs botrytis. However, some disease management inputs carry additional record-keeping requirements. Restricted-use pesticides (including mancozeb, some organophosphates) require the applicator's license number and county filing. Organic-approved inputs require OMRI documentation. Biological control agents have their own registration and record requirements distinct from conventional pesticides. And for sustainable or organic certifications layered on top of DPR compliance, disease-specific documentation of spray decision rationale, FRAC rotation, and IPM threshold records become part of the required package.

How should records document a situation where the same application targets powdery mildew and botrytis simultaneously in a pre-harvest tank mix?

A tank mix application targeting both powdery mildew and botrytis in the same spray event should list all products in the mix, the FRAC group for each, the individual PHI for each product, and the controlling PHI -- the most restrictive PHI that applies to the block's harvest clearance date. If the powdery mildew component has a 14-day PHI and the botrytis component has a 7-day PHI, the 14-day requirement controls harvest timing for that block. Your record should show both target diseases, all products, all FRAC groups, and the single harvest clearance date that results from the most restrictive PHI in the mix. VitiScribe computes this automatically and updates block harvest clearance dates in real time as applications are logged.

What is Vine Disease Spray Records: Documentation Requirements for Every Major Vineyard Disease?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vine Disease Spray Records: Documentation Requirements for Every Major Vineyard Disease. Target 50-150 words.]

How much does Vine Disease Spray Records: Documentation Requirements for Every Major Vineyard Disease cost?

How does Vine Disease Spray Records: Documentation Requirements for Every Major Vineyard Disease work?

What are the benefits of Vine Disease Spray Records: Documentation Requirements for Every Major Vineyard Disease?

Who needs Vine Disease Spray Records: Documentation Requirements for Every Major Vineyard Disease?

How long does Vine Disease Spray Records: Documentation Requirements for Every Major Vineyard Disease take?

What should I look for when choosing Vine Disease Spray Records: Documentation Requirements for Every Major Vineyard Disease?

Is Vine Disease Spray Records: Documentation Requirements for Every Major Vineyard Disease worth it?

Sources

UC IPM Program
FRAC (Fungicide Resistance Action Committee)
California Department of Pesticide Regulation (CDPR)
Cornell Cooperative Extension
American Vineyard Foundation

Get Started with VitiScribe

Eleven disease-targeted applications per season means 11 records that need FRAC group, PHI, growth stage, and weather conditions documented alongside the compliance fields -- and when multiple diseases share a tank mix, the most restrictive PHI across all products must control harvest clearance for that block. VitiScribe's disease-specific spray templates pre-load FRAC group and PHI from product selection, compute tank mix PHI conflicts before application, and generate season-end reports by disease category showing rotation history and program cost. Try VitiScribe free and log your first disease-specific spray record today.