What is an IPC phase classification, and how does satellite vegetation data feed into it?

The Integrated Food Security Phase Classification, IPC for short (CH in Francophone West Africa), is the five-phase scale that turns a pile of food security evidence into one call: whether an area sits at Minimal, Stressed, Crisis, Emergency, or Catastrophe/Famine. If you've sat through a Technical Working Group session, the acronym is already second nature. The mechanics matter for anyone newer to the calendar: what goes into that call, and why a vegetation anomaly layer keeps turning up in the evidence pack.

How the five phases get decided

IPC runs as a protocol: analysts from government, UN agencies and NGOs convene, bring whatever evidence they have for a given livelihood zone, and classify that zone against the IPC's reference tables using a convergence-of-evidence approach. The core evidence streams usually include:

• Food consumption and coping strategy data from household surveys
• Market price and terms-of-trade data
• Nutrition survey results, wasting prevalence especially
• Mortality data, when it's available
• Biophysical and agro-climatic indicators: rainfall performance, flood extent, and vegetation condition

No single indicator decides the phase on its own. A poor vegetation season alone doesn't push a zone into Crisis, though it rarely gets waved off either, especially in pastoral and agropastoral zones where the survey data lags badly behind the season it's supposed to describe.

Where vegetation data enters the process

Household surveys run on a fixed cycle. Nutrition surveys and the major food security assessments typically happen once or twice a year, and in parts of the Sahel and the Horn, funding and access gaps stretch that cycle further still. Vegetation condition doesn't wait on that cycle. A rainfall anomaly or a poor reading shows up within weeks of the dry spell, not months after an assessment team gets funded and fielded.

That gap is where satellite vegetation data enters the IPC process, as a leading indicator that a zone is heading somewhere before the survey confirms it. A vegetation condition index compared against the long-term seasonal average for that pixel, aggregated up to the livelihood zone, gives analysts a number to set next to the market and nutrition evidence on the analysis worksheet. When that number sits well below normal for two or three consecutive periods, and rainfall totals back it up, that's the kind of convergence that either moves a classification call or, more often, triggers the anticipatory-action process ahead of the next formal IPC round.

That's also the evidence stream that gets reused outside the IPC proper. The same vegetation anomaly reading that lands in a Technical Working Group packet is the one an anticipatory-action calendar runs its own trigger on, usually on a tighter clock than the IPC's own update schedule.

Why analysts still end up pulling this by hand

None of the underlying science here is new. Vegetation anomaly products have existed for decades, and most agencies around the IPC table know how to read one. The friction is operational: someone has to pull the latest raster for the right cropping or grazing zone, clip it to the livelihood zone boundary, compare it against the historical baseline, and turn that into the single number the trigger memo needs. Multiply that across every zone on the watch list, every month, and it stops being a one-off task and starts being a standing job nobody's budget actually has a line for.

Food Security Warning exists for that specific step: a monthly vegetation and rainfall anomaly reading per zone, built to drop straight into the slot an anticipatory-action calendar, or an IPC evidence packet, already has waiting for it.

If your calendar is still waiting on someone to pull and plot that number by hand, get in touch about an early look.