A PGS-India certificate is issued from the farmer and plot data held on the portal. If that data is wrong, the certificate is wrong, and a buyer or inspector usually finds the error first. This episode sets out the checks to run before issuance and how to keep records aligned through the year.
The short version
- The certificate is only as good as the portal record behind it.
- Five checks before issuing: area, appraisal, crop, yield and membership.
- Find duplicate farmers by Aadhaar first, then by name, survey number and mobile.
- Compare counts and area with the portal after every submission.
The Checks to Run Before Issuing a Certificate
Run five checks against the portal record: area, appraisal, crop match, yield and membership.
Five checks catch most issues. Run them against the portal record, not against the Regional Council's own spreadsheet, because the portal record is what the certificate is generated from.
| Check | What to compare | Why it matters |
|---|---|---|
| Area consistency | Sum of plot areas against declared total area | Certified area exceeding held land invalidates the certificate |
| Appraisal completeness | Peer appraisal recorded for every farmer | A farmer without an appraisal cannot be certified |
| Crop match | Crops appraised against crops listed for certification | Certificates naming an unappraised crop are challenged by buyers |
| Yield plausibility | Declared yield against plot area | Quantities exceeding what the area can produce indicate mixed produce |
| Membership status | Farmer active in the local group | Certificates issued to departed members are a recurring finding |
The area check is the one most often skipped and the most damaging. Where a farmer's plots total more than the area declared, every downstream figure inherits the error, including the quantity a buyer is entitled to treat as certified organic.
Where Data Goes Wrong Between Appraisal and Issuance
Errors enter through re-typing, partial updates, duplicate farmers and crops added after appraisal.
Errors rarely originate at issuance. They enter earlier and survive because nothing checks them.
- Re-keying between systems. Farmer data captured on paper at appraisal, typed into a spreadsheet, then typed again into the portal, passes through two transcription steps. Each introduces error.
- Partial updates. A farmer adds a plot mid-cycle. The plot is added but the declared total area is not updated, so the two no longer reconcile.
- Duplicate farmer records. The same person registered twice, usually with a name spelling variation or a different father's name format. Both records then receive appraisals, and both can be certified.
- Crop entries added after appraisal. A crop recorded for certification that was never appraised. The certificate names it regardless.
A certificate can only be as accurate as the portal record behind it. Verification after issuance corrects one document; verification before issuance corrects the record every future document is drawn from.
Finding Duplicate Farmers Before They Are Certified
Find duplicates by Aadhaar first, then name with father's name, survey number with village, and mobile.
Duplicates are the hardest of these to detect by eye, because the two records are rarely identical. Check for them on combinations rather than on name alone:
- Aadhaar number. The most reliable identifier. Any repetition across the group is a duplicate, whatever the names say.
- Name with father's or husband's name. Catches records where Aadhaar is missing from one entry.
- Survey number with village. Two farmers cannot hold the same survey number in the same village. Where this appears, one record is wrong.
- Mobile number. Shared numbers within a household are legitimate, so treat repetition here as a prompt to check rather than as proof.
Resolve duplicates before appraisal where possible. Once both records carry appraisals, deciding which to retain means deciding which appraisal to discard, and the Regional Council has to justify that choice.
Keeping Records Aligned Across the Annual Cycle
Compare counts and total area with the portal after every submission, not once a year.
Regional Councils handle the same farmer data at three points each year: registration or renewal, peer appraisal, and certificate issuance. Where each stage maintains its own copy, the three drift apart.
A single reconciliation practice prevents most of this. After every portal submission, compare the count and total certified area held by the Regional Council against the portal's own figures.
A shortfall in count usually means rejected records. A difference in area usually means a plot was added or amended in one place only.
Doing this at each submission takes minutes. Doing it once a year, immediately before issuance, means reconstructing which of three sources was correct for each affected farmer.
Check yourself
Tap an answer to see whether you are right, and why.
Two records share an Aadhaar number but have different spellings. What are they?
- Two farmers
- A duplicate
- A portal error
Aadhaar is the most reliable identifier; a repeat is a duplicate.
A farmer's plots add up to more than their declared total area. Why does it matter?
- It does not
- The certified area is more than the land held
- It only affects the map
Every figure after it, including certified quantity, inherits the error.
Remember these things
- Check the portal record, not your own spreadsheet.
- Run the five checks before issuing.
- Remove duplicates before appraisal.
- Reconcile after every submission.
Checking the record before issuance is far faster than correcting a certificate afterwards. KrushiFlow validates these fields and submits farmer records to the portal in bulk.