A server step that loads the tenant's active contract template, builds a substitution context from customer, builder, project and estimate data, renders the body, extracts which sections require initials, and writes a contracts row with the rendered body frozen on it. It also mirrors the form fields back onto the contact record so future invoices and contracts use the latest legal information.
Also called: auto contract · build the agreement automatically · contract template tokens
- 1The active template for the tenant is looked up, falling back to the default body
- 2buildContractContext assembles the substitution values including payment schedule lines
- 3extractRequiredSections freezes the list of clauses that must be initialed
- 4The rendered body, required sections and contract id are stored and stamped on the link
- 5Stage automation, attention automations and builder notifications fire
Between a signed estimate and a signed contract sat a builder rewriting a template by hand — retyping names, addresses and figures that were already on file, and getting one wrong often enough to matter. Submitting the details form generates the agreement from the builder's own template with every value filled in, ready for the customer to sign and the builder to counter-sign. The finished wording is frozen onto the record at that moment, so editing the template later can never change what somebody has already signed.
- Manual contract drafting per job
- Template edits retroactively altering signed agreements
- Contract figures drifting from the approved estimate
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 →