Seasonal Spray Calendar for Vineyards: Plan Applications from Dormancy to Harvest

By VitiScribe Editorial·August 15, 2025·Updated September 16, 2025

Pre-harvest PHI violations are the leading cause of rejected wine grape deliveries in California. The grape is perfect. The fruit is ready. The winery rejects it because a spray record shows a product was applied inside its PHI window relative to the delivery date.

This happens because spray calendars get built without cross-referencing PHI. You plan a late-season fungicide application based on disease pressure and weather, schedule it for the week before harvest, and don't realize until the winery asks for your spray records that the product you chose has a 14-day PHI.

Building a seasonal spray calendar in VitiScribe prevents this. PHI conflicts get flagged at the planning stage before you've committed to a schedule, before you've purchased product, before you've informed your contractor. You see the conflict while there's still time to change the product or adjust the timing.

TL;DR

PHI violations discovered after application have no good remedies -- winery rejection is the common outcome; catching PHI conflicts at the planning stage while substitution is still possible is the primary value of a pre-season spray calendar
Each block's harvest date drives its own PHI cutoff calculations -- a product with a 21-day PHI is fine to apply in August on a late-harvest October block but creates a conflict on an early-September block in the same vineyard
Planned applications flagged with FRAC rotation concerns at the scheduling stage can be adjusted before product purchase; the same correction at application time requires emergency product sourcing
Sharing the spray calendar with your spray contractor through VitiScribe sub-accounts means planned applications, PHI notes, and REI requirements are communicated before each application without a separate call
When harvest dates shift -- pushed earlier by ripening conditions or later by weather -- updating the block's harvest date in VitiScribe automatically recalculates all PHI windows for every planned product on that block
Applications logged inside a PHI window appear flagged in spray records; if the application proceeded for a legitimate reason (harvest date estimate error, for example), the record documents the conflict and your rationale for winery or auditor review

How Do I Build a Seasonal Spray Calendar in VitiScribe?

The seasonal spray calendar starts with your harvest dates. Everything else gets built backward from there.

Entering Harvest Date Targets

For each block, enter your target harvest date or harvest window. This is the date you expect to deliver fruit or begin harvest operations. The calendar uses this date to calculate when the PHI window closes for every product you plan to use.

If your harvest target changes as the season progresses pushed earlier by ripening conditions or later by weather you update the harvest date in the system and all PHI calculations update automatically.

Building the Application Schedule

With harvest dates established, you build your application schedule by adding planned applications to the calendar. For each planned application, you specify:

Block(s) to be treated
Target application date or date window
Product(s) to be applied
Intended pest or disease target

As you enter each application, VitiScribe checks the planned application date against the block's harvest date and the product's PHI. If the planned application falls inside the PHI window, you see an alert immediately not when you're trying to log the actual application.

For the full PHI reference by fungicide class and product that supports calendar planning, see the PHI and REI guide for viticulture.

Resistance Rotation Planning

PHI conflict alerts prevent scheduling sprays too close to harvest on a block-by-block basis. But the calendar also helps you manage resistance rotation across the season.

When you build your fungicide program for powdery mildew or Botrytis management, VitiScribe tracks the FRAC (fungicide resistance action committee) mode-of-action code for each product. If you've scheduled two consecutive applications with the same mode of action in a short interval, the calendar flags the rotation concern so you can substitute a different FRAC group.

Resistance rotation isn't just an agronomic best practice it's becoming a sustainability documentation requirement for some premium wine programs and export market certifications.

How Does VitiScribe Flag PHI Conflicts on My Spray Schedule?

PHI conflict detection works at both the planning stage and the application stage.

Planning-Stage Alerts

When you add a planned application to the calendar, the system checks whether the planned date falls within the PHI window for each product in the planned application. A planned application scheduled 12 days before harvest for a product with a 14-day PHI triggers an immediate alert.

The alert shows you which product is creating the conflict and how many days inside the PHI window the application falls. You see your options: push the application earlier, push the harvest date later (if feasible), or substitute a different product with a shorter PHI.

This planning-stage detection is the most valuable point to catch the problem. At the planning stage, all options are available. After the application, your options are much more limited.

Application-Stage Alerts

If a planned application gets logged without resolving a PHI conflict, VitiScribe alerts again at the application stage. The system won't prevent you from logging the application you may have a legitimate reason for applying inside the PHI window, such as an error in your original harvest date estimate but the conflict is documented.

Any application logged inside a block's PHI window appears with a flag in your records. When a winery buyer or auditor reviews your spray records, they see that the conflict was identified and can see your notes about why the application proceeded.

Multi-Block PHI Management

On vineyards with multiple blocks being harvested on different dates, PHI management is inherently complex. Block A might be planned for early September, Block B for mid-October. A product with a 21-day PHI is fine to apply in August to Block B but creates a conflict for Block A if applied after mid-August.

