DPO Radio

A vendor risk lead onboarding new vendors at volume — twenty a quarter for a procurement-heavy organisation — spends a disproportionate share of the week on a low-value sorting task. They have to work out which uploaded file is the data processing agreement, which is the SOC 2 report, which is the ISO 27001 certificate, and which is the insurance policy. The work is necessary but routine, and routine work at scale is where automation pays off.
The vendor onboarding evidence collector workflow takes the vendor intake folder, classifies each uploaded file by purpose, and assembles the tier-driven evidence pack ready for vendor risk review. The vendor risk lead reviews the classification per file, accepts or overrides, and the platform creates the evidence chain for the vendor record.
The workflow runs against the vendor onboarding intake folder. Each uploaded file enters the classification queue.
Files are classified into four artefact types — data processing agreement, SOC 2 report, ISO 27001 certificate, and insurance policy — by matching the filename against an explicit rule set, most specific rule first. The rules are readable and fixed, so the same filename always classifies the same way and a misclassification is a rule to correct rather than a model to re-prompt. A fifth category, incident history, is surfaced as a finding rather than as a required artefact.
The vendor risk tier (low / medium / high) determines the required-artefact list. Missing artefacts are surfaced so the vendor onboarding outreach can request them before the assessment runs.
The vendor risk lead reviews per file, accepts the classification or overrides with the correct one. The evidence chain commits on accept.
Accepted classifications attach the evidence to the vendor record. The audit trail walks the chain from intake through classification and operator decision.
Standard workflow audit shape — proposed, accepted or rejected, evidence attached.



Classification is rule-based rather than inferred, so it is inspectable and repeatable: the same filename always lands in the same artefact type. The vendor risk lead overrides any classification before the evidence chain commits.

The workflow does not attach evidence autonomously. The accept-or-override decision is recorded in the audit trail.

The audit lineage walks every vendor evidence chain back through the originating intake and the workflow run.
| Framework | How Vendor Evidence Collection Supports It |
|---|---|
| EU GDPR | Drafts the vendor evidence pack against GDPR Article 28 processor obligations. |
| ISO 27001 | Drafts the vendor evidence pack against ISO 27001's supplier-relationship controls. |
| SOC 2 | Drafts the vendor evidence pack against SOC 2 vendor-management criteria. |

Use the collector for onboarding evidence. The vendor risk and questionnaire reviews examine what the team can support from those records. See Third-Party Workflows.
Ready to see a 12-file vendor intake classified into a structured evidence pack in three minutes? Request a personalised demo.


Run the vendor evidence collector against your active vendor onboarding pipeline for one quarter.

Talk to our team about how the workflow fits your vendor onboarding cadence.
Four: the data processing agreement, the SOC 2 report, the ISO 27001 certificate, and the insurance policy. Classification is by filename against an explicit ordered rule set rather than by inference. Incident history is tracked as a fifth category but is reported as a finding, not as a missing artefact, because it is not something a vendor is expected to supply on request.
The vendor risk tier (low / medium / high) determines the required-artefact list. Missing artefacts surface for outreach before the formal assessment runs.
No. The vendor risk lead accepts each classification before the evidence chain commits.
Yes. The vendor risk lead overrides any per-file classification before commit. The override is recorded in the audit trail.
Yes. Each run sends requests to the AI provider your organisation has configured, and your provider bills your organisation for them directly. A run is never refused because a Forseti allowance ran out, and the Usage page reports what each feature consumed.