Farm spray records: capture the job and finish the handover

This page follows the daily handover from operator to office. For the printable document, open the spray record sheet guide. For evidence assembled around a visit or review, use the inspection guide. Keep those purposes connected while preserving the original job information.

For an overview of the application, purchase, disposal and IPM documents to assemble, use the pesticide spray records file guide.

Prepare a field note that can become a complete entry

Before work, identify the holding, treatment place and intended application. Keep a planning entry clearly distinguishable from the finished record. If the job changes, preserve what actually took place rather than copying every planned line into the historical diary.

DAFM’s completed example includes herd identification, date, product name and PCS, crop/situation, location/LPIS, treated extent, rate, water volume, method, buffer, conditional STRIPE nozzle detail, reason, applying PU and sprayer certificate number. Use those headings to organise the operator’s handover.

Prepare a working location list in a form the operator recognises. Include ordinary field names beside formal references where useful. DAFM identifies the most recent BISS application as a source for the LPIS/location reference. Resolve any uncertainty about which parcel is meant before completing the application history.

Distinguish the application date from office administration

The date-applied field in the DAFM guide means when the product was applied to the crop or situation. It is separate from the date a report is received, checked or typed into a workbook.

Keep the operator’s original note with its source and the job reference. If the office receives a report later, record the receipt in your administration notes without replacing the application date. Ask the operator to clarify an ambiguous date while their supporting diary or job information is available.

When work spans different days, preserve the actual relationship between each application and its date. Do not consolidate separate events solely to make a page look tidy. Give the office enough context to understand whether two lines describe different products in one job or separate applications.

If a planned treatment is postponed because of weather, leave it in the planning list with its reason. The rain guide helps organise the decision information. A later completed treatment gets the date on which it actually occurred.

Identify the product from the container used

DAFM’s instructions say to copy the product name from the container, not an invoice. For PCS, the guide also directs users to the actual container and expressly excludes an invoice or the PRCD website as the source for that recorded number.

Preserve the full name and distinguishing suffix when passing the note to the office. Keep each product in a mixture independently identifiable. If the supplied name is incomplete, ask a question tied to the original job rather than choosing a similar name from a saved catalogue.

The pesticide-register guide explains authorisation research. Use it to investigate the product and its documentation, while keeping the recorded identity of the container actually used. Store a clarification alongside the original note so the reason for the final spelling or identifier is recoverable.

For a historical correction, preserve the original evidence and the explanation. A current product lookup and a question about a past container are different tasks. Record which task is being resolved before changing the season copy.

Keep area, rate, total product and water distinct

DAFM separates area/tonnage, pesticide rate and water volume in its crop sheet. Its end-user requirements also include quantity actually applied in kilograms or litres. Clear units are essential to understanding the individual values.

Keep the heading and unit with a number when transferring it between phone notes, paper and workbook. Ask whether an unexplained figure means a rate or a total before filing it. Retain the operator’s answer with the report it repairs.

Use the tank-capacity calculator for arithmetic with established inputs. Keep a batch plan distinguishable from actual use. If the treated area changed, reconcile the completed report against the original plan and explain the difference in the handover.

Link the reason to the observation

DAFM’s record-keeping page requires IPM evidence demonstrating the general principles, alongside purchase, disposal and use records for professional-use products. The crop example provides an IPM rationale/reason-for-use field.

Write the observation supporting the intervention in a retrievable form: affected place, issue assessed and the associated monitoring or decision note. A short application cell can point to a fuller assessment where necessary. Preserve the assessment with the job reference rather than relying on a spoken explanation months later.

Record subsequent observations separately from the initial reason. If control appears poor, keep that outcome note with its date and author. A transcription correction answers what was entered incorrectly; a later field observation describes the treatment’s outcome. Keep those two kinds of note distinguishable.

For grassland, use the grassland record guide to organise paddock and weed information. For sensitive public settings, follow the local-authority guide for the separate assessment pack.

Obtain a usable contractor handover

EU 2023/564 requires professional users working under contract to give the client access to the relevant records, or a copy, without undue delay or restriction. Keep the delivered file connected to the customer’s treatment location.

Before the job, agree the practical delivery contact and file arrangement. Afterwards, review whether the copy identifies the application date, product, treated place, quantities and applying operator. Ask a targeted question about any missing unit or location. Preserve the original file and the corrected version with a note explaining their relationship.

If several customers appear in a contractor’s office system, ensure the copy in your farm file clearly identifies your holding and work. Use a job reference in correspondence. Keep an invoice as the commercial document and the application report as evidence of the treatment details; connect them through the reference you use.

Account for the current EU content and format rules

EU 2023/564 applies from 1 January 2026. Its annex sets information by use type, including product name and authorisation number, timing, dose, location, treated extent and crop/situation information. Crop and land-use coding and conditional growth-stage information form part of that framework. The older DAFM example remains useful for field meanings, but assess the newer requirements when defining your record structure.

The regulation also specifies machine-readable electronic records. The later EU 2025/2203 amendment allows Member States to permit records for uses before 1 January 2027 not to be transferred to that format. That option is not itself an Irish instruction announcing a national postponement. Keep a structured electronic working record when organising the season rather than treating the printed example as proof that the format question is settled.

