Construction Specifications Mastery: Writing Clear, Complete Specs

Construction specifications often determine whether your design gets built as intended—or becomes a source of delays, RFIs, and costly mistakes. We’ve all seen it happen: the drawings show one thing, the specifications say another, and suddenly you’re fielding angry calls from the contractor while the project bleeds time and money. That disconnect between what you envisioned and what gets built often traces back to one overlooked document—the specification.

Specifications aren’t glamorous. They don’t win design awards or make it into magazine spreads. But they determine whether your carefully selected finishes actually show up on site. They define whether the millwork meets your quality standards. They establish whether you have legal ground to stand on when a contractor substitutes your premium laminate for something that looks like a hotel bathroom circa 1987.

We’ve watched talented designers lose control of projects because their specs were vague, outdated, or contradictory. We’ve also seen specification mastery transform project outcomes—reducing RFIs, eliminating substitution battles, and ensuring design intent survives the construction process intact.

In this article, you’ll learn:

• Why specifications function as legal documents that protect your design and your practice
• How the CSI MasterFormat system organizes construction information into a universal language
• What belongs in each part of the three-part specification format
• When to use proprietary, performance, or basis-of-design specification approaches
• How to write substitution language that actually works
• Where coordination failures happen between specs and drawings—and how to prevent them
• What clear submittal requirements look like in practice
• Which common specification errors generate the most RFIs and disputes

Why Specification Writing Matters More Than You Think

Specifications as Legal Documents

Here’s what many designers don’t realize until something goes wrong: specifications aren’t just technical guidelines. They’re legally binding contract documents that define materials, quality standards, and execution requirements.

According to the Young Architect Academy’s analysis of specification errors, specifications “bring your vision to life” while simultaneously protecting you, your client, and your design. When done right, proper construction specifications form the backbone of quality management. When done wrong, poor specification writing leads to conflicts, cost overruns, and legal disputes.

The drawings show what to build. The specifications tell everyone how to build it, what materials to use, and what quality standards to meet. Together, they form the complete instruction set for construction.

The Cost of Poor Specs

Let’s talk numbers. According to Navigant Construction Forum research cited by construction attorneys, the average construction project generates 796 RFIs. The estimated cost to respond to each RFI runs approximately $1,080. That means a typical project spends over $859,000 just answering questions—many of which stem from unclear or conflicting specifications.

Poor specs don’t just generate questions. They create:

• Change orders when contractors discover conflicts between documents
• Delays when submittals get rejected for not meeting undefined requirements
• Disputes when “or equal” products don’t match design intent
• Legal exposure when quality issues trace back to ambiguous language

As AORBIS research from their Beyond the Specs 2025 survey confirms, copy-pasted sections from old projects introduce errors. Vague wording invites disputes. Overcomplicated submittal processes waste everyone’s time. These frustrations aren’t just annoyances—they’re costing contractors projects and costing designers their reputations.

Where Specifications Fit in the Contract Document Hierarchy

When drawings and specifications conflict—and they will—which document governs? Most standard contracts, including AIA documents, establish that specifications take precedence over drawings for quality and material requirements.

This hierarchy matters. A contractor might order materials based on what they see in the drawings, only to learn during submittal review that the specs require something different. Understanding this hierarchy helps you write specs that coordinate properly and anticipate potential conflicts.

Understanding the CSI MasterFormat System

The “Dewey Decimal System” of Construction

Think of CSI MasterFormat as the organizational backbone of construction documentation. Developed by the Construction Specifications Institute, MasterFormat provides a standardized system for organizing construction information that everyone in the industry understands.

Just like libraries use the Dewey Decimal System to organize books by subject, MasterFormat organizes construction specifications into 50 divisions. When a contractor mentions “Division 09,” every architect and project manager immediately knows they’re talking about finishes. This universal language prevents miscommunication that can derail projects.

The system expanded from 16 divisions to 50 in 2004 to accommodate new materials, technologies, and sustainable practices. The current structure includes reserved divisions for future expansion as the industry evolves.

Division Numbers Interior Designers Use Most

While MasterFormat covers everything from earthwork to electrical, interior designers typically work within specific divisions:

• Division 06: Wood, Plastics, and Composites — Architectural woodwork, plastic laminate, panel products, millwork
• Division 09: Finishes — Plaster, gypsum board, tile, ceilings, flooring, wall coverings, painting
• Division 10: Specialties — Signage, compartments, lockers, protective covers
• Division 12: Furnishings — Window treatments, furniture, artwork, accessories

