👋
How can we help today?
Search for articles...
Setting item importance scores
Importance determines how much each item contributes to the compliance score shown in the comparison. You set it while editing the specification. By default, all items have equal importance.
Changing an item's importance
Each item row in the specification has an importance field next to it. Click the field to edit the value. Compliance scores in the comparison update automatically — you don't need to rerun verification.
Choosing importance levels
Start by identifying the few items that actually drive the decision — usually compliance clauses, must-have integrations, or critical performance thresholds. Give these a higher importance score.
Leave "nice to have" items at the default. Making every item critical dilutes the score and makes it harder to separate options.
Category importance
The same logic applies at the category level. When items are grouped into categories on the specification, a category's importance determines the combined weight of all items inside it. Raising importance on Security makes every security item more dominant in the final compliance score.
Hard requirements
If an item is a strict must-have — a product or service provider that fails it cannot win — higher importance is still useful, but the compliance score alone may not tell the full story. Check each option manually against your hard requirements.