# Can you spray pesticides after rain? URL: https://leafwrit.com/mt/can-you-spray-pesticides-after-rain/ Reviewed: 2026-10-27 **You can spray after rain only when the conditions suit the particular product and use.** For a foliar treatment, inspect the actual foliage, read the product’s weather instructions and allow its specified rain-free period before the next shower or irrigation. Rainfastness describes resistance to rain **after application**; it does not tell you how long to wait after yesterday’s rain. University extension guidance distinguishes wet-leaf runoff, product absorption and subsequent wash-off. For a Maltese application, start with the authorised product label. Article 55 of Regulation 1107/2009 makes compliance with the authorised conditions specified on the labelling part of proper use. [Read the official use rule in the current consolidated text](https://publications.europa.eu/resource/consolidation/2009R1107%2F20260616.ENG). The June 2026 amendment concerns Annex III; Article 55 retains the authorised-use and labelling conditions. ## Separate the questions before choosing a spraying time | Your situation | What to establish | Useful information to keep | | --- | --- | --- | | Rain has stopped; leaves remain wet | Whether the intended foliar treatment can be applied in that condition | Actual leaf condition and the relevant label instruction | | Leaves have dried; another shower is forecast | Whether the application fits the product’s rain-free period | Proposed finish time, forecast issue time and product instruction | | Rain arrived after a completed treatment | Whether it affected that product’s performance | Application timing, rain onset and the subsequent assessment | | Irrigation is planned | How the product instructions address irrigation | Irrigation method and scheduled or actual timing | | Treatment is directed at soil | Whether the intended use has different moisture or incorporation instructions | Exact use and its own label wording | This is an editorial decision worksheet, not a table of approved treatments. Its distinctions follow the extension explanations of wet-foliage runoff, rainfastness and soil-applied products. No single row supplies a permitted product, a dose or a universal interval. ## Inspect the crop where you intend to work Washington State University’s weed-management handbook explains that spraying wet foliage can cause herbicide runoff; it describes foliar sprays working best on clean, dry, actively growing weeds. That is foliar-herbicide guidance. It is not a reason to invent an identical moisture requirement for every fungicide, insecticide or soil treatment. For your field assessment, look at the target leaves in the actual block rather than describing the entire holding with a weather-app icon. Note where you inspected and whether the observation represents the intended treatment area. If sheltered foliage and exposed foliage look different, preserve that distinction in the note you give the adviser. Do not translate a casual observation into an unsupported numerical leaf-wetness measurement. Describe the condition in plain terms: droplets present, foliage visibly dry, or the intended area still awaiting inspection. Keep an uncertain observation as a question to resolve before making a decision. A dated photograph can accompany your description, but give it a parcel and crop reference so somebody else knows what it shows. These are practical documentation suggestions, not statutory weather-record fields. ## Read rainfastness in the correct direction The University of Missouri explains rainfastness as a product’s ability to remain effective after rainfall or irrigation. It identifies rainfall timing, amount and duration, together with formulation and chemistry, as factors affecting the result. Rain or irrigation shortly after application can dilute or remove pesticide from the target surface. Use that explanation to frame the label question precisely: “How much time does this product need after application before rain?” Keep the answer distinguishable from “Are the leaves suitable for application now?” A dry leaf at the start does not document the weather after the work finished. Equally, a long gap since a previous shower does not establish that another shower will stay away. When recording a forecast, retain its location and issue time. When recording what happened, label it as an observation. For a later discussion, separate predicted rain from observed rain so the adviser can see whether the plan or the subsequent event is being described. A forecast screenshot alone should not be presented as evidence of the precise time rain actually started in a particular parcel. ## Use the exact formulation and intended use Oregon State University’s pesticide-redistribution publication distinguishes products that remain on the plant surface from products that move into plant tissue. It explains that rainfall or irrigation can dislodge surface material and that the label may specify a rainfast interval. Those mechanisms explain why copying another product’s waiting time is unreliable. Prepare the trade name, formulation and Maltese authorisation details before asking a supplier or adviser about wet weather. Include the crop, intended use and the wording you need explained. A question that says only “weedkiller” or “fungicide” leaves the actual product unidentified. Keep any written answer with the label version to which it refers, rather than filing an unattributed number under a generic product category. An example from a foreign extension publication explains a mechanism; it does not establish a Maltese authorisation. This page therefore gives no list of foreign brand names with supposed Malta waiting times. The use decision remains tied to the authorised conditions of the actual product. ## Do not turn “systemic” into permission to spray wet leaves Redistribution inside a plant and retention of a spray on a wet surface are different questions. Oregon State’s discussion of absorption and rainfastness supports checking the product instructions even for redistributing products. Its explanation also makes the biological target and the product’s behaviour relevant to assessing an application after rain. For your own decision note, write down the unresolved issue rather than answering it with a marketing category. For example: “Confirm whether this label permits the proposed application with the observed foliage condition.” Obtain an answer about the actual product and use. Do not replace the label instruction with an assumed rule based on a neighbouring farm’s treatment, a different formulation or a previous season’s recollection. Likewise, distinguish the observation that leaves look dry from the conclusion that all conditions for spraying have been satisfied. Keep the rest of your normal application assessment intact. This guide addresses the rain question; it does not calculate a weather window or select the treatment for you. ## Check irrigation and additives separately Rainfastness guidance also discusses irrigation. Oregon State notes that labels may identify a suitable adjuvant, while some sticker additives can reduce penetration of particular pesticides. Adding an additive is therefore not a universal remedy for a wet-weather problem. Include planned overhead irrigation in the timing discussion with the person responsible for the crop. Keep the irrigation plan separate from the application plan, then compare the relevant instructions before committing to either. If responsibility is shared between a grower and a contractor, explain who will communicate a change. A record that merely says “water later” leaves the sequence difficult to reconstruct. Write an additive’s identity separately from the main product in your preparation notes. Preserve the advice or label instruction behind its proposed use. The purpose is to make the reasoning reviewable, not to infer compatibility from the fact that two materials are both described as improving spraying. ## Rain after spraying: assess before repeating An unexpected shower does not, by itself, establish that the original treatment failed. Oregon State advises basing a reapplication decision on the pest or pathogen, crop risk, product and weather. Missouri likewise links the decision to rainfastness and the precipitation event. Neither explanation supports a single automatic repeat-treatment rule for every crop in Malta. Start a follow-up note with the original application reference. Add what is actually known about the weather sequence and crop observations. Keep a later adviser recommendation distinct from a completed second application. If a repeat is proposed, review it against the product’s authorised conditions; rain does not override those conditions. Avoid changing the old application date to make it look as though the original job took place after the shower. Preserve the completed event and document the subsequent assessment beside it. Use the [IPM monitoring sheet guide](/mt/ipm-monitoring-sheet/) to organise observations, and the [application-record fields](/mt/application-record-fields/) to describe any application actually performed. ## Make the weather note useful at the filling point Prepare the note around a decision somebody else must make. Identify the inspected section, the observer and the observation time. Explain whether the assessment concerned the upper canopy, lower leaves or the actual weed target. Keep the description specific enough to revisit that location. A statement such as “it rained on the farm” leaves the condition of the intended target unanswered; wet-foliage runoff is the issue identified in the foliar-herbicide guidance. Use separate headings for evidence and instructions. Under evidence, put the observed leaf condition and the source of the weather information. Under instructions, retain the relevant product wording and the adviser’s explanation. Under the decision, state whether the job remains planned, is postponed or has actually been completed. This is a suggested working layout, not a government form. For a postponed contract job, communicate the change to the operator who would otherwise arrive with the original plan. Identify the affected parcel, the revised status and the person who will authorise the next review. Keep the message with the job reference. Do not convert a provisional rescheduling discussion into a completed spray entry. The [electronic-record guide](/mt/electronic-pesticide-records/) explains how a completed application is documented separately. ## Distinguish a measured shower from an estimate For a later rainfastness assessment, explain where the rainfall information originated. A nearby gauge reading, a weather-service estimate and somebody’s recollection are different types of evidence. Label each accordingly. If the gauge represents another location, preserve that location instead of presenting its reading as a measurement taken inside the treated block. Missouri identifies the timing, amount and duration of precipitation as relevant factors; those details deserve their own sources. Keep the original display or observation note alongside a transcription. Describe the units actually reported and whether the information covers a single shower or an accumulated period. An accumulated total does not itself identify the sequence of individual events. Avoid assigning an exact start time retrospectively when nobody recorded it. A precise-looking figure without an identifiable origin does not resolve the agronomic question. ## Explain what the rain assessment can establish A wet-weather review concerns the identified treatment and its circumstances. It cannot establish that a neighbouring holding used an equivalent formulation, that a different crop had the same exposure, or that a previous result will recur. Oregon State links post-rain assessment to product behaviour, pest biology, crop risk and weather. Keep those factors together when asking for an interpretation. For the season’s archive, preserve the question, evidence, reply and final action as connected documents. Identify any later correction to the weather chronology so the person reviewing the job can distinguish the first account from the corrected one. This approach records the grounds for the decision while retaining an accurate history of the work. ## An invented weather-decision example **Invented record example, not a spraying recommendation:** a fictional orchard operator finds droplets on the intended target foliage after a shower. The operator records the inspected block and postpones the proposed foliar job while obtaining advice about the exact product. No application is entered as completed. Later, the operator records a fresh inspection and the decision reached using the relevant label instructions. If the fictional job eventually happens, its actual completion details belong in the application journal. If rain subsequently arrives, that is a separate observation linked to the event. The example deliberately supplies no product, dose, waiting time, rainfall quantity or permission to apply. Its purpose is to show how to document a postponed plan without inventing a treatment history. ## Prepare a useful question for your adviser Send a concise account of the situation: parcel and crop, target problem, exact product, proposed use, observed foliage condition, recent rainfall and the next forecast relevant to the job. Attach the part of the label that prompted the question. Identify whether you want to assess a proposed treatment or investigate one already completed. Ask for an explanation that resolves the specific uncertainty. Keep the reply attributable, including whether it was a written response or your own note of a conversation. If the advice depends on inspecting the crop, record the outcome of that inspection rather than silently treating a preliminary discussion as the final instruction. Before handing the job to a contractor, communicate the decision and the material that supports it. After the job, reconcile the planned block with the area actually treated. The companion [spray tank calculator](/mt/spray-tank-calculator/) is awaiting publication: its live URL returned HTTP 404 when checked on 27 October 2026. Keep any preparation arithmetic with its established inputs; a calculation does not determine whether weather or authorised-use conditions permit spraying. Return to the [Malta records hub](/mt/) for the wider documentation workflow. ### Can you spray pesticides after rain? Base the decision on the actual foliage, product and authorised use. Wet-leaf runoff and the rain-free interval after application are separate issues; this guide gives no universal waiting time. ### Rain after spraying pesticides? Keep the application and rain chronology, product formulation and crop observations. Assess effectiveness with the product instructions and adviser before deciding on a repeat treatment.