> ## Documentation Index > Fetch the complete documentation index at: https://help.polygon-one.com/llms.txt > Use this file to discover all available pages before exploring further. # EUDR Status Glossary > What article, supplier and compliance statuses mean — and what to do next ## Overview Distinguish the assessment from the next task: * **EUDR-relevant** — does this article fall within the regulation's scope? * **Compliance** — how does Polygon One assess the available data for this article? * **Task / request history** — is information missing, are you waiting for the supplier, or is a decision yours? An article can be EUDR-relevant and still have the compliance status **Data missing**. For **Not EUDR-relevant**, also check whether a manual classification is still open. Suppliers use the same **compliance** values as a summary of their articles. Request progress and responsibility are separate: requested does not mean answered or compliant. > [!NOTE] > > Plot and DDS statuses have their own lists of values. See [Risk Assessment](https://help.polygon-one.com/en/eudr/datensammlung/risikoanalyse.md#area-status-after-analysis) and [Incoming DDS](https://help.polygon-one.com/en/eudr/dds-bestellungen/dds-eingehend.md#dds-status). ## EUDR relevance (the article's EUDR-relevant column) Relevance is derived automatically from the **HS code** when an article is created — see [EUDR Relevance Check](https://help.polygon-one.com/en/eudr/eudr-analyse.md). | Display | Meaning | What to do | | - | - | - | | **Yes** | The article's HS code falls within the EUDR's scope. | Check the origin route and evidence; create your own DDS only where your role and transaction require one. | | **No** | The stored relevance value is negative; a manual check can still be open. | Without an open check, no data collection for this article. With an open check, resolve classification first. | | **Needs Manual Check** | Classification is unresolved, for example for an ex-heading, an overly broad code or a missing HS code. | Check the code and product. For composite articles, clarify this through the **material composition** — see [Article Import or Bill of Materials?](https://help.polygon-one.com/en/eudr/datenhaltung/import-oder-stueckliste.md). | The relevance filters distinguish **EUDR Relevant**, **Not EUDR Relevant** and **Needs Manual Check**. A supplier response to a material question can also be waiting for review. An open manual check can coexist with either a positive or a negative relevance value. > [!WARNING] > > **Not EUDR-relevant is not an approval.** A missing HS code creates an open manual check. An incorrect but apparently unambiguous code can also produce a wrong result. Check the code, material and open classification together. ## Compliance statuses (the Compliance column for articles and suppliers) These are the values used for **articles and suppliers**. The plot list has a separate, longer list that also includes some of these values, such as **Not EUDR-relevant** and **Not required (before cutoff)**; see the note below. On articles and suppliers, the label says **more** than the underlying value: instead of a generic “Unknown”, it names **what** is missing; instead of a generic “Non-compliant”, it tells you when evidence has simply never been submitted. | Display | Meaning | What to do | | - | - | - | | **Compliant** | The current platform assessment is complete; if manually set, its basis needs separate review. | Check any required DDS, quantities and submission data separately. The status alone is not a TRACES submission. | | **Non-compliant** | Risk or compliance issues were found that must be resolved before the status can be compliant. | Resolve them through the compliance gaps view — see [Risk Mitigation](https://help.polygon-one.com/en/eudr/datensammlung/risiko-behebung.md). | | **Evidence outstanding** | The same assessment as **Non-compliant**, with extra information: **no document has ever been submitted** for the flagged legal categories. Evidence has not failed; it is missing. | Request evidence from the supplier or upload it yourself. | | **Invalid** | Geodata was provided but assessed as invalid, for example plots overlapping water or built-up areas. | Correct the affected plots before they can be assessed. | | **Pending review** | Documents, data or evidence have been submitted and await review. | Accept or reject the response or evidence. | | **Data missing** | Compliance cannot yet be assessed because required information is missing. | Add the data or request it from the supplier. | | **Data missing: …** | The same, naming the areas: **Geodata**, **Documents**, **Questionnaire**, sometimes several separated by commas. | Complete those specific areas. | | **Questionnaire missing: …** | A complete questionnaire is missing for the named production countries. | Complete or request the questionnaire for those countries. | | **Assessment pending** | No required data is missing; pending reviews or analyses still prevent a result. | Check open decisions and wait for running analyses. If an error appears, open the affected analysis. | | **Not EUDR-relevant** | This entry is outside the EUDR's scope and needs no compliance assessment. | Nothing. | | **Not required (before cutoff)** | Polygon One sets this platform status when every plot's production period ends before 1 January 2021. | Verify the production periods and legal applicability. Polygon One treats this status like Compliant in automated processing. | > [!NOTE] > > The label's help explains its state. **Data missing**, **Data missing: …** and **Assessment pending** have different explanations. For **Non-compliant**, the hint can distinguish missing evidence, a legal finding and geo risk. > > **Filters are broader than the displayed labels.** Article and supplier filters offer **Compliant**, **Non-compliant**, **Invalid**, **Pending review**, **Data missing**, **Not required (before cutoff)** and **Not EUDR-relevant**. Finer variants — **Evidence outstanding**, **Data missing: …**, **Questionnaire missing: …** and **Assessment pending** — appear only on the label. Find an article with **Evidence outstanding** through the **Non-compliant** filter. ### The most common case: Data missing **Data missing** is the starting state, not an error: there is simply not enough data yet. Typical causes: * No **production plots** have been recorded for the article. * The plots' **production periods** are missing (Art. 9(1)(d) EUDR). * The legal compliance **questionnaire** is incomplete. Where the view knows the open gaps, the label names the areas: **Data missing: Geodata**, **Data missing: Questionnaire**, **Data missing: Geodata, Documents**, and so on. If nothing remains to be supplied but no final assessment exists, it can show **Assessment pending**. Check pending reviews and analyses in that case. A request the supplier has not answered still counts as missing. Other lists show a more general value from stored results. Depending on the available details, the label can name **Geodata**, **Questionnaire** or the specific production countries missing a questionnaire. Open the gaps view for the cause; a general Data missing label does not mean you need to upload existing plots again. > [!NOTE] > > The **plot list** uses its own analysis and risk statuses, including **Pending**, **Analysing**, **Analysis failed**, **Exempt**, **Skipped** and **Unknown**. These are distinct from the article status. For a pending or failed result, open the plot and its messages — see [Plots](https://help.polygon-one.com/en/eudr/optional/plots.md). ### Coverage by an upstream DDS **Covered by upstream DDS** is a detail state of the geo and legal pillars, not a separate overall status in the article or supplier Compliance column. When both pillars are satisfied this way, the overall status is **Compliant**. This coverage arises **only** when the article is covered exclusively by upstream DDS references. It says nothing about other evidence obligations. If the supplier **also** provides plots, this coverage does not apply: the article is assessed normally, and the legal assessment uses the **countries of the provided plots**. A different declared production country no longer contributes. For an origin declared exclusively as **post-consumer recycled material**, with no plots or reference, Polygon One can set **Not EUDR-relevant**. Check the material declaration and its coverage: a recycled fraction does not automatically exempt other virgin materials in the product. If both recycled material and a DDS reference are declared, the reference takes precedence in this platform logic. ### Not required (before cutoff) Polygon One sets this status when the production period ends before 1 January 2021 for **every** plot of an article. Automated processing treats the status like **Compliant**. > [!WARNING] > > **31 December 2020** is the EUDR's deforestation and forest-degradation cutoff. It is **not a general exemption from the Regulation's scope**. Whether a particular product is covered also depends on the product, your role, and the applicable application and transitional rules. Read the Polygon One status as a platform-logic result, not as a standalone legal clearance. Source: [European Commission — Due diligence](https://green-forum.ec.europa.eu/nature-and-biodiversity/deforestation-regulation-implementation/understand-due-diligence_en). ### How the overall status is formed Polygon One assesses two pillars separately — **geo compliance** (satellite analysis of plots) and **legal compliance** (questionnaire and documents) — then combines them: **1. Both pillars must be satisfied** Both Geo **and** Legal must be assessed as satisfied. The platform includes Compliant, Not required (before cutoff) and Covered by upstream DDS in this group. If both pillars are exclusively Not required (before cutoff), the overall status keeps that label. This summary does not replace checking your legal role or any required DDS. **2. Otherwise, the worst status takes precedence** When results are aggregated (several plots into an article, or several articles into a supplier), the worse value takes precedence in this order: **Non-compliant** → **Invalid** → **Pending review** → **Data missing** → **Compliant** → **Not required (before cutoff)** → **Not EUDR-relevant** > [!NOTE] > > One incomplete plot can therefore put an otherwise clear article into **Data missing**, and one unresolved finding can make the entire supplier **Non-compliant**. Open the entry to see which item determines its status. ### Manually Set Assessments A manually set overall status can differ from the underlying geo and legal results. The report discloses that manual setting. Check the report, assessment history and evidence instead of automatically interpreting a green value as the result of passed automatic checks. ## Tasks and Request Progress | Display / situation | Next step | | - | - | | **Request** | Request missing information or add it yourself. | | **Waiting on supplier** | Check history and delivery. Opened or in progress is not a completed response. | | **To review / Review** | Open the response and analysis, accept adequately supported information or request a correction. | | **History** | Check previous requests and responses before asking again. | A saved draft is not yet a submitted response. An accepted response closes that particular task; other articles, categories or plots may remain open. **Compliant** describes the current article assessment, while **Validated** describes a DDS status. See the [recommended workflow](https://help.polygon-one.com/en/eudr/prozess.md) for the path from saving to the returned response. ## Related pages > **[EUDR Relevance Check](https://help.polygon-one.com/en/eudr/eudr-analyse.md)** > > How EUDR relevance is derived from the HS code. > **[Risk Assessment](https://help.polygon-one.com/en/eudr/datensammlung/risikoanalyse.md)** > > Plot statuses, geo risk indicators and legal risk categories. > **[Findings Catalogue](https://help.polygon-one.com/en/eudr/datensammlung/befund-katalog.md)** > > Each compliance finding: meaning, severity and resolution. > **[What Is Missing for This Supplier?](https://help.polygon-one.com/en/eudr/datensammlung/lieferanten-luecken.md)** > > Supplier gap labels and what the supplier needs to provide. > **[Incoming DDS](https://help.polygon-one.com/en/eudr/dds-bestellungen/dds-eingehend.md)** > > The separate list of due diligence statement statuses. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.