---
updatedAt: 2026-07-15T21:05:47.000Z
agentTools:
  siteIndex: https://help.socure.com/llms.txt
  projectIndex: https://help.socure.com/riskos/llms.txt
---

# Workflows

A workflow is a configurable sequence of steps that processes an evaluation — collecting data, calling enrichments, applying rules, and returning a decision.

A **workflow** is a configurable sequence of steps that automates decision-making in RiskOS™. When an [evaluation](evaluations) is triggered, RiskOS™ executes the specified workflow — processing data through input collection, enrichment calls, conditional logic, and rules — to reach a final [decision](decisions).

You build workflows visually in the RiskOS™ Dashboard using the Workflow Editor.

<br />

## What a workflow does

A workflow defines:

1. **What data to accept** — The Input step specifies required fields in the evaluation payload.
2. **What data services to call** — Enrichment steps call Socure products or third-party APIs for additional [signals](signals-and-attributes).
3. **How to evaluate the data** — Condition steps, Rule Scorecards, and Transformation steps apply logic to route and score data.
4. **What decision to return** — A Decision step or Manual Review step terminates the workflow with an outcome.

<br />

## Custom workflows vs Hosted Flows

RiskOS™ supports two workflow delivery models. Both use the same evaluation runtime, enrichment pipeline, and decision model.

| Aspect            | Custom workflow                                          | Hosted Flow                                     |
| :---------------- | :------------------------------------------------------- | :---------------------------------------------- |
| **Configuration** | Built and managed by the customer in the Workflow Editor | Preconfigured with a Socure-managed end-user UI |
| **End-user UI**   | Customer-built (API + SDK)                               | Socure-hosted (web-based)                       |
| **Extensibility** | Full — any step type, any enrichment, any rule           | Template customization and branding             |

Both models produce [evaluations](evaluations), return [decisions](decisions), and follow the same [lifecycle states](statuses-and-lifecycle). The distinction is operational — ownership and configuration model — not architectural.

<br />

## Related topics

* [Workflow Steps Reference](https://help.socure.com/riskos/docs/workflow-steps) — Step-level configuration and field definitions
* [Manage Workflow Lifecycle](https://help.socure.com/riskos/docs/manage-workflow-lifecycle) — Draft → Published → Live
* [Hosted Flows](hosted-flow-core-concepts) — The Hosted Flow delivery model
* [Rules & Conditions](rules-and-conditions) — The logic layer inside a workflow
* [Evaluations](evaluations) — The runtime execution of a workflow

# Sibling pages

* [Understanding RiskOS™](https://help.socure.com/riskos/docs/understanding-riskos.md)
* [Evaluations](https://help.socure.com/riskos/docs/evaluations.md)
* [Enrichments](https://help.socure.com/riskos/docs/enrichments.md)
* [Signals & Attributes](https://help.socure.com/riskos/docs/signals-and-attributes.md)
* [Rules & Conditions](https://help.socure.com/riskos/docs/rules-and-conditions.md)
* [Decisions](https://help.socure.com/riskos/docs/decisions.md)
* [Synchronous vs Asynchronous Evaluations](https://help.socure.com/riskos/docs/sync-vs-async-evaluations.md)
* [Statuses & Lifecycle](https://help.socure.com/riskos/docs/statuses-and-lifecycle.md)
* [Cases & Manual Review](https://help.socure.com/riskos/docs/cases-and-manual-review.md)
* [How Hosted Flows Work](https://help.socure.com/riskos/docs/hosted-flow-core-concepts.md)
* [Step-up Verification Flows](https://help.socure.com/riskos/docs/step-up-verification.md)
* [Glossary](https://help.socure.com/riskos/docs/terminology.md)