Pesticide Check is designed to help farmers and agronomists quickly and easily check the compliance of planned pesticide applications based on label guidance. This tool performs various checks on label restrictions such as expiry for use, target crop and max dose. This saves time and helps avoid costly errors. It is not intended as agricultural advice and is no substitute for reading the manufacturer label. If in doubt you should seek the advice of an agronomy professional.
Pesticide Check is available via the fieldmargin web app for farms on the Pro plan in the UK, Ireland, South Africa, Canada, Australia, and New Zealand. You can find out more about coverage and the data we use for Pesticide Check in our FAQs.
To use Pesticide Check you simply need to set up a Field Job with inputs that are from the Pesticide Database and then click on “Check Pesticides”. This will then perform checks on
Product expiry date
If product is permitted for use on the target crop
If the application rate set on the field rate is within the maximum dose
If the total dose applied on the field in the Farm Year is within the maximum dose per season
If the total number of Field Jobs using the product in the Farm Year is within the maximum treatments per season
Application interval which will check the time since the product was last recorded as being applied
Latest application timing
Withholding period
Grazing re-entry period
You can watch a video of the full process of using Pesticide Check, from setting up a job to checking your planned pesticide rates, below. Otherwise read on for step-by-step instructions.
How to use Pesticide Check
2. Add Inputs - these are the pesticide products you are planning on using. Make sure that the inputs you add are from the pesticide database. These will appear with a green shield next to them on the 'Your farm inputs section' or choose one from the Pesticide database section. You can also add water at this stage.
3. Once you have your job set up click on ‘Check Pesticides’ in the Inputs section to start the check.
4. A dialogue will open, after agreeing to the terms of use you will be prompted to choose the target crop if more specific information is needed for the check, the target pest and the crop stage. The options you see here are returned by the pesticide data source as the ones that are permitted on the label restrictions.
5. After you have filled in this information click 'NEXT'.
6. The next screen shows the pesticide check results. For each check there are three possible results:
‘Fail’, which is a non-compliance error.
‘Warning’ which is for information and should help you to perform your own checks. For example for expiry date we show the expiry date but you will need to work out if your planned application date would comply with that. A grey warning symbol means that check information was not returned and you will need to look it up.
‘No error found’
You can filter to just show a particular type of result if you wish.
If there are multiple products and fields on your Job, results are grouped by product and then by fields with the same crop and treatments. For example if you had some fields that had had 1 dose of a fungicide and some that had had 2, these would be separate.
For checks which use data across the Farm Year (max dose per season and max number of treatments) fieldmargin includes all jobs on a field using a product whether they are planned or completed.
Products which are not from the pesticide database will not return results.
If we don’t have label information returned for a product we will show a grey warning symbol.
7. Once you are done click ‘I have read and acknowledge these warnings’ to dismiss the window.
8. If you want to have a record of your check results and when you did it you can take a screenshot of the result and attach it to the job as a picture.
Notes
Make sure that the fields that you are including on the Field Job have a field usage with a Crop set. You will know this because when you set up the usage you would have chosen the crop from a list and it will appear on your usage list in block capitals. If they aren’t you will be able to change this as part of the checking flow.
For some crops there is more than one crop in the database which can impact what check results are returned.