Each contract_templates row is a distinct named template, not just a version of one. The settings editor has a template picker plus '+ New template'; one template at a time carries `active` (the org default used for new contracts). The Review & Send modal exposes the same list so staff can switch a specific customer's contract to a different template.
Also called: multiple contracts · post-frame vs concrete contract · contract per job type · named templates
- 1Name the template (placeholder text suggests 'e.g. Post-Frame Building, Concrete, Garage…').
- 2Untick 'Default for new contracts' to keep it alongside the default rather than replacing it.
- 3saveTemplate() deactivates other active rows when makeActive is set, enforcing one default per org.
- 4On any specific contract, 'Switch template…' re-renders that customer's body from a different saved template.
Documented in the save function: 'Each row is now a DISTINCT named template (e.g. "Post-Frame", "Concrete") that a sub-account can keep alongside others and pick per contract — not just versions of one.' A concrete job and a post-frame kit are not the same legal transaction, and forcing one body to cover both meant hedged wording that protected nobody.
- One contract body stretched to cover unrelated scopes
- No way to switch a generated contract to the right template without retyping
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 →