Cadenio for BPM

Cadenio does not model BPMN. It executes what you modeled.

This page is for people who work in the BPM discipline. The rest of the site speaks in SOPs, operations, and compliance. Here we translate: where Cadenio fits the lifecycle, where it does not, and how the product vocabulary maps onto yours.

Partner program See the product glossary

Cadenio's Logic Summary view showing an onboarding flow with 11 tasks, 16 rules and 12 dependencies, including dependency arrows, two conditional repeat loops, a fork into five parallel paths and a final merge. — A real process in Cadenio: dependencies, two conditional repeat loops, a fork into five parallel paths and a merge. This diagram is derived from the configured process, not hand-drawn, so it never drifts from what actually runs.

First things first

What Cadenio is not

You will ask this in the first meeting. Better to answer it here.

Not a BPMN 2.0 modeling tool
We do not draw BPMN notation, we have no palette of events, gateways, and pools, and we neither import nor export BPMN XML. Keep using Bizagi, Camunda Modeler, Visio, or whatever you use today.
Not a process architecture repository
We do not hold the value chain, the macroprocess hierarchy, or a maturity matrix. Cadenio knows the process it executes, not the organization's full map.
No simulation or capacity analysis
We do not simulate scenarios with hypothetical volumes. Cadenio's numbers come from real execution, once the process is running.
Not a replacement for analysis work
Discovery, interviews, root-cause analysis, and redesign remain consulting work. The tool will not discover the process for you.

The practical consequence: Cadenio competes with neither the modeling tool nor the analysis work. It solves what usually happens next, when the redesigned process is approved and nobody manages to make it happen day to day.

Lifecycle

Where Cadenio fits, phase by phase

2 phases out of scope, 2 with partial support, 3 where Cadenio is the primary tool.

Plan
Out of scope
Strategy alignment, process prioritization, process-office governance.
Analyze (AS-IS)
Out of scope
Discovery, interviews, current-state modeling, root-cause and value analysis.
Design (TO-BE)
Partial support
The design is yours. Cadenio comes in when the TO-BE has to be specified into owner, deadline, decision, and evidence per activity.
Implement
Where Cadenio works
The redesigned process becomes an executable template: tasks, fields, conditional rules, approval gates, deadlines, and escalation.
Execute
Where Cadenio works
Every instance runs with a named owner, in-step context, attachments, comments, and an immutable audit trail.
Monitor
Where Cadenio works
Cycle time per instance and per activity, deadline breaches, bottlenecks, reopens, adherence. Reports and export.
Refine
Partial support
Cadenio provides the execution data and versions the change. The refinement decision remains human analysis.

Vocabulary

What your term is called in the product

The product uses its own names. This is the translation, so you do not have to guess while reading the docs.

Process
Flow (template)
Versioned, with draft and publish
Process instance
Run
One execution, with its own state and history
Activity
Task
With description, context, attachments, and a done criterion
Performer role
Assignee, group, or assignment rule
Fixed assignment or derived from a field
Business rule, gateway
Smart Logic (WHEN/THEN)
Shows, hides, and branches tasks based on the data
Decision point, authority level
Approval gate
ANY or ALL policy, with signature and immutable record
Handoff
Task transition
New owner, new deadline, automatic notification
Time indicator, SLA
Deadline and SLA with escalation
Alert threshold and escalation levels
Evidence, record
Audit trail
Immutable, written at event time, exportable
Process data
Field
Typed, required or optional, used by the rules
Master data, lookup table
Data Source
Centralized tables with records and relations
Process documentation
Context embedded in the task
The instruction lives in the step, not in a separate manual
Process change management
Published version
In-flight runs keep the current version; the new one applies to the next

Mapping between BPM terms and Cadenio terms
In BPM	In Cadenio	Note
Process	Flow (template)	Versioned, with draft and publish
Process instance	Run	One execution, with its own state and history
Activity	Task	With description, context, attachments, and a done criterion
Performer role	Assignee, group, or assignment rule	Fixed assignment or derived from a field
Business rule, gateway	Smart Logic (WHEN/THEN)	Shows, hides, and branches tasks based on the data
Decision point, authority level	Approval gate	ANY or ALL policy, with signature and immutable record
Handoff	Task transition	New owner, new deadline, automatic notification
Time indicator, SLA	Deadline and SLA with escalation	Alert threshold and escalation levels
Evidence, record	Audit trail	Immutable, written at event time, exportable
Process data	Field	Typed, required or optional, used by the rules
Master data, lookup table	Data Source	Centralized tables with records and relations
Process documentation	Context embedded in the task	The instruction lives in the step, not in a separate manual
Process change management	Published version	In-flight runs keep the current version; the new one applies to the next

