Process Templates & Checklists
Approval processes, their steps and their checklists are configuration, not code. They're assembled from data, cloned from what already works, and published without a deploy.
Illustrative UI only. Data and individuals shown are fictitious; any resemblance to real persons or data is coincidental.
The whole template is data
A process, its steps, its routing conditions, its outcomes and its checklists are records, defined and published as configuration, with no schema change and no release.
Clone, then adjust
An entire process, steps and checklists included, can be duplicated into a fresh draft, adjusted, and published. New sign-off flows start from the closest existing one, not from zero.
Checklists that gate submission
Required items block a submission until they're ticked, and items can appear or disappear based on what the record actually says, so nobody answers questions that don't apply.
Checklists that tick themselves
An item the record can evidence on its own resolves automatically and is badged as such. The submitter confirms what only a human can, and skips what the data already proves.
Why we like this one
The detail that sold us is where the checklist is enforced. The submission screen evaluates which items apply and which have auto-resolved, but the server evaluates them again, on its own copy of the rules, before the submission is accepted. A crafted request can't skip a required item any more than an honest one can. Compliance that only lives in the browser isn't compliance; this one doesn't.
Book a demo ➝