Decisions
A decision is the final outcome of an evaluation — ACCEPT, REJECT, or REVIEW — determined by enrichment data, rules, and scoring logic.
A decision is the final outcome of an evaluation. It represents the platform's determination — based on enrichment data, rules, and scoring logic — of whether to accept, reject, or flag an entity for further review.
Terminal workflow steps assign decisions: a Decision step for automated outcomes, or a Manual Review step for human review.
Decision values
The Evaluation API returns three standard decision values:
| Value | Meaning | Typical action |
|---|---|---|
ACCEPT | The entity passed all checks | Proceed with onboarding, transaction, or access |
REJECT | The entity failed one or more checks | Deny the request |
REVIEW | The evaluation requires human assessment | Route to Case Management for manual review |
Decision Rules steps can also assign custom values such as
RESUBMITandCANCEL, or route to Manual Review.
Two types of decisions
Automated decisions — A Decision step or Decision Rules step in the workflow assigns the outcome. The evaluation API response returns the decision without human involvement.
Manual review decisions occur when a workflow routes to a Manual Review step. The evaluation enters Case Management, where a human reviewer makes the final determination. RiskOS™ communicates the reviewer's decision via webhook (decision_update event) or API polling.
Related topics
- Interpret a Decline — Trace a
REJECTorREVIEWback to the enrichment scores and reason codes that drove it - Reason Codes & Score Interpretation — How to read the scores and reason codes behind a decision
- Statuses & Lifecycle — How decisions relate to evaluation states and case statuses
- Cases & Manual Review — How reviewers handle
REVIEWdecisions - Rules & Conditions — The logic that assigns decisions
- Evaluations — The execution that produces a decision
Updated 17 days ago