# Link spray records to harvest intervals and site access

URL: https://leafwrit.com/uk/harvest-interval-spray-records/
Reviewed: 2026-10-23

For a **Red Tractor Fresh Produce** operation, the spray record includes the harvest interval and the **first permissible harvest date**. PR.EC.8.1 separately requires systems ensuring statutory harvest intervals are respected. Keep those fields connected with the product, application and identifiable crop so the person arranging harvest can locate the relevant treatment history. [^1]

Harvest, worker access and livestock access answer different questions. The Scottish pesticide code explains that records help track each of these conditions, as well as intervals between repeat applications. GB regulation 12 requires product use to meet the conditions in its authorisation and label. Use the actual product conditions for the next planned activity. [^2][^4]

## Begin with the product and actual application

Identify the full product, applicable use and treatment date before calculating or communicating a restriction. HSE's register offers authorisation searches, notices for changes and information on withdrawn products. Keep the relevant authorisation reference beside the application information used in your business. [^5]

A label or notice describes conditions for an authorised use; your diary describes what happened at a particular place. Preserve the connection between them. If the product identity or treatment timing is uncertain, obtain clarification from the operator or original document before entering a first permissible date.

Where a crop has several treatments, review the full relevant history for the intended harvest. Do not select one convenient row while overlooking another product entry for the same crop. Keep the product-specific information separate enough that a reviewer can establish which treatment each restriction belongs to.

## The Fresh Produce scheme fields

PR.EC.8 requires records of all PPP applications, including seed, rootstock and young plants, in-field treatments, crop-store treatments and post-harvest uses. The scheme's field list includes the following information. [^1]

| Record group | Fresh Produce entries |
| --- | --- |
| Crop identity | Crop and variety; sowing or planting date |
| Location | Field or store identifier for post-harvest treatments |
| Application | Date and time; reason or target |
| Product | Product name, active ingredient and application rate |
| Conditions | Water volume, wind direction and speed |
| Harvest | Harvest interval and first permissible harvest date |
| Responsibility | Sprayer operator's name |

Retain the meaning of each field when reorganising a form. A crop identifier should let the harvest team locate the same production unit described in the treatment record. A variety name can support that identity, while the field or store reference connects the entry to a place. [^1]

For your own procedure, agree how identifiers appear in the treatment diary, harvest plan and customer or contractor reports. Keep a correspondence for older names and avoid replacing them in historical entries without explanation. The objective is to follow the crop history through the documents used by different people.

## Transfer the restriction into a usable date

Fresh Produce records ask for both the harvest interval and first permissible harvest date. Store the applicable restriction and the resulting date together, retaining the product and application reference used to derive them. A date entered without its basis is harder to review when the treatment record is corrected. [^1]

Read the applicable conditions carefully before applying arithmetic. A product's restriction can depend on its authorised use, and the record needs to preserve the relevant context. This guide does not supply a standard number of days for pesticides generally: that number belongs to the actual product and use being documented. [^4]

Use a review step when the date is passed to the harvest planner. Compare the treatment date, product identity and condition with the completed field. Keep the reviewed version and make the person scheduling harvest aware of a correction that changes it. Record this as your own management procedure rather than presenting it as an official additional form.

## Example: an invented restriction used for arithmetic

This is a **fictional date calculation**, not a recommendation for any pesticide or crop. Assume an invented instruction says harvest must wait until **168 complete hours** after an application ending at **10:00 on 1 June 2026**. Seven blocks of 24 hours give 168 hours, reaching **10:00 on 8 June 2026**.

| Fictional input or result | Example value |
| --- | --- |
| Application completion | 1 June 2026, 10:00 |
| Invented interval | 168 complete hours |
| Arithmetic result | 8 June 2026, 10:00 |

The calculation illustrates why a time can matter when an instruction uses elapsed hours. It establishes no authorised seven-day interval. For an actual application, preserve the product's wording and use the date or stage rules that apply to that use, instead of adopting the invented instruction here.

## Keep worker and livestock access distinct

The Scottish code names periods when workers cannot enter treated areas and periods when livestock cannot go onto them. Annex F includes those restrictions, harvest and ventilation among the relevant information to record. A harvest date should therefore not silently become permission for every other activity on the site. [^2][^3]

Create separate references in your own schedule for harvest, worker tasks and grazing where the actual conditions require them. Identify the treated unit, responsible contact and source of the restriction. Provide the information to the person organising the relevant activity, and keep the communication tied to the treatment record.

If a contractor completed the treatment, obtain the information needed for the site's next use. Ask for the particular product condition and application detail behind an unclear restriction. The [contract handover guide](/uk/contract-sprayer-records/) explains how to keep the customer copy connected with the applicator's original.

## Include bought-in treated material

PR.EC.8.2 requires records for bought-in seed, rootstock and young plants treated with PPPs. The scheme therefore includes a documentary route for treatments that were not applied by the grower's own sprayer to an established field crop. [^1]

For an orchard or propagation operation, connect the incoming material with its supplier documents and the crop identity used after planting. Keep the treatment information available with the corresponding planting record. If the supplier's description does not identify the material clearly enough, ask for the detail needed to follow the batch in your own system.