Understanding which divisions apply to your work helps you locate relevant sections quickly and ensures you’re placing specifications in the correct location for contractors to find them.

How the Six-Digit Numbering System Works

MasterFormat uses a six-digit numbering system that gets progressively more specific. The first two digits indicate the division. The next two indicate the section. The final two indicate the subsection.

For example, 09 30 00 refers to Tiling. Within that, 09 31 00 covers Thin-Set Tiling, and 09 31 13 specifies Thin-Set Ceramic Tiling. This granular organization allows contractors and suppliers to reference exactly what they need without hunting through unrelated content.

When to Use Broad-Scope vs. Narrow-Scope Sections

Here’s a practical decision you’ll face: should you write one section covering multiple related products or separate sections for each?

Conspectus, a leading specification consulting firm, recommends choosing broad-scope numbers (sections ending in 0 or 00) when specifying multiple types of the same product class. For example, if your project includes both veneer and plastic laminate faced cabinets, writing one section for both saves repetition and eliminates unintended differences between sections.

Narrow-scope sections make sense when products require distinctly different requirements or when clarity demands separation. The goal is reducing redundancy while maintaining precision.

Mastering the Three-Part Specification Format

Every technical specification section follows the same three-part structure established by CSI’s SectionFormat. This consistency means anyone familiar with the format knows exactly where to find specific information.

Part 1 — General

Part 1 sets the administrative and procedural foundation for the section. According to the Construction Specifications Institute’s SectionFormat guidelines, this section addresses:

• Summary — What work this section covers and related sections
• References — Applicable standards (ASTM, ANSI, etc.)
• Submittals — What the contractor must submit for approval
• Quality Assurance — Qualifications, certifications, pre-installation meetings
• Delivery, Storage, and Handling — How materials should arrive and be protected
• Warranty — Duration and coverage requirements

Part 1 extends and supplements Division 01 General Requirements. It shouldn’t duplicate statements found there but should add section-specific requirements.

Part 2 — Products

Part 2 defines what materials, equipment, and products will be incorporated into the work. This section specifies:

• Manufacturers — Acceptable sources for products
• Materials — Physical properties, compositions, grades
• Performance Requirements — Functional criteria products must meet
• Fabrication — Shop assembly requirements
• Source Quality Control — Factory testing and inspection

This is where you name specific products, establish performance criteria, or describe material characteristics. As EPRO’s specification guide notes, Part 2 includes “material standards and requirements, performance characteristics of these materials, and criteria for acceptable alternatives, if any exist.”

When specifying laminate panels, for example, Part 2 would identify acceptable manufacturers, specify panel core types, define surface durability requirements, and list acceptable colors and patterns. Quality manufacturers like KML Designer Finishes provide specification assistance and three-part guide specs that designers can adapt to project requirements.

Part 3 — Execution

Part 3 describes how the products from Part 2 will be installed. This section covers:

• Examination — Verifying conditions before installation begins
• Preparation — Surface prep, priming, conditioning
• Installation — Methods, tolerances, sequencing
• Field Quality Control — Testing and inspection during construction
• Cleaning — Interim and final cleaning requirements
• Protection — Protecting installed work until substantial completion

Part 3 specifies the quality of workmanship required without dictating the contractor’s specific processes. You establish the results expected, not the means and methods to achieve them.

How the Three Parts Work Together

The three-part format creates a logical flow: Part 1 establishes administrative requirements, Part 2 defines what you’re getting, and Part 3 explains how it gets installed. When questions arise, reviewers know exactly where to look.

This standardization also means anyone picking up your specifications—even mid-project—can navigate them efficiently. Consistency builds confidence and reduces errors.

Choosing Your Specification Approach

How you write specifications determines how much control you retain over product selection. Understanding your options helps you match your approach to project requirements.

Proprietary Specifications — Maximum Control

Proprietary specifications name specific products, systems, or manufacturers that must be used. According to Procore’s specification guide, proprietary specs “refer to specific products that must be used, like light fixtures, paint colors and countertop materials.”

A closed proprietary specification prohibits substitutions entirely. You specify exactly what you want, and that’s what gets installed. This approach works well when:

