Step 1: Weight your domains
The Risk Domains tab lists each domain with its Weight, its share of the roll-up, and its Risk Group (its reviewers). A domain with no weight reads Not weighted and is left out of the weighted roll-up. Click Edit risk domains to change them on the risk domains page.- Leave every weight empty to keep the questionnaire’s flat score. Weighting turns on only when at least one active domain has a weight.
- Weights are relative. They do not need to add up to 100, because the score is normalized by the weights of the domains that scored.
- A questionnaire section must name a risk domain for its answers to count toward that domain. Answers in sections without a domain, or in a domain without a weight, are counted and shown on the review as unweighted answers.
Turn AI off or restrict a domain
Each risk domain has two access settings on Configuration → Risk Domains: AI features and Visible to. Use them for a domain whose content AI must not read, or whose results only one team may see. Both save as soon as you change them, and both are also in the domain’s create and edit dialog.
Configuration → Risk Domains, with AI features off for Intellectual Property and two domains visible only to their own user groups.
- Questionnaire answers are not autofilled.
- Evidence is not reviewed by AI, in an assessment or a Zero Touch assessment.
- Findings are not drafted.
- The IRQ answer check skips the domain’s questions.
Step 2: Choose how ratings roll up
On Tiers, Scales & Cadence, under How Ratings Roll Up, choose one:
How Ratings Roll Up on the Tiers, Scales & Cadence tab, with Weighted average only chosen.
Step 3: Route reviews with the reviewer matrix
On Reviewer Matrix, click Add rule and fill in the Add Reviewer Rule dialog:
The Reviewer Matrix, listed in the order routing checks the rules.
Step 4: Escalate overdue work
On SLAs & Escalation, SLA Targets lists how long each stage of an assessment may take before it is overdue: the Organization default, and any risk domain that overrides it. Edit SLA targets changes them. These targets drive the engagement’s expected decision date. Under Escalation Rules, click Add rule and fill in the Add Escalation Rule dialog:- Name the rule, for example “Overdue Risk Group review”.
- Choose the Work it applies to. Leave it empty to escalate every kind of work.
- Set Days Overdue.
- Choose who it escalates to: a User, a Group, or a Group lead (the group’s lead at the time the item escalates).
- Choose Notify, so the target gets their own copy and the assignee keeps the item, or Reassign, so the item moves to the target.
Step 5: Version your inherent risk questionnaires
IRQ Versions lists each inherent risk questionnaire with its Version, Published date and Content Review Due. Use the row’s actions to Open template or View changelog: every change across all of its versions.Draft
Edit
Publish
Set a review cadence
Compare two versions
From a version’s actions, choose Compare with previous version or Compare with published, or Compare to pick any two. The page shows both side by side: Sections and Questions Added, Removed or Changed, with answer options, weights, risk domains, answer types and review flags. Swap versions reverses them, and Show unchanged questions shows everything.Retire versions
Select versions and choose Retire, or use Discard draft on one draft. A retired draft can no longer be published. Retiring the published version stops new sends of that questionnaire until a new version is published; questionnaires already sent finish on their version.Step 6: Override a score with a rationale
Anywhere you edit an inherent or residual score by hand (Edit Inherent Risk Score, Edit Residual Risk Score or Edit Assessment Score), the editor asks for a Rationale, recorded with the override in the score history, and Override Expires: Never, or After 30 days, 90, 180 or 365. The rationale is required. With an expiry, the editor says when the calculated score returns. While it is active, a chip beside the score reads Override ends in N days (or Override ends today). When an override expires, a daily job restores the last calculated score for each risk type the override changed, and the risk profile shows Override expired. If someone or something has replaced the override in the meantime, the newer score stands.Set how far residual risk can fall
Residual risk starts from the formula under Configuration → Scoring → Risk Scoring → Residual Risk Formula: inherent risk reduced by the assessment score, weighted by Assessment score weight. Residual Risk Step Down then decides how far below inherent risk the result may land.- No limit: residual risk follows the formula, however many levels it drops.
- Cap the step down: the formula still sets the score, but residual risk lands at most Most Levels Below Inherent levels below inherent risk. With a one level cap, Critical inherent risk ends no better than High.
- Set by rating: residual risk lands exactly one level below inherent when the assessment’s rating is one you tick under Ratings That Step Down One Level, and stays at inherent for any other rating. A qualifying rating moves residual risk one level down even when the formula would have left it at inherent. Inherent risk already at your lowest level stays there.
Try a what-if
- On a submitted inherent risk questionnaire, Inherent Risk What-If lets you change answers and shows where each domain and the overall rating would land, for example “With 2 changed answers, inherent risk moves from High 72 to Medium 48”. Reset puts the answers back. Nothing is saved; the respondent’s answers are unchanged.
- On an assessment’s summary, Residual Risk What-If lists the open issues. Turn on Remediate for the ones to fix and read the Domain Change and Overall Change, for example “Remediating ISS-311 drops Privacy residual risk from High 61 to Medium 44”. A significant deficiency floor stays in force, so a floored score may not move until the deficiency itself is resolved.
Simulate a rule change
To see what a scoring change would do before you make it, click Simulate impact on How Ratings Roll Up (the Tiers, Scales & Cadence tab). Nothing is saved.Propose the change
Run it
Read the result

Simulate Impact after raising the Cybersecurity weight from 25 to 40. No record changes tier.
POST /v1/risk_methodology/simulation also simulates new scores for answer options and a new supplier tier rule. It needs organization settings permission.
Reading an IRQ result

Why This Rating and the Inherent Risk What-If on a submitted IRQ.
Configure methodology from MCP or the API
You can read and change the methodology from an MCP client or with an API key, as well as on this page. An MCP client reads withquery_platform(kind=...) (risk_methodology, risk_domains, reviewer_matrix_rules, escalation_rules, vendor_tier_rule). It writes with mutate(entity="risk_methodology", action="update"), mutate(entity="risk_domain", action=...), mutate(entity="reviewer_matrix_rule", action=...), mutate(entity="escalation_rule", action=...) and mutate(entity="vendor_tier_rule", action="update").
The API routes are /v1/risk-methodology, /v1/risk-domains, /v1/reviewer-matrix-rules, /v1/work-queue-escalation-rules and /v1/vendor-tier-rule. See Change configuration and methodology.
Before an MCP client sends a write, it shows you the change and waits for you to confirm it. The MCP tool reference lists every field.
Risk domains need risk permission, which API keys hold. The other routes need organization settings permission, which they do not, so use a key created by a person whose role holds it. A rating override that needs approval is a change request. A member of the approver group decides it with mutate(entity="change_request", action="decide"). With an API key you can read, create and withdraw change requests at /v1/change-requests, but not decide them. See Change requests.