Stage-Based Workflows
The stages work moves through, and the sub-stages within them, are defined as configuration, with every transition journalled, timed and reportable.
Illustrative UI only. Data and individuals shown are fictitious; any resemblance to real persons or data is coincidental.
Stages, and stages within stages
A workflow binds a stage field and, optionally, a sub-stage field, so "in progress" can say which part of in progress it means, and both levels are clickable on the record itself.
The form follows the stage
Sub-stage options are filtered to what's legal for the current stage, and a selection that's no longer valid clears itself the moment the stage moves. That behaviour is configuration, not code.
Every move is journalled
Each transition records who moved the work, when, from where to where, and how long the record sat in the stage it just left.
Bottlenecks fall out for free
Average time spent in each stage, and a live count of how many records are sitting in each one right now, with no report to build first.
Why we like this one
Stages can carry a positive or negative outcome, so "Done" and "Voided" aren't just two more grey chips, and a workflow knows the difference between finishing and failing. Sensitive transitions can demand a confirmation, or be vetoed outright before they happen. And because a stage change is an ordinary record update, "when a case reaches this stage, do that" needs no special machinery, because the automation engine sees it like any other change.
Book a demo ➝