Blog

What is the EU monitoring approach for CAP checks?

7 October 2026

Rolling green farmland divided by hedgerows under an overcast sky.

Anyone who has sat through a CAP control planning meeting has heard both terms thrown around like they mean the same thing: OTSC and Monitoring Approach. They don't. Mixing them up in a control statistics return is the kind of thing an auditor flags on day one.

OTSC: the sample-based model

The traditional CAP control model works on a sample. A paying agency pulls a percentage of declared parcels, usually through risk analysis plus a random slice, and sends an inspector or uses remote sensing to verify that one parcel against the declaration. If the parcel passes, the farmer's claim is cleared on that point. The rest of the parcels in the scheme never get individually checked that year. That's the nature of a sample: it tells you something about the population, not about every single file.

This is still the backbone of IACS control in most Member States for a lot of interventions, and it works. The gap is coverage. A 5% sample means 95% of declared parcels are accepted on the strength of the declaration and the sample's statistical validity, not on direct verification of that specific parcel.

Monitoring Approach: every parcel, every season

The Monitoring Approach, introduced under the current CAP legal framework, lets a paying agency replace OTSC for a given intervention with continuous monitoring of the full population of parcels declared under it. Instead of sampling, the agency (or its contracted service) runs Copernicus Sentinel-1 and Sentinel-2 data across the whole declared area on a regular cycle through the growing season, and classifies each parcel against the eligibility conditions for that intervention: green for compliant, red for non-compliant, yellow where more evidence is needed, grey where cloud cover or data gaps left the parcel unresolved.

Every declared parcel in the population gets a check each season. Cost per parcel holds flat well past the few-thousand-parcel mark, which is roughly where a walking inspection schedule runs out of budget. A Member State can run the Monitoring Approach for some interventions (say, a greening requirement or a crop diversification rule) while keeping classic OTSC for others in the same campaign. That swap happens at the intervention level, inside the same campaign, rather than across the whole control system.

Where the yellow and grey outcomes land matters. Those parcels still need evidence: a geotagged photo, a farmer declaration, or a targeted visit. The Monitoring Approach cuts down how many parcels need boots-on-the-ground follow-up. It doesn't remove that follow-up entirely, and any agency that's run a pilot year knows the grey bucket from persistent cloud cover is the one that eats staff time.

What this changes for a crop-type check specifically

For interventions tied to the crop grown on the parcel, declared crop type is one of the easiest things to verify from a seasonal reflectance signature, because different crops have distinct growth curves across the season. That's exactly the kind of check the Monitoring Approach was built to absorb: instead of a sample walk confirming that a few hundred maize declarations match reality, every declared parcel gets a crop-type read for the season, dated and sourced, sitting next to the claim file rather than replacing it.

If your agency is weighing whether to bring a crop-type intervention under the Monitoring Approach for next campaign, it helps to see what a parcel-level output actually looks like before committing staff hours to the switch. Crop Type Mapping builds that output as a straightforward layer: a crop-type call per declared parcel, exportable alongside the rest of your control file, without needing to stand up continuous monitoring infrastructure for the whole scheme.

Get in touch if you want to see a sample output against your own declared-parcel list before the next campaign.