Templated spec rows filled from the job's answers, with per-frame-type template sets. Post-frame gets posts spaced along the eave wall; stud-frame gets dimensional studs at a fixed spacing and a perimeter footing row. Frame type is auto-detected from the answers.
Also called: spec sheet · building specifications · what is included · proposal specs
- 1Templates use {FieldName} placeholders with pipe alternatives, filled case-insensitively from the answers.
- 2Post and bay spacing comes back from SmartBuild in INCHES and is formatted in feet; stud and girt spacing stays in inches, because that is how each is read.
- 3Truss spacing is printed in feet to match the proposal rather than inches.
- 4Orphan-prefix cleanup handles a leading placeholder resolving empty, and a row that filled nothing or reduced to punctuation is hidden rather than printed.
- 5Openings are built from the estimate's Doors and Windows material section, ordered garage then walk doors then windows, skipping hardware and custom or labor lines.
Customer proposals were going out with lines reading @A1 wall steel and on-center LM326{LF} — internal codes printed straight onto a document someone was being asked to sign. A specification a customer reads should read like a specification, not like a database dump. Spec rows are resolved to real descriptions before they reach a proposal, and a code that cannot be resolved is handled rather than printed.
- Internal SKUs and raw units printed on a customer document.
- Spec sheets hand-written per job.
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 →