When group decisions pile up waiting for a Regional Council, the deadline in the guidelines keeps running. After 30 days a group's decision is auto-approved and a non-compliance is recorded against the RC. This episode explains the rule, how to work through a backlog, and how to stop one forming again.
The short version
- The RC must act within 30 days of a group's summary sheet.
- Past 30 days, the decision is auto-approved and a non-compliance is recorded against the RC.
- Return incomplete decisions with reasons; the group resubmits within 15 days.
- There is no renewal of group registration; what waits is the season's decision.
What Is Actually Waiting
A group's certification decision for the season, sent with its peer appraisal summary sheet; not a renewal of registration.
A Local Group registers once; the guidelines say there is no renewal of registration. Each season the group appraises its members, decides each farmer's status, and uploads its peer appraisal summary sheet. That decision is what waits for the Regional Council.
| Deadline | Rule |
|---|---|
| RC decision | Within 30 days of the summary sheet; otherwise auto-approved, with a non-compliance recorded against the RC |
| Resubmission after a return | Group resubmits within 15 days; RC decides within 15 days |
| Actual yields | RC approves within 15 days of upload |
Working Through a Backlog
Sort by date received, check each decision against the seven checkpoints, and return incomplete ones with clear reasons.
- Sort by date received.The oldest decisions are closest to the 30-day limit.
- Check against the checkpoints.Meetings, trainings, summary sheet, complaints, RC inspection, past record and residue results.
- Decide or return.Endorse when complete; return with written reasons when not.
- Record the outcome.The group leader then generates the scope certificate online after approval.
| Checkpoint for endorsing a group's decision | What to look at |
|---|---|
| Meetings | Required group meetings held, and members present |
| Trainings | Key trainings organised, and members present |
| Summary sheet | Complete, and a full reflection of the certification process |
| Complaints | Any complaints received during the period |
| RC physical verification | The RC's own inspection report |
| Past record | Earlier non-compliances, and whether advice was followed |
| Residue testing | The result of any residue test |
Illustrative workload. At about 15 minutes per group, 10 groups take 2.5 hours and 100 groups about 25 hours.
Preventing the Next Backlog
Plan review time around each crop's harvest dates, and ask groups to upload early.
- Summary sheets arrive at least 7 days before harvest, so plan review time by crop season.
- Ask groups to upload as soon as the appraisal is done, not at the last day.
- Track decisions received and days elapsed in one list, checked weekly.
- Timely certification is itself a rule for RCs: repeated delays bring sanctions from the PGS Secretariat.
Check yourself
Tap an answer to see whether you are right, and why.
What happens if an RC does not act on a group's decision within 30 days?
- Nothing
- It is auto-approved and a non-compliance is recorded against the RC
- The group is suspended
The deadline protects groups from RC delays.
Who generates the scope certificate after RC approval?
- The RC
- The group leader, online
- APEDA
The RC approves; the group leader generates it.
Remember these things
- 30 days to decide.
- Return incomplete decisions with reasons.
- Check the seven checkpoints.
- Plan review time by crop season.
An RC that decides within 30 days keeps its groups certified and its own record clean. KrushiFlow validates these fields and submits farmer records to the portal in bulk.