Settings holds every stage's operating checklist in one editable place. Add, rename, reorder or remove steps per stage; save per stage; reset a stage to the built-in default. What reps see inside a pipeline card is this exact list, resolved through the same function.
Also called: custom SOP · edit sales checklist · our own process · settings stage SOPs
- 1Step keys never change once created, because deals and analytics store them
- 2Renaming a step keeps its key; new steps get generated keys server-side
- 3The stage's entry marker is pinned first and cannot be deleted
- 4Custom checklists override the defaults everywhere — checklist, progress, reminder suggestions and the audit timeline's labels
Every builder runs a different process, so a fixed checklist meant reps ticking steps that did not match their job. Checklists are now editable per stage in settings and go live on every rep's board the moment they save. One rule makes that safe: the identity of a step never changes once created, because deals and analytics have already stored it — without that, editing a checklist would silently rewrite the history of what reps were asked to do. Historical steps resolve their labels through the custom list too, so an old record reads in the builder's own words rather than as a raw key.
- A fixed process that does not match a given shop
- Editing a checklist corrupting historical records
- Custom steps rendering as raw keys in the audit trail
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →