How to Design a Vineyard Spray Program from Scratch

By VitiScribe Editorial·January 16, 2025·Updated February 25, 2025

A well-designed spray program saves an average of 25% compared to ad-hoc calendar-based approaches -- not by skipping necessary applications, but by eliminating unnecessary ones and timing required applications to their most effective windows. VitiScribe spray program templates are pre-built by region and variety rather than blank spreadsheets you'd fill in from scratch.

Starting a new vineyard, taking over management of an existing block, or redesigning a program that's developed organically over the years all start with the same process: figure out what you're actually managing before you decide how to manage it.

TL;DR

A well-designed spray program saves an average of 25% compared to calendar-based approaches -- not by skipping applications but by eliminating unnecessary ones and timing required applications to their most effective windows; the savings come from monitoring-based decisions, not reduced diligence
Program design starts with a pest inventory, not product selection: which diseases and pests are present, at what pressure, and with what block-to-block variation; a program designed without this foundation will be a calendar program by default
FRAC group rotation for powdery mildew requires at minimum 4-6 groups rotated through the season with no more than 2 consecutive applications from the same group; Group 11 (QoI) should be capped at 1-2 applications per season where resistance has been confirmed
PHI constraints are part of program design, not just record-keeping -- 0-day PHI materials (sulfur, potassium bicarbonate) need to be in the final application slots; products with 14-30 day PHIs must be scheduled so the last application date leaves the required interval before your estimated harvest date
Record-keeping infrastructure -- blocks entered with variety and GPS, product library loaded, applicator license numbers stored -- should be complete before the first application, not assembled during the season or from memory at audit time
When you shorten spray intervals based on infection conditions, document the weather conditions that drove the decision in your spray records; this documented IPM rationale is what distinguishes a responsive program from a calendar program at certification audit

Step 1: Build Your Pest Inventory

Before selecting any products, know what you're managing. A pest inventory answers: which pests and diseases are present in my blocks, at what pressure levels, and with what pattern of distribution?

For a new vineyard, pre-plant assessment:

Regional pest pressure data from your local Cooperative Extension office
PCA assessment of the site, surrounding land use, and regional disease pressure
Soil sample for nematode populations (fanleaf virus vector assessment)
Site history for prior disease or pest problems

For an existing vineyard:

Review prior seasons' spray records and scouting logs
Identify which diseases or pests required the most applications in prior years
Note any blocks where breakthrough disease occurred despite full program coverage (resistance signal)
Assess which blocks have pest pressure distinctly different from others (microsite, variety, or vine age differences)

Your pest inventory should identify:

Primary diseases requiring full programs (powdery mildew, botrytis, downy mildew for your region)
Secondary diseases warranting periodic management (Phomopsis, black rot, trunk disease)
Primary insect pests (GBM, leafhoppers, mealybug)
Secondary insects requiring monitoring but not always treatment (spider mites, sharpshooters)

Step 2: Identify Information Gaps and Monitoring Needs

A spray program designed without monitoring data will be a calendar program by default. Before deciding what to spray, decide what you'll be watching for.

For each pest on your inventory, establish:

Monitoring method (scouting protocol, trap type, weather model)
Monitoring frequency (weekly, biweekly, at-emergence)
Economic threshold (the population level at which damage exceeds control cost)
Who will conduct monitoring and where it will be recorded

VitiScribe's scouting module provides a framework for entering monitoring observations that connect to spray decisions. See the block scouting template for practical monitoring protocols.

Step 3: Select Fungicides for Each Disease Target

For each disease requiring spray management, select the specific fungicide groups you'll rotate through the season.

Powdery mildew fungicide selection:

Identify which FRAC groups are at risk for resistance in your region (Group 11 resistance is widespread in most US wine regions)
Select 4-6 FRAC groups to rotate through the season
Plan the rotation sequence: which group at what seasonal window
Identify 0-day PHI products for late-season use

Botrytis fungicide selection:

Identify FRAC groups with known resistance in your region (Groups 1, 2, 9, 17 in some areas)
Select 4-5 groups for seasonal rotation
Plan application timing to critical windows (50% capfall, bunch closure, veraison)
Identify products compatible with organic programs if relevant

Downy mildew fungicide selection (wet-spring regions):

Assess phenylamide (Group 4) resistance risk based on prior use history
Plan Group 4 applications as premixtures only if resistance is a concern
Select Group 40, 43, and 45 materials as rotation partners
Schedule copper applications around infection event timing

Step 4: Select Insecticides by IRAC Group and Pest

Grape berry moth program (GBM regions):

Select insecticides from at least 2-3 different IRAC groups
Plan group assignment by generation: first, second, third
Check PHI compatibility for any applications near harvest dates
Plan biofix monitoring approach for degree day tracking

Leafhopper program:

Establish economic threshold monitoring protocol
Select materials from different IRAC groups for rotation
Identify if biological control (parasitic wasps) is active in your blocks -- broad-spectrum applications may suppress natural enemies

Mealybug program:

Plan systemic application (Movento, Group 23) timing relative to crawler emergence
Identify second material for contact coverage during crawler emergence
Note neonicotinoid restrictions during bloom

Step 5: Build Your FRAC/IRAC Rotation Calendar

With your pest list, product list, and monitoring framework established, create a rotation calendar showing which group goes in which application slot through the season.

A sample powdery mildew rotation for a 12-application program:

|-------------|--------|------------|-----------------|

| 1 | Budbreak | M2 | Sulfur |

| 2 | 4-6 inch shoot | 3 | Rally |

