EUDR False Positives: What to Do When Satellite Data Flags a Plot

EUDR False Positives can lead to unnecessary supplier investigations, delayed procurement decisions and additional compliance costs, making accurate satellite-based deforestation screening and risk assessment essential for businesses managing complex supply chains. Satellite monitoring has become an important source of evidence for businesses preparing for the EU Deforestation Regulation (EUDR). It can help teams identify possible forest loss around a production plot and focus their attention where further checks may be needed. But an alert is not, by itself, a complete compliance decision.

A flagged plot may require closer examination because of an inaccurate boundary, inconsistent datasets, cloud cover or gaps in historical imagery. Equally, the absence of an alert does not prove that a plot is compliant. Businesses need to evaluate the satellite signal alongside plot information, supplier evidence and the wider due diligence context.

For EU importers and operators, the practical question is not simply, “Did the system flag this plot?” It is: “What does the evidence show, what remains uncertain, and can we explain how we reached our conclusion?”

Key Takeaways

• A satellite alert does not automatically mean non-compliance: Satellite monitoring may flag changes in forest cover, but an alert alone does not establish that deforestation has occurred or that a plot violates EUDR requirements.
• Validate before making procurement decisions: Businesses should investigate flagged plots before rejecting suppliers or excluding them from their supply chains.
• Understand the reason behind the alert: Tree-cover changes may result from different activities or events, including agricultural expansion, harvesting, natural disturbances or data-related limitations. The underlying cause needs to be assessed.
• Use plot-level evidence for verification: Review plot boundaries, satellite imagery, historical land-cover information and supporting documents to understand the flagged change.
• Consider the EUDR cut-off date: The assessment must establish whether relevant deforestation occurred after 31 December 2020. Historical evidence is essential to this evaluation.
• Combine satellite monitoring with ground-level verification: Supplier information, field assessments and other reliable evidence can help clarify alerts that satellite data alone cannot conclusively explain.
• Maintain an audit trail: Document the alert, investigation, evidence reviewed, findings and final decision to support transparent and consistent risk assessment.
• Avoid treating every alert as a confirmed violation: A structured verification process helps reduce unnecessary supplier rejections, procurement delays and compliance costs while ensuring genuine risks receive appropriate attention.

What does a false positive mean in an EUDR assessment?

In this context, a false positive is an alert that initially suggests possible deforestation or forest degradation but, after further investigation, is not supported as evidence of the relevant non-compliant activity. For example, a change detected in imagery might relate to a plot-boundary error or a feature that the monitoring method has misclassified.

The term should be used carefully. A business should not label an alert a false positive simply because another dataset does not show the same change or because a supplier disputes it. The conclusion should follow from a documented review of reliable, relevant evidence. Where the evidence remains inconclusive, the uncertainty should be recorded and investigated further rather than assumed away.

Why satellite alerts can be difficult to interpret

1. Geolocation and polygon errors

Coordinates can be misplaced, polygon boundaries can be drawn inaccurately, and uploaded geometries can contain errors. A small shift may cause monitoring to evaluate the wrong area or include nearby land. Validate the plot’s coordinates, perimeter and geometry before interpreting the alert.

Read our guide to avoid common geolocation errors and ensure your plot data is ready for EUDR assessment.

[Read the Guide to Common GeoJSON Errors in EUDR]

2. Different datasets can tell different stories

Satellite products differ in resolution, observation dates, classification methods and the phenomena they are designed to detect. One dataset may identify a change that another does not. Differences are a reason to investigate the methods, dates and spatial coverage—not a reason to select whichever result is more convenient.

Discover how combining satellite intelligence with geolocation data and supplier information can help businesses identify potential risks, investigate alerts and strengthen their due diligence process.

[Read the Guide to Satellite Monitoring in EUDR]

3. Historical imagery and the EUDR cutoff date

The EUDR deforestation-free criterion is tied to the cutoff date of 31 December 2020. Teams need to understand when the relevant change occurred, not merely whether a satellite product reports a change. Historical imagery may be incomplete, obscured or difficult to interpret, so the timeline should be assessed using suitable evidence and the applicable legal definitions.

4. Land cover can be misinterpreted

Seasonal crop cycles, plantation management, agroforestry, temporary disturbance and other land-cover changes can complicate image interpretation. These factors do not automatically establish compliance. They are context to test against the actual plot, production history and relevant EUDR requirements.

5. Supplier evidence may be incomplete

A supplier may provide a written explanation, photographs or land records, but the business still needs to assess whether that material is relevant, credible and consistent with other evidence. An unsupported assurance should not replace verification.

Discover how a structured risk assessment approach can help businesses identify potential red flags, investigate concerns and determine appropriate risk mitigation measures.

[Read the Guide to Deforestation Risk Assessment Under the EUDR]

A practical five-step process for investigating an alert

Step 1: Verify the plot geolocation

Confirm that the plot belongs to the supplier and commodity being assessed. Check the coordinates, polygon perimeter, geometry validity and any available mapping source. Confirm that the monitored area matches the production plot rather than adjacent land. If an error is identified, correct it through a controlled process and retain a record of the original data and correction.

TraceX Automatically validates and repairs plot boundaries, detects duplicates, standardises WGS84 coordinates, verifies actual plot area and flags unreliable or invalid geolocations. It also checks whether plots are geographically and agriculturally plausible, identifying issues such as urban locations, water bodies, unsuitable elevations and missing vegetation—with clear reasons for correction before submission.

Step 2: Compare relevant forest datasets and imagery

