> ## 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.

# Recommended Workflow

> Our recommended path to EUDR compliance — compact, in the right order

## The Path to EUDR Compliance

This page summarizes the entire process in one place — in the order that has proven itself in practice. Each step builds on the previous one; you'll find the details in the linked chapters.

<Tip>
  You don't need to memorize this order: after login, the [EUDR Cockpit](/en/eudr/cockpit) always shows you the next sensible step as the **main action**. This page explains *why* the steps make sense in this order.
</Tip>

The most important practical tip up front: **collecting data from your suppliers is the most time-consuming part of the process** — responses typically take days to weeks. Handle everything within your own control (master data, your own evidence, TRACES access) quickly, send supplier invitations as early as possible, and let the automatic reminders do the follow-up.

## The Six Steps

<Steps>
  <Step title="Step 1: Initial Setup" icon="rocket">
    Set up your [company account](/en/eudr/onboarding/firmenaccount) and store your [TRACES credentials](/en/eudr/onboarding/traces) — without them, no DDS submission is possible at the end, and obtaining them from the EU can take time.

    Take care of email deliverability now, not once suppliers fail to respond:

    * Forward the [IT whitelist](/en/eudr/onboarding/it-whitelist) to your IT department.
    * Optional but very effective: send supplier emails from your [own sending domain](/en/eudr/versanddomain) — emails from your own domain are far more likely to reach corporate mailboxes.
  </Step>

  <Step title="Step 2: Import Master Data" icon="database">
    Import [suppliers](/en/eudr/datenhaltung/lieferanten) and [articles](/en/eudr/datenhaltung/artikel) via CSV import — bulk import instead of manual entry. Perfection is not required here: the platform will point out missing information in the following steps.
  </Step>

  <Step title="Step 3: EUDR Relevance Check" icon="magnifying-glass-chart">
    The [relevance check](/en/eudr/eudr-analyse) runs automatically based on your articles' HS codes and determines which articles are EUDR-relevant. Review the result and correct classifications manually where needed — only relevant articles enter data collection, everything else stays out of scope.
  </Step>

  <Step title="Step 4: Data Collection (Art. 9 EUDR)" icon="folder-open">
    For every relevant article you need geolocation data (plots) and evidence. Two paths you can use in parallel:

    * **Upload yourself** whatever you already have: [evidence and documents](/en/eudr/datensammlung/evidence-upload) as well as plots — the import [automatically validates](/en/eudr/datensammlung/parzellenimport-pruefung) the geodata.
    * **Invite suppliers** for everything that's missing: invite all affected suppliers in one go via [supplier onboarding](/en/eudr/datensammlung/supplier-onboarding) and enable automatic reminders in the [settings](/en/eudr/einstellungen).

    <Info>
      Inviting early pays off twice: while your suppliers respond, you can keep working on the remaining steps undisturbed.
    </Info>
  </Step>

  <Step title="Step 5: Risk Assessment (Art. 10 EUDR)" icon="chart-line">
    The [risk assessment](/en/eudr/datensammlung/risikoanalyse) runs automatically as data arrives — satellite imagery analysis for deforestation risks and document analysis for legality risks. Your job is [resolving identified risks](/en/eudr/datensammlung/risiko-behebung): review risks, follow up with suppliers, document decisions. [Reports](/en/eudr/datensammlung/berichte) preserve the outcome for your documentation obligations.

    For origins in **low-risk** countries, simplified due diligence applies (Art. 13) — you can adjust the analysis for those origins in the [settings](/en/eudr/einstellungen).
  </Step>

  <Step title="Step 6: DDS & Orders (Art. 3 EUDR)" icon="file-signature">
    Create or import [orders](/en/eudr/dds-bestellungen/import-erstellung), generate [due diligence statements](/en/eudr/dds-bestellungen/uebersicht) (DDS) from them, and submit them directly via the TRACES integration. For day-to-day operations, the [automations](/en/eudr/einstellungen) take over DDS assignment and creation.
  </Step>
</Steps>

## Afterwards: Ongoing Operations

Once the process is set up, EUDR compliance becomes routine:

* **New articles and suppliers** automatically follow the same path — relevance check, data collection, analysis.
* **[Supplier requests](/en/eudr/datensammlung/update-anfragen)** ask for corrections and missing evidence exactly where [risk mitigation](/en/eudr/datensammlung/risiko-behebung) finds a gap.
* **[Notifications](/en/eudr/optional/benachrichtigungen)** alert you whenever something needs your attention — e.g. new supplier responses or identified risks.
* The **[Cockpit](/en/eudr/cockpit)** remains your starting point: progress, bottlenecks, and the next sensible action.

<Card title="Questions about the process?" icon="envelope" href="mailto:help@polygon-one.eu">
  Our team is happy to guide you through the setup personally.
</Card>