Cadenio for BPM
From process design to execution
For people who already map and redesign processes. These are real product screens: AI assembling the Flow from your spec, every run with an owner and a deadline, and the reports that sustain the next improvement cycle.
Feature
AI that builds the Flow: from description to structure
Describe the process in plain language, at the level of detail you would use to explain it to a new colleague. AI returns tasks, fields, phases, conditional rules, and approvals, ready to review.
In this screen
In this real generation, one paragraph about vendor onboarding became 9 steps across 4 phases, with 43 fields, 10 logic rules, 2 approvals, and 8 dependencies. It is a draft to adjust, not a Flow to publish unreviewed.
Feature
Flowchart: process logic that stays current
The diagram is derived from the Flow's configuration, not drawn separately. When a rule changes, the drawing changes with it, so it never contradicts what is running.
In this screen
Here a decision node forks into four parallel paths with a 2-way conditional split, opening the IT, Marketing, and HR tracks, which converge into a shared wrap-up. Filters at the top isolate dependencies, approvals, assignment, or automation.
Feature
Execution: owner, deadline, and trail from step one
Every process instance runs with an owner, per-task progress, and required fields that block progress until they are filled in.
In this screen
The side panel shows the published version in use, who started it, elapsed time, and the activity history. Tasks outside the chosen track simply do not appear: 7 visible steps out of a 13-task Flow.
Feature
Pipeline: where each run is stuck
The pipeline view organizes in-flight runs by the stage they are sitting in, with time-stalled visible on every card.
In this screen
It is bottleneck reading without building a report: you can see which instances are stuck, at which stage, and for how many days. The same Flow also renders as a table and a calendar.
Lifecycle
Which lifecycle phases Cadenio covers
Seven phases in the cycle. Cadenio is the primary tool in 3 of them. In the other 4 it assists or simply stays out, and that is better said now than at rollout.
Plan
Out of scopeStrategy alignment, process prioritization, process-office governance.
Analyze (AS-IS)
Out of scopeDiscovery, interviews, current-state modeling, root-cause and value analysis.
Design (TO-BE)
Partial supportThe 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 worksThe redesigned process becomes an executable template: tasks, fields, conditional rules, approval gates, deadlines, and escalation.
Execute
Where Cadenio worksEvery instance runs with a named owner, in-step context, attachments, comments, and an immutable audit trail.
Monitor
Where Cadenio worksCycle time per instance and per activity, deadline breaches, bottlenecks, reopens, adherence. Reports and export.
Refine
Partial supportCadenio 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 has its own names for things. 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
Feature
Reports that come out of the execution itself
A documented process generates no data at all. A process executed on a platform does, and that data is what the next improvement round rests on.
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.
And when the metric is yours, not ours
Beyond the built-in reports, you can assemble the panel metric by metric: pick the source, the scope, what to measure, and the columns. AI generation of that panel is being rolled out gradually.
To be precise
What Cadenio is not
It is the first question that comes up in a technical conversation, so it is worth answering up front.
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.
In practice, Cadenio does not compete with your modeling tool or with the analysis work. It solves what usually comes next: the process was approved and, day to day, nobody manages to make it happen.
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 every claim on this page
Glossary
Every product term, defined one by one.
Smart Logic
How conditional rules replace process variants.
Approvals
ANY and ALL policies, signatures, and segregation of duties.
SLA and deadlines
Deadline contracts, alert thresholds, and escalation levels.
Audit trail
What is recorded, when, and how to export it as evidence.
API and webhooks
12 permission scopes and 9 outbound events, to integrate with the customer's stack.
For consultants and educators
Get your redesign off the page.
If you make your living redesigning processes, we have a partner program with recurring commission, and your services revenue stays entirely yours.