Professional pesticide records in Malta connect several distinct documents: the application journal, product and label information, purchase evidence, IPM observations and, where relevant, the ARPA crop-plan workflow. Article 67 of Regulation 1107/2009 requires professional users to retain product-use records for at least three years. Regulation 2023/564 supplies the detailed information groups and electronic-format rules. Start with the record you need to prepare, then follow the relevant guide. [1][2]
Choose a guide by the task in front of you
| Your situation | Start here | What the guide helps you distinguish |
|---|---|---|
| You have completed an application | Application record fields | Product identity, date, dose, location, treated extent and crop or situation |
| You are organising a digital journal | Electronic pesticide records | Content, machine-readable format, initial recording, conversion and access |
| You are preparing an ARPA response | Pesticide inspection evidence | Purchase/use evidence, labels, people, protection, equipment and storage |
| You are documenting pest observations | IPM monitoring sheet | Monitoring, thresholds, decisions and evaluation of results |
| You are working on an ARPA crop plan | BiedjaCam crop-plan guide | Registered parcels, crops, scheme context and photographic evidence |
Keep those tasks connected through understandable references. A parcel identifier can connect an observation with an application and a crop plan, while each document retains its own purpose. Use the table as an editorial route through this portal; it is not an official form or a substitute for the agency’s actual request.
Begin with the professional activity
The professional-user definition in Directive 2009/128 includes anyone using pesticides in professional activities, including operators, technicians, employers and self-employed people in agriculture and other sectors. Article 3(25) of Regulation 1107/2009 refers to that definition. The relevant question is the activity being performed, rather than the name of a particular software package. [3][1]
For an internal responsibility note, identify who performs the treatment, who supplies the event information and who keeps the business copy. If a contractor applies the product, Article 4 of Regulation 2023/564 requires access to or a copy of the records for the contracting person without undue delay or restrictions. Keep the service report connected to the client’s parcel references. [2]
Prepare the handover around actual work. A booking describes an intended job; an invoice describes a commercial transaction; the application record describes product use. Compare those documents where necessary, but obtain the completed event from the person who carried it out. Preserve a clarification if a location nickname or unit could otherwise be misunderstood.
Know which application category you are recording
The EU Annex distinguishes surface areas, closed spaces and seeds or plant reproductive material. It gives different dose denominators and treated-extent measurements for those categories. Surface treatments include agricultural fields, amenity areas and non-crop areas; the closed-space row identifies stores or greenhouses; the seed row includes seed potatoes as an example. [2]
Use the fields guide to choose headings that describe the actual category. For a surface treatment, keep product rate per hectare and hectares treated distinguishable. For a closed-space application, identify the facility and corresponding square or cubic measurement. For reproductive material, preserve the relationship between the product rate, treated weight or seed count and relevant batch. [2]
The Annex identifies product name and authorisation number across all categories. Crop or situation terminology follows EPPO codes where applicable, and growth stage follows the BBCH monograph where relevant. Start time for surface treatments is likewise conditional on relevance, with examples in the footnotes. These qualifications matter when designing the record, because an apparently neat universal row can conceal a missing unit or conditional detail. [2]
Keep local authority documents accurately identified
The Pesticides Control Act, Chapter 430, as amended in 2025, defines the Authority as the Food Safety and Security Authority. Article 3 assigns it authorisation-processing, pesticide-register and implementation functions. The current FSSA website publishes resources, contact details and a list of trainers in pesticide use. [4][5]
The retrieved S.L. 430.07 regulation 4 still identifies MCCAA’s Technical Regulations Division as the competent authority for Article 75 of Regulation 1107/2009. The different institutional names appear in the cited documents. Keep the title, issuing body and date of a document intact when filing it; do not rewrite an older certificate or guidance note to remove its original issuer. [6][4]
For a product-specific enquiry, organise a concise evidence pack: the exact trade name, authorisation identifier, relevant label and description of the intended or historical use. Identify whether the enquiry concerns authorisation, a record field, training or an ARPA scheme. This is a practical way to direct the question without treating every agricultural service as the same authority.
Product conditions belong beside the journal
Maltese implementing regulation 2(2) requires relevant labels in Maltese and English. Article 55 of Regulation 1107/2009 requires proper use, including compliance with authorisation conditions and the labelling. Keep the actual product document with a reference from the application record. [6][1]
Use that document for product-specific restrictions such as the applicable crop, use conditions or waiting interval. The portal supplies no universal dose, harvest interval, re-entry time or buffer distance. Those questions begin with the actual authorised use and label condition, rather than with the crop name alone. The inspection guide explains how product and label evidence connects to an application selected for review. [1]
For archive clarity, distinguish a historical label copy from a later product document obtained for a new enquiry. Explain which one supports the event being discussed. If a supplier description is abbreviated, preserve the original and obtain a specific clarification instead of silently choosing a similar name from a different document.
Electronic records involve content, format and timing
Regulation 2023/564 applies from 1 January 2026. Article 2 requires electronic records using a machine-readable format; Article 3 requires each use to be recorded without undue delay and sets the ordinary thirty-day transfer period when the record is not initially created in the prescribed format. National timing choices are described separately in the regulation. [2]
Regulation 2025/2203 adds an option for Member States concerning transfer into electronic format of records for uses before 1 January 2027. The amendment adds a paragraph to Article 3. It does not itself replace the Annex or enact an identical territorial decision for every Member State. The electronic-record guide explains the boundaries of those provisions and the authority-request mechanism. [7][2]
Choose a working method that preserves the information when it leaves the editing screen. For your own review, inspect exported identifiers, date displays, units and unusual characters. Keep the original report available for resolving transcription discrepancies. A clear data dictionary and an archive inventory help a different authorised colleague retrieve the season’s records without relying on the original operator’s memory.
ARPA evidence adds a payment-framework context
ARPA’s conditionality guidance places pesticides under SMR 7 and SMR 8. It asks for up-to-date pesticide purchase and usage records, and addresses licence, authorised use, protective clothing, measuring/application equipment, storage and empty containers. Organise these as connected evidence groups, rather than considering a treatment table to be the entire inspection file. [8]
The booklet describes conditionality applicability for holdings exceeding ten hectares and a payment-penalty exemption for beneficiaries with holdings up to ten hectares. It also says identified non-compliances are reported to competent authorities, including for beneficiaries outside conditionality. These statements concern the payment and control framework; the professional-user use-record duty remains a separate provision in Article 67. [8][1]
Payment reductions depend on the assessment described in ARPA’s guidance. The document distinguishes first breaches, recurrence and intentionality. Chapter 430 Article 9 separately sets conviction penalties, with the link for EU infringements in S.L. 430.07 regulation 6. Use the ARPA guide to keep those mechanisms distinct when preparing an explanation. [8][4][6]
IPM observations and a completed application tell different stories
The general IPM principles in Annex III of Directive 2009/128 include prevention, monitoring, decisions based on monitoring, preference for satisfactory non-chemical methods, targeting, necessary intervention levels, resistance management and evaluation of success. The monitoring evidence explains the decision-making context; a product-use row describes an application that actually occurred. [3][2]
ARPA’s legacy AECM guidance version 3.7, dated 5 February 2020, contains an “IPM Monitoring Sheet” in Annex 10. Its headings include parcel, date, pest, number of pests present and traps checked, with name, identity and year above the table. It is an observation template from that guidance period, with different fields from the application-record Annex. [9][2]
Use the monitoring guide to connect observations, an adviser’s reasoning and later follow-up. Preserve a decision that resulted in no application without generating a fictitious spray event. Where treatment followed, link the observation and application references while retaining the actual product, quantity and location information independently.
BiedjaCam belongs to the published ARPA workflow
ARPA describes BiedjaCam as its app for organising and planning agricultural holdings digitally. The published booklet lists registered parcels, crop-plan management, structures, equipment, aid applications, payments, events, geotagged photographs and agency notifications or communication. Its crop-plan instructions address Eco-Schemes 1, 2 and 3. [10]
The booklet says taking geotagged photographs is mandatory for Eco-Schemes 1 and 3 and voluntary for Eco-Scheme 2. It also explains how a planting date can generate a harvest date that can be altered. Those are specific features of the documented ARPA process; keep the resulting crop-plan information distinguishable from the application history of a particular product. [10]
The BiedjaCam guide follows the published booklet and the CAP plan’s IPM context. For your working archive, use a consistent parcel reference to connect the crop-plan document, monitoring evidence and completed application. Explain a discrepancy between records through the source documents rather than assuming that one screen automatically supplies every other record category.
Use agricultural advice for the agronomic question
The Research and Advisory Services Directorate describes AgriConnect as its frontline advisory service, including support for crop planning and integrated pest management. It describes AgriKonsulta as a national initiative providing field visits, tailored advice and expert knowledge focused on IPM and sustainable fertiliser use. The directorate’s remit expressly includes Malta and Gozo. [11]
Prepare an adviser visit around a parcel, crop, observed problem, monitoring history and existing plan. Identify which question needs agronomic interpretation and which is a transcription issue. Keep the adviser’s supplied explanation with the relevant observation and decision. A field visit can inform the operational reasoning without changing the historical account of which product was actually applied.
For a follow-up conversation, list the unresolved points specifically. Explain a pest-count method, trap reference or crop-stage description rather than submitting an undifferentiated folder. Preserve the original wording of a recommendation and distinguish it from the farmer’s subsequent action. This helps the next person understand how the observation, advice and application relate.
Maintain one intelligible documentary chain
Give each event or document a reference that makes sense within the business. Keep a parcel-name correspondence list, explain operator abbreviations and identify the archive custodian. Preserve original reports, subsequent corrections and the explanation of what changed. These are editorial organisation suggestions for maintaining a readable evidence chain.
When preparing a handover, select a real historical application and retrieve the associated product document, location information and any linked monitoring observation. Ask a colleague to explain the event from those records. Note an unreadable attachment, ambiguous heading or broken reference as a concrete issue to resolve. The exercise assesses retrieval and comprehension; it does not predict an inspection outcome.
For a request from an authority, retain the request and copy set with its scope. Article 4 of Regulation 2023/564 requires provision of requested information without undue delay, with a separate rule for an express electronic-format request before the conversion period expires. The electronic guide explains that rule without turning it into a general record-creation deadline. [2]
Use the five guides above as a connected reference set. Each starts with a different document or user situation and keeps the legal, scheme and organisational roles visible. The shared Leafwrit pre-registration controls on these pages provide the portal’s product route; the reference material remains available alongside them.