A settings tab holding the acceptance contract a crew lead signs when they take a project. The builder writes their own text and drops in placeholders for the labour amount, project name, customer name and today's date. Saving creates a new version; contracts already signed keep the exact text they were signed on.
Also called: subcontractor agreement · crew contract · what my leads sign · acceptance contract
- 1The current agreement and its version number load from the crew-agreement API.
- 2Saving through the admin-gated endpoint creates a new version and reports it: new signings use it immediately, already-signed contracts keep their frozen snapshots.
- 3Placeholders fill at view and sign time per project.
- 4Saving requires at least a minimum body length so an empty agreement cannot be published.
Filed asfor Chris. The critical design point is in the comment: the labour amount token pulls from the APPROVED estimate 'so the number the lead signs is the number that was sold'. Versioning with frozen snapshots exists because changing a template must never retroactively alter what someone already signed.
- The crew acceptance text was not the builder's own.
- Editing the template risked altering already-signed agreements.
- The labour figure was retyped and could differ 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 →