| 3 | Pre-bloom | 7 | Luna Privilege |

| 4 | Early bloom | 13 | Quintec |

| 5 | Full bloom | M2+3 | Sulfur + Elite tank mix |

| 6 | Post-set | U8 | Vivando |

| 7 | Berry development | 7 | Sercadis |

| 8 | Cluster | 3 | Tebuzol |

| 9 | Veraison | M2 | Sulfur |

| 10 | Mid-veraison | 7+11 | Pristine (0-day PHI) |

| 11 | Pre-harvest | M2 | Sulfur |

| 12 | Pre-harvest | 45 | Kaligreen (0-day PHI) |

No more than 2 consecutive applications from the same group. Group 11 limited to 1-2 applications per season. 0-day PHI materials in the final 2-3 applications.

Step 6: Set Up Record Keeping and Compliance Infrastructure

A well-designed spray program is only as good as its documentation. Before the season begins, ensure:

Record system ready: All blocks entered in VitiScribe with variety, rootstock, planting year, and GPS information. Product library loaded with products you'll use this season. Applicator license numbers stored in user profiles.

State compliance requirements confirmed: Filing deadlines, required fields, applicator license requirements for your state and county. If this has changed from prior season, update your process.

Scouting protocol documented: Who scouts what, how often, what data is recorded, where observations are logged.

PHI tracking system active: Harvest date estimates entered by block. PHI calculation will update as applications are logged.

See how VitiScribe connects spray programs to compliance records.

Step 7: Review and Adjust Through the Season

A program designed in January needs to flex through the season based on actual conditions. High-pressure years may require shortened intervals or additional applications. Low-pressure years may allow interval extension.

In VitiScribe, the spray window alerts and weather integration help you identify when conditions warrant deviating from your planned program. When you shorten intervals based on favorable infection conditions, document the weather conditions that drove the decision in your spray records -- this is the documented IPM rationale that certification programs look for.

At season end, review: which program elements worked, which blocks required more intensive management than planned, where costs ran higher or lower than anticipated, and where FRAC/IRAC rotation could be improved for next season.

Frequently Asked Questions

How do I start designing a vineyard spray program from scratch?

Start with your pest inventory: identify which diseases and pests are present or likely in your blocks based on regional data and prior site history. Then establish your monitoring framework -- what you'll watch for, how often, and at what thresholds you'll act. Once you know what you're managing and how you'll track it, select fungicides and insecticides from multiple FRAC and IRAC groups for rotation, plan the application timing to critical pest windows, and identify which products have the PHI constraints that limit late-season use. Set up your record-keeping infrastructure before the first application.

What information do I need to select fungicides for my vineyard spray program?

You need: the primary diseases you're managing and your region's disease pressure profile; the FRAC groups with confirmed resistance in your region (Group 11 QoI resistance in powdery mildew is relevant in most US wine regions); the PHI requirements for all candidate products relative to your intended harvest timing; whether you're managing a conventional or organic program (OMRI-listed vs conventional products); your spray equipment and its ability to deliver adequate coverage for the products you're considering; and your budget constraints, as high-efficacy newer products often carry notable price premiums over older conventional materials.

How does VitiScribe help vineyard managers design and track spray programs?

VitiScribe provides pre-built spray program templates by region and variety that give you a starting point rather than a blank page. The product library includes FRAC and IRAC group data, PHI and REI values, and restricted-use pesticide flags for all registered products, pre-populating spray records with the data you'd otherwise need to look up. As you log applications through the season, the FRAC rotation report shows your group sequence by block, flagging any consecutive same-mode applications. PHI is calculated and displayed for every block. Scouting records connect to spray decisions, documenting the IPM rationale that sustainable certification programs require.

How do I handle program adjustments mid-season when pest pressure is higher or lower than expected?

For high-pressure years requiring shortened intervals or additional applications, document the observation or weather event that drove the decision in your spray record notes -- "interval shortened from 14 to 10 days due to extended wet period, powdery mildew germination risk elevated." This note is your documented IPM rationale. For low-pressure years where you extend intervals or skip planned applications, document the scouting data that supported that decision -- "application skipped: no powdery mildew detected at weekly scouting, low disease pressure confirmed." These notes transform your spray log from a record of what was done into a record of why -- which is what sustainable certification programs and winery buyer audits expect to see.

What is How to Design a Vineyard Spray Program from Scratch?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to How to Design a Vineyard Spray Program from Scratch. Target 50-150 words.]

How much does How to Design a Vineyard Spray Program from Scratch cost?

How does How to Design a Vineyard Spray Program from Scratch work?

What are the benefits of How to Design a Vineyard Spray Program from Scratch?

Who needs How to Design a Vineyard Spray Program from Scratch?

How long does How to Design a Vineyard Spray Program from Scratch take?

What should I look for when choosing How to Design a Vineyard Spray Program from Scratch?

Is How to Design a Vineyard Spray Program from Scratch worth it?

Sources

UC Cooperative Extension Viticulture
UC IPM Program
FRAC (Fungicide Resistance Action Committee)
IRAC (Insecticide Resistance Action Committee)
American Vineyard Foundation

Get Started with VitiScribe

Designing a vineyard spray program from scratch starts with a pest inventory and ends with a record-keeping system -- and the record system you build into your program design is what determines whether your program documentation satisfies compliance, certification, and winery buyer requirements. VitiScribe's pre-built region and variety templates give you a starting program, and the record system captures every application, rotation decision, and scouting observation as the season progresses. Try VitiScribe free and set up your first complete spray program today.