Review the source, date, resolution and methodology behind the alert. Where appropriate, compare independent datasets or imagery from multiple dates. Look for whether the apparent change is persistent, where it occurs relative to the plot boundary, and whether the available imagery supports the initial interpretation. Record both corroborating and conflicting evidence.

Combines multiple independent global, national and TraceX satellite data sources to assess each plot, flagging non-compliance only when multiple sources agree to reduce false positives. It distinguishes tree-crop plantations and established farmland from forest conversion, enabling more accurate deforestation risk assessments.

Step 3: Test the timeline against 31 December 2020

Build a timeline from the available historical evidence. Distinguish a detected change from a conclusion about when it occurred and what it represents. If the dates cannot be established confidently, document that limitation and identify what additional evidence or expert review is needed.

TraceX Provides transparent, plot-level assessment reports explaining the decision rules, evidence, satellite imagery, yearly clearance maps and reasons for false-positive dismissals, with PDF exports for auditors and buyers. It preserves submitted boundaries, dataset versions and assessment engine versions to ensure results are reproducible, supporting the five-year record-retention requirement.

Step 4: Request and verify supporting supplier evidence

Ask the supplier for relevant plot history, production information, land-use records, dated photographs, field observations or other supporting material. Assess whether the evidence relates to the exact plot and relevant period. Where warranted, consider independent technical review or field verification. Keep the request, response and assessment together.

Step 5: Document the assessment, mitigation and conclusion

Record the original alert, datasets reviewed, geolocation checks, supplier responses, evidence gaps, corrections, reviewers and reasons for the conclusion. If the assessment identifies risk, determine and document appropriate risk-mitigation measures. Reassess when new evidence materially changes the picture. Preserve the history rather than simply deleting an alert or overwriting an earlier result.

Hypothetical example: A rubber plot flagged in Southeast Asia

An EU importer is assessing a shipment of natural rubber. A satellite monitoring tool flags a supplier’s plot in Southeast Asia for possible forest loss. A second dataset shows a different pattern, and the initial alert appears close to the plot boundary.

The importer does not immediately reject the plot, and it does not dismiss the alert. The team first validates the polygon and finds that a section of the submitted boundary may include adjacent land. It checks the geometry and compares the alert with imagery from multiple dates. The team then asks the supplier for plot-specific production history and dated supporting records. The evidence helps explain part of the discrepancy, but one period remains uncertain.

The importer records the original alert, the boundary issue, the datasets reviewed, the supplier’s response and the remaining evidence gap. The team seeks additional review before reaching a conclusion. If the evidence ultimately supports that the alert was not evidence of relevant non-compliant activity, the rationale and supporting documents are retained. If the uncertainty cannot be resolved, the business does not treat the plot as cleared merely because one source looks reassuring.

The lesson is simple: the defensibility of the decision comes from the quality and traceability of the investigation not from whether the first alert was red or green.

What to do when an alert is confirmed to be a false positive

• Record the reason the alert was considered a false positive and link the conclusion to supporting evidence.
• Correct plot geometry or underlying data when an error is confirmed; preserve the original version and change history.
• Request additional supplier information when needed and document how it was verified.
• Keep the original alert, review notes, data sources and investigation history rather than deleting the alert.
• Reassess the plot and document the final risk conclusion before relying on it in the relevant due diligence decision.

Common mistakes to avoid

• Automatically rejecting a plot based on a single alert without checking its context.
• Ignoring an alert because another dataset does not show the same result.
• Accepting a supplier explanation without verifying its relevance and supporting evidence.
• Correcting data while losing the original alert or investigation history.
• Treating a green software status as proof that all due diligence requirements have been met.

A sound process avoids both extremes: it neither treats every alert as conclusive proof of non-compliance nor assumes that a conflicting result makes the alert irrelevant.

How EUDR software can help—and what it cannot replace

Software can make the investigation more consistent and explainable when it connects plot data, satellite evidence, supplier information and decisions in one workflow. Useful capabilities include:

• Plot geolocation validation to identify geometry and boundary issues before the evidence is interpreted.
• Satellite monitoring and dataset comparison to help teams review alerts and the relevant historical context.
• Centralised evidence management to connect supplier documents, plot records, findings and mitigation actions.
• A shipment-specific audit trail showing the alert, investigation, supporting evidence, changes and rationale behind the conclusion.

These capabilities support the due diligence process; they do not replace the operator’s responsibility to assess the evidence, make the required decisions and apply appropriate risk mitigation. A risk score or automated status is an input to the assessment, not a substitute for it.

A checklist for compliance and sustainability teams

• Have we confirmed that the coordinates and polygon correspond to the correct production plot?
• Do we understand the source, date and limitations of the satellite alert?
• Have we reviewed relevant datasets and historical imagery where appropriate?
• Have we assessed the timeline against the 31 December 2020 cutoff and applicable EUDR criteria?
• Have we requested and evaluated plot-specific supplier evidence where needed?
• Are unresolved uncertainties clearly recorded and assigned for follow-up?
• Can we show the original alert, evidence reviewed, corrections, mitigation and reason for the conclusion?
• Can we trace the plot assessment to the relevant supplier, commodity and shipment?

How TraceX can support the process

TraceX EUDR Solutions helps businesses connect plot-level geolocation, satellite monitoring, supplier evidence and traceability records so that an alert can be investigated within a structured workflow. Centralised evidence and a shipment-specific audit trail can help teams retain the context behind a decision and make their assessment easier to review.

The objective is not simply to detect a possible issue. It is to help the business organise the evidence, investigate the signal, document the rationale and understand what still needs to be resolved. Technology can make this work more manageable, but the due diligence decision remains the responsibility of the relevant business.

Frequently asked questions