Vine Growth Regulator Spray Records: PHI and Application Precision Requirements

By VitiScribe Editorial·June 23, 2025·Updated August 4, 2025

Growth regulator over-application can delay fruit ripening by 10-14 days, affecting harvest scheduling in ways that cascade through your entire operation. For regulated products with approved rate ranges, over-application also violates the label, which is a federal FIFRA issue regardless of the agronomic outcome.

Plant growth regulators used in viticulture have precision requirements at both the low and high end of the rate range that most other pesticide categories don't. Too little and the product doesn't achieve its intended effect. Too much and you've potentially altered fruit development in ways you didn't want and may have violated the label. The documentation requirements for PGR applications need to reflect this precision.

TL;DR

Growth regulator over-application is both an agronomic risk and a federal FIFRA label violation -- over-application of ethephon can cause excessive defoliation and premature softening; over-application of GA3 can reduce fruit set at concentrations only 10-20 mg/L above target
S-ABA (ProTone SL) applied at veraison to improve red variety color has a tight registered rate range where over-application causes excessive berry softening that creates cluster quality problems directly affecting winery pricing
Tank concentration documentation -- product amount per tank and total tank volume -- is required for PGR records to verify the intended concentration was achieved in the field; estimation is not adequate for these applications
Growth stage at application is more critical for PGRs than any other pesticide category: GA3 for cluster elongation, ethephon for ripening, and S-ABA for color development each require application at a specific phenological window that the spray record should document
VitiScribe flags rate entries outside the registered label range before saving and triggers supervisor notification -- catching calculation errors at record entry rather than after observing vine response a week later
PGR program evaluation requires records that link application rate, vine stage at application, and post-application vine response to build a site-specific evidence base for refining programs across vintages

Plant Growth Regulators Used in Vineyards

The PGR category in viticulture includes several different compounds with distinct use patterns:

Ethephon (Ethrel): Used in some programs to accelerate anthocyanin development and uniform ripening in red varieties. Rate sensitivity is notable. PHI varies by product registration, often 7-14 days depending on crop stage at application.

Gibberellin (GA3): Used to elongate clusters (particularly in tight-clustered varieties like Thompson Seedless and table grapes) or to reduce cluster compactness. In wine grape programs, GA3 is used selectively. Rate precision is critical because GA3 affects berry set in ways that are not reversible.

Cytokinins (6-benzylaminopurine, forchlorfenuron/CPPU): Used primarily in table grape programs to increase berry size. Less common in wine grape production.

Abscisic acid (ABA) / S-ABA (ProTone): Used to improve color development in red varieties, particularly in warm inland California sites where heat reduces anthocyanin expression. This is one of the most common PGRs in California wine grape programs.

Chlormequat (Cycocel): Used to manage excessive shoot elongation in some high-vigor programs.

Each of these compounds has specific registered rate ranges, application timing requirements, and PHI restrictions that differ from each other. The "PGR" category isn't monolithic from a compliance standpoint.

Precision Requirements at Application

Unlike most fungicides where you're operating within a rate range with reasonable tolerance, many PGRs have effect curves where application rate directly determines the outcome. Getting the rate wrong isn't just a compliance issue. It's an agronomic one.

S-ABA (ProTone SL) for red varieties: Applied at veraison to improve color development. The registered rate range is tight. Under-application produces inadequate response. Over-application can cause excessive berry softening that creates cluster quality problems. Your rate calculation and your documentation of the actual rate applied need to be precise.

GA3 for cluster elongation: The rate differential between "effective elongation" and "excessive elongation with reduced fruit set" can be as narrow as 10-20 mg/L in the effective concentration in the tank. This is a situation where actual measurement of product amount and tank volume, not estimation, is required for both compliance and agronomic success.

Ethephon for ripening: PHI and rate compliance are both critical. Over-application can cause excessive defoliation or premature softening. The rate and timing documentation needs to show that the application was made at the intended growth stage at the intended rate.

Documentation Requirements for PGR Records

All standard DPR-required fields apply to PGR applications. Additional considerations specific to PGRs:

Tank concentration calculation: For PGRs applied in concentrate or dilute spray, documenting the product amount per tank and the tank volume (to confirm concentration in tank) is important for both compliance and agronomic records. This is the actual application rate record that verifies the intended concentration was achieved.

Application stage documentation: Growth stage at application is more critical for PGRs than for most other pesticide categories. Ethephon applied at the wrong growth stage produces a different effect than intended. GA3 for cluster elongation must be applied at a specific cluster stage. Document the growth stage in the spray record.

PHI documentation against harvest date: For PGRs used near harvest (S-ABA, ethephon), PHI calculation against your anticipated harvest date is essential. VitiScribe's PHI/REI compliance system tracks PGR PHIs with the same block-specific harvest date calculation used for fungicides.

Post-application observation notes: PGR effects are visible in plant tissue in ways that other pesticide effects are not. Noting the vine response 7-14 days after a PGR application (reduced shoot growth from chlormequat, improved color development from S-ABA) is useful for both program evaluation and for defending the rate decision if questions arise later.

