What a Specification Actually Is
Drawings and specifications are the two halves of a single legal instruction to the contractor, and neither one is complete without the other. Drawings show what is being built and where it goes — dimensions, locations, quantities, and the geometric relationship between building elements. Specifications define which products, materials, standards, and workmanship quality apply — what a drawn wall assembly is actually made of, which reference standard a weld or a concrete mix must meet, and what quality of finish or installation is acceptable.
A drawing might show a 6-inch concrete slab. It will not tell you the required compressive strength, the air-entrainment requirement, the vapor barrier product, or the curing method — that information lives in the specifications. Conversely, a specification section for cast-in-place concrete will not tell you where the slab is or how thick it is — that is drawn information. The two documents are legally complementary, not redundant: each is written to cover territory the other does not, and a well-coordinated set has as little overlap as possible.
Why Conflicts Between Drawings and Specs Are Not Yours to Resolve Informally
Because drawings and specifications are prepared by different people (often different firms) on different schedules, conflicts between them are common — a drawing note might call for a different fastener spacing than the specification section, or a specified product might not fit the dimensions shown. When a conflict exists, a contractor cannot simply pick whichever requirement looks easier or cheaper to build. Nearly every standard form of construction contract (AIA A201, ConsensusDocs, EJCDC) includes a contract documents precedence and conflict-resolution clause requiring the contractor to identify the discrepancy and formally request clarification — typically through a Request for Information (RFI) — rather than proceed on an assumption.
Some contracts state a strict order of precedence (e.g., addenda govern over specifications, which govern over drawings) as a fallback rule, but this is meant to resolve genuine ambiguity after the design team has been asked, not to license the contractor to bypass clarification. Proceeding on an unresolved conflict without a documented answer is one of the most common sources of costly rework and disputes on a project, because "the drawing said X" is rarely accepted as an excuse for ignoring a specification requirement the contractor should have flagged.
The CSI MasterFormat Three-Part Structure
Nearly all U.S. commercial specifications are organized using the Construction Specifications Institute's MasterFormat, which divides work into numbered divisions (Division 03 – Concrete, Division 09 – Finishes, Division 23 – HVAC, and so on) and further divides every individual specification section within a division into the same three parts:
- Part 1 — General: administrative and procedural requirements specific to that section — required submittals (shop drawings, product data, samples, certificates), quality assurance requirements (installer qualifications, mockups, pre-installation meetings, applicable reference standards), warranty length and terms, delivery/storage/handling requirements, and coordination with other trades.
- Part 2 — Products: what may actually be installed — acceptable manufacturers (sometimes a specific approved list, sometimes "or equal"), material and product standards (ASTM, ANSI, UL, or similar reference specifications the product must meet), and fabrication requirements for shop-built assemblies.
- Part 3 — Execution: installation requirements — surface preparation, installation method and sequence, tolerances, field quality control (inspections and field testing required during or after installation), and clean-up/protection of finished work.
This consistent three-part structure means an experienced reader can jump directly to the part they need: a purchasing agent checking product acceptability goes straight to Part 2, while a field superintendent verifying installation tolerances goes to Part 3.
Performance Specifications vs. Prescriptive/Proprietary Specifications
Specifications state requirements in one of two fundamentally different ways. A prescriptive (or proprietary) specification names specific products, manufacturers, or exact methods — "install a [Manufacturer X], Model Y roof drain" or "concrete shall be mixed in strict accordance with the following proportions." Prescriptive specs give the designer tight control over the outcome and are common for products where performance is hard to define generically (architectural finishes, specialty hardware) — but they also limit competitive bidding to whatever is specified.
A performance specification instead states the required outcome — the load capacity, flow rate, efficiency, or durability a product or assembly must achieve — and leaves the contractor or manufacturer free to select any product that meets it. Performance specs are common for mechanical/electrical equipment and structural products where measurable criteria (BTU/hr, GPM, PSI, STC rating) clearly define acceptable performance, and they generally produce more competitive pricing because more products qualify.
Because pure prescriptive specifications can unintentionally lock a project into a single supplier — sometimes raising legal and procurement-fairness concerns on public work — most specifications include an "or equal" substitution clause. This clause allows a contractor to propose an alternate product that is demonstrably equivalent in function, quality, and performance to the named basis-of-design product, subject to the design team's review and approval. The substitution request is typically processed as its own submittal, with the burden of proof on the contractor to show true equivalence — not just a lower price.
How Specifications Coordinate with Submittals
Every specification section's Part 1 lists the exact submittals required before that portion of the work may proceed — this is the direct link between the written specification and the physical submittal process. A concrete specification section, for example, will typically require a mix design submittal, reinforcing steel shop drawings, and material certifications, each cross-referenced to the specific ASTM or ACI standard the specification calls out in Part 2. When the design team reviews a submittal, they are checking it against these specification requirements, not against the drawings — the drawings simply establish geometry, while the specification is the actual approval yardstick.
Well-coordinated project manuals include a submittal schedule (sometimes a standalone document, sometimes embedded in Division 01) that consolidates every submittal required across all specification sections into a single tracked list, which is the same submittal log a general contractor manages throughout construction.
Reading Specifications Effectively
When reviewing a specification section, read Part 1 first to understand the procedural requirements and quality-assurance expectations before ordering or fabricating anything — missing a required mockup or pre-installation meeting is a common and preventable submittal rejection. Then check Part 2 to confirm the actual product or material meets every referenced standard, not just the manufacturer name. Finally, use Part 3 to plan the installation sequence and to know what field testing or inspection will be required before the work can be considered complete. Cross-reference every specification section against the corresponding drawing sheets — a conflict caught during bidding or shop-drawing preparation is far cheaper to resolve than one discovered in the field.