Prerequisite 7 of 21

NAMP crop matching (EFCAS)

← All prerequisites
7Not built

The 2015 proposal

A National Agri Matching Programme (NAMP/EFCAS): match farmers' ranked crop choices to zone-wise demand by a fair computer algorithm — the way doctors are matched to hospitals — with incentives, crop holidays and experimental crops.

Redrawn from the 2015 deck

StateSoil scientistFarmerCredit facilityBuyerEFCAS
EFCAS — the Electronic Farmer’s Crop Application Service the deck proposed: a single hub linking the farmer to the state, soil science, credit and the buyer.

Where it stands in 2026

No country has built crop matching as the deck conceived it, and that is the honest starting point. The nearest working analogues are partial: Brazil’s ZARC zones credit and insurance to climate-appropriate planting windows, while the now-abolished EU production quotas allocated output by fiat — and were dismantled precisely because mandatory quotas distort more than they fix. The defensible form is therefore not allocation but advice: a voluntary matching engine that helps farmers and the nation avoid the recurring boom-and-bust glut, built on the Nobel-winning deferred-acceptance (Gale–Shapley) mechanism. That engine is the working simulator on this site — proof the idea computes, not a claim that it has been deployed anywhere.

The open gap

Build it as voluntary advice with incentives, never binding quotas — the deck’s most original, still-unbuilt idea.

The path to close it

Ship it as a voluntary advisory layer on AgriStack, never an allocation engine. Farmers rank their crop preferences; the algorithm proposes a zone-balanced match that clears expected national demand against local suitability (the deferred-acceptance simulator on this site), and uptake is nudged, never ordered — through assured procurement, input support and crop-holiday payments for switching out of a glutted crop. Borrow Brazil’s ZARC lever: condition the cheapest credit and insurance on planting within the advised window, so the recommended choice is also the financially easiest one. De-risk the politics by piloting in a single district, publishing the welfare gain and the count of unstable ‘blocking pairs’ openly, and scaling only on demonstrated farmer benefit — the opposite of a quota imposed from Delhi. It is the deck’s most original idea, and it earns trust by staying advisory and transparent.

Specifications — what “built” requires

Illustrative — a proposed specification and sequence, not an official government roadmap.

Acceptance criteria

  • A voluntary advisory engine — never a binding allocation or quota.
  • Farmers rank crop preferences; the algorithm returns a zone-balanced, stable match.
  • Uptake is nudged only by incentives (assured procurement, input support, crop-holiday payments).
  • Credit and insurance terms may be conditioned on planting within the advised window (ZARC-style), never mandated.
  • Welfare gain and blocking-pair counts are published openly for every pilot.
  • Runs as a layer on AgriStack; scales only on demonstrated farmer benefit.

Technical spec

Mechanism
deferred-acceptance (Gale–Shapley), stability-checked
Inputs
farmer crop-preference ranks + zone suitability + national demand estimate
Output
proposed zone-balanced crop match per farmer (advisory only)
Incentives
procurement assurance, input subsidy, crop-holiday payment
Integration
AgriStack FarmerID; ZARC-style credit/insurance conditioning
Transparency
published welfare delta + blocking-pair metrics per pilot

Roadmap to built — phase 1 → 2 → 3

Illustrative — a proposed specification and sequence, not an official government roadmap.

  1. 1
    Phase 1 · Now

    Ship the advisory engine

    Launch the voluntary deferred-acceptance simulator on AgriStack (advisory only).

    Farmers receive a zone-balanced crop suggestion.

  2. 2
    Phase 2 · 6–12 months

    Add the incentives

    Wire in procurement assurance, input support and crop-holiday pay, plus ZARC-style credit conditioning.

    The advised crop becomes the financially easiest one.

  3. 3
    Phase 3 · 12–24 months

    Pilot, prove, scale

    Run a single-district pilot and publish welfare and blocking-pair metrics; scale only on demonstrated gain.

    Evidence-led national rollout — built.

See it working: Agri-Match simulator →

Where it sits in the chain

See the full map →

Depends on

Enables

Nothing yet — this is a capstone of the chain.

Sources