A grower group is certified as one entity, but nobody inspects 400 farms individually every year. What makes group certification work — and what a certification body actually audits — is the Internal Control System.
The ratios that define an ICS
- 2× a yearInternal inspection of 100% of the group's farmers
- 1 : 50–60At least one internal inspector per 50 to 60 farmers
- √nExternal sample the certification body inspects, scaled by risk
- Min 20Farmers inspected during any external inspection
What the ICS Is
The ICS is the control system organised by the member farmers themselves to ensure the group meets NPOP requirements. One identified person — the ICS Manager, preferably an existing member of the group — carries responsibility for that compliance.
The certification body does not replace the ICS. It audits it, then samples members to test whether the ICS's own findings can be trusted.
What NPOP Requires the ICS to Have
| Requirement | Detail |
|---|---|
| An office | At or near the group's location — and the certification body physically verifies it before accepting the group |
| A defined structure | An organisational chart with defined roles and responsibilities for ICS personnel |
| Vetted people | Qualified, experienced personnel whose credentials, including previous employment, the group verifies |
| Internal standards | Formulated in the local language, within the NPOP framework |
| Enough inspectors | Adequate internal inspectors to inspect 100% of farmers twice a year, at least one per 50–60 farmers |
| Farm diaries | Every farmer maintains a diary of activities on their farm |
Two of these quietly decide whether a group passes. The office is physically verified — an ICS that exists only in a consultant's laptop fails at that step. And internal standards in the local language are what make the rules usable by the people expected to follow them, which is the whole point of an ICS.
The Sampling Rule
When the certification body inspects the group, it inspects a sample of members. The size of that sample is set by the group's risk category:
| Risk | Sample size | 100 farmers | 400 farmers |
|---|---|---|---|
| High | 2 × √(number of farmers) | 20 | 40 |
| Medium | 1.5 × √(number of farmers) | 20 (floor) | 30 |
| Low | √(number of farmers), minimum 20 | 20 | 20 |
A minimum of 20 farmers is inspected during external inspections regardless. The sampling plan must also be built so that all farmers are covered in due course, and the same farmer is not repeated — except where there is verification to do or a suspicion of non-compliance.
Risk category is the lever that matters. The difference between low and high risk for a 400-farmer group is 20 external inspections versus 40 — double the disruption and double the chance that a weak member is the one sampled. Past sanctions, changes in the production plan and newly joined members all feed that assessment.
The Unique ID Prerequisite
NPOP sets out a farmer registration step that takes effect once the Ministry of Agriculture and Farmers Welfare's Unique ID system is formally operationalised: farmers register on the ministry's centralised portal, receive a unique ID, and give that ID to the group's ICS. Farmer information is then validated against the ministry's database and transferred electronically into the NPOP database through an API, after which the group's registration proceeds on Tracenet.
It is worth tracking, because it changes the order of work — farmer registration would become a prerequisite to group registration rather than a parallel task.
Building an ICS That Survives an Audit
- Appoint the ICS Manager from within the group, and write down what they are accountable for.
- Count your inspectors against the 1:50–60 ratio before you count your farmers — a 300-farmer group needs five or six.
- Translate the internal standards. If members cannot read them, the inspections will not hold.
- Run both internal inspection rounds, and keep the records that prove each one happened.
- Keep farm diaries current at the farm, not reconstructed at the office before an audit.
For the FPO view of the same structure, see FPO Internal Control System and NPOP internal inspection. Next: certifying a processing or packing unit. KrushiFlow validates these fields and submits farmer records to the portal in bulk.