What Are Architectural Specifications?

Architectural specifications are written documents that describe the materials, installation standards, product types, and performance criteria required to complete a construction project. While architectural drawings show the layout and quantity of components, specifications define the quality and execution of those components.

Specifications are a core part of the contract documents. Alongside drawings and general conditions, they provide legal and technical standards for the contractor to follow. In practice, specifications serve multiple functions: they communicate design intent, enforce building codes, guide material selection, and reduce ambiguity in the construction process.

Specifications are not optional. They are used in public and private projects alike and are typically issued during the Construction Documents phase. They may be reviewed by permitting authorities, consultants, contractors, and subcontractors, and often determine how the project is priced and constructed.

How Specifications Fit Into the Project Lifecycle

Specifications evolve in detail as the project progresses. They may start as informal narratives and end as structured technical manuals. By the time construction begins, the specifications are part of the official bid set or construction contract.

Specifications are updated through addenda or revisions when design changes occur during construction.

Types of Architectural Specifications

Specifications may be organized by the method of describing the work. Each approach allocates different levels of responsibility to the architect and contractor.

Proprietary Specifications

Proprietary specifications name specific manufacturers, models, or product lines required for construction. This type of specification is often used when aesthetic consistency, system compatibility, or known performance are essential.

Proprietary specs may be either:

• Closed: No substitutions are permitted. The contractor must provide the exact product specified.

• Open: Alternate products may be submitted for approval if they are functionally equivalent and meet the same standards.

Examples of Closed Proprietary Specifications

Closed proprietary specs are common when performance history matters, such as:

• Matching existing building systems

• Meeting strict warranty requirements

• Aligning with owner's facility standards

• Preserving design intent in high-visibility elements

However, this approach may reduce bid competition, raise material costs, or delay schedules due to lead times or limited distribution.

In public-sector projects, closed proprietary specifications are often restricted by law to encourage competitive bidding. When allowed, justification or “basis-of-design” language may be required.

Performance Specifications

These define the required results, such as fire resistance, energy efficiency, or structural strength, without prescribing the exact product or method. This allows contractors to choose solutions that meet or exceed the required outcomes.

Performance specifications are useful when innovation or flexibility is desired, but they must include clear metrics and testing standards to ensure enforcement.

Descriptive Specifications

These describe the characteristics of materials, components, and installation without naming a brand. For example, a descriptive spec may require wood of a certain species, grain, thickness, and finish. This method places full responsibility on the specifier to define requirements thoroughly.

Reference Specifications

These point to existing industry standards, such as ASTM, ANSI, or UL, to define quality or performance. Referencing third-party standards can improve clarity, avoid redundancy, and ensure up-to-date practices without rewriting technical content.

MasterFormat and Section Organization

Most architectural specifications in the United States follow MasterFormat, a standardized organizational system developed by the Construction Specifications Institute (CSI). MasterFormat divides construction work into numbered divisions and sections for consistency and coordination.

Each division groups related trades or scopes. Specifications are written using a three-part format within each section.

Each section typically includes:

• Part 1 – General: Administrative requirements, submittals, quality assurance, mockups

• Part 2 – Products: Acceptable materials, manufacturers, finishes, and performance data

• Part 3 – Execution: Installation procedures, tolerances, field quality control, protection

This structure helps teams locate relevant information quickly and keeps documentation consistent across disciplines.

Who Writes Specifications?

Specification authorship depends on firm size, project complexity, and delivery method.

• In smaller firms, the project architect or job captain often writes or assembles specifications using templates or software.

• In larger firms, technical architects or dedicated specifiers lead this task.

• On complex projects, consultants may be hired to develop and coordinate the full specification set.

Specification writers need to interpret the design intent accurately and translate it into enforceable language. They must also stay current on product certifications, sustainability requirements, and industry standards.

Software tools such as BSD SpecLink, Deltek Specpoint, and e-SPECS are commonly used to manage formatting and database content. These platforms help with consistency, cross-referencing, and version control.

Coordinating Drawings and Specifications

Drawings and specifications must align. If the two contradict each other, it can create confusion, delays, or disputes during construction.

For example, a door may be shown on drawings with a particular hardware set, but the specifications list a different set. Or a wall type may be detailed with specific fire resistance, while the specs refer to an outdated system. These mismatches create risk and erode trust.

Spec coordination is often included in internal QA/QC workflows. Reviews may occur during Construction Documents or prior to bid issuance. On BIM-enabled projects, some firms link specifications directly to model elements using structured parameters.

Specifications as Contract Documents

Architectural specifications are legally binding components of the construction contract. Alongside the drawings and general conditions, they are enforceable by the owner and may be referenced in disputes, claims, or audits.

If there is a conflict between the drawings and specifications, the governing priority is typically defined in the general conditions. In some contracts, the specification takes precedence. In others, the more stringent requirement applies.

To reduce risk, language in specifications must be:

• Consistent and specific

• Based on measurable criteria

• Aligned with referenced standards and codes

Terms like “shall,” “must,” and “provide” create binding obligations. Terms like “as required,” “as selected,” or “per architect” introduce ambiguity and should be minimized.

Best Practices in Specification Writing

Specification errors can lead to cost overruns, delays, or legal liability. For this reason, many firms treat specification writing as a parallel discipline to design and modeling.

Further Resources

If you're developing architectural specifications or coordinating them with BIM and project documentation, these guides can help:

• Everything You Ever Wanted to Know About Construction Documents →

• Architectural Room Data Sheets Explained →

• The Door and Window Schedule Process Explained →

• Design Development Phase and Coordinating Around the Revit Model →

• Construction Administration Phase and Closing Out the Revit Model →