Rows like dimensions, square footage, support structure, siding, roofing, overhangs, concrete, openings and attached buildings. The row set is chosen by frame type (post frame or stud frame). Values are re-resolved live from the raw SmartBuild answers so template mapping fixes reach estimates already sent, and per-tenant fallback copy fills anything the answers do not cover.
Also called: what is included · building specifications · scope rows · post frame vs stud frame specs
- 1Frame type resolves from an explicit snapshot override, then auto-detection, then post frame
- 2customSpecs are rebuilt from rawAnswers and treated as authoritative for template-managed rows
- 3Square footage is derived by parsing feet and inches out of the dimension strings
- 4Missing rows fall through to portal_defaults.spec_fallbacks, then to compiled-in post-frame copy
Spec rows kept producing things a customer reads as a mistake. A height rendered as "40 x 60 x 12" with no unit, so the buyer could not tell feet from inches, and a six-inch slab came through as 0 feet 6 inches — correct, and it still reads as a bug sitting next to a price. A slab with no depth entered is dropped rather than shown as zero, raw supplier part numbers can never resurface on a customer document, and the same spec is worded identically on every quote, so one buyer does not see "4/12 pitch" where another sees "4.0/12 pitched roof."
- Sparse templated answers producing a scope that reads incomplete
- Unit-less and zero-value specs printing nonsense to a buyer
- Internal SKU codes leaking onto a customer-facing 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 →