A Contingency Plan That Can Change Its Mind: ICAR's Dynamic Dashboard and the Rabi Risk Map
Contingency plans in Indian agriculture are usually printed, filed and overtaken by the weather. The one drawn up for this rabi season is built to move. The government has prepared contingency plans for 225 districts hit by an erratic monsoon — described by officials as a first for the rabi season — and, alongside the plans, a dashboard designed to revise a district's risk status as conditions change. For lenders, insurers and buyers who price districts rather than farms, that design choice matters more than the headline count.
A list that expires in a week
The case for a live list is in the sowing numbers themselves. Rabi area stood at 37.56 lakh hectares on 30 October, down nearly 46 per cent on the year, after a monsoon that ended 13 per cent deficient and left thin residual soil moisture. One week later the same ministry count had reached 10.87 million hectares by 6 November — still 17.21 per cent behind, but a different season from the one a static 30 October assessment would describe. A district flagged as drought-vulnerable on the first count may simply have been late. Treating the two states as the same risk is how credit limits and procurement plans get set wrong.
What the dashboard actually joins up
ICAR Director General M. L. Jat described the build plainly: the platform will integrate the IMD's weekly forecasts, data on water bodies and other relevant information, at district level, so officials can decide on local conditions. His key point was the revision rule — a district first marked vulnerable could move out of that category if it receives adequate rain, with the assessment reworked from updated forecasts and rainfall, including a 15-day look-ahead. The dashboard is planned for the whole country, not only the 225 districts, and is meant to carry advisories for normal conditions as well as emergencies. ICAR also intends, in time, to integrate it with AgriStack, joining the weather and water layers to the farmer and crop registries underneath.
The weather feed it has to digest
The first test of that feed is already awkward. The IMD's extended-range release of 5 November records post-monsoon rainfall from 1 October to 4 November at 30 per cent below average for the country — yet the single week ending 4 November ran 96 per cent above average, as cyclone Murasu crossed the Andhra coast. The season deficit is not evenly spread either, which is precisely why a national average is a poor underwriting input:
| Region | Rainfall, 1 Oct – 4 Nov 2026 (mm) | Normal (mm) | Departure |
|---|---|---|---|
| East & Northeast India | 63.8 | 127.2 | −50% |
| Central India | 32.2 | 59.5 | −46% |
| South Peninsula | 140.2 | 171.5 | −18% |
| Northwest India | 26.6 | 23.3 | +14% |
| Country as a whole | 56.7 | 81.2 | −30% |
Post-monsoon rainfall by region. Source: IMD extended-range press release, 5 November 2026. Visualisation: Farmioc.
Behind those numbers sits the season's driver. The same release states that very strong El Niño conditions are prevailing over the equatorial Pacific, and that the Monsoon Mission coupled forecast system and other global models expect them to persist through November–December 2026 — a forecast, labelled as such, not an outcome. Its own two-week outlook has countrywide rainfall normal to above normal in the first half of week two (12–18 November). A dashboard that ingests this weekly has to hold both facts at once: a dry season to date, and a wet fortnight possibly arriving.
Advice that changes with the category
The contingency content is crop-switching, not just warning. ICAR has set up a task force to examine oilseeds and pulses in the fallows left after the rice harvest, and Jat's advice for moisture-short fields was direct: where residual soil moisture is insufficient for wheat, farmers could grow suitable oilseed and pulse crops instead. A separate soil health policy is expected in the next two to four months, aimed at fertiliser planning based on nutrient deficiency. Each of these is a data product wearing policy clothes — a switch recommendation is only as good as the district moisture, seed and water data behind it.
What a risk desk should do with it
Three practical consequences follow. First, district risk lists for this rabi should carry a date and a revision history; a lender still working from the 30 October map is underwriting a season that has already moved. Second, the 15-day forecast window the dashboard uses is short enough to schedule against — seed, fertiliser and working-capital releases can be staged to it rather than to the calendar. Third, the AgriStack join, when it lands, is where exposure mapping gets precise: weather and water layers over verified farmer and crop records is the difference between a district average and a portfolio view. That is the layer Farmioc's DataStore is built to work at — district-level sowing, water and weather signals joined to the exposure a bank or buyer actually holds. The dashboard's promise is not the map. It is that the map admits when it has changed.