• Matching existing installations
• Exact duplication matters for design continuity
• You’ve tested products and know they perform
• The client has specific brand preferences

The downside? Closed specs can limit competition, increase prices, and create problems if products become unavailable.

Performance Specifications — Outcome-Focused

Performance specifications focus on the ends to be achieved, not the means of achieving them. You define what the product must do, not which brand to buy.

For example, instead of naming a specific laminate manufacturer, you might specify:

• Surface hardness minimum (NEMA LD3 Test 3.4)
• Chemical resistance requirements
• Color and pattern range
• Warranty duration

Performance specs are considered “open” because any manufacturer meeting the criteria can compete. This approach works well for public projects requiring competitive bidding or when multiple products genuinely meet your requirements.

The challenge? You must define performance criteria precisely enough to evaluate submissions fairly. Vague performance requirements invite disputes about whether products truly comply.

Prescriptive Specifications — Method-Focused

Prescriptive (or descriptive) specifications provide detailed instructions on exactly which materials, products, and installation methods must be used. As Document Crunch’s analysis explains, prescriptive specs “outline, step by step, how contractors should perform the work.”

This approach benefits projects where uniformity and predictability are essential. The contractor follows a precise procedure with minimal deviation. However, prescriptive specs place more liability on the designer if problems arise—you specified exactly what to do, so issues become your responsibility.

Basis of Design Specifications — The Hybrid Approach

The most common approach in commercial interiors combines proprietary and performance elements. Basis of design specifications identify a preferred product but allow equivalent alternatives.

You name the product that informed your design, then define the characteristics alternatives must match. This balances design control with competitive pricing and availability flexibility.

When to Use Each Type

Consider these factors when choosing your approach:

• Budget constraints favor open/performance specs that encourage competition
• Design-critical applications favor proprietary specs for control
• Public projects often require open specs by law
• Existing conditions may require proprietary specs to match
• Client preferences may dictate specific manufacturers

Most projects use a combination. High-visibility finishes might be proprietary. Concealed materials might be performance-based. The key is matching your approach to what matters most for each application.

The “Or Equal” Dilemma — Substitution Language That Works

Why “Or Equal” Creates Confusion

Few phrases generate more disputes than “or equal.” As specification consultant Liz O’Sullivan notes, “Or equal” means something different to everyone. Sometimes it’s defined in the documents. Sometimes it’s not. When undefined, the phrase relies on a “generally-accepted understanding” that doesn’t actually exist.

Writing Effective Substitution Clauses

Better substitution language defines exactly what “equal” means for your project. Consider specifying:

• The specific characteristics that alternatives must match
• How and when substitution requests must be submitted
• Who evaluates and approves substitutions
• What documentation substitution requests must include
• Whether cost differences are included in base bid

Defining Salient Characteristics for Evaluation

When you name a product with substitution allowed, list the salient physical, functional, or performance characteristics that alternatives must meet. For example:

“Floor tiles shall be [Manufacturer], style [Model], color [Name], or equal meeting the following: porcelain body, minimum 0.50 coefficient of friction, minimum 7 Mohs hardness, color range within specified sample.”

This language gives contractors clear criteria for proposing alternatives and gives you objective grounds for evaluation.

Pre-Bid vs. Post-Bid Substitution Requests

Many specifications require substitution requests before bidding, with approved alternatives issued via addendum to all bidders. This approach ensures competitive pricing reflects actual products.

Post-bid substitutions create complications. The contractor priced the specified product, so substitution savings may not flow to the owner. Review takes time that may delay construction. Consider whether your project benefits from pre-bid substitution processing.

Public Project Requirements

Public projects often mandate open specifications that allow any product meeting stated requirements. Some jurisdictions treat all specifications as including “or equal” regardless of what’s written. Understanding local requirements prevents specification language that conflicts with procurement rules.

Coordinating Specifications and Drawings

The Hierarchy of Contract Documents

Standard contracts establish document hierarchy for resolving conflicts. Typically, the order runs: agreement, modifications, supplementary conditions, general conditions, specifications, drawings. Specifications generally govern over drawings for quality and material requirements.

Understanding this hierarchy matters. If your drawings show one ceiling height and specifications state another, the specification typically prevails. Coordinate carefully to prevent conflicts that put contractors in impossible positions.

Common Coordination Failures

AORBIS research identifies the most common coordination failures:

