A CBBO supporting several FPOs sees the same registration errors again and again. Most come from how data is collected, not from the portal. This episode sets out a standard way to collect, check and correct farmer data across FPOs.
The short version
- Use one template across all FPOs, based on the NPOP farmer details.
- Check twice: in the field, then centrally.
- Look for farmers in more than one FPO; one scope, one certification.
- Read the Certification Body's query, fix at the source, and respond on time.
One Template for Every FPO
The same columns, units and instructions in every FPO prevent most errors.
- Columns for every NPOP farmer detail: name, father's or husband's name, address with pin code, location, area, crops and status.
- Area in hectares everywhere; dates in one format.
- Written instructions for field staff, in the local language.
- One version of the template, used by all FPOs.
Two Checks Before Submission
Field staff check against documents; a central team checks again and looks across FPOs.
- Field check.Every name, Aadhaar number and survey number against the original documents.
- Central check.A second person reviews each FPO's sheet.
- Cross-FPO check.Search Aadhaar numbers across all FPOs. An operator cannot hold two certifications for the same scope.
- Master list.One list of all farmers, their FPO and their ICS code.
Illustrative workload. At about two minutes per farmer, checking 500 farmers across 10 FPOs takes about 17 hours, every year.
Correcting Queries and Rejections
Read the Certification Body's remarks, fix the source record, and respond within its stated timeline.
| Common query | Fix |
|---|---|
| Name differs from documents | Correct to the Aadhaar and land record spelling |
| Location or survey number wrong | Re-check in the field and against the land record |
| Farm history missing | Collect the crop and input history that sets the conversion period |
| Agreement missing | Get the farmer's signed ICS agreement |
Respond within the timeline in the Certification Body's remarks. A late response can mean starting the application again.
Check yourself
Tap an answer to see whether you are right, and why.
A farmer appears in two FPOs you support. Why does it matter?
- It does not
- One scope can have only one certification
- It doubles the subsidy
NPOP 4.4.2.3 prohibits multiple certifications for the same scope.
Where should corrections be made first?
- On the portal only
- In the source record, then everywhere it is used
- In an email
Fixing only the portal leaves the error in your own records.
Remember these things
- One template for all FPOs.
- Field check, then central check.
- Search for duplicates across FPOs.
- Respond to queries on time.
A standard process across FPOs turns repeated rejections into rare ones. KrushiFlow validates these fields and submits farmer records to the portal in bulk.