Wild Animal Damage and Paddy Inundation: The Kharif 2026 Localised Covers and the 72-Hour Rule

The PMFBY Operational Guidelines applicable nationwide from Kharif 2026 made two additions inside the scheme's localised-risk architecture. Wild animal attack was added as a new add-on under the Localised Risk category, covering crop damage caused by elephants, wild boar, nilgai and deer. Paddy inundation was reintroduced as a Localised Calamity Cover for coastal and flood-prone states.

Neither addition changes the scheme's main yield cover. Both sit in the part of PMFBY that assesses damage on an individual field, on the strength of an event the farmer reports, and that distinction is the operational story for anyone buying the output of those fields.

The season they landed in was not a quiet one. Between 1 June and 23 July 2026 India received 306.9 mm of rain against a normal of 370.9 mm, a cumulative monsoon deficit of 17 per cent on India Meteorological Department data reported in July 2026. A deficit at that point in the season is not a quiet signal for the localised covers. Rain that closes a gap of that size tends to arrive in fewer and heavier events, which is the pattern that puts standing water on transplanted paddy, and a dry first half pushes wildlife further onto cultivated land in search of feed and water.

Enrolment ran late to match. The PMFBY enrolment deadline for Kharif 2026 was extended to 15 August 2026, and as of 27 August 2026 the scheme had insured 241.38 lakh farmers across 278.12 lakh hectares, on figures released by the Press Information Bureau. That is the base of insured area against which every localised claim this season will be argued.

PMFBY's principal cover is an area-yield index. The insured object is the insurance unit, usually a village or panchayat for major crops, and the season's actual yield for that unit, established through Crop Cutting Experiments, is compared against a threshold yield. If the unit's yield holds, no insured farmer in that unit is paid, whatever happened to an individual plot. The mechanics and the basis risk that comes with them are set out in how PMFBY is awarded and administered.

That cover asks nothing of the farmer after enrolment. The measurement is a state process, and a passive policyholder is paid exactly as much as an attentive one.

Localised covers invert this. They are assessed on the affected field, for the affected farmer, on the basis of an event that has to be reported before anyone from the insurer or the agriculture department arrives to look at it. A wild animal attack on four hectares of a village's maize does not move the village's yield index enough to trigger the main cover, and it is not supposed to. It is meant to be picked up by the localised route, and the localised route only opens if someone opens it.

The practical translation for a buyer sitting downstream of those fields: the yield cover is insurance you can rely on without touching it, and the localised covers are insurance you have to operate. Treating both as the same asset in a supply plan is how a sponsor discovers, after the season, that the loss it absorbed was insurable and simply unreported.

For localised calamities (inundation, hailstorm, landslide and cloudburst) and for post-harvest losses, the 2026 operational guidelines require the farmer to report the damage within 72 hours of the event. That is the condition on which the individual-field assessment rests.

Read the clock carefully. It runs from the event, not from the day the water receded, not from the day the field was next walked, and not from the day the sponsor's field officer happened to visit. Intimation can be made through the crop insurance app, the insurer's toll-free line, the financing bank for a loanee farmer, a Common Service Centre, or the local agriculture department, and any of those routes stops the clock. What does not stop the clock is an internal report inside a processor's own supply chain.

The failure modes are consistent across states and crops:

• Loanee farmers assume the bank does it. The financing bank debits premium and uploads enrolment in bulk, so the farmer reasonably infers the bank also handles claims. The bank has no way to know a specific field flooded on a specific night.
• The event is not recognised as an insured event. Standing water for two days after heavy rain reads as normal monsoon to a cultivator and as inundation to the policy.
• Enrolment particulars do not match the field. A wrong survey number or a crop mismatch on the portal record turns a valid intimation into a contested one, and after the enrolment cut-off it is generally unfixable.
• Nobody owns the deadline. Where a processor, an FPO, a lender and an insurer are all adjacent to the same field, the intimation obligation falls into the gap between them.

The new cover is specific. It sits under the Localised Risk category as an add-on, and it names the damage it addresses: crop damage by elephants, wild boar, nilgai and deer.

The word add-on is the operative one. An add-on is available under the guidelines and applies where it has been taken up for the crop, the district and the season in question. That makes the pre-season question a documentary one, and it has to be asked at enrolment rather than at claim:

1. Does the state notification for this season list the add-on for the notified crops in this district?
2. Was it opted for at enrolment on the specific applications the buyer is relying on, and does the acknowledgement show it?
3. Which of the four named species is the actual exposure in this geography, and does the damage pattern on these fields match what the cover describes?
4. Who is the assessment authority the insurer will send, and what evidence does that assessor expect on arrival?

A sponsor that can answer those four questions before the season starts has an insurable exposure. One that cannot has an assumption. The difference shows up when standing maize is flattened in a night and the only record is a field officer's WhatsApp photograph with no timestamp, no survey number and no intimation reference.

The reintroduction of paddy inundation as a Localised Calamity Cover for coastal and flood-prone states restores a cover to the crop most exposed to the pattern a deficit monsoon produces, where a season running 17 per cent below normal to late July has to take whatever rain follows in fewer and heavier events.

Transplanted paddy tolerates water. It does not tolerate submergence for long, and the loss curve is steep once the crop is under. From a buyer's side of the transaction, that produces an exposure that is not about any single farmer's income:

• Rice millers and parboiling units buy against an expected arrival volume from a known catchment. A flood-hit block does not reduce the price of paddy for that mill, it removes the paddy.
• Contract-farming sponsors carrying advances, seed and input credit against a delivery commitment lose the delivery and keep the advance as a receivable from a farmer who has just lost a season.
• Branded rice programmes with variety-specific sourcing cannot substitute at short notice, because the paddy available in an unaffected district is a different variety with a different buyer already attached.
• Agri-lenders carrying KCC and crop-loan books in a flood-prone block see the credit consequence of the same event, one season later.

In each case the compensation available to the primary producer is the thing that keeps the counterparty solvent enough to plant the next season and repay the advance. That is a commercial interest for the buyer, whether or not the buyer is a party to the insurance contract. The broader agribusiness exposure map, including the storage and processing risks that sit downstream, is covered in agriculture insurance for commercial agribusiness.

The 72-hour rule can only be met by someone standing near the field. A processor's procurement head in another state cannot meet it, and a clause that simply requires the farmer to maintain insurance does not either. The obligation has to be written onto the party with the eyes on the crop, with a deadline shorter than the statutory one and a consequence attached.

Six clauses that do the work, for a contract-farming agreement, an FPO aggregation agreement or a buyer-linked input-credit arrangement:

1. Insurance status as a condition precedent. Advances, seed and inputs release only against evidence of PMFBY enrolment for the notified crop and the correct survey numbers, with the application acknowledgement and any localised add-ons listed by name. Collect the acknowledgement, not an assurance.
2. A named intimation officer per cluster. One person, named in the schedule with a phone number, responsible for intimation across a defined set of villages. Vacancy in that role is a notified event to the sponsor, not an internal staffing matter.
3. An internal deadline of 24 hours. The statutory window is 72 hours from the event. Contract for intimation within 24 hours of the event or of discovery, whichever is earlier, so that two thirds of the window survives for the cases where the first attempt fails.
4. A weather-trigger sweep obligation. On a defined trigger (a district flood warning, a recorded rainfall threshold, a hailstorm advisory), the counterparty is obliged to walk and photograph the covered fields within a fixed number of hours and to intimate anything found. This converts intimation from a discovery-driven act into a scheduled one.
5. A defined evidence pack. Geotagged photographs with visible date and time, the survey number, the crop and stage, the estimated affected area, and the intimation reference number returned by the app or the call centre. The evidence pack goes to the sponsor within 24 hours of intimation.
6. A remedy that bites without being unenforceable. A missed intimation should not void the whole arrangement, but it should shift the loss. Tie a defined portion of the advance recovery, or the next season's input credit line, to compliance with the intimation obligation rather than to the outcome of the claim, which nobody controls.

The drafting principle is narrow. Do not contract for a claim to be paid, since the assessment is the insurer's and the scheme's. Contract for the act that preserves the right to a claim, on a timeline the counterparty can actually keep, and audit the act rather than the outcome.

The workflow below is what turns those clauses into something operable. It is short because anything longer will not run at 11pm in a flooded block.

Before the season

1. Build the covered-field register: farmer, survey number, notified crop, insurance unit, application acknowledgement, add-ons taken, financing bank if loanee.
2. Record, per district, which localised covers are notified this season and which add-ons the enrolments actually carry.
3. Store the insurer's toll-free number, the district agriculture officer's contact and the app credentials in the field officer's handset, not in a shared drive.
4. Reconcile the register against the portal record before the enrolment cut-off, because crop and area mismatches are correctable then and effectively not correctable afterwards.

When an event happens

1. Log the event time, not the discovery time. Everything downstream is measured from it.
2. Intimate within 24 hours through any available route, and capture the reference number that comes back.
3. Photograph the affected area with geotag, date and time visible, from a fixed set of positions per field so the images are comparable across visits.
4. Notify the sponsor's procurement desk with the reference number and the estimated affected area, so the supply plan starts adjusting on day one rather than at harvest.
5. Keep the field undisturbed until assessment where that is agronomically possible, and record the date it stopped being possible.
6. Track the intimation to assessment and log the assessment date, because an intimated loss that is never inspected is a different escalation from a loss that was inspected and declined.

The reference number is what converts a claim about how a field looked into a dated record inside the scheme's own system. Without it, a dispute is an argument between two parties' photographs.

PMFBY compensates the cultivator. It does not compensate the processor whose line ran at half capacity, the sponsor who financed a season that did not arrive, or the lender whose recovery slipped by a year. Even a perfectly operated intimation workflow leaves that gap open, and it is the gap that costs a commercial buyer the most.

Three things close part of it:

• Sourcing diversification written into the procurement plan, so that a single flood-prone catchment is not carrying an entire variety-specific programme.
• Parametric weather cover held by the buyer in its own name, which pays on a measured index rather than on a field assessment and therefore has no 72-hour intimation dependency at all. The structure, the trigger design and the basis-risk trade-off are set out in parametric rainfall cover for corporate agriculture buyers.
• Advance recovery structured against the season's realistic downside, rather than against a normal-monsoon assumption that the first half of 2026 already broke once.

The scheme-level direction of travel, including the settlement discipline and funding changes working through PMFBY, is covered in the PMFBY reform package.

The Kharif 2026 additions are worth having. A wild animal add-on and a restored paddy inundation cover reach two losses that the yield index was never going to pick up, on a base of 278.12 lakh hectares. They also come with a condition that most field-level counterparties will miss unless somebody makes it their job. Deciding who that somebody is, and writing it down before the next flood warning, is the whole of the work.