PGS India Local Group Registration: Setup and Farmer Entry

A new Local Group goes onto the PGS-India portal in two stages: first the group, then its farmers. Most delays come from preparing farmer records before the group is approved, or from village names that do not match the portal's lists. This episode sets out both stages and the field rules the portal enforces.

Stage One: Registering the Local Group

Register the group and wait for approval; farmers can only be added to a group that already exists on the portal.

A local group is the unit a Regional Council certifies. Before registration, confirm three things:

1. Minimum membership. A group needs at least 5 members, and the guidelines advise about 7 to 10, so that it survives if one or two members leave. Members appraise each other, so a very small group cannot run a proper appraisal.
2. A named contact. One member acts as group leader and is the point of contact for the Regional Council. This is set on the portal and can be changed later.
3. Nearby villages. Members should come from the same village or nearby villages with continuous territory. Groups spread over several sub-districts are harder to appraise and inspect.

Register the group first and wait for it to appear in your Regional Council's group list. Only then prepare farmer data. Farmer records prepared against a group ID that does not yet exist cannot be submitted.

Stage Two: Farmer Registration Field Rules

The portal rejects the whole farmer record if the Aadhaar, mobile, pincode or area fields break its rules.

The portal validates several fields strictly and rejects the whole record if any fail. These are the rules worth checking before submission rather than after.

Excel causes more of these failures than data entry does. A column formatted as Number will drop the leading zero from a pincode and may convert a 12-digit Aadhaar to scientific notation. Format these columns as Text before entering anything.

The area offered for organic certification can never exceed the farmer's declared total area. Where several plots are listed, their combined area is checked against the total, not each plot individually.

Why Location Fields Cause Most Rejections

The village is checked against the sub-district you select, and the spelling must match the portal's list exactly.

Location is not free text. The portal holds its own list of states, districts, sub-districts, blocks and villages, and each level is loaded from the level above it. Your entry must match the portal's spelling exactly.

The dependency chain is not what most people assume:

• District is loaded from the selected State
• Sub-district is loaded from the selected District
• Block is loaded from the selected District — not from the sub-district
• Village is loaded from the selected Sub-district — not from the block

This difference matters. A valid block and a valid village can belong to the same district yet fail together, because the village is checked against the sub-district you selected rather than against the block.

Village names are among the most common reasons for rejection. Portal spellings often differ from local usage, including hyphenation and transliteration: a village recorded locally as Vadwala Rana may exist on the portal only as Vadwala-Rana. The record is rejected outright, not corrected.

Reducing location failures

1. Pull the portal's village list for your sub-district once, and use it as the reference for every submission from that area.
2. Keep a mapping of local spellings to portal spellings. The same corrections recur across batches.
3. Where a village genuinely does not appear, check whether it is listed under a neighbouring sub-district before raising it with the Regional Council.

Preparing a Batch That Submits Cleanly

Check the data before you submit, then compare the number registered with the number you sent.

Regional Councils registering fifty or more farmers at a time gain most from validating before submission rather than correcting afterwards. A rejected record in a large batch is slow to find and slower to resubmit.

A practical sequence:

1. Confirm the group is live on the portal and note its identifier.
2. Format Aadhaar, mobile and pincode columns as Text in the spreadsheet before entry.
3. Check every location against the portal's own lists, sub-district by sub-district.
4. Verify plot areas sum correctly against each farmer's declared total.
5. Submit, then reconcile the count registered against the count sent. A silent shortfall usually means rejected records, not a display delay.

Keep the submitted spreadsheet. At peer appraisal and again at renewal, the Regional Council needs the same farmer and plot data, and re-keying it is where inconsistencies enter the record.

Most registration failures are format and location rules that can be checked before submission. KrushiFlow validates these fields and submits farmer records to the portal in bulk.