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 Process Modeler is BPMN 2.0 with automatic validation while you design, form tasks bound to screens with preview, assignment to a user, group member, self-service queue or the case starter, a 72-hour default due time with dynamic due dates, manager escalation and reassignment, plus boundary timer, error, signal, conditional and message events and multi-instance loops, with tasks landing in a task inbox. We found no public information on four-eyes approvals, substitutes, a simulation of a whole process before publishing, or whether running cases stay on their original version when a new version is published. 2 3