Pesticide Spray Records for MRL Compliance: A Practical Farm System
Polyhouse Constructions Agronomy Desk · 12 నవం, 2026
For pesticide spray records for MRL compliance, write down each application on the same day and connect it to a clearly identified crop block and harvest lot. Your record should show what was observed, what input was used, its batch number, the application details, and the label pre-harvest interval (PHI).
A notebook, printed register or spreadsheet can work. The important point is that entries are complete, readable and made at the time of work—not reconstructed after a buyer asks. Records do not guarantee that produce will meet a Maximum Residue Limit (MRL). They do give you traceability, support correct harvest scheduling and show where to investigate if a residue test or buyer query raises a concern.
Understand what MRL compliance records need to prove
An MRL is the maximum permitted level of a pesticide residue in a food commodity under a particular market’s rules. Limits can differ by crop, active substance and destination market. A domestic buyer, organised retailer, processor or export buyer may also have its own residue protocol.
Your records should allow someone to answer five basic questions quickly:
- Which crop and which area produced this lot?
- What pest or disease prompted the action?
- What product was applied, and from which purchased batch?
- When was it applied, and when was the crop harvested?
- Who carried out the work, and what checks were made?
This is called traceability. For example, if cucumber crates from Block C-2 are packed on 18 August, you should be able to find all sprays, biocontrol releases and harvests for C-2 before that date.
Use only products registered and labelled for the relevant crop and purpose, and follow the product label. The label PHI is the minimum time between the last application and harvest. It is not a suggested period and should never be shortened to meet an urgent market order. Where a buyer or destination-market requirement is stricter, follow the stricter requirement after confirming it with that buyer or a qualified agronomist.
For the broader background, read pesticide residue and MRL basics for polyhouse growers.
Set up block, crop and harvest-lot identification first
Spray records become weak when a farm has one vague entry such as “tomato sprayed.” In a polyhouse, different bays may have different planting dates, varieties, pest pressure and harvest dates. Treat them separately.
Give every production area a permanent code
Mark each naturally ventilated polyhouse, nethouse or fan-and-pad compartment on a simple farm map. Then divide it into practical blocks where crop age and management are the same.
A workable code could look like this:
- NV-1 / A: Polyhouse 1, block A
- NH-2 / C: Nethouse 2, block C
- FP-1 / Bay 4: Fan-and-pad house 1, bay 4
Display the code at the entrance and use exactly the same code in the scouting register, spray register, fertigation notes, harvest register and dispatch record. Do not change codes halfway through a crop cycle.
Create one crop-cycle sheet per block
At transplanting, start a crop-cycle sheet with:
- block code and protected structure type;
- crop, variety or hybrid, and rootstock where relevant;
- transplanting date and expected first harvest period;
- seedling supplier and seedling batch, if available;
- area in m² and approximate plant count;
- irrigation source and basic fertigation plan reference;
- intended market: local, retail, processor or export channel.
This sheet is the front page for the full traceability file. It is especially useful where the same farm grows cucumber, capsicum and tomato at the same time.
Assign harvest-lot codes every day
A harvest lot is the produce picked from one identified block on one date, or during one clearly defined shift. Example: NV1-A-CUC-2025-08-18-AM.
Put this code on the harvest sheet, crate tag, grading sheet and dispatch invoice or challan. If produce from two blocks is mixed, record both block and harvest-lot codes. Do not mix lots if one block is still within a PHI period.
Maintain a same-day pesticide application register
The spray register is the central document for pesticide spray records for MRL compliance. Record the entry before or immediately after the job, while the container, operator and conditions are known.
Keep the original invoice, a photograph or copy of the product label, and the empty-container disposal record where your buyer programme asks for it. This supports the register entry but does not replace it.
Record field | What to enter | Why it matters |
|---|---|---|
Application date and time | Start and finish time, plus date | Establishes the PHI calculation and work sequence |
Farm, structure and block code | For example, NV-1 / A | Connects use to a specific harvest lot |
Crop stage | Vegetative, flowering, fruiting or harvest stage | Explains risk and likely harvest timing |
Target problem | Observed pest, disease or weed and severity | Shows that application followed a field need |
Product details | Product name, active ingredient as printed on label, formulation and label registration details where required | Makes the entry identifiable during an audit |
Purchase and container traceability | Supplier invoice reference, manufacturing/batch number and expiry date | Helps investigate a specific input batch |
Area treated | m² or block area actually covered | Prevents confusion between whole farm and partial treatment |
Application details | Water volume used, equipment ID and application method | Supports consistent operation and troubleshooting |
Operator and supervisor | Names or initials | Shows accountability and allows follow-up |
Label PHI and earliest harvest date | PHI from label; calculate the first permitted harvest date | Prevents harvest inside the waiting period |
Weather and house conditions | Outside rain/wind if relevant; inside temperature, humidity or ventilation status | Useful for explaining poor spray performance or disease pressure |
Remarks | Leak, nozzle blockage, incomplete coverage, crop stress or corrective action | Captures exceptions that matter later |
Do not use entries such as “medicine sprayed” or “fungicide done.” They cannot establish what was used or when harvesting can resume. Avoid overwriting a mistake. Draw one line through the incorrect entry, write the correction, and initial and date it. In a spreadsheet, retain a change history or note the correction in remarks.
Record biopesticides, microbial products, beneficial insect releases and other crop-protection inputs too. They may not create the same residue concern as conventional pesticides, but recording them helps explain your IPM programme and prevents duplicate or conflicting actions.
Link scouting, spray and harvest records
A spray register alone often shows what was applied but not whether it was necessary or effective. Add a scouting record and harvest record to turn it into a useful farm-management system.
Use scouting notes to justify decisions
At least weekly—and more often in a fast outbreak—inspect fixed locations in every block. Note the date, scout, crop stage, pest or disease, affected plants or trap counts, hotspot location and action decided.
For example, yellow sticky trap counts and underside-leaf observations can show rising whitefly pressure before a large infestation develops. Your follow-up inspection should record whether the population fell, remained stable or increased after the action. See this guide on how to scout pests in a polyhouse every week.
This history helps prevent routine calendar spraying. It also reveals recurring hotspots, such as an insect-net tear near an entrance, weeds outside a side vent, or poor airflow in one corner. Addressing the source may reduce future pesticide use.
Keep a harvest and dispatch register
For each harvest, record:
- harvest date, shift and harvest-lot code;
- crop block code and picker or team;
- quantity harvested and grade, in kg or number of crates;
- PHI status checked by the supervisor;
- packing date, buyer, vehicle or dispatch reference;
- any lot kept aside, rejected or sampled for testing.
Before picking begins, the supervisor should compare that day’s harvest list with the “earliest harvest date” field in every recent application entry. This simple check is more reliable than depending on memory.
If a residue sample is taken, record sample date, harvest-lot code, laboratory report reference and result. Keep it with the lot file. A laboratory result applies only to the represented sample and lot; it should not be used to assume that all later produce is compliant.
Make PHI and market checks part of harvest planning
Protected crops may be picked every two to four days during peak production. That makes PHI management particularly important for cucumber, tomato, capsicum and flowers. A crop can be safe to pick in one block while another block of the same crop is still under a PHI restriction.
Use a visible harvest-status board at the packhouse or farm office. List each block, the last application date, the label PHI and the earliest harvest date. Update it after every application.
Situation | Correct record and planning action |
|---|---|
Only one corner is treated | Record the exact affected rows or sub-block; segregate its harvest if practical |
A market order is due before PHI ends | Do not harvest that treated lot; supply another eligible block or communicate early with the buyer |
Two products are applied on different dates | Use the latest permissible harvest date based on all relevant label PHIs |
A buyer has an additional residue requirement | Record the written requirement and review planned inputs before use |
A label or batch detail is missing | Quarantine the information gap, locate invoice/container details and seek agronomy advice before dispatch decisions |
MRL compliance also begins before spraying. Pest exclusion, sanitation, trap monitoring and climate management can reduce the number of corrective applications needed. For an organised season-long approach, use this guide to build an IPM plan for a polyhouse crop cycle. If thrips are your recurring issue, the detailed thrips management guide for protected cultivation can help you improve monitoring and prevention.
Check application quality and safety in separate logs
A residue issue is not only about the product selected. Uneven coverage, leaks, poor calibration or an untrained operator can lead to poor control, repeat applications and avoidable risk.
Maintain a small equipment log for each knapsack sprayer, power sprayer or fogging equipment. Record its ID, nozzle condition, hose leaks, filter cleaning, calibration check, repairs and date of next check. Use clean measuring equipment and keep it separate from food handling areas.
Also maintain a stock register. When an input enters the farm, record purchase date, supplier, invoice number, product name, batch number, expiry date, quantity received, storage location and quantity issued. Match the quantity issued with spray-register entries periodically. Differences may indicate a missed entry or a stock-control problem.
Keep pesticide storage secure, labelled and away from fertilisers, harvested produce, packing material, feed and living areas. Train workers on personal protection, re-entry instructions and label directions. For product-specific safety, application and disposal directions, follow the label and consult your KVK or crop agronomist. Do not rely on an old register entry as a substitute for the current label.
Review records weekly, not only during an audit
A weekly 20-minute review can turn records into better decisions. The farm manager should check which blocks are under PHI, which pests are repeating, whether the same active ingredient is being used too frequently, and whether equipment or climate issues are increasing disease pressure.
A practical review checklist is:
Keep paper registers in a dry, accessible place. Scan or photograph completed pages regularly, or maintain a backed-up spreadsheet. Retain records for the period required by your buyer, certification programme, lender or applicable market rule. Where no specific period is stated, ask the buyer in writing rather than making assumptions.
Next steps
Start with three linked sheets: a block-and-crop master sheet, a same-day spray register and a harvest/dispatch register. Give every structure and block a code before the next transplanting, then train one responsible person to check PHI status before each harvest.
Use your first month of records to identify repeated pest hotspots and avoidable applications. Good traceability works best alongside strong physical exclusion and hygiene. If you are upgrading the protected structure, review insect-proof net selection for pest exclusion and, where needed, browse individual protected-cultivation materials for planning your requirements.
Frequently asked questions
Is a spray register enough for MRL compliance?
No. A spray register is central, but it should link to crop-block identification, scouting, input purchase and batch records, harvest lots, and dispatch details. These records provide traceability; compliance is ultimately assessed against applicable market requirements and, where required, residue testing.
How do I calculate the earliest harvest date after a spray?
Use the PHI printed on the current product label and count it from the application date according to the label direction. Record the calculated earliest harvest date in the spray register and check it again before picking starts.
Should I record biocontrol releases and biopesticides?
Yes. Record the date, block, product or organism details, batch information where available, quantity and purpose. This documents your IPM programme and helps the next scout understand what action has already been taken.
What if one part of a polyhouse was sprayed but the rest was not?
Record the exact rows, beds or sub-block treated rather than writing only the whole polyhouse code. Keep harvest from the treated area identifiable, and avoid mixing it with produce from untreated areas until the applicable PHI has passed.
Can I use one pesticide record for several crops growing in the same structure?
Only if the record clearly separates each crop and block, and the product label permits use on each relevant crop. Different crops may have different harvest schedules and market requirements, so separate entries are safer and easier to audit.
