Verdana Compliance · third-party risk segmentation

Third-party risk segmentation with rule-based risk profiles

Verdana's risk profiles and segmentation assign each third party an analysis profile through rules, based on what it declared and what the verifications returned. Your compliance team stops spreading its time evenly and spends it on the third parties where the risk is concentrated, with explicit criteria you can show an auditor.

Each risk factor of a third party weighs on the profile it is assigned.

What risk-based segmentation saves your team

Review hours spent where they matter, criteria you can defend, and a process that adjusts on its own.

  • Effort goes where the risk is

    Low-risk third parties follow a short path and critical ones move to enhanced due diligence, so your team stops reviewing everyone at the same depth.

  • Criteria you can defend

    Profiles are built on objective factors and applied the same way to every third party, so each assignment traces back to an explicit rule rather than a judgment call.

  • The process adjusts on its own

    If a factor changes later on, the third party is reclassified and its document package, due diligence level and revalidation adjust with it.

What third-party segmentation looks like

An abstraction of a third party's risk factors, its assigned profile, and the questionnaire it answers.

Third-party record: risk factors, the assigned profile, and the workflow that profile sets.Supplier portal: its answers start defining its profile.

How third-party risk segmentation works in Verdana

From the criteria your organization sets to the process each third party follows.

  1. Profiles defined by rules

    Your organization defines analysis profiles on objective factors—sector, jurisdiction, amount, type of service, dealings with government agencies, access to facilities or data—through rules, with no development work.

    What is third-party segmentation →
  2. Onboarding questionnaire

    The third party completes the questionnaire for its type, and its answers start defining which controls apply.

    Forms →
  3. Verifications

    The results of screening against lists and sources are added to what the third party declared.

    Due diligence →
  4. Profile assignment

    Based on what was declared and verified, the third party gets its profile: document package, due diligence level, approval workflow and revalidation frequency.

    What is enhanced due diligence →
  5. Reclassification

    If any factor changes later on, the third party is reclassified and the process adjusts.

    What is continuous third-party monitoring →

Risk profiles and segmentation in depth

The process in detail, and why it is designed this way.

Applying the same level of scrutiny to every third party produces two failures at once: unnecessary friction for the irrelevant ones and superficial review of the critical ones. The solution is to segment by objective factors —sector, jurisdiction, amount, type of service, dealings with government agencies, access to facilities or data, prior history— and define for each segment which documentation, which verifications and what review frequency apply.

In Verdana, those segments are defined as analysis profiles through rules, with no development work. When a third party registers, Verdana evaluates what it declared and what the verifications returned, and assigns it to the matching profile: that profile determines the document package requested, the level of due diligence, the approval workflow and how often the third party is revalidated. If any factor changes later on, the third party is reclassified and the process adjusts.

The practical effect is on how effort is allocated. The team stops splitting its time evenly across three hundred suppliers and focuses it on the ones where the risk is concentrated, with explicit, defensible criteria instead of discretionary ones.

A rule, not a judgment callInput: What the third party declared and what the verifications returned. Rule: Objective factors, Sector, jurisdiction, amount, service, access to facilities or data. Low-risk segment: Limited document package and less frequent revalidation. Critical segment: More documentation, more verifications and more frequent review. A factor changes: The third party is reclassified and the process adjusts on its own. Effort goes where the risk is: explicit, defensible criteria instead of discretion.A RULE, NOT A JUDGMENT CALLInputWhat the third partydeclared and what theverifications returnedObjective factorsSector, jurisdiction, amount, service,access to facilities or dataLow-risk segmentLimited document packageand less frequent revalidation.Critical segmentMore documentation, more verificationsand more frequent review.A factor changesThe third party is reclassifiedand the process adjusts on its own.Effort goes where the risk isexplicit, defensible criteria instead of discretion.
Applying the same requirements to everyone creates friction for the irrelevant and superficial review of the critical. Segmentation avoids both.

Frequently asked questions

What teams usually ask when they design a third-party risk management program.

How do you segment suppliers by risk level?

By grouping them on objective factors—sector, jurisdiction, amount, type of service, dealings with government agencies, access to facilities or data, prior history—and defining for each segment which documents, which verifications and what review frequency apply.

What is the difference between simplified, standard and enhanced due diligence?

They are levels of depth assigned according to a third party's risk profile. Enhanced due diligence adds verifications not required of the rest and is triggered by factors such as jurisdiction, dealings with government agencies, opaque ownership or adverse history.

How often should you re-review a supplier based on risk?

Review frequency should follow the risk classification: higher-risk third parties are revalidated more often than low-risk ones. A flat annual review of the whole supplier base comes too late for the critical ones and is wasted effort on the rest.

What happens when an approved supplier's risk changes?

In Verdana, if any factor changes, the third party is reclassified and its process adjusts: document package, due diligence level, approval workflow and revalidation frequency become those of its new profile.

Do you need developers to set up third-party risk profiles?

No. In Verdana, analysis profiles are defined through rules, with no development work, using the criteria your organization sets.

Related concepts