Configure AI risk scoring and routing
Table of Contents
Who this is for: administrators configuring forms and approval routing.
Use this guide to enable risk scoring on a form and check how risk-based conditions affect approval routing. For interpreting a submission’s risk level and signals, see Read AI-generated risk information.
Enable risk scoring on a form
- In admin view, open Form builder.
- Select the form and open Settings.
- Locate Risk scoring and enable it for the form when required by your program.
- Follow the form’s saving and publishing process. Verify the published version before testing new submissions.
The setting states that records are scored when submitted and that routing rules can read the risk bucket. Enabling scoring and defining a risk-based approval route are separate configuration tasks.
Configure how risk affects routing
- Open the form’s Workflow tab.
- Review the phases, step destinations, and conditions. Identify any conditions that use the risk bucket.
- Confirm which reviewers should receive each applicable risk-based path and whether the reviews should run sequentially or in parallel.
- Check the form’s Unmatched submissions settings and each step’s missing-approver fallback.
- Save and publish the validated configuration according to your organization’s process.
For detailed phase, step, and condition instructions, use Build an approval workflow. For the concepts, see Understand approval phases, steps, and routing.
Keep risk, approval status, and exceptions separate
| Situation | What controls the outcome |
|---|---|
| A submission has a risk level | The risk information provides review context and can be read by configured routing rules. It is not itself an approval status. |
| No workflow step matches | The form’s Unmatched submissions configuration determines whether to route the request or automatically approve it. |
| A step matches, but no eligible approver can be found | The step’s own fallback applies. Without one, it waits for an approver; this is not the unmatched-submission case. |
A Low risk result does not by itself establish that automatic approval is enabled. Check the actual workflow conditions and unmatched behavior.
Validate the configuration
- Test representative submissions for each intended risk-based route.
- Compare the displayed risk bucket with the resulting review timeline and assigned reviewers.
- Test a submission that matches no step and confirm the configured unmatched behavior.
- Test an unavailable manager or empty reviewer group and confirm the step-level fallback or waiting state.
- Record the form version, submission reference, expected route, and actual result before making the configuration available to users.
Support reviewers with missing or questionable risk information
If a reviewer reports a missing Risk panel, check the form’s risk-scoring configuration, the capability’s availability, and the reviewer’s access. If a signal appears inaccurate, collect the record reference, displayed signal, and underlying information that needs checking for your support investigation.
Direct reviewers to Read AI-generated risk information for how to interpret signals and use them during a human review. For general form configuration, see Find forms and understand their configuration.