architectural-specification

Architectural Specification Section

Wide tender prices are almost always a specification problem: three contractors read the same section and priced three different buildings. The cure is not more words. It is being precise about performance, unambiguous about who does what at the interfaces, and explicit about what must be submitted and tested — so the cheap tender and the expensive one are pricing the same thing.

What This Skill Produces

• Scope and interfaces — what this section covers, what it does not, and who is responsible at each junction
• Performance requirements — measurable criteria with the standard and test method named
• Product or system definition — either a named product with an equivalence rule, or a performance description a contractor can propose against
• Execution requirements — preparation, sequence, workmanship, and stated tolerances
• Submittals and samples — what must be approved before order, and before installation
• Testing and inspection — what is tested, when, to what standard, and who witnesses

Required Inputs

Ask for these if not provided:

• The element — what is being specified, and where it occurs in the building
• The performance it must achieve — structural, thermal, acoustic, fire, weather, durability, or appearance
• The selection basis — whether a specific product is intended, or a performance outcome is being sought
• The interfaces — what this element meets, and which other trades are involved
• The procurement context — the contract form, the specification system in use, and whether equivalents are permitted

Framework: Performance, Product, Execution, Proof

1. Define scope by exclusion as well as inclusion. Most interface defects live in the gap between two sections that each assumed the other covered the junction.
2. State performance as a measurable with a test method. 'Weathertight' is not specifiable; a pressure test to a named standard is.
3. Choose your specification mode deliberately. Prescriptive names a product and gets what you drew. Performance describes an outcome and transfers design risk. Mixing them accidentally is how you get an unpriceable section.
4. If naming a product, state the equivalence rule. What 'or equal approved' means, who approves, what evidence is required, and by when.
5. Give tolerances. Unspecified tolerance becomes whatever was achieved, and the argument happens on site with the work already built.
6. Specify the proof. Submittals before order, samples before installation, tests during. An unproved requirement is an aspiration.
7. Coordinate with the drawings explicitly. Where the two could conflict, say which governs.