For documentation of near-harvest applications where PHI conflicts may arise across multiple products, see tank mix planning for vineyards for how VitiScribe resolves PHI conflicts in multi-product applications.

Supervisor Notification for Rate Errors

VitiScribe's PGR records require rate verification before saving. If you're entering a rate outside the registered label rate range, the system flags the discrepancy before the record is saved.

PGR applications logged outside label rate ranges trigger an immediate supervisor notification in VitiScribe. This isn't about distrust. It's about catching calculation errors before they become field events. A 10x concentration error in a PGR (mixing product for 10 gallons into a 100-gallon tank) might not be caught until the vine response shows the problem a week later. The supervisor notification at record entry catches it at the input stage.

VitiScribe's pesticide label compliance system validates PGR rates against registered label data for each product in the database.

Record Retention and PGR Program Evaluation

PGR programs are evaluated seasonally based on their agronomic outcomes. Keeping spray records that include application stage, rate, and tank concentration alongside vineyard performance data (harvest date, color development scores, yield data) builds an evidence base for refining your program year over year.

A complete S-ABA program record that shows application rate, vine growth stage at application, weather conditions during the application window, and post-application berry color assessment for each block builds the database for understanding when and at what rate the product achieves your intended outcome on your specific varieties and sites.

Frequently Asked Questions

What application records are required for growth regulator use in vineyards?

Growth regulator applications require all standard California DPR pesticide use record fields plus: tank concentration documentation (product amount per tank and total tank volume confirming the intended application concentration), vine growth stage at the time of application, and PHI documentation against anticipated harvest date for any PGRs applied in the pre-harvest period. Post-application observation notes documenting vine response are not required by regulation but are valuable for program evaluation and rate compliance documentation.

How does VitiScribe handle PHI for plant growth regulators?

VitiScribe pulls registered PHI from the product database for each PGR product when you log an application. The PHI calculates against the block's entered anticipated harvest date, the same as fungicide and insecticide PHI calculations. If the application date plus PHI would not clear before the anticipated harvest date, the system flags the conflict before the record is saved.

What happens if I accidentally apply a PGR at the wrong rate?

Above-label PGR application is a federal FIFRA violation regardless of the agronomic outcome. The practical consequences depend on the specific product and rate error: minor rate deviations may have minimal plant effect but still constitute a label violation; notable over-application can produce unintended effects including delayed ripening, excessive defoliation, or altered berry development that affects wine quality and harvest timing. VitiScribe's rate validation flags entries outside the registered label rate range before saving and triggers supervisor notification so errors are caught at the point of record entry rather than after the application.

How should vine response to a PGR application be documented alongside the spray record?

Post-application vine response observations are not DPR-required but are valuable for both compliance defense and program improvement. The observation record should note the date of assessment (typically 7-14 days after application), the specific vine response observed (berry color development rating, shoot growth reduction, cluster elongation change), the blocks assessed, and whether the response aligned with the intended program outcome. In VitiScribe, these observations can be logged as scouting entries linked to the spray record for the same block, creating a timeline that shows application rate, application stage, and observed vine response in one record view -- the documentation needed if a winery buyer or auditor asks whether a PGR application achieved its intended effect.

What is Vine Growth Regulator Spray Records: PHI and Application Precision Requirements?

[FAQ_ANSWER_PLACEHOLDER: This answer needs to be generated by AI with specific data, examples, and actionable advice relevant to Vine Growth Regulator Spray Records: PHI and Application Precision Requirements. Target 50-150 words.]

How much does Vine Growth Regulator Spray Records: PHI and Application Precision Requirements cost?

How does Vine Growth Regulator Spray Records: PHI and Application Precision Requirements work?

What are the benefits of Vine Growth Regulator Spray Records: PHI and Application Precision Requirements?

Who needs Vine Growth Regulator Spray Records: PHI and Application Precision Requirements?

How long does Vine Growth Regulator Spray Records: PHI and Application Precision Requirements take?

What should I look for when choosing Vine Growth Regulator Spray Records: PHI and Application Precision Requirements?

Is Vine Growth Regulator Spray Records: PHI and Application Precision Requirements worth it?

Vineyard Spray Records in Ohio: ODA Requirements for Lake Erie Shore Vineyards

Sources

California Department of Pesticide Regulation (CDPR)
UC Cooperative Extension Viticulture
UC Davis Department of Viticulture and Enology
USDA Agricultural Research Service
American Vineyard Foundation

Get Started with VitiScribe

PGR applications have the narrowest acceptable rate ranges of any pesticide category in the vineyard, and a 10x concentration error from a mixing calculation mistake can delay harvest by 10-14 days -- a cascade that affects the entire season schedule. VitiScribe validates PGR rates against label data at the time of entry, triggers supervisor notification for out-of-range entries, documents tank concentration calculations alongside growth stage at application, and tracks PHI against anticipated harvest dates. Try VitiScribe free and log your first PGR application with full rate verification today.