When a large batch of farmer registrations is returned, the causes are usually few and predictable: missing documents, details that do not match, and unreadable scans. This episode sets out those causes and a verification routine that catches them before submission.
The short version
- Three causes: missing documents, mismatched details, poor scans.
- Check every farmer against a master checklist before scanning.
- Submit a small pilot batch first and learn from the queries.
- Ask your Certification Body for its specific requirements early.
Why Batches Are Returned
Missing documents, details that differ between documents, and scans that cannot be read.
| Cause | Examples |
|---|---|
| Missing documents | No land record, no signed commitment, no farm map |
| Mismatched details | Name spelt differently; area differs from the land record; local units not converted |
| Poor scans | Blurred, cropped, or upside down |
A Verification Routine
A master checklist, a field check, consistent file names, and a cross-check of every detail.
- Master checklist.Every required document, adjusted for your state's land records.
- Field check.Missing items and signatures flagged at the village.
- Clear scans and names.One file per document, named FarmerCode_DocumentType.
- Cross-check details.Name, father's name, area and address across all documents.
- CB requirements.Confirm formats and extra requirements with your Certification Body early.
Illustrative workload. At about a minute per farmer to check village spellings, 200 farmers take over 3 hours.
Submitting in Stages
Submit a small pilot batch, learn from the queries, then submit the rest.
- Submit 5 to 10 farmers first.
- Read every query that comes back and fix the cause in the whole batch.
- Train field staff on what went wrong.
- Submit the rest in manageable batches.
Check yourself
Tap an answer to see whether you are right, and why.
What should come before submitting a batch of 300 farmers?
- Nothing
- A small pilot batch
- A second copy of every file
A pilot shows the problems while they are cheap to fix.
A farmer's area is in guntha. What must you do?
- Enter it as it is
- Convert it to hectares
- Leave it blank
Use your state's official conversion.
Remember these things
- Know the three causes.
- Use a master checklist.
- Pilot batch first.
- Check CB requirements early.
A routine that catches errors before submission is the fastest way through certification. KrushiFlow validates these fields and submits farmer records to the portal in bulk.