• Poor communication between teams working on different parts of the project
• Last-minute changes to drawings without updating specifications (or vice versa)
• Copy-paste mistakes from previous projects with different requirements
• Missing cross-references that leave contractors hunting for related information

These failures generate RFIs, delays, and disputes that everyone involved would rather avoid.

Cross-Referencing Best Practices

Effective cross-referencing connects related information across documents. In specifications, reference:

• Related specification sections by number and title
• Drawing sheets where products appear
• Detail numbers showing installation conditions
• Schedules containing finish selections

In drawings, reference specification sections that govern materials and installation. This bidirectional linking helps everyone find complete information quickly.

Version Control and Change Management

Documents evolve throughout design. Without rigorous version control, outdated specifications circulate while current versions exist elsewhere. Establish clear protocols for:

• Dating all documents
• Tracking revision history
• Distributing updates to all parties
• Confirming receipt of current versions

Cloud-based project management platforms help, but discipline matters more than technology.

Writing Clear Submittal Requirements

What Submittals Should Include

Submittals allow contractors to demonstrate their understanding of your requirements before proceeding with work. According to Procore’s submittal guide, submittals “provide another level of detail usually not included as part of the design documents.”

Clear submittal requirements specify:

• What types of submittals each section requires
• What information each submittal must contain
• How submittals should be formatted and transmitted
• How long review will take
• What constitutes acceptable versus rejected submittals

Shop Drawings vs. Product Data vs. Samples

Different submittals serve different purposes:

• Shop drawings show fabrication details, dimensions, and installation conditions
• Product data includes manufacturer literature, specifications, and test reports
• Samples provide physical examples of materials, colors, and finishes

Specify which types apply to each product. Requiring shop drawings for simple products wastes time. Omitting samples for visible finishes invites surprises.

Setting Realistic Review Timelines

Submittal review takes time. Complex shop drawings for custom millwork may require multiple review cycles. Standard products with manufacturer data may move quickly.

Specify review timelines that reflect actual complexity. Unrealistic deadlines pressure reviewers into approving inadequate submittals or create bottlenecks that delay construction.

Approval Language That Protects You

The language you use when approving submittals matters legally. Standard practice reviews submittals “for conformance with design intent” rather than approving every detail. This acknowledges that contractors remain responsible for dimensions, quantities, and construction means.

Avoid approval stamps that could be interpreted as assuming responsibility beyond design intent. Consult your professional liability advisor about appropriate language.

Common Specification Errors and How to Avoid Them

Copy-Paste Syndrome

The UCOP Facilities Manual lists numerous errors that stem from copying previous project specifications without careful review:

• References to documents that don’t exist on the current project
• Requirements for alternates without corresponding bid form entries
• Section references that don’t match current organization
• Project-specific language that doesn’t apply

Every pasted specification requires thorough review to remove project-specific artifacts and update references.

Conflicts Between Specs and Drawings

When specifications refer to drawings for information—like contract limits, locations, or dimensions—that information must actually appear on the drawings. Referencing nonexistent information creates confusion and RFIs.

Similarly, drawings referencing specification sections that don’t exist leave contractors without necessary quality information.

Incomplete or Ambiguous Language

Common language problems include:

• Words missing from sentences
• Sentences missing from paragraphs
• Statements that conflict with themselves
• Undefined terms used without explanation
• References to standards without edition dates

Read specifications aloud. Ambiguities that slip past silent reading often become obvious when spoken.

Specifying Means and Methods

Specifications should establish required results, not dictate how contractors achieve them. Assigning work to specific subcontractors circumvents the general contractor’s responsibility for construction means and methods.

For example, requiring “the electrical subcontractor” to make connections to door hardware may conflict with union rules, void warranties, or simply annoy contractors who organize work differently.

Missing References to Standards

Industry standards provide objective quality criteria. References to ASTM, ANSI, and other standards establish testable requirements. But incomplete references create problems:

• Citing standards without specifying which edition applies
• Referencing tests without identifying acceptable results
• Naming standards that don’t exist or have been superseded

Verify every standard reference for accuracy and completeness.

Sustainability Documentation Gaps

Modern projects increasingly require sustainability documentation—EPDs, HPDs, FSC certifications, VOC testing. BluEnt’s specification analysis notes that “incorrect or incomplete specs for sustainability features lead to failures or non-compliance.”

