Process design, forms & approvals
How this is scored
Modelling the process people take part in: a visual designer or BPMN, forms, approval steps with roles and substitutes, deadlines and escalation, and versioning of a process that is already running — judged on whether a business owner can change a process without breaking the instances in flight.
0 — No human steps at all: neither forms nor approval steps, only machine-to-machine automation.
3 — A visual builder with branching and a simple approval or form step.
5 — A visual designer with conditions and parallel paths, forms and approval steps assigned to roles or groups, and deadlines or reminders for open tasks.
8 — BPMN 2.0 modelling or an equivalent documented notation, versions of a process kept with running instances on their original version, substitutes and escalation chains, multi-stage approvals with four-eyes rules, forms in German with validation and file upload, a task inbox for participants, and a test or simulation mode before publishing.
10 — The process is a governed asset: version history with diff and rollback, migration of running instances to a new version documented, process analytics on cycle time and bottlenecks per step, and the design documented well enough that a business team can maintain it without the vendor.
The Skeptic
The drag-and-drop builder documents conditions, parallel steps, forms and maker-checker approvals with four-eyes, and the versioning story is unusually concrete: instances keep the version they started on, rollback does not interrupt running instances, and each change gets its own changelog line with a sandbox for testing drafts. We found no public information on deadlines, reminders or escalation chains for open tasks, on BPMN or an equivalent notation, or on form validation, file upload or a participant task inbox, which keeps this below the full governed-notation level. 4 5 8