In the product

The specification and the instance

Two screens, because these are two distinct objects: the process you design once, and each execution of it. Conflating them is the source of most confusion for newcomers to the product.

Cadenio's Flow editor showing the Employee Onboarding process at published version 1, an 11-task list on the left with dependency, due-date, approval and rule-count chips, the open task in the centre with its instruction and required fields, and the field-type palette on the right. — The TO-BE specified for execution. Each task explicitly carries what it depends on, its deadline, whether it requires approval, and how many conditional rules govern it. The version is published, so process change has a history.

A run of the Employee Onboarding flow in Cadenio, status Running, 2 of 11 tasks complete, a named owner, two completed tasks, and the current task showing required fields and a Submit for approval button. — One instance running. Per-task progress, an owner, required fields that block progress, an approval gate and a comment on the step. Every one of those actions becomes an audit-trail record the moment it happens.

Measurement

What becomes measurable after go-live

The difference between a documented process and a process executed on a platform is that the second one produces data.

Cadenio's Reports dashboard: 89% on-time delivery, an 8-hour median cycle time, 65 currently overdue tasks, 100% deadline coverage. Below, on-time delivery by process ranging from 80% to 100%, a list of tasks stuck for weeks, and cycle time by process from 7 to 22 hours. — A real dashboard, not a perfect case: 89% on-time delivery, with processes ranging from 80% to 100%. "Where we slip" names the longest-stuck tasks, with the exact age of the delay. This is the evidence that sustains the next redesign round, generated by execution, not estimated.

Cycle time
Per run and per task, start to finish, with the distribution and not just the average.
Bottleneck per activity
Which task concentrates waiting time. This is the evidence that sustains the next redesign.
Deadline breaches
How many instances missed the SLA, which escalated, and to whom.
Rework
Task and run reopens, the most direct signal of a poorly designed process.
Adherence
What ran as designed and where it deviated, task by task.
Volume per variation
How many instances fell into each branch of the conditional rules. Shows whether the designed variation exists in practice.

In practice

How a consulting project uses Cadenio

01
AS-IS in your tool
You discover and model the current state where you already work. Cadenio does not enter here.
02
TO-BE specified for execution
Every activity gets an owner, a deadline, a done criterion, an authority decision, and the evidence it must leave behind.
03
Materialized in Cadenio
The specified TO-BE becomes a template: tasks, fields, Smart Logic, approval gates, deadlines, and escalation.
04
Pilot with a real instance
An actual run, with actual people. This is where what the map did not show shows up.
05
Measure and publish a new version
Execution data feeds the adjustment. The change ships as a new version, with history.

To go deeper

The docs behind each claim above

For consultants and educators

Your TO-BE deserves somewhere to run.

If you deliver process redesign, there is a partner program with recurring commission and your services revenue untouched.

See the partner program Try it for 14 days

In BPM

In Cadenio

Note

Process

Flow (template)

Versioned, with draft and publish

Process instance

Run

One execution, with its own state and history

Activity

Task

With description, context, attachments, and a done criterion

Performer role

Assignee, group, or assignment rule

Fixed assignment or derived from a field

Business rule, gateway

Smart Logic (WHEN/THEN)

Shows, hides, and branches tasks based on the data

Decision point, authority level

Approval gate

ANY or ALL policy, with signature and immutable record

Handoff

Task transition

New owner, new deadline, automatic notification

Time indicator, SLA

Deadline and SLA with escalation

Alert threshold and escalation levels

Evidence, record

Audit trail

Immutable, written at event time, exportable

Process data

Field

Typed, required or optional, used by the rules

Master data, lookup table

Data Source

Centralized tables with records and relations

Process documentation

Context embedded in the task

The instruction lives in the step, not in a separate manual

Process change management

Published version

In-flight runs keep the current version; the new one applies to the next