The Polygon Problem

The date is fixed. From 30 December 2026 the operative provisions of the EU Deforestation Regulation apply to large and medium operators and traders. Natural persons and micro or small undertakings established as such by 31 December 2024 have until 30 June 2027 — but not for products that were already inside the old EU Timber Regulation, which are due from 30 December 2026 whatever the operator's size. That carve-out sits in the last line of the amended Article 38, and it catches wood first. The dates are not a forecast; they are the amended text of Article 38, rewritten by Regulation (EU) 2025/2650 of 19 December 2025 — the second twelve-month postponement, and the one that also introduced the downstream operator and the simplified declaration. The Commission's own timeline carries the same dates and adds a third: the products brought newly into scope by the July 2026 delegated act — soluble coffee, certain palm oil derivatives, frozen cattle tongues — apply from 30 December 2027.

What it asks of anyone who grows something on a slope fits in two lines. Article 9(1)(d) of Regulation (EU) 2023/1115 requires the operator to collect the geolocation of all plots of land where the commodity was produced, with the date or time range of production. Article 2(28) sets the form: six decimal digits minimum, and for plots over four hectares producing anything other than cattle, polygons with enough points "to describe the perimeter of each plot of land."

The tooling for that is free. Open Foris Whisp, FAO's plot-level screening service, is free and open source, takes geometry from a mobile app, a QGIS plugin, a browser or an API, and returns a convergence-of-evidence read against public geospatial layers. FAO is explicit that the output is not a determination of legal compliance — it tells you where to look, not whether you have passed. The JRC's global forest cover map for 2020 is published openly, no licence and no royalty, and sits in Earth Engine. The Commission's Information System — a specialised tool on the TRACES platform — takes coordinates drawn on a map, entered one by one, or supplied in bulk as GeoJSON, offers a machine-to-machine API, and free online operator training resumed once the system re-opened in mid-2026.

So nobody's submission is going to fail because the software cost money. It will fail because of what happened, or did not happen, on the ground three harvests earlier.

The phrase that does the damage

Read Article 2(27) before Article 2(28). A "plot of land" means land within a single real-estate property, as recognised by the law of the country of production, enjoying sufficiently homogeneous conditions to allow an aggregate deforestation-risk evaluation.

That clause quietly imports the host country's land law into an EU customs filing. Where cadastral title is clean, it is trivial. Where production sits on ancestral domain, on a community-based tenure instrument, on undivided inherited land, or on a boundary that exists in a barangay's memory and nowhere in a registry, "single real-estate property" has no clean referent — and the operator still has to declare one. The definition is per-property and Article 9(1)(d) says all plots, so a cooperative footprint submitted as one geometry does not answer the question asked, however well-formed the ring is.

Most compliance programmes discover this late. Geometry is downstream of tenure, and you cannot draw your way out of an unresolved boundary.

Geolocation and consent are the same file

The regulation makes that explicit, and the connection is routinely missed because it lives in a different chapter. Article 3(b) prohibits placing products that were not produced in accordance with the relevant legislation of the country of production, and Article 2(40) defines that term to include land use rights, third parties' rights, and "the principle of free, prior and informed consent (FPIC), including as set out in the UN Declaration on the Rights of Indigenous Peoples." Article 9(1)(h) requires "adequately conclusive and verifiable information" that the commodity was produced in accordance with that legislation, "including any arrangement conferring the right to use the respective area."

The risk-assessment criteria in Article 10(2) then name, in sequence, the presence of Indigenous Peoples, consultation and cooperation in good faith with them, and duly reasoned claims by Indigenous Peoples — based on objective and verifiable information — regarding the use or ownership of the production area. Annual public reporting under Article 12(4)(c) requires non-SME operators to give, where applicable, a description of the process of consultation of Indigenous Peoples, local communities and other customary tenure rights holders — or of the civil society organisations present in the production area. The "where applicable" carries less relief than people hope: once Article 10(2) has you recording Indigenous presence and Indigenous claims, the reporting limb is hard to argue away.

A polygon drawn across a contested boundary is therefore not a neutral geometric object. It is a written assertion, lodged in a European government database with a reference number attached, about who has the right to use that ground. Communities read it that way, and they are right to.

Where the risk tier helps, and where it does not

Under Commission Implementing Regulation (EU) 2025/1093 of 22 May 2025, the Philippines is classified low risk. Uganda is not on the low-risk list, so it is standard risk by default. Only four countries are high risk: Belarus, DPRK, Myanmar and the Russian Federation. Two consequences follow, and they pull in opposite directions.

