Second-level control in IACS: what it is and why paying agencies run one
26 October 2026

Every paying agency running an IACS-funded scheme runs two layers of checking, and it's easy to blur them together if you're new to the control cycle. The first-level check happens on the claim itself: administrative cross-checks plus field-visit or remote-sensing inspection of a sample of parcels, run by the agency's own control unit before money moves. The second-level control sits above that: it checks whether the first-level control did its job properly, working back through a resampled subset of the parcels that already cleared the first pass.
That distinction matters because the two checks answer different questions. First-level control asks: is this specific claim correct? Second-level control asks: is the agency's whole control system producing reliable answers? One is about a parcel. The other is about a process.
Second-level control vs first-level check
A first-level check is wide and shallow by design. It covers the sample size the regulation sets, often a few percent of claims, using a mix of cadastral cross-checks, VHR imagery, and field visits. It's the layer that decides whether a given farmer gets paid, docked, or flagged.
A second-level control is narrow and deep. It's usually run by a separate unit, sometimes the certification body that signs off the agency's annual accounts, and it goes back over a subset of parcels that already cleared first-level control. The reviewer wants to confirm the inspector got the right answer and that the agency can show its working: the finding, the evidence behind it, and the date it was made. If the re-inspection disagrees with the original finding on crop type or boundary, that's a quality gap the agency reports up the chain, not something that gets quietly patched and forgotten.
How the re-inspection sample works
Most second-level control cycles pull a random or risk-weighted sample from parcels the first-level control already closed out. For each one, the reviewer wants three things sitting together: what was declared, what was found, and what the evidence was based on. If a first-level finding was built on a field visit note with no supporting imagery, or a photo from a date that doesn't line up with the crop's growth stage, the re-inspection has nothing solid to check against. That gap, not necessarily a wrong call, is often what second-level control finds.
This is the part that turns into real work for a compliance team. Pulling archived imagery for a parcel that was inspected eight months ago, matching it to the declared crop calendar, and reconstructing why an inspector made the call they made, done parcel by parcel across a sample list, eats days during a window when the agency is also closing the current claim year.
What the second-level control is actually checking for
Three things tend to come up across most second-level reviews:
- Whether the crop-type call on the parcel matches what the imagery or site evidence shows for that growing season
- Whether the finding is dated and traceable to a specific source, not just an inspector's note
- Whether the sampling and methodology the first-level unit used match what was documented in the control plan
None of this requires a bigger sample or more inspectors. It requires the first-level finding to already carry its own evidence trail, so a second-level reviewer can check it without starting over.
That's the gap a parcel-level crop-type layer is built to close. Crop Type Mapping gives every declared parcel a dated, sourced crop-type call built from its seasonal reflectance signature, sitting next to the claim file rather than buried in an inspector's field notebook, so when the re-inspection sample comes around, the evidence is already there to check.
If your agency is building out this season's control file, it's worth seeing what that layer looks like before the second-level sample gets pulled.