Specify exactly what documentation contractors must submit to verify sustainability compliance. Generic requirements invite disputes about what actually satisfies them.

The RFI Connection — How Good Specs Reduce Questions

What Triggers RFIs

RFIs arise when contractors encounter unclear, missing, or conflicting information in contract documents. According to Smartsheet’s construction RFI guide, common triggers include:

• Design coordination issues between disciplines
• Constructability concerns about specified details
• Ambiguous or incomplete requirements
• Conflicts between drawings and specifications
• Missing information needed to proceed

Every ambiguity in your specifications potentially generates an RFI that costs time and money to resolve.

The Difference Between RFIs, Submittals, and Specifications

Understanding how these documents interact helps you write better specifications:

• Specifications establish requirements and serve as binding contract documents
• Submittals demonstrate contractor’s intent to comply with specifications
• RFIs clarify gaps or conflicts in contract documents

As RedTeam’s construction guide explains, “Specifications set the rules of the game. Submittals show how the contractor plans to meet those rules. RFIs keep the rules clear when questions come up.”

Responding to RFIs Without Changing the Contract

RFIs request clarification—they don’t authorize changes. According to AIA Document A201, changes to contract sum or time require formal change orders, not RFI responses.

When responding to RFIs, clarify design intent without inadvertently expanding scope. If clarification reveals that additional work is needed, that work requires proper change documentation.

Building Your Specification Library

Master Specifications vs. Project-Specific Specs

Master specifications are template sections maintained for common project types. They establish your firm’s standard language, preferred manufacturers, and quality expectations. Project-specific specs adapt masters to individual project requirements.

Conspectus recommends that fewer than 200 architectural master specs suffice for most practices when using broad-scope sections. The key is maintaining these masters with current standards, products, and language.

Working with Manufacturer Guide Specifications

Quality manufacturers provide guide specifications that designers can adapt to their projects. These resources save time and ensure accurate product information.

When using manufacturer guide specs, verify that content matches current products and that language coordinates with your project’s Division 01 requirements. Manufacturer specs often need adaptation to match your firm’s style and project requirements.

Quality Assurance Reviews Before Issue

Before issuing specifications, conduct systematic reviews:

• Verify all cross-references resolve correctly
• Confirm coordination between specs and drawings
• Check that standard references cite current editions
• Review submittal requirements for completeness
• Ensure substitution language matches project intent

Fresh eyes catch errors that writers miss. Having someone unfamiliar with the project review specifications reveals assumptions and ambiguities.

Continuous Improvement Through Post-Project Review

After project completion, review what worked and what didn’t:

• Which specifications generated the most RFIs?
• Where did substitution disputes arise?
• What coordination problems emerged?
• Which products performed as expected?

Feed lessons learned back into master specifications. Each project improves your library for the next one.

Specification Checklist for Interior Design Projects

Before issuing specifications, verify:

• All sections follow three-part format consistently
• Division numbers match current MasterFormat
• Cross-references between sections resolve correctly
• Drawing references match actual sheet numbers
• Standard references cite current editions
• Submittal requirements specify what’s needed for each product
• Substitution language defines evaluation criteria
• Performance requirements include test methods and acceptable values
• Warranty requirements match project duration expectations
• Sustainability documentation requirements are specific and verifiable
• Quality assurance provisions address installer qualifications
• Coordination with related sections is complete and bidirectional

FAQs

What’s the difference between specifications and drawings? Drawings show location, dimensions, and relationships. Specifications define quality, materials, and execution standards. Together they form complete construction instructions. When conflicts arise, specifications typically govern material and quality requirements.

Who is responsible for writing specifications? Responsibility varies by firm size. Large firms may have dedicated specifiers. Smaller firms often assign specification writing to project architects or principals. Some firms engage independent specification consultants for complex projects.

Can I just copy specifications from previous projects? Copying saves time but creates risk. Previous project specs contain project-specific references, outdated standards, and requirements that may not apply. Every copied spec requires thorough review and updates for current conditions.

What certifications help with specification writing? The Construction Documents Technologist (CDT) certification from CSI provides foundational specification knowledge. The Certified Construction Specifier (CCS) designation indicates advanced expertise. Both demonstrate commitment to specification quality.

How often should I update master specifications? Review master specifications annually at minimum. Update immediately when standards change, products are discontinued, or post-project reviews reveal problems. Current masters prevent errors from propagating across projects.