Automatic Requirement Category Assignment

Overview

Automatic Requirement Category Assignment lets administrators define rules that determine which requirement category is applied to a vendor's compliance assignment, based on values entered in selected fields. When enabled, users no longer manually select a requirement category during vendor setup — they fill in the underlying field values, and the system applies the correct category automatically.

This article explains how to configure the logic, what end users will experience, and how to enable the feature.

Who can use this feature

Automatic Requirement Category Assignment is currently available only to Software + Services clients. To enable it on your account, contact your Customer Success Manager. They will configure the logic with you, train your team, and toggle the feature on once setup is complete.

When to use this feature

Use Automatic Requirement Category Assignment if any of the following apply:

• Your requirement categories map to vendor attributes that can be captured in a field (e.g., trade, service type, vendor type, region, portfolio, location)
• You have multiple users setting up vendors and want to enforce consistent category assignments
• Your rules for which category applies are complex enough that users may forget or misapply them
• You want to remove the requirement category dropdown from the vendor setup flow

If your category selection is straightforward and your users apply it consistently, manual assignment may remain the simpler option.

How to configure the logic

Step 1: Choose the field that drives the logic

When configuring a new rule, select a field from your BCS account to use as the criteria. Common examples include service type, vendor type, region, or portfolio.

If the field you want to use does not yet exist, create it first under Settings before returning to this configuration screen.

Step 2: Create branches for each value

For the field you selected, create a branch for each grouping of values that should map to the same requirement category. For example, using a service type field, you might create:

• A High Risk branch containing your highest-risk trades
• A Medium Risk branch containing your medium-risk trades
• A Low Risk branch containing your lowest-risk trades

Each branch can be renamed for clarity, and you assign the field values that belong to it.

Step 3: Assign a requirement category to each branch

For every branch you create, select the requirement category that should apply when a vendor's field value falls into that branch.

Step 4: (Optional) Set a fallback requirement category

You can designate a fallback requirement category to handle vendors whose field values don't match any of the branches you've defined. This ensures every vendor receives a requirement category, even if their attributes fall outside your configured rules.

Step 5: (Optional) Add additional logic or sub-branches

You can add a second logic layer based on a different field — for example, layering vendor type on top of service type. You can also add sub-branches off any existing branch to support more granular rules.

There is no enforced limit on how granular your logic can be, but we recommend keeping your rule set as simple as possible while still meeting your program's needs.

What end users will experience

Once your logic is active:

• The requirement category dropdown will no longer appear during vendor setup
• Users will instead be prompted to fill in values for the fields you configured as logic criteria (e.g., service type, vendor type)
• After the user enters those values, the system automatically assigns the corresponding requirement category to the vendor's compliance assignment

This means users no longer need to know your requirement category rules — they only need to know the attributes of the vendor they are setting up.

Related settings

• Custom fields: Create or edit fields under Settings before referencing them in your logic
• Requirement categories: Existing requirement categories will appear as selectable options when building branches; create or edit them in the standard Requirement Categories settings area

Need help?

To enable Automatic Requirement Category Assignment, configure your logic, or train your team on the new workflow, contact your Customer Success Manager.