VitiScribe manages these block-specific PHI windows independently. Each block's calendar shows its own PHI cutoff dates for each product based on its own planned harvest date. Multi-block spray events prompt PHI verification for each block in the application, not just one.

Can I Share My Spray Calendar with My Spray Contractor?

Yes. The spray calendar is shareable with any user who has access to your VitiScribe account, including contractor sub-accounts.

When you share the calendar with your spray contractor, they see the planned application schedule for their assigned blocks which products are planned for which dates, and any PHI or REI notes relevant to timing. They can prepare for upcoming applications without needing a separate briefing call.

Contractor Modification Permissions

You control whether contractors can modify the calendar or only view it. For most operations, contractors view the planned schedule and log completed applications against it. The calendar remains under the vineyard owner's control.

When a contractor completes a scheduled application, they log it in their sub-account. The planned application in the calendar gets marked complete, and the actual application record is linked to the calendar entry. This creates a clean record showing that the application was planned, authorized, and completed.

Calendar and Harvest Compliance Documentation

For winery buyers who request pre-harvest compliance documentation, the spray calendar is useful supplementary evidence. It shows that your spray program was planned with PHI requirements in mind, that you were scheduling applications to respect harvest date constraints, and that the program was executed as planned.

This kind of proactive compliance documentation is increasingly valued by premium wine programs that want to see evidence of systematic management, not just retroactive records.

For the spray program management framework that connects calendar planning to compliance record generation, see the spray program management guide.

Related guides:

Frequently Asked Questions

Why do pre-harvest PHI violations happen most often in California wine grape operations?

PHI violations typically occur when a spray calendar is built forward from bud break rather than backward from harvest date. A grower plans a late-season botryticide for August based on disease pressure without referencing the 14-day PHI against the block's September harvest date. The application looks reasonable in isolation; the violation only becomes visible when the winery requests spray records and finds a product applied inside the required window. Calendar planning built around harvest dates -- with PHI cutoffs calculated at the planning stage -- catches these conflicts before the product is applied and while substitution is still possible.

How should a vineyard manager handle a planned spray calendar application when the anticipated harvest date shifts earlier by 10 days?

When the anticipated harvest date shifts earlier, any product with a PHI that would be violated by the new harvest date must be flagged for review. The practical approach is to update the block's anticipated harvest date in the spray calendar, which automatically recalculates PHI cutoffs for all planned products on that block. Products whose PHI windows are now violated by the updated harvest date should either be moved to an earlier application date if that is still agronomically appropriate, or substituted with a product carrying a shorter PHI that clears the new harvest date. The key is making the adjustment before the product is applied -- not discovering the problem when the winery reviews spray records at delivery.

What records should accompany the spray calendar as documentation of pre-season compliance planning?

The spray calendar itself is a planning document; the application records generated as the season progresses are the compliance documents. However, for premium wine program audits and sustainable winegrowing certifications (SIP Certified, Lodi Rules, CSWA), having a documented pre-season spray plan that shows PHI awareness and FRAC rotation design is increasingly valuable. A one-page pre-season program summary that lists planned products by block, their FRAC groups, target pests, and PHI clearance dates serves as the planning documentation. VitiScribe's calendar export generates this summary from your planned application schedule.

What is Seasonal Spray Calendar for Vineyards: Plan Applications from Dormancy to Harvest?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Seasonal Spray Calendar for Vineyards: Plan Applications from Dormancy to Harvest. Target 50-150 words.]

How much does Seasonal Spray Calendar for Vineyards: Plan Applications from Dormancy to Harvest cost?

How does Seasonal Spray Calendar for Vineyards: Plan Applications from Dormancy to Harvest work?

What are the benefits of Seasonal Spray Calendar for Vineyards: Plan Applications from Dormancy to Harvest?

Who needs Seasonal Spray Calendar for Vineyards: Plan Applications from Dormancy to Harvest?

How long does Seasonal Spray Calendar for Vineyards: Plan Applications from Dormancy to Harvest take?

What should I look for when choosing Seasonal Spray Calendar for Vineyards: Plan Applications from Dormancy to Harvest?

Is Seasonal Spray Calendar for Vineyards: Plan Applications from Dormancy to Harvest worth it?

Sources

California Department of Pesticide Regulation (CDPR)
EPA FIFRA (Federal Insecticide, Fungicide, and Rodenticide Act)
UC Cooperative Extension Viticulture
American Vineyard Foundation
Wine Institute

Get Started with VitiScribe

A spray calendar that isn't built backward from harvest dates will create PHI conflicts that only become visible when a winery buyer reviews records before delivery -- and at that point, the options are limited. VitiScribe builds PHI conflict detection into the planning stage, flags FRAC rotation concerns before product purchase, and manages multi-block harvest date differences independently so that a program adjustment on one block doesn't affect another. Try VitiScribe free and build your next seasonal spray calendar with PHI clearance tracking from day one.