Skip to main content

Overview

In Polygon One, requests to suppliers are created directly from risk mitigation: every open task in the compliance gaps view that the supplier has to solve can be sent to them as a request. A request always names concrete targets — the missing, rejected, or expired document, the production plots to correct, the affected questionnaire answers, or the required certificate — instead of a whole data area.
There is no longer a separate dialog where you tick areas such as “geodata” or “questionnaire” for updating. The path always leads through the concrete gap: the request automatically carries what is missing, why it was flagged, and which articles are affected.

Creating a Request

1

Open the compliance gaps view

For an article or supplier with an open risk, click “Mitigate”. The compliance gaps view shows every open task as a card — identical problems are bundled across all affected articles.
2

Request the task

Open the task and choose the request action, e.g. “Request from supplier for 23 articles” or “Request evidence”. The button always states the exact scope. Several open, requestable problems for the same supplier can be sent together in one request.
3

Add a message (optional)

Add a personal message if needed. The factual context — affected documents, plots, review notes, and rejection reasons — is attached to the request automatically; you do not have to retype it.
4

Send

Choose the delivery method:
  • Send request — the supplier is notified automatically by email.
  • Copy & send yourself — the message and link are copied to your clipboard so you can send them through your own channel.

What the Supplier Sees

The supplier opens their familiar invite link and sees the request as a task: one card per target with the reason it was flagged, the affected document or plot, and the matching action (replace file, upload, correct a plot or an answer). They work through only what was requested and send back one combined response — without going through the entire onboarding again. The step-by-step walkthrough from the supplier’s perspective is in the supplier guide.

Tracking and Review

The state of each request is visible directly in the compliance gaps view: In addition, notifications inform you about sent, viewed, ready for review, and completed — see the notification center. A request that is still open can be withdrawn from its detail view.
A sent request does not count as a mitigated risk. It stays “Waiting for supplier” until the response has arrived and you have reviewed it. If you reject a response, your review notes are forwarded to the supplier with the next request.
Requests are most precise after the risk assessment: by then it is clear which legal categories are open and which plots a document has to cover.