Delegation & Recall
Hand a pending approval to a colleague without losing the chain of custody, and pull back a submission that's already in flight, cleanly, and with everyone who touched it told.
Illustrative UI only. Data and individuals shown are fictitious; any resemblance to real persons or data is coincidental.
Delegation keeps the chain
Handing off doesn't overwrite the original request. It's marked delegated, recording who passed it and to whom, and the delegate's eventual decision sits alongside it in the history.
Four ways to move people
An approver can delegate their own item, an admin can reassign it or add an approver to a live step, and a one-off ad-hoc approval can be raised on any record without a template.
Recall is a clean unwind
Pending steps cancel, outstanding requests void, the record unlocks, and the process's own undo actions run, all in one transaction, so a recall either completes or didn't happen.
Departures handled in bulk
A leaver can be replaced or removed across every process and every in-flight request in one pass, with a dry-run preview of exactly what will be touched before you commit.
Why we like this one
The rules encode how sign-off actually works between people. Only the person who submitted can take a request back, and a template can forbid recall outright for the approvals that must run to completion. When a recall does happen, everyone who ever touched the request hears about it exactly once. No orphaned to-dos sitting in an inbox for a decision that no longer exists.
Book a demo ➝