Skip to main content

Quick path

1

Open the outstanding task

In the compliance dashboard, select Resolve for the affected article. Choose To request, Waiting on supplier or To review for its current state, then open the task card.
2

Inspect the cause

Open the flagged evidence in the document viewer or the affected plot on the map. Check which articles and findings the task covers.
3

Resolve and review the result

Submit suitable evidence or a reasoned geo explanation, link an existing certificate, or ask the supplier. A request alone does not resolve the risk: review the response afterwards under To review.

Overview

When the risk assessment detects geo risks (deforestation, degradation) or legal risks for an article, these must be mitigated. For this, the compliance gaps view is available to you — a central tool with which you can submit evidence, link existing certificates, or request documents directly from the supplier.

The Compliance Gaps View

For an open geo or legal risk, click “Resolve”. The list is ordered by area, category and country, and cannot be re-sorted. What you steer are the three tabs — they filter by who owes what: Each tab carries its count in the title. It counts everything under that tab — search and paging can show fewer.
On the compliance dashboard a progress line sits under each supplier name: “… of … articles ready” and, where something is missing, “missing: …” with the areas Geodata, Documents, Questionnaire. An article counts as ready as soon as it has no blocking point left — a mere warning does not hold it back.
Below the counters, each card represents one task, not every technical finding. The same problem is grouped across all affected articles. For example, “Missing geolocation data” appears once with “23 affected articles” instead of appearing 23 times. Proposed document uses are grouped by the actual document, and sent requests are grouped by supplier request. The card keeps the number of affected articles separate from the number of technical findings. Open the task to search its affected articles. At most 20 articles are shown on each page.

Working Through a Problem

1

Open details

Open the task card. When several articles are affected, you first see a searchable article list. Open an individual finding only when you want to inspect or resolve it yourself.
2

Inspect the source

Use the direct link to open the flagged document in the document viewer or the affected plot on the map. Review feedback and technical details remain available in a separate section so the main task stays clear.
3

Choose the resolution path

Under Recommended fix, resolve the problem yourself — for example with new evidence, an existing certificate, or a reasoned geo explanation — or ask the supplier. A grouped request states its exact scope, for example “Request from supplier for 23 articles”. The number of technical findings is never presented as the number of requests.
4

Review the result

After a supplier response, the problem changes to “Review response”. The submitted document opens in the full document viewer — with the same review capabilities as on the documents page. Read the response and accept it, or reject it with a clear explanation.
A sent request is not a resolved risk. The overview holds it under “Waiting on supplier” until new information arrives and has been reviewed. On the point itself it says: “Already asked for from the supplier; no answer has arrived yet.”

Requesting the Right Correction

  • Document missing: Name the required legal category and ask for the available evidence.
  • Document rejected: The review feedback is passed to the supplier. Ask for a corrected or more complete file.
  • Document expired: Ask for a renewed, valid version.
  • Plot data incorrect: Link the affected plots and ask for corrections to geometry, country of production, commodity producer, or production period.
  • Questionnaire incomplete: Request only the affected information.
You can send several open, requestable problems to the supplier together. Review each returned problem individually so the decision and its rationale remain traceable. How a request is sent, answered by the supplier, and tracked is described in Supplier Requests.

When the supplier says the document does not exist

For a legal requirement the supplier can give a statement instead of a document — with a mandatory reason. In the compliance gaps view it then appears above the requirement as its own card: “Supplier states no document exists (…)”, with their wording unchanged below it. You have two decisions:
Accepting is not fulfilment. The app says so itself: “Accepting records that you have reviewed this statement. It does not satisfy the requirement — the category stays open.” The compliance status does not change: the requirement stays exactly as blocking as before, and the point stays in the list. What you gain is a documented reason for the gap — not its closure. The article therefore also stays blocked for the automatic DDS creation.
A rejected statement disappears from the card — it has been answered. In their portal the supplier sees your note and can supply the document.

When evidence falls away

A settled risk mitigation hangs on its piece of evidence. If that falls away, the mitigation is re-opened automatically rather than quietly kept.

What re-opens a mitigation

The causes you can recognise yourself: The plot concerned then carries the sentence “Risk mitigation required. The supporting evidence was removed and this plot needs review again.”, and the risk level is recalculated.
Changing a plot’s geometry is something else — and more drastic. Change a plot’s outline and its mitigations are not re-opened but deleted, together with the plot’s entire analysis result. The plot goes back to Pending, analysis restarts immediately, and mitigations are built again from scratch. The audit log records this as “Plot geometry updated”.

What the app then does by itself

If another accepted, still-valid certificate covers the same plot, the app can re-fill the re-opened mitigation itself and settle it again — it then carries the marker Resolved automatically. That does not happen at the moment the old evidence falls away. It happens as soon as you accept a suitable certificate’s category coverage, accept an expired document despite its expiry, or restore a deleted document — and otherwise only the next time that plot or a certificate is analysed. Until then — and permanently, if no suitable certificate is left — the mitigation reads Evidence missing: “No evidence is attached to this mitigation — the document was removed, or none was uploaded. Nothing is under review.” Closing it again is then your decision. Where the check is not clear-cut, the mitigation reads Your confirmation is required or More plot-specific evidence is required instead.

How you notice

