The generator reads the snapshot's material sections (handling both camelCase and raw PascalCase SmartBuild shapes), escapes any pipe characters in names, and emits a markdown pipe table of Item / Amount. If no sections exist it degrades to a single 'Project Total' row. The contract renderer draws it as a styled table with a right-aligned, tabular-numbers money column.
Also called: contract line items · exhibit A · specs in the contract · what's included
- 1Read materialSections or MaterialSections from the snapshot.
- 2Emit '| Item | Amount |' with a separator row and one row per section.
- 3Subtotal is computed as grand total minus sales tax; tax and total render from their own tokens.
- 4ContractMarkdown parses the pipe table and renders a bordered table with the last column right-aligned.
The GCS agreement's Part 1 is literally the approved estimate's specs and payment schedule, injected at generation from the estimate snapshot. Without a table renderer the contract would either print raw pipes or force builders to attach a separate PDF exhibit — and an exhibit that travels separately is an exhibit that gets lost.
- Contracts that reference an exhibit nobody attached
- Scope disputes with no itemisation in the signed document
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 →