Agencies implementing the National Mission on Natural Farming (NMNF) often encounter data validation blocks during cluster setup. The most frequent blocker occurs when selecting revenue villages or Gram Panchayats during the creation of a 50-farmer cluster. When a location does not appear, farmer registration cannot proceed.

This guide explains why these location records go missing on the portal. It provides direct, manual steps to resolve Local Government Directory (LGD) mapping mismatches, reconcile land records, and prevent rejection by District Nodal Officers.

Resolving Missing Gram Panchayat and Village Dropdown Entries

The NMNF portal sources its administrative hierarchy directly from the central Local Government Directory. If a revenue village or Gram Panchayat was recently created, bifurcated, or renamed, the NMNF master list may not reflect the update immediately.

When a village is missing from the dropdown list during cluster entry, follow these steps to isolate the issue:

  1. Open the official Local Government Directory portal at lgd.gov.in in a separate browser tab.
  2. Navigate to the rural administrative hierarchy section. Select your State, District, Sub-district (Tehsil/Taluka), and Gram Panchayat.
  3. Verify whether the revenue village is listed under that specific Gram Panchayat and note its 6-digit LGD village code.
  4. Confirm if the village is recorded under a neighbouring Gram Panchayat due to recent administrative boundary reorganisations.
  5. If the village exists in the LGD directory but does not appear in the NMNF dropdown, check if your agency profile is restricted by assigned operational blocks.

If the entity is absent from the LGD portal itself, the change must be submitted by the local revenue administration through the state Panchayati Raj department. The NMNF portal team cannot manually insert villages outside the LGD framework.

Correcting LGD Code Mismatches to Prevent Cluster Rejection

District Nodal Officers review cluster applications against official administrative boundaries. A common cause for cluster rejection is an LGD code mismatch between the cluster master profile and the individual farmer records linked to it.

District Nodal Officers require all 50 farmers in a standard NMNF cluster to reside within geographically contiguous LGD-mapped revenue units before signing off on cluster validation.

When village names differ slightly between local usage and central databases, errors compound during cluster submission. To rectify an LGD mismatch before final submission:

  1. Download the draft farmer list from your agency work area on the NMNF portal.
  2. Cross-check each farmer's assigned village code against the target cluster LGD code.
  3. Identify any farmer mapped to a different sub-district or non-contiguous village code.
  4. Remove the misallocated farmer records from the cluster draft.
  5. Re-assign those farmers to their correct LGD-compliant cluster group.

Reviewing and validating each farmer's 6-digit LGD code manually takes about two minutes per record. For a single 50-farmer cluster, this requires roughly two hours of verification. For an agency managing 20 clusters across two districts, manual verification takes over forty hours of cross-referencing against government directories.

Aligning Farmer Land Records with Portal Master Location Data

Discrepancies often occur between state land revenue documents (such as RoR, 7/12 extracts, or Patta) and the NMNF master location data. State revenue portals and the central LGD directory sometimes use different transliterations or historical names for the same revenue village.

To reconcile farmer land records with NMNF portal master data, execute the following manual checks:

  1. Inspect the farmer's land document to identify the revenue village (Mauza or Hadbast number) and Tehsil.
  2. Search the LGD directory using the local revenue sub-district identifier rather than English name spellings.
  3. Match the survey numbers to the corresponding LGD village code established on the NMNF portal.
  4. Enter the farmer profile using the exact LGD-recognised name, recording the local revenue variation in the secondary address field if available.
  5. Ensure the total registered land area under that survey number does not exceed the land parcel ceiling for natural farming support.

For organisations that also manage groups under the Paramparagat Krishi Vikas Yojana, review our companion walkthrough on the NMNF Cluster Registration: Portal Steps for Agencies for structural workflow differences.

Maintaining strict alignment between local land documents, LGD codes, and NMNF portal records prevents validation errors and cluster rejections. KrushiFlow validates these fields and submits farmer records to the portal in bulk.

Related Reading