Parallel & Sequential Routing
Multi-step sign-off that branches on the conditions you set. Steps run in strict order, all at once, or first-response-wins, and a rejection anywhere stops everything still pending.
Illustrative UI only. Data and individuals shown are fictitious; any resemblance to real persons or data is coincidental.
Parallel at two levels
Steps can be grouped to run simultaneously, and within a step the approvers can respond in strict turn order, unanimously, or first-decision-wins, whichever the sign-off actually needs.
Routing that reads the record
Conditions decide which process a record qualifies for and which steps apply, and they can reach across relationships, so a submission can branch on a field of a related record, not just its own.
Rejection short-circuits
One rejection voids the remaining requests and cancels the parallel steps alongside it, so nobody spends an afternoon approving something that's already dead.
Steps that act
A step can fire actions when it activates and when it completes (update a field, notify someone, run a business function) inside the same transaction as the decision itself.
Why we like this one
Our favourite part isn't the routing. It's what it takes to use it. Any record type becomes approvable by flipping a single setting: the record grows an approvals tab and a submit action on its own, with no per-object build. And the separation of duties is enforced by the engine, not by convention. You cannot approve your own submission, and the screen tells you why the buttons are disabled rather than pretending they aren't there.
Book a demo ➝