First, the relief is narrower than it looks. Article 13 simplified due diligence disapplies Articles 10 and 11 — risk assessment and mitigation — but only once the operator has assessed supply-chain complexity and satisfied itself there is negligible risk of circumvention or of mixing with product of unknown, standard-risk or high-risk origin, and it must be able to produce documentation showing that on request. It does not touch Article 9, so the information obligation, including plot-level geolocation, survives intact. Low risk lowers your analytical burden and your odds of being checked. It does not delete the polygon.

Second, the relief that is material is geographically bounded. The new Article 4a, inserted by Regulation (EU) 2025/2650, creates a one-time simplified declaration for a "micro or small primary operator" — defined in the new Article 2(15a) as a natural person, micro-undertaking or small undertaking, whatever its legal form, established in a country classified as low risk, placing on the market or exporting products it has itself grown, harvested, obtained from or raised on plots located in that same country. For those operators, Article 4a(5) says the Article 9(1)(d) geolocation "may be replaced by the postal address of all plots of land" or of the establishment. The recitals attach a condition the operative text leaves out: the address must clearly correspond to the geographic location of the plot. An address that resolves to a barangay hall does not.

That is the largest concession in the regime for smallholders, and it is available to a Philippine grower-exporter and unavailable to a Ugandan one, for reasons that have nothing to do with either farm. It is also narrower than it reads: it reaches the producer only where the producer is itself the operator placing product on the Union market. The moment an EU importer is the operator — the normal shape of a coffee or cocoa chain — Article 9(1)(d) applies in full, and the postal address is worth nothing to the person filing.

For the record on scope: the commodities are cattle, cocoa, coffee, oil palm, rubber, soya and wood. Coffee is in. Vanilla and coconut are not. A vertically integrated agroforestry operation can be half in scope and half out, which is its own reconciliation problem at the plot level.

An error taxonomy for farm polygons on land without title

These are the recurring failure modes. None is exotic. All are cheap to fix on the slope and expensive to fix from an office.

Failure mode	What it looks like in the field	Where it surfaces
No real-estate referent	Production is real, the holding is recognised locally, and there is no instrument that answers "which single property is this?"	Article 2(27) and 9(1)(h). Fails on the legality limb, not the geometry
Moving customary boundary	Fallow rotation or seasonal reallocation means the walked perimeter is true for one production year and wrong for the next	The production date or time range no longer matches the geometry it is filed against
Two families, one slope	Undivided inheritance or overlapping claims. Both parties walk you a perimeter; the perimeters intersect	Overlapping polygons, double-counted volume, and a live dispute now recorded in an EU database
Aggregated footprint	One geometry drawn around a cooperative's whole membership, or a barangay outline used as a proxy for member farms	Article 9(1)(d) requires all plots; a per-property definition cannot be satisfied by a group boundary
Handset error at the tree line	Consumer GNSS under canopy. Vertices wander into standing forest that the farm never touched	Screening flags forest overlap on a plot that is clean. A false positive costs the same to answer as a true one
No signal, no basemap	Offline capture with no imagery to check against, so nobody notices the track has drifted until it is uploaded	Self-intersections, unclosed rings, implausible vertex counts — rejected or, worse, accepted and wrong
Straddling four hectares	A holding captured as a point because it was assumed to be under the threshold, then measured above it	Point where a polygon is mandatory under Article 2(28). Re-collection, not correction
Geometry without provenance	A clean GeoJSON arrives with no record of who walked it, when, with what accuracy, or with whose agreement	Nothing to defend with under Article 18 examination. The only remedy is to go back

The forest edge is the expensive metre

Two independent sources of error point the same way, and they meet at the boundary between farm and forest.

On the ground: the US government's own guidance states that GPS-enabled smartphones are typically accurate to within a 4.9 m radius under open sky, and that accuracy worsens near buildings, bridges and trees. A boundary walked at the tree line is walked in precisely the conditions the specification excludes.

On the map: the JRC's GFC2020 layer, built to the regulation's forest definition and to its 31 December 2020 cut-off, is a 10 m product. The peer-reviewed assessment of it reports an overall accuracy of 91%, a forest omission error of 8% and a forest commission error of 18% (Bourgoin et al., Earth Syst. Sci. Data 18, 1331–1365, 2026). Read the version number before you quote an error rate at anyone: those figures assess version 2, and the published layer has been revised since. The authors call the map a "non-exclusive, non-mandatory, and not legally binding source" and recommend complementing it with national or regional datasets aligned to the EUDR's own definitions.