For an office mapping exercise, list every source field, its unit and its destination in the workbook or diary. Preserve the ordinary crop name alongside the relevant coded information. Keep the original report available when checking an import so an apparently successful transfer does not conceal a lost denominator or location reference.

Keep purchases, use and disposal connected

DAFM’s end-user guidance describes purchase records identifying supplier, product brand and PCS, pack sizes and quantities received. Return or disposal records identify the receiving company, product, date and quantity.

Give those transactions their own source references. Link them to the product history without forcing all paperwork into an application row. A pack received, a quantity applied and a remainder returned describe different events; preserve each event’s actual date and evidence.

During a monthly office review, choose a product entry and retrieve the related purchase document. Then locate an application and its operator note. Finish by checking any relevant return/disposal evidence. Resolve a broken link in the file while the people involved can still explain it.

Finish a season copy somebody else can retrieve

Article 67 requires professional users to retain application records for at least three years. Preserve the underlying notes and delivered reports when reorganising the archive.

Create an index by season and holding. Check that a colleague can retrieve a field history, identify the operator and open the attached source report. Inspect a printed or exported copy with long names and decimal quantities; keep its headings, references and units readable.

Leave a short list of unresolved transcription enquiries with their owner and the evidence needed. When answered, file the clarification beside the entry concerned. Keep future jobs, completed applications and corrections identifiable throughout the handover.

Give the office an intelligible location description

DAFM’s location/LPIS field identifies where the treatment took place, while the crop/situation field describes what was treated. Preserve both meanings during the handover. The guide’s examples include crops, grassland, yards and associated areas.

For a partial field treatment, add a description or supporting sketch that another person can follow. Label the treated sector and its relationship to the formal parcel reference. Keep the sketch’s job reference visible so it cannot be confused with a plan prepared for a different application.

For an orchard or vineyard, use the block names your business recognises alongside the formal location information. For protected cropping or material treated by tonnage, preserve the appropriate use-type and quantity basis in the record structure. EU 2023/564 distinguishes types of use in its annex; do not force a different treatment setting into an unexplained hectare column.

Check the applying person and machine independently

DAFM’s PU field identifies the registered person who applied the product, including an owner or contractor. The sprayer certificate field refers to the number located on the equipment. These identifiers answer different questions.

At handover, ask who actually carried out the work and which machine was used. If the planned operator was replaced, preserve the substitution in the application report. If the office entered a saved default, compare it with the operator’s original evidence before filing the final row.

Use a people directory and equipment directory as navigation aids, with references to the supporting documents. Keep historical identities available when the current team or machinery changes. An older job should remain understandable after an employee leaves or a sprayer is sold.

Record aquatic-buffer and nozzle information with context

DAFM’s crop instructions include the aquatic buffer actually applied and make the nozzle field conditional on use of STRIPE to reduce the buffer. The nozzle entry is not a generic requirement to insert any remembered nozzle name in every row.

Keep the relevant product and site evidence with the decision. Write the distance with its unit and retain the specific nozzle identification where it supports the STRIPE use. If the operator’s report contains only a reduction category, ask for the details needed to understand the actual equipment used.

Use the STRIPE guide for that evidence trail. Avoid replacing an actual buffer entry with a copied label figure unless the source information explains that they describe the same applied condition. Preserve any clarification with the original job report.

Handle a report with missing or contradictory information

Create an enquiry note identifying the job, uncertain field and person able to clarify it. Quote the relevant entry in your internal correspondence, including its heading. Ask whether a number describes rate, total product or water volume instead of asking somebody to “check the figures” without context.

Keep the original report readable. When the answer arrives, record the correction and its source. If two documents give different dates or locations, resolve the discrepancy from the underlying evidence rather than choosing whichever version is easiest to import.

Maintain a short outstanding-enquiry list with an owner and next action. Review it before issuing a season copy. A file marked complete should not depend on an unanswered question stored only in somebody’s personal message history.

Keep a daily handover manageable for several operators

Choose a practical collection point for field notes and contractor reports. Give every report a recognisable holding and job reference before it moves to the office. Separate the operator’s description from the office checklist used to verify that all documents have arrived.

For repeated work, review the application date, actual place, crop, products, quantities, method, buffer, person and equipment rather than copying a previous row unchanged. The official example’s headings provide a useful review structure; a repeated programme still needs an accurate description of the actual application.

At the end of the handover, tell the operator which entries are filed and which need clarification. Keep the response concise and tied to the affected job. This prevents a general discussion of missing paperwork from becoming detached from the specific record being repaired.

Prepare a copy for an adviser or inspection enquiry

Identify the requested holding, period and purpose before selecting records. Assemble the application rows and the supporting documents needed to understand them. Open the delivered copy and inspect names, dates, decimal places and attachment references.

Keep a contents note explaining where the IPM rationale, contractor source report and relevant product documentation can be found. Preserve the request and the copy supplied. If further clarification is needed, keep it connected to that response set rather than altering unrelated historical records.

Use the inspection guide for the wider evidence pack. The daily workflow here is the foundation: a legible, attributable application entry that retains its source information and can be retrieved without reconstructing the season from memory.