Documenting conditionality and landscape features

The word covers two different kinds of requirements that interlock. One set concerns the condition of the land – soil cover, erosion protection, and how you handle permanent grassland, wetlands and landscape features. The other set is basic requirements from other areas of law that are tied to the payment, for example water, animal welfare and plant protection law. Both apply at the same time, and a breach in one area affects the payment in the other.

That has an uncomfortable consequence: conditionality can't be limited to the fields you applied for. It attaches to the farm, not to the application. A hedgerow at the edge of a field that receives no payment at all can still trigger a reduction – and if you never documented it, you can't prove its original condition afterwards.

The standards themselves are set out in the ordinance and get updated over time. This article deliberately doesn't reproduce them: it explains what records they require from you, so you can look up the binding version in the right place.

Hedgerows, tree rows, copses, field margins, ponds and terraces look like a contradiction in the system at first glance. They count as eligible area even though nothing grows on them that gets harvested – and at the same time, they may not be removed. That's not a flaw, it's the essence of the rule: preserving these features isn't banned on one hand and rewarded on the other – it's built directly into the condition for the payment.

In practice, that means a feature has two roles. As part of the land, it enters the applied area; as a protected object, it falls under a ban on removal. Coppicing a hedgerow is maintenance; grubbing it out can cost you both – the feature itself and part of the payment.

That's why the question of how long a feature has existed and what condition it's in is not a side issue. It decides whether a change counts as maintenance or as removal.

A feature is identifiable from its description, or it isn't. An entry reading “hedgerow on the north edge” helps nobody when someone wants to know, two years later, how long it was. The record needs the type, the location, the dimensions and the condition – and how long the feature has existed, because that's what the protection depends on.

The dimensions follow the shape: a linear feature like a tree row is described by length and width, an area-shaped one by its footprint, and a group of trees additionally by its number of trees. Once you've recorded that cleanly, all that's left is to keep it up to date.

The field block is the officially delineated reference area that both the application and the inspection relate to. It doesn't belong to the farm but to the administration's cadastre – and that's exactly where its value lies: both sides are talking about the same piece of land, even if the farm divides it differently than the authority does.

Differences between the farmed boundary and the official one are normal – a field can be smaller than the field block, and several fields can share one. It becomes noticeable when the sum of the applied-for area exceeds the field block, or when a feature recorded there disappears. Anyone who keeps that reference in their own system spots such discrepancies before the authority does.

Many requirements don't depend on what you grow, but on what the land is and what it was. Permanent grassland comes about through the passage of time, not through a decision; sensitive permanent grassland is additionally tied to its location. Wetland and peatland carry their classification independent of how they're used, and erosion risk follows slope and soil.

These characteristics are therefore properties of the land and belong on record there – together with the water buffer strip and its width, minimum soil cover, and whether a field is managed as non-productive. Anyone who attaches them to the crop instead loses them at the next crop change.

The difference becomes visible at the latest when land is swapped. The history stays with the land, not with the person farming it – and it's the history that justifies a classification.

The actual record isn't today's condition, but the condition that applied in the relevant application year. An inspection looks backward: it wants to know how the land was classified at the point in time the payment was claimed for. A system that only knows the current state can't answer that question – it has overwritten the answer.

That's why the condition needs to be recorded for each year before it changes. After that, a change is unproblematic, because it has a prior state you can point to. Without that prior state, every change turns into an explanation in the next application – and explanations are less convincing than records.