Skip to content

Workflows

Describe a process as steps and see the obligations assessed for each one.

Create a workflow

Open Workflows → New workflow in Eli. Import a JSON file or edit the supplied example. Replace its business context, step descriptions, system prompts, and tools with your actual workflow. Each step needs a stable ID; adding a step must not renumber the IDs of existing steps.

The preview lists the steps you are about to submit. Editing does not start an assessment. Choose Save and assess to register the version and assess its steps asynchronously.

Workflows can have connected steps, branches, cycles, or independent agent contributions. They are separate from standalone Agents and from the Release workflow review/sign-off feature. Workflow steps appear inside their Workflow, not in the Agents tab.

Read results

Open a Workflow to see how many steps have finished. Expand a step for its submitted description and obligations, including the assessment reasoning and full obligation detail. Download combined JSON returns all step results for the selected version.

A Workflow is complete only when every step has finished. Successful steps remain visible when another step is pending or failed. A stalled or failed step offers Retry step. Partial legal coverage remains labeled even after a processing job completes.

Counts are obligation associations with steps. A duty affecting two steps may appear twice; this does not mean two different legal duties. System prompts describe intended behavior and do not establish that deployed controls comply.

Change a workflow

Choose Edit and reassess, review the complete JSON, and select Save and assess. This creates a new version. Earlier versions and their accepted results remain accessible through the version selector. If someone else has updated the Workflow, reload it before submitting your edits.

Access and limits

Users with active organisation access can manage Workflows through Eli or their API key. The default Free allowance includes one Workflow with up to 20 steps, separate from standalone Agents. Current allowances appear above the Workflows list. Assessment scope limits continue to apply.

For automation and the full input schema, see the Workflow API guide.

When versioned reviews are enabled, expand a step and open Legal / Engineering / Release review. Legal decides applicability and requirements, Engineering implements them and supplies evidence, Legal accepts evidence, and the Release manager signs off the component. Each step has its own decisions and evidence within the parent Workflow.

Open Release workflow to see Standalone agent review progress, followed by Workflow review progress. Both tables show version, current team, review state, Legal progress, Engineering progress, and open blockers. Workflow agents are grouped under their parent Workflow; the team filter applies to both sections.

Select a workflow agent's name to open its review and CSV actions directly below its Workflow. Legal, Engineering, and Release managers use the same role-specific review controls as standalone agents. CSV imports, exports, evidence, and decisions apply to the selected step and version. Repeat for other steps; a workflow-wide CSV import is not provided.

Assessment completion alone does not mean release readiness. Every step needs its own review and sign-off. Earlier Workflow versions remain available from the Workflow detail page and are read-only after a newer version is submitted.