Villages missing from the dropdown, and LGD code mismatches, block cluster setup and cause rejection. This guide covers why they happen and how to fix them.
The short version
- The portal's village list comes from LGD — recent changes may lag.
- Cluster and farmer LGD codes must match.
- Reconcile land-record names with LGD names.
- Report missing villages with official LGD evidence.
Resolving Missing Gram Panchayat and Village Dropdown Entries
New, split or renamed villages may be missing from the portal's list until it syncs with LGD; report them with evidence.
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:
- Open the official Local Government Directory portal at lgd.gov.in in a separate browser tab.
- Navigate to the rural administrative hierarchy section. Select your State, District, Sub-district (Tehsil/Taluka), and Gram Panchayat.
- Verify whether the revenue village is listed under that specific Gram Panchayat and note its 6-digit LGD village code.
- Confirm if the village is recorded under a neighbouring Gram Panchayat due to recent administrative boundary reorganisations.
- 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
Make sure the cluster profile and each farmer record use the same LGD codes, or the cluster is rejected.
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 check that a cluster's farmers sit within contiguous, LGD-mapped revenue units before validating the cluster.
When village names differ slightly between local usage and central databases, errors compound during cluster submission. To rectify an LGD mismatch before final submission:
- Download the draft farmer list from your agency work area on the NMNF portal.
- Cross-check each farmer's assigned village code against the target cluster LGD code.
- Identify any farmer mapped to a different sub-district or non-contiguous village code.
- Remove the misallocated farmer records from the cluster draft.
- 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
Match land-record village names to LGD names, since transliterations differ between systems.
Mismatches 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:
- Inspect the farmer's land document to identify the revenue village (Mauza or Hadbast number) and Tehsil.
- Search the LGD directory using the local revenue sub-district identifier rather than English name spellings.
- Match the survey numbers to the corresponding LGD village code established on the NMNF portal.
- Enter the farmer profile using the exact LGD-recognised name, recording the local revenue variation in the secondary address field if available.
- 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.
Check yourself
Tap an answer to see whether you are right, and why.
Why might a new village be missing from the dropdown?
- It isn't eligible
- The portal hasn't yet synced a recent LGD change
- Too many farmers
The list is sourced from LGD and recent changes can lag.
Remember these things
- The list follows LGD.
- Match LGD codes everywhere.
- Report gaps with evidence.
Consistent location data prevents validation errors and cluster rejections. KrushiFlow validates these fields and submits farmer records to the portal in bulk.