Every certified operator is inspected at least once a year. What surprises people is the rest of it: a tenth of operators get an additional inspection, a tenth get one with no warning at all, and which tenth you fall into is decided by a risk assessment you never see.

The inspection regime

  • 100%Every operator, inspected at least once annually โ€” all facilities, owned or contracted
  • +10%Minimum additional inspections each year, chosen on risk assessment
  • +10%Minimum unannounced inspections, on top of the annual and additional ones
  • UnpredictableTiming "shall not be so regular, so as to become predictable"

What Decides How Often You Are Inspected

Certification bodies must have a written policy on inspection methods and frequency, and NPOP lists what that policy has to weigh:

FactorWhy it raises or lowers frequency
Intensity and type of productionSome systems carry more risk of prohibited input use than others
Size of operationMore area and more members means more to verify
Previous inspections and compliance recordA clean history counts; so does a history of findings
Complaints received under NPOPA complaint is a trigger in its own right
Whether the operator is engaged only in certified productionParallel conventional production raises the stakes
Contamination and drift riskNeighbouring conventional farms, shared equipment, shared storage
Complexity of productionMore processes, more points where organic status can be lost

The Risk Assessment Behind It

Certification bodies must have a documented risk-assessment procedure covering non-compliance across all scopes of activity โ€” and NPOP requires it to include the risk of fraudulent activity and misrepresentation of non-organic products as organic. Operators are sorted into high, medium or low risk, and that rating drives who gets the additional and unannounced visits.

๐ŸŽฏ

Fraud is named in the standard, not implied. If your volumes, your land area and your transaction certificates do not reconcile, the system is built to treat that as a risk signal rather than a clerical error โ€” and Tracenet's analytics are pointed at exactly this.

Residue Testing and Sampling

Certification bodies must hold documented policies on residue testing, genetic testing and other analysis. Those policies have to identify the cases where samples are taken, based on a general evaluation of the risk of non-compliance โ€” and that evaluation must take in all stages of production, processing and chain of custody, with procedures for risk-based sampling at different stages of crop production.

In practice, a sample can be drawn from soil, from a standing crop, from stored produce or from a finished pack. The result attaches to the consignment and to your record.

flowchart TD A["Application to a
certification body"] --> B["First inspection
(conversion clock may start)"] B --> C["Inspection report"] C --> D{"Certification
decision"} D -->|"Granted"| E["Scope certificate
on Tracenet"] D -->|"Conditions"| F["Corrective actions,
then re-check"] E --> G["Annual inspection +
risk-based visits"]
From application to a live certificate, and the cycle that follows.

Preparing for the Visit

  1. Have the records the inspector will ask for in one place: land documents, the crop production plan, input purchases and usage, harvest quantities, storage and sales records.
  2. Be able to walk the chain. From a plot to a harvest to a store to an invoice, with numbers that agree at each step.
  3. Show your buffer zones and contamination controls where neighbouring land is conventional.
  4. Do not stage the farm. Unannounced inspections exist precisely because a prepared farm and a working farm can differ.
  5. Ask for the report. You have the right to a copy; read it before you sign anything.

Group certification is inspected differently โ€” the certification body checks your Internal Control System and then samples members. That is the subject of episode 7. What the inspector is measuring your land against, and when your clock starts, is next. KrushiFlow validates these fields and submits farmer records to the portal in bulk.