Put those together. A pixel is 10 m across, a handset vertex under canopy can be out by half that or more, and the reference layer over-calls forest roughly one time in five. A boundary walked carelessly at the edge generates flags that are not real, on plots that are clean — and there is no cheap way to tell those from the flags that matter.

It gets sharper. Regulation (EU) 2025/2650 rewrote Article 16(3), the criteria competent authorities use to decide where to aim their checks, and the amended list now names, expressly, "whether the plots of land concerned are adjacent to forests." The most consequential metre of the entire perimeter is now also one of the things that helps decide whether you are inspected at all — and checks under Article 18 may include Earth observation data, anatomical, chemical or DNA analysis, and spot checks including field audits in third countries, where those countries agree. For a legal person, Member States must set the maximum fine at no less than 4% of total annual Union-wide turnover in the financial year before the fining decision.

The field sequence that produces a clean submission

This is an order of operations, not a checklist. The order is the whole point: every step exists to stop a later one from being run twice.

• Tenure instrument first, geometry second. Establish on paper what instrument confers the right to use the area, and what unit that instrument recognises, before anyone walks anything. If the instrument is communal, decide what the declared plot is going to be — and get that agreed — while you are still at a table.
• Consent as a process, not a signature at the gate. A farm boundary is personal data and a claim record. Run and document consultation before capture, at community pace. Non-SME operators have to describe that process, where applicable, in annual public reporting under Article 12(4)(c) — design it so the description is worth publishing.
• Sketch map before satellite. Reconcile the perimeter with the holders on a printed basemap, with neighbours present, before a receiver is switched on. Most overlaps surface here, on paper, at almost no cost.
• Walk it; do not trace it. Vertex discipline where it matters: dense at the forest edge and at contested segments, tied to permanent features, sparse along fence lines nobody disputes.
• Log accuracy per vertex, offline. Timestamp, satellite count and accuracy estimate stored with each point. This is what lets you defend a boundary later instead of re-walking it, and it is the difference between geometry and evidence.
• Resolve overlaps the same day, on site, with both holders present. An intersection fixed on the slope is a conversation. The same intersection fixed from an office six months later is a dispute with a paper trail.
• Screen before you leave the district. Run the plot through Whisp or an equivalent while the team is still within reach of the ground. A flag raised in the field is a walk. The same flag raised after demobilisation is a flight.
• Reconcile geometry to the batch last. One geometry per plot, each tied to its production date or time range and to the volume it actually contributed, then build the GeoJSON. Grouping happens in the Information System, by reference number, under the grouping rules that Implementing Regulation (EU) 2026/1565 of 13 July 2026 inserted into Implementing Regulation (EU) 2024/3084 — not by merging polygons in a spreadsheet.

What re-collection actually costs

We do not publish client cost data, so take the structure rather than a number. The structure is the point: a second pass is not a fraction of the first. It is more, for reasons that are not incidental.

Mobilisation dominates and does not divide. Getting a team, a receiver and a vehicle to an upland barangay costs what it costs whether you are capturing four hundred plots or fixing eleven — so a re-walk carries most of the original field cost with none of its scale.

The harvest window is annual. If a boundary error is caught after the production period it was filed against, the honest correction is not a week's work; it waits for the next season, because the geometry has to be true for the production date it is attached to.

Consent does not re-run at the same price. The first visit spends a community's goodwill on the premise that the exercise is competent; a second visit to the same boundary is read, reasonably, as evidence that it was not. That conversation happens from a weaker position, usually with more parties in the room.

And it is a different activity. The first pass is a survey; the second is a negotiation over a line already written down somewhere official. Desk area and ground-truthed area are rarely the same number, and in our own coastal work the direction of travel has been sharply down (the arithmetic is set out here). That gap is not an argument against remote sensing. It is an argument for walking the ground before a number becomes load-bearing — and under EUDR the number becomes load-bearing at the moment it is filed.

What to require, and what not to build for

If a supplier can hand you a GeoJSON but cannot hand you the tenure instrument, the sketch-map reconciliation record, the per-vertex accuracy log, the overlap register, a dated screening output and a consent record, you have geometry. You do not have due diligence, and under Article 18 the difference is the only thing a competent authority will be looking at.

One last thing worth designing around. The amended Article 34 requires the Commission, in its general review by 30 June 2030, to evaluate "the threshold for mandatory use of polygons as referred to in Article 2, point (28)" and the regulation's impact on smallholders, Indigenous Peoples and local communities. The four-hectare line is explicitly under review. Build a field process that produces a defensible perimeter for every plot, not one that produces points below the threshold and polygons above it — because a process built to a threshold has to be rebuilt when the threshold moves, and rebuilding it means going back up the hill.