# Pesticide spray records: assemble a complete Irish treatment file

URL: https://leafwrit.com/ie/pesticide-spray-records/
Reviewed: 2026-10-27

For **pesticide spray records in Ireland**, start with [DAFM's official record-keeping collection](https://www.pcs.agriculture.gov.ie/sud/professionaluserssprayeroperators/recordkeeping/). It provides crop and amenity application sheets, completed examples and purchase/disposal sheets. Professional-use records cover purchases, disposals, applications and the implementation of Integrated Pest Management (IPM). An application row is one part of that file.

Use this guide to identify what belongs together and what each document proves. For line-by-line form completion, open the [spray record sheet guide](/ie/spray-record-sheet/); for the sequence from field note to office entry, use the [daily farm workflow](/ie/farm-spray-records/).

## Separate the documents before filling gaps

DAFM's end-user requirements distinguish the supplier and products received, the products actually applied, and products returned or disposed of. Its application requirements include the date, crop and area, actual quantity and rationale for use. The purchase and disposal sections identify different transactions.

| Document in your working file | Question it should help you answer |
| --- | --- |
| Application record | What treatment actually happened at this location? |
| Purchase evidence | Which supplier delivered which product and quantity? |
| Return or disposal evidence | Which recipient took the material, when and in what quantity? |
| IPM material | What observation and decision explain the treatment? |
| Product and equipment references | Which label, machine and nozzle documents explain the entry? |

Give these categories separate headings in your own contents list. Cross-reference them using the product identity and your job reference. Keep the operator's original report beside any office transcription. That arrangement lets you follow an event without mistaking the paperwork for a different event.

For example, an invoice may help locate the supplier transaction in your archive. To establish the container used during spraying, DAFM's completed crop instructions expressly direct you to the container for both product name and PCS number. Preserve that distinction when reconciling an unclear abbreviation.

## Establish the application, location and responsible person

DAFM's crop example asks for a herd number or equivalent, the application date, crop/situation, location/LPIS, treated extent, application rate, water volume, method, aquatic buffer, conditional nozzle details, IPM reason, applying PU and sprayer certificate. These are the headings of the published crop example.

Begin your review with the completed job rather than the purchase date. Find the location description and compare it with the operator's report. Distinguish the person who applied the product from whoever entered the row later. Keep a recognisable machine reference alongside the certificate information in your equipment file.

DAFM permits several location/LPIS references together when locations with the same crop or situation receive the same spray programme. If you use that arrangement, keep the list readable and attached to the programme concerned. A shared heading should still let the reader identify the locations to which each entry relates.

Use familiar field names as additional navigation aids in your own index. Preserve the documentary reference beside the familiar name. When a plot is divided, renamed or taken out of a contract, retain a dated explanation of the change with the historical file. This is a filing method, not a new official parcel-identification system.

## Keep the quantities understandable

The end-user guidance asks for the quantity of each product applied in kilograms or litres. The completed crop sheet separately identifies treated area or tonnage, product application rate and water volume. Its instructions emphasise clear units. Keep these quantities distinguishable when transferring notes into a spreadsheet.

Label the columns with their meaning and unit. A number standing alone should prompt a question to the operator, not an assumption by the person typing it. For a multi-product job, preserve each constituent's name and quantity. Attach a continuation sheet if the original report runs out of room.

When reviewing a discrepancy, compare like quantities. First establish whether the note describes product, water or treated extent; then establish its unit. Save the clarification with the affected entry. Avoid replacing a reported quantity with a value calculated from a plan unless the operator's supporting information explains the correction.

The [tank-mix calculator](/ie/spray-tank-mix-calculator/) can help organise arithmetic using values you supply. Keep the completed-treatment information in the records and the calculation assumptions in the working note. A tidy total does not resolve an unidentified container or an uncertain treated location.

## Connect the reason for use to IPM evidence

DAFM requires records showing implementation of the general IPM principles. Its IPM page links guidance and describes prevention, monitoring, non-chemical methods, targeted pesticide selection, anti-resistance strategies and recording success. Its crop example includes a rationale/reason-for-use field. Use these resources together when deciding where the supporting explanation belongs.

Write a concise reason connected to the actual location and issue assessed. Refer to the scouting note, observation or adviser information you hold. Keep a later assessment of the outcome distinguishable from the explanation recorded before the job. Preserve both under the same treatment reference.

During an office review, ask whether somebody unfamiliar with the field can follow the explanation. An unexplained code may be useful to the operator but difficult for a colleague to interpret. Add a key in the season folder or expand the wording in the supporting note, preserving the original report.

## Use the DAFM IPM sheet for the holding and notes for each decision

An IPM record should show what you observed, why you acted and what happened afterwards. DAFM's [IPM and Pesticide Application Record Sheet](https://www.pcs.agriculture.gov.ie/media/pesticides/content/sud/professional/1.%20IPM%20Pesticide%20Application%20Record%20Sheet%20080223%20140223.pdf) covers the practices on your holding as a whole, and dated crop notes cover each single decision. The form says to tick only the practices you actually follow.

The sheet is built around prevention, monitoring, decisions, non-chemical methods, specificity, necessary use, resistance strategy and results, and it asks for your herd number (or equivalent) and the year. Read each group against what you really do. Treat the printed examples as prompts, not as boxes to fill: use the Other space for a short explanation of a practice that fits none of them, and never claim a method only because it appears on the sheet.

Use the prevention and non-chemical groups to talk through rotation, hygiene, resistant varieties, mechanical work or biological control on the field in question, and record what you did and which problem it addressed. Keep any [biological-control enquiry](/ie/biological-pest-control/) specific to the organism and the crop: a general remark that beneficial insects are welcome does not describe a commercial release or a microorganism treatment. For a grassweed problem, keep the patch and the field history, and use the [resistance guide](/ie/italian-ryegrass-varieties/) to investigate survivors and plan alternatives across the rotation.

## Write a scouting note and a no-spray decision someone else can follow

Start a scouting note with the date, the crop, the field or structure and the exact area you inspected. Add what you saw and how you looked. Keep a trap count, a symptom description and an adviser's diagnosis apart. If you use a threshold, note where it comes from and which crop or pest situation it covers. Ask the adviser how your observation supports the next decision rather than inventing a trigger for every field.

The DAFM form lists forecast use, crop monitoring, adviser involvement and traps as monitoring options. Tick what you used, and keep the dated evidence behind any operation it informed.

Agree a route through the field and record the crop stage, the places inspected, the sampling method and the counting unit: per plant, trap, leaf or length of row. Mark uncertain identifications. If you looked at only part of the field, say so, add a sketch or a marked photograph of an affected patch, and separate the margins from the interior. One badly damaged plant tells you little about the whole holding, but keep the note that raised the concern while you seek identification.

A decision not to spray belongs in the file too. Write down what you observed, who decided, why you did not treat and what follow-up you planned. Say what would bring you back to the field or send you to the adviser. Keep it as a crop decision, not as a pesticide application. If you treat later, keep the earlier entry, because the sequence shows how the situation developed.

An example shows the structure. A first visit records symptoms at a mapped corner, and a later adviser visit finds a different cause from the scout's first guess. Keep both entries with their dates and authors, so the corrected diagnosis steers the next decision without erasing what was first seen.

## Review the result at the marked location

The last group of the DAFM form covers the success of the measure: whether it was measured and recorded, and whether the results were discussed with the adviser. Agree what you will assess before you judge the outcome. Keep measured observations apart from an overall impression, and note other work or weather changes that affect the comparison. A better-looking crop does not by itself show the effect of one intervention.

At the season review, keep the observations that support next year's plan. For each failed control, write down the likely cause and the change you plan. Fill in the holding-level sheet from that real history, and keep a practice you used apart from an improvement you only propose.

## Obtain the contractor's relevant records

Article 4 of Regulation 2023/564 requires a professional user acting under a contractual arrangement to give the contracting person access to the relevant records, or a copy, without undue delay or restriction. This concerns access to the records; an invoice alone does not describe the application particulars listed in the regulation's annex.

Before requesting a missing report, identify the customer, place and work concerned in your message. Ask for the application information and any clarification needed to interpret it. Keep the response and original attachment together. If you transcribe the contractor's row into your own system, preserve the link back to that attachment.

Prepare a short list of unresolved items instead of sending the whole season back for correction. Separate an unreadable identifier from a missing quantity and a disagreement about location. Close each question using the contractor's answer and retain that answer with the job. This makes a subsequent customer copy explainable without reconstructing a telephone conversation.

## File purchases and disposals using their own particulars

DAFM's purchase particulars include supplier name and address, brand name, PCS, pack sizes and quantities received. For a return or disposal, its guidance identifies the receiving company or organisation, product brand and PCS, transaction date and quantity. Keep the source transaction documents with those entries.

Create an archive reference for each delivery, return or disposal document. Record which physical folder or electronic attachment contains it. Where a receipt uses a shortened description, preserve the receipt as received and attach the clarification used to identify the product.

Use reconciliation as a way to find questions. If the amounts in your purchase, use and disposal records do not explain a difference, list the missing transaction or uncertain unit for investigation. Keep stock-count observations identifiable as observations. Do not create a fictitious application to make the arithmetic balance.

## Read electronic-record changes as separate rules

Regulation 2023/564 sets detailed record content and machine-readable electronic format requirements and applies from 1 January 2026. Its annex distinguishes area treatments, enclosed spaces and seed/plant reproductive material treatments. Depending on the use, it includes product authorisation, location, extent or quantity, crop/land-use coding and conditional growth-stage or start-time particulars.

The later Regulation 2025/2203 amended Article 3: Member States may allow records of uses on their territory before 1 January 2027 not to be transferred into the prescribed electronic format. This is a Member State option in the EU text. It does not announce an Irish national decision or create a universal exemption from recording applications.

For your own file design, keep structured fields separate from supporting photographs. Preserve the date, product identity, units and location as identifiable values when migrating a season. Save any authority correspondence about your own recording arrangements with its date and scope. Do not label a general spreadsheet or PDF an approved submission merely because it contains a treatment table.

## Match the record to the type of treatment

The annex to Regulation 2023/564 uses hectares for area treatments. For enclosed-space treatments it describes installation identification and treated cubic metres or square metres. For seed or plant reproductive material, including seed potatoes, it uses the treated quantity and, where applicable, a batch number. The associated dose denominator changes with the type of use.

Keep a specialist treatment in the appropriate category when designing your workbook. A grain-store treatment and a field application should not acquire identical units simply because they were performed by the same business. Preserve the original description of a seed lot or installation; create an additional explanatory reference if your office uses a different naming convention.

The annex's notes make start time and growth stage conditional: for example, when the authorised use is restricted to particular times or stages, or the information is relevant to that use. They also address identifying a treated fraction of an area. Keep those qualifications with the corresponding headings instead of filling every optional-looking cell with an arbitrary value.

## Resolve a specific documentary fault

Use the following examples as an editorial troubleshooting exercise, with no invented pesticide, dose or treatment date.

| Fault discovered during review | Document or clarification to retrieve |
| --- | --- |
| Illegible PCS suffix or digit | Container identification supplied for the actual job |
| Denominator missing from a quantity | Operator clarification of the unit and meaning |
| Whole parcel listed for a partial treatment | Original sketch, mapped fraction or location description |
| Contractor's trading name entered as the operator | Report identifying the person who applied the product |
| Empty reason column | Contemporaneous observation or decision explanation |
| Repeated row after copying attachments | Source report establishing whether this is a duplicate |
| Product name replaced after a catalogue update | Original label evidence and dated transcription history |

Retain the unresolved issue in your working list until the source explains it. Ask a precise question, attach the relevant extract, and identify which entry the reply concerns. This approach keeps a reconstructed office record distinguishable from a field observation and prevents an attractive printout from hiding an unfinished enquiry.

## Keep label changes separate from diary changes

Regulation 2026/1123 concerns product labelling. Article 14 sets application from 1 January 2028, and Article 12 contains transitional provisions. It is a different instrument from the professional-user record-content and electronic-transfer rules. Its publication does not mean every container already has a digital label in October 2026.

DAFM's register resources distinguish plant protection product lists and associated authorisation information. Use the [Irish register guide](/ie/pesticide-register-ireland/) to follow that route. Keep the exact product and PCS identification from the container alongside the label or authorisation material used to explain a historical job.

For a buffer decision, use the dedicated [STRIPE record guide](/ie/stripe-buffer-zone-records/). Store the label passage, relevant nozzle identification and distance actually applied with the treatment. This overview connects that specialist evidence to the complete file; it does not choose a buffer or an application rate.

## Retain a retrievable record through a system change

Article 67 of Regulation 1107/2009 requires professional users to keep their plant protection product use records for at least three years. It covers product name, time and dose, area treated and crop, and requires the relevant information to be available to the competent authority on request. Keep the retention obligation attached to the historical records when changing software or staff.

Choose a season folder with an intelligible contents list. Preserve originals, explanations and the copy issued to a customer. If an entry is corrected, identify which treatment it concerns and retain the evidence behind the correction. Keep a cancelled plan distinguishable from completed work so it cannot be mistaken for another application during migration.

Test retrieval by asking a colleague to locate a treatment from a field name, then from a contractor reference. Follow the entry to its product evidence, reason and original report. Open exported material independently of the entry screen. Check that wrapped headings, decimal values and long identifiers remain legible after printing or transfer.

## Finish with a clear handover

Use the following editorial checklist when assembling your own pack. It organises the documents discussed above; it is not a prescribed additional government form.

- Mark the holding, season and person responsible for resolving questions.
- Locate the completed application history and its original source reports.
- Provide the field/location index and explanations of internal abbreviations.
- Connect purchase, return and disposal entries to their transaction evidence.
- Keep IPM observations and decision explanations beside the corresponding treatments.
- Reference the product documents and equipment details used for specialist decisions.
- List outstanding questions explicitly and preserve the answers when received.
- Identify the final customer copy and the place where originals remain available.

For a visit-specific evidence pack, continue to the [pesticide records inspection guide](/ie/pesticide-records-inspection/). For choosing a paper layout, use the [agricultural spray record book guide](/ie/agricultural-spray-record-book/). The [Irish hub](/ie/) links the other tasks without requiring you to treat every document as one form.

### Pesticide spray records?

For professional-use products, assemble application, purchase, disposal and IPM records. DAFM supplies different sheets for these tasks; keep their references connected.

### How long to keep spray records?

Article 67 of Regulation 1107/2009 sets a minimum of three years for professional users' application records.

### Spray record sheet?

DAFM's record-keeping collection links crop and amenity sheets and completed examples. Choose the document for the treatment setting.

### Farm spray records?

Identify the actual application and its product, location, date, quantities, operator and reason. Keep the original contractor report with the corresponding entry.

### Spray application record sheet?

Use the completed crop instructions to interpret the headings. Product and PCS identifiers come from the container used; a purchase invoice belongs in the purchase record.