What A Week! Reference Standards: Say It Once. Say It In The Right Place.
Mon Jan 26 2026
In this episode, Dave Stutzman, Steve Gantner, and Elias Saltz tackle a deceptively simple question that carries real contractual risk: Where should reference standards live in the specifications, and should they be dated? Reference standards belong in Part 2 of the technical sections, not in consolidated lists. Avoid listing dates unless a specific edition is required by code. Rely on Division 01 Quality Requirements to govern which standards apply. Saying things once, in the right place, reduces conflicts, RFIs, and unnecessary risk.
Learning PointsIndustry insight: Reference standards create more risk through duplication and dating than through omission when they are not placed intentionally.Practice takeaway: Keep reference standards in Part 2 of technical sections and let Division 01 govern applicability to avoid conflicts.Process lesson: Saying things once, in the right place, is the simplest way to improve clarity and reduce downstream rework.Risk or opportunity: Eliminating dated, consolidated reference lists reduces RFIs and protects the contract from unnecessary ambiguity.People & culture: Good specifications reflect disciplined thinking, shared responsibility, and respect for how teams actually use the documents.
More
In this episode, Dave Stutzman, Steve Gantner, and Elias Saltz tackle a deceptively simple question that carries real contractual risk: Where should reference standards live in the specifications, and should they be dated? Reference standards belong in Part 2 of the technical sections, not in consolidated lists. Avoid listing dates unless a specific edition is required by code. Rely on Division 01 Quality Requirements to govern which standards apply. Saying things once, in the right place, reduces conflicts, RFIs, and unnecessary risk. Learning PointsIndustry insight: Reference standards create more risk through duplication and dating than through omission when they are not placed intentionally.Practice takeaway: Keep reference standards in Part 2 of technical sections and let Division 01 govern applicability to avoid conflicts.Process lesson: Saying things once, in the right place, is the simplest way to improve clarity and reduce downstream rework.Risk or opportunity: Eliminating dated, consolidated reference lists reduces RFIs and protects the contract from unnecessary ambiguity.People & culture: Good specifications reflect disciplined thinking, shared responsibility, and respect for how teams actually use the documents.