An IPM monitoring sheet records the observations behind a pest-management decision. It differs from the application record of a plant protection product actually used. Malta’s legacy ARPA AECM guidance contains an “IPM Monitoring Sheet” in Annex 10, with parcel, date, pest, pests present and traps checked. The EU application-record Annex instead identifies the product, authorisation, dose, location, treated extent and crop or situation. [1][2]
Identify the official sheet and its historical scope
The ARPA AECM guidance PDF is version 3.7 dated 5 February 2020, covering the Rural Development Programme 2014–2020. Its Annex 10 appears on printed page 47. The blank monitoring table has name, identity and year above the observation rows. Describe it as the legacy monitoring template from that document, with its date visible in your archive. [1]
That source also reproduces the general IPM principles in Annex 9. The current-period CAP Strategic Plan version 3.1 separately describes DP ECO-IPM commitments, including dated monitoring, pest identity and the number recorded, with traps installed according to the plan. The historical template and the CAP commitment description are different documentary sources. Keep each attached to its own purpose. [1][3]
A download of an older blank table is useful for understanding the observation headings. It does not turn the publication into a new application form or establish a fresh scheme application deadline. Use the BiedjaCam and crop-plan guide for the published digital workflow and the separate IPM scheme context. [1][4]
Read the observation headings as a connected event
| Heading in the legacy sheet | What the recorded information identifies | Practical entry discipline |
|---|---|---|
| Name, identity and year | The person and annual document | Keep the sheet associated with its original season |
| Parcel | The place monitored | Explain the parcel reference used in your own files |
| Date | The observation visit | Distinguish observation from any later intervention |
| Pest | The monitored organism | Retain the actual identification or adviser clarification |
| Number of pests present | The recorded count | Preserve the observation and its counting context |
| Traps checked | The inspection of the traps | Connect the count with the traps and visit concerned |
The headings come from Annex 10. Its footnotes connect the pest monitored with the farmer’s IPM and the stage being monitored; the document’s own example belongs to that legacy guidance. This guide does not supply a new pest threshold or a recommendation to apply a product. [1]
For your working procedure, prepare a reference list for trap positions and parcel nicknames. Identify what was inspected on each visit so a subsequent reader can understand a count. A bare number becomes difficult to interpret when the sampling method changes without explanation. Record the method or explanatory note in associated working material rather than silently pretending two different observations are identical.
Start with prevention rather than with a product entry
Annex III of Directive 2009/128 lists prevention or suppression approaches including crop rotation, cultivation techniques, resistant or tolerant cultivars, suitable seed and planting material, balanced fertilisation, irrigation/drainage, machinery hygiene and protection of beneficial organisms. These are elements of the IPM framework, not a requirement to invent an application every time a parcel is visited. [5]
For an adviser discussion, describe the actual practices relevant to the parcel. Keep a cultivation or hygiene note connected to the crop and season it concerns. Distinguish an existing practice from a proposed change. That simple separation helps the adviser understand the situation without converting every discussion into a claim that a particular action was performed.
Malta’s CAP plan includes a list of techniques for the IPM plan, such as pruning and tillage methods, field and seedbed sanitation, pest-resistant varieties, management of planting or harvesting dates, irrigation, soil/nutrient management, predator populations, traps, biological inputs and other specified approaches. Under the described commitment, the IPMP includes at least three of the listed techniques. These are scheme-plan requirements in that version of the CAP document. [3]
Record monitoring before interpreting the need to intervene
The Directive’s monitoring principle includes adequate methods and tools where available, field observations, scientifically sound warning or forecasting systems where feasible, early diagnosis and qualified adviser input. Its decision principle ties whether and when to apply plant protection measures to monitoring results, with robust, scientifically sound thresholds and relevant regional, crop and climatic conditions where feasible. [5]
Keep a warning notification distinguishable from your own field observation. Record its source and relevant date in the supporting material, then link it to the parcel visit or adviser enquiry it informed. A forecast and an observed count describe different information even if they concern the same pest. Preserving both helps explain the reasoning without overstating what was actually seen.
For a doubtful organism identification, retain the original observation and obtain a clarification from the appropriate adviser. Explain whether the clarification changes the pest name or the interpretation of its significance. Avoid rewriting an older count to make it fit a later decision. The monitoring record should remain an intelligible account of the observation used.
Keep the threshold and decision attributable
A threshold is not supplied by the blank Annex 10 table. The Directive requires scientifically sound decision-making thresholds and consideration of relevant region, crop and climatic conditions where feasible. Keep the source of the threshold or the adviser’s interpretation with the decision it informed. [5][1]
In your own working record, describe the decision in ordinary language: continued monitoring, a non-chemical measure, or a completed application recorded elsewhere. Give the decision a date and reference. Distinguish a recommendation from its later implementation, and preserve the person’s explanation if the operation differed from the initial plan.
Invented documentary example: a monitoring visit is filed under a fictional parcel reference with an observation note and a later adviser response. The decision is to continue observation, so no pesticide-use event is created. A second visit is documented separately. This example demonstrates the distinction between evidence and action; it gives no pest, threshold, product, interval or treatment instruction.
Preserve the reasoning for non-chemical measures
Annex III says sustainable biological, physical and other non-chemical methods are preferred when they provide satisfactory pest control. Its targeting principle says pesticides should be as specific as possible for the target, with the least side effects on human health, non-target organisms and the environment. [5]
Keep the consideration and chosen measure in the plan or decision record supplied for the parcel. Explain the source of any agronomic assessment rather than adding a universal statement that one method will work for every crop. Record the action actually carried out and any follow-up observation under separate dates.
For a supplier or adviser document, preserve its title and scope. A general leaflet can inform a discussion, while a parcel-specific plan explains the intended programme. Give both documents distinct references so an administrator can identify which statement belongs to the farm’s particular situation and which is general background material.
Necessary use and resistance management are linked principles
The Directive calls for pesticide use and other intervention levels to be kept necessary, considering acceptable risk and avoiding increased resistance risk. Where resistance to a measure is known and repeated applications are needed, it calls for available anti-resistance strategies, which may include products with different modes of action. These principles describe the decision framework; they do not provide a dose or a product sequence for your crop. [5]
Retain the relevant adviser or plan explanation with the decision history. Link completed applications by their event references so the actual products and dates can be examined. If an intervention was omitted, delayed or changed, document the actual outcome in its own terms instead of editing the proposed plan to imply that everything happened as originally scheduled.
Article 55 of Regulation 1107/2009 separately makes authorised-use and labelling conditions part of proper use. Keep those product conditions connected to any application recorded. An IPM discussion does not replace the authorised product identity or the specific conditions attached to its use. [6]
Follow the result after the intervention
The eighth IPM principle says the professional user should check the success of the applied plant protection measures using pesticide-use records and monitoring of harmful organisms. Keep later observations connected to the measure they evaluate, including an outcome that differs from expectations. [5]
For a practical review, identify the original observation, decision, completed action and follow-up. Note whether the same parcel area and monitoring method were used. Preserve an explanation when the comparison changed because a trap was moved or a different part of the parcel was assessed. Do not manufacture a numeric improvement where the underlying observations are not comparable.
A concise end-of-season note can identify which supporting documents explain the sequence. List a specific unresolved question for the adviser, such as an uncertain identification or unexplained change in counts. Keep that question open as a working enquiry until its answer is available, rather than substituting a confident historical statement unsupported by the observations.
Connect monitoring to the CAP plan without merging the records
The DP ECO-IPM commitment description in CAP plan version 3.1 requires following an IPM plan across the identified parcel area for at least three consecutive years. It says competent individuals draft the plan, trap installation follows the plan, and farmers retain monitoring date, pest and number recorded, if any. It also describes an eligible committed area of at least 0.04 hectares. These statements belong to the scheme description in that version. [3]
Keep the plan’s parcels and crop descriptions consistent with the monitoring references. Retain the plan version and the explanation of a change. Where a visit covers only part of a parcel, describe the observed part in the associated note so a later reader does not infer that the count represents an unexamined area.
The CAP plan separately requires eligible beneficiaries to use ARPA’s mobile apps to submit and update crop plans and their use of plant protection products. That digital submission context is explained in the BiedjaCam guide. Preserve the monitoring evidence that supports the plan even where a digital interface presents the crops and applications in separate screens. [3]
Vineyards and orchards: preserve the original scheme context
The legacy AECM guidance includes AECM 4 for implementation of an IPM plan targeting vineyards and orchards. Annex 10’s footnote likewise refers to understanding pests affecting vineyards and orchards. These references identify the historical context of the template; retain that context when using the sheet to understand the headings. [1]
For a current working monitoring file, identify the actual crop, parcel, plan and observed organism. Keep a vine block and an orchard block distinguishable through their own references. An observation from one should not be copied into the other merely because the blank table looks the same. The Directive’s decision principle explicitly considers crop and relevant local conditions. [5]
A crop-specific plan can carry agronomic detail that a short monitoring row cannot explain. Keep the plan accessible with the observation history, and identify the adviser who can clarify its meaning. Preserve the dates of field visits so a later review can distinguish an earlier recommendation from the conditions recorded on a later visit.
Prepare useful material for AgriConnect or AgriKonsulta
The Research and Advisory Services Directorate describes AgriConnect as its frontline advice service, including crop planning and IPM. AgriKonsulta is described as a national initiative focused on IPM and sustainable fertiliser use, with field visits, tailored advice and access to expertise. These are advisory routes described by the agriculture department. [7]
Before a discussion, select the relevant observation sequence and accompanying plan. Identify the parcel, crop, monitoring method and specific uncertainty. Keep product-use records available where an application followed, but avoid sending an unexplained collection of unrelated seasons. The purpose is to make the agronomic question understandable from the evidence you actually hold.
After the conversation, retain the supplied advice with the observation or decision it concerns. Distinguish a verbal explanation recorded in your own note from a written plan provided by the adviser. If the recommendation leads to a completed pesticide use, create the separate application record with the required product, date, dose, location, extent and crop information. [2]
Keep certification requests in their own document category
If a customer or certification body asks for records, preserve the actual request and applicable standard alongside the copy set prepared for that purpose. Identify which application, observation or plan document answers each item. This is an editorial filing recommendation; it does not assign a particular certification edition or invent a buyer requirement.
The statutory application-record Annex and the IPM principles remain the documented foundations described above. Keep their source distinct from an additional commercial instruction. A certification label in a folder name should not obscure whether an attached document records a monitored pest, an application or an agreed plan. [2][5]
Review the documentary sequence before filing the season
Read the file as a chain of evidence: prevention context, observation, decision, any completed intervention and later evaluation. The sequence reflects the IPM principles, with the application record kept separately when a plant protection product was used. Preserve references that allow the reader to move between those documents. [5][2]
For an internal handover, explain trap abbreviations, parcel nicknames and the location of the plan. Assign a custodian for unresolved adviser enquiries. Check that a different authorised colleague can retrieve the relevant dated observation and its linked action without relying on the person who performed the visit.
Use the ARPA inspection guide for the wider purchase, use and storage evidence pack. The electronic-record guide explains application-data timing and access. Return to the Malta hub when choosing the next task rather than extending the monitoring sheet into an all-purpose pesticide form.