Do not add an invented orchard-specific pesticide interval to fill a blank. Use the applicable treatment information and product conditions. The verified scheme fields provide the traceability framework; a particular product case requires the actual authorisation and treatment evidence for that case. [^1][^4]

## Biological controls have their own record

Fresh Produce PR.EC.8.d requires records of biological-control applications, such as natural predators, and other substances not classed as PPPs. PR.EC.8.4 recommends following and documenting professional guidance on biological controls where it is provided. Keep those records recognisable within the crop history. [^1]

Use a description that identifies the intervention rather than forcing it into the identity of a chemical product. Preserve the source of any guidance and its relationship to the crop. If your diary contains several intervention types, make them distinguishable when exporting or reading a crop history.

## Review harvested output against treatment history

The scheme's harvest-interval requirement is a system requirement as well as a field in the spray diary. Organise the records so the relevant crop and application history can be found before the harvest decision is recorded. [^1]

For a practical review, choose a crop unit and assemble its treatment entries, applicable restrictions, first permissible dates and harvest documentation. Compare identifiers and application times. Ask someone responsible for the harvest schedule to find the same information without help from the original sprayer operator.

If a discrepancy appears, preserve the documents involved and resolve it with the person holding the original information. Document any change to the first permissible date and identify the schedule or report affected. Keep the reason with the revised entry so another reviewer can follow the decision.

## Keep records readable through the retention period

Fresh Produce PR.EC.8.c requires application records for at least three years. The Scottish code also explains the value of keeping treatment information accessible at the farm or local office, including contractor copies. [^1][^2]

Use an archive index that links crop or variety, field or store, application period and supporting documents. Before changing software, export a sample crop history and compare it with the original record. Retain the information needed to reconstruct the restriction, rather than saving only a summary that loses product or date detail.

For form completion, continue with the [spray-record guide](/uk/spray-record-form/). For electronic data choices, use [spray log apps and exports](/uk/spray-log-app/). Keep the operational purpose in view: the record must connect the actual treatment with the subsequent harvest or access decision.

## Keep the planting and treatment chain together

Fresh Produce distinguishes bought-in treated propagation material from applications recorded on the holding. Connect delivery references, supplier paperwork, rootstock or young-plant identity, planting information and subsequent interventions in your archive. The scheme requires treated-material records and includes sowing or planting dates in the application-record framework. [^1]

For a practical reconciliation, start with the incoming batch and identify where it was planted. Follow the crop or variety into its field history, then locate the relevant treatment and harvest documents. Preserve explanations for renamed blocks, split deliveries or changes in internal identifiers. This is a suggested traceability exercise, allowing a colleague to follow the same production history without relying on personal recollection.

### What must pesticide application records include for harvest planning?

Red Tractor Fresh Produce PR.EC.8.b includes harvest interval and first permissible harvest date alongside crop, product, date, rate, water, wind and operator information. [^1]

### How long to wait after herbicide spray?

Use the actual product’s applicable conditions for the intended next activity. Harvest, worker entry and livestock access are separate restrictions recorded as relevant; this guide gives no universal waiting period. [^4][^2]

### How do fruit and vegetable spray records connect with harvest?

Keep the actual crop identity with each treatment and its relevant harvest interval or first permissible date. DAERA supplies separate fruit and vegetable crop-code lists, while Fresh Produce PR.EC.8 includes crop/variety and harvest information. [^1] [^7]

### Do farm spray records include bought-in young plants?

Fresh Produce PR.EC.8.2 requires records for bought-in seed, rootstock or young plants treated with PPPs. [^1]

### Can an orchard use a spray diary?

Use an identifiable crop or variety and field record, with the applicable product conditions and harvest history. Fresh Produce records include crop variety, planting date and bought-in treated plant material. [^1]

### Do pesticide records include worker and livestock restrictions?

The Scottish record guidance explains that treatment records support worker-entry and livestock-exclusion periods, separately from harvest and repeat-application intervals. [^2]

## Sources

- [Red Tractor — Fresh Produce Environment standards, version 5.1, PR.EC.8–8.2](https://redtractor.org.uk/assurance/standards/environment-6/), read 2026-10-23
- [Scottish Government — pesticide code, Section 6: keeping records (2007)](https://www.gov.scot/publications/pesticides-code-practice-using-plant-protection-products-scotland/pages/9/), read 2026-10-23
- [Scottish Government — pesticide code, Annex F: record sheet for pesticide treatments](https://www.gov.scot/publications/pesticides-code-practice-using-plant-protection-products-scotland/pages/15/), read 2026-10-23
- [FAOLEX — official UK Plant Protection Products Regulations 2011, consolidated copy generated 18 May 2023](https://faolex.fao.org/docs/pdf/uk110361.pdf), read 2026-10-23
- [HSE — Pesticides Register of Great Britain and Northern Ireland Authorised Products](https://secure.pesticides.gov.uk/PestReg/default.asp), read 2026-10-23
- [DAERA: template user guidance, July 2026](https://www.daera-ni.gov.uk/sites/default/files/2026-07/Template%20Guidance.pdf), read 2026-10-23
- [DAERA — PPP Spray Record Template and Guidance, 7 July 2026](https://www.daera-ni.gov.uk/publications/plant-protection-product-spray-record-template-and-guidance), read 2026-10-23