No notification tells you which mitigation is open again. There is no “mitigation re-opened” message, neither in the app nor by email.What you see are the consequences, and those only under conditions:
  • If an article tips to non-compliant as a result — from whatever status — the notification “Article … is non-compliant” appears. If the article was already non-compliant, nothing arrives; for articles from upstream tiers nothing arrives either.
  • If you rejected an evidence assignment, the notification “Evidence document rejected for …” (with the article’s name) appears as well. Deleting a document produces neither, and rejecting a risk mitigation produces no notification either — not even when it rejects the document with it.
Both sit in the app’s notification centre. By default they are not emailed; anyone who switches email on for them receives them in the daily digest. Neither names the plot or the mitigation.
So after deleting or rejecting any piece of evidence, check for yourself which mitigations were resting on it.

What the audit log shows

Your own act is there: “Evidence deleted”, “Evidence decision” or “Bulk evidence decision”. The mitigations that fell away with it are not separate entries — they count as the documented consequence of that row. “Plot risk changed” is written by the application alone — after an analysis, after the expiry check, or after a re-assessment. “Risk resolution updated”, by contrast, marks every change to a mitigation: your own accept or reject carries that entry just as the automatic assessment does. No name on the row means the application wrote it; your name means it was your click. Neither carries a row for the re-opening itself.

The exception for expired documents

Confirming the “Valid until” field in the document review does not exempt a document from the expiry check. It only corrects the date.The exception comes from a different, explicit act: “Accept Despite Expiry” on the expired document, with a mandatory reason. Only then does the daily check leave that document alone. The acceptance is recorded in the audit log as “Expired document accepted” together with your reason, and it only permits the document to be reviewed further — it accepts no suggested category; the categories already accepted are re-assessed, though, and matching mitigations can be closed again as a result.

Reviewing Documents in Bulk (Review Queue)

When many submitted documents pile up, you do not have to open each one through the task cards: the review queue on the documents page lists all open document reviews company-wide as a queue. There you can decide several documents at once:
  • Bulk accept is only possible for documents without blocking findings — a document with an open finding still requires an individual decision.
  • Bulk reject uses a shared reason, which is forwarded to the supplier.

What the Decision on a Piece of Evidence Says

When you attach evidence to a risk flag, the card afterwards carries one reasoned decision per document. There are exactly three: Underneath sits one sentence naming the reason — for example “The document’s coordinates don’t cover this plot”, “The document concerns a different country than this plot”, “The document could not be read”, or “The document does not address this risk signal”. Each of those sentences also names the next step. The same sentence appears in the document viewer, so the two places can never say different things.

The Operator Confirmation

When a piece of evidence sits at “Your confirmation is needed”, the button “Confirm and resolve” appears. The dialog “Confirm the negligible-risk conclusion?” says what you take on:
“You take responsibility for this conclusion on the attached evidence. It is recorded in the audit trail, and the document then counts as accepted for this risk on every plot its coordinates cover — except plots with a confirmed loss, which you confirm one by one.”
Unlike a plain accept on the row, this confirmation applies to every plot the same file covers. A management plan covering 40 areas is confirmed once instead of forty times. Plots with a confirmed loss stay excluded — those are still asked one by one.
Where you can read this back. There is no separate decision overview. You recognise a carried-over earlier decision by its reason sentence — “You already accepted this document for this risk. It applies to every plot its coordinates cover.” If a stored decision automatically cleared a plot you never saw, that appears in the audit log as “Operator ruling applied to risk resolution”. The full decision history is included in the company-wide data export.

Two Rules That Never Pass Automatically

  • Self-issued statements. If the holder issued the document about its own land, it is never accepted automatically: “Self-issued statements are never accepted automatically — please review and confirm it yourself.”
  • Coordinates that provably exclude the plot. If a document names coordinates that do not contain the plot, it lands with you instead of resolving automatically. A document with no coordinates — a general company certificate, say — is not affected by this.

When No Verdict Was Produced

Two states are not a rejection but a sign of an interrupted run:
  • Validation failed — “The automatic check for this mitigation did not return a result. Submit the mitigation again to retry.” The resubmit action sits right there.
  • Evidence missing — “No evidence is attached to this mitigation — the document was removed, or none was uploaded. Nothing is under review. Upload evidence to resolve this risk.”
If you resubmit a mitigation while the first check is still running, the superseded run is discarded — it does not stamp a failure verdict on the row.

When Only the Supplier Can Help

When a plot flag sits at “More plot-specific evidence is needed”, the task can be sent as a targeted evidence request via the “Ask supplier” tab. A request that is already running is shown beside the editor, so you can still accept or reject an incoming answer.

FLEGT Fast Track

For wood products from FLEGT VPA countries, there is a fast track: uploading a valid FLEGT license automatically fulfills the legal compliance requirements for all categories. This eliminates the need to mitigate each legal category individually.
Only from a country with an operational FLEGT licensing scheme. If a document is filed as a FLEGT licence but the declared country of production runs no operational FLEGT scheme — currently Indonesia alone — it is rejected. The finding reads “FLEGT licence from a country without an operational FLEGT scheme”.The finding follows from Art. 10 EUDR and blocks. You can accept the document only by entering a written reason in the accept dialog; it is recorded in the audit trail. A confirmation you already stored on a risk mitigation does not lift the finding. If the document was merely mis-filed — it is in fact a different permit — correct the document type and re-analyze. For every other country the regular route applies: the questionnaire and the individual legal categories.

Missing or Rejected Evidence

A rejected document must not be silently treated as resolved. Read the feedback, open the original document, and then request the appropriate correction or replacement evidence.