What Is a Basis of Design Specification — And Why It Matters for Building Product Manufacturers
The Document That Gets Your Product Built Into a Project
If you manufacture building products — flooring, roofing systems, wall assemblies, hardware, fixtures, glazing, or anything else that ends up in a construction project — there is one document that determines whether an architect specifies your product or your competitor’s.
It’s called a basis of design specification. And most manufacturers either don’t have one, have one that’s outdated, or have one that isn’t written the way architects actually use specifications.
This post explains exactly what a basis of design specification is, why it matters, how architects use it, and what a well-written one needs to include to actually move your product from a manufacturer’s catalog into a project manual.
What Is a Basis of Design Specification?
A basis of design specification — often called a BOD spec — is a written technical document that establishes a specific product as the standard of quality and performance for a construction project. When an architect names your product as the basis of design, they are saying: this is the product we designed around, and any substitution must match or exceed its performance in every measurable way.
It is one of the most powerful positions a building product can occupy in a project. Being named basis of design means your product is the benchmark. Every competitor who wants to be considered has to prove they measure up to you — not the other way around.
It looks something like this in practice:
“Basis of Design: [Manufacturer Name], [Product Name and Number]. Substitutions will be considered provided the requesting party demonstrates compliance with all performance requirements specified herein.”
That language — simple as it looks — is the result of an architect trusting your product enough to design their project around it.
How a Basis of Design Specification Differs From a Generic Spec
To understand why being named basis of design matters, it helps to understand the range of ways an architect can specify a product.
Proprietary specification. Names one manufacturer and one product with no substitutions permitted. Common on projects where the owner has selected a specific product or where performance requirements are so specific that only one product qualifies.
Basis of design specification. Names one product as the design standard but allows substitutions that can be demonstrated to meet the same performance criteria. This is the most common approach on competitive bid projects and gives the architect design control while maintaining bid competition.
Descriptive specification. Describes the required performance, materials, and standards without naming any manufacturer. Any product meeting the description qualifies. This gives manufacturers the opportunity to compete but gives your product no advantage over any other that meets the criteria.
Reference standard specification. Calls out an industry standard — an ASTM standard, for example — and requires compliance with it. Similar to descriptive in that no manufacturer is named.
The basis of design position is the sweet spot for most manufacturers. It gets your product named in the document, establishes your specifications as the benchmark, and keeps you in the project even on competitively bid work.
Why Architects Use Basis of Design Language
Architects name a product as basis of design for a specific reason: they designed around it.
They selected your dimensions, your performance data, your installation requirements, and your aesthetic characteristics when they were making design decisions. Your product is embedded in their drawings, their details, and their project in ways that may not be immediately obvious from reading the spec alone.
When a contractor or owner pushes for a substitution, the architect’s job is to evaluate whether the proposed alternative truly matches what was designed. The basis of design specification gives them the tool to do that evaluation — because it defines exactly what your product delivers, in measurable, documentable terms.
This is why a well-written manufacturer specification matters so much. If your product data is vague, inconsistently formatted, or missing key performance metrics, the architect cannot use it effectively as a basis of design benchmark. They may still like your product. But they’ll specify it loosely — or not at all.
What a Well-Written Basis of Design Specification Includes
A manufacturer’s guide specification written for basis of design use follows the same 3-part format that architects use for their project specifications. This is not a coincidence — it’s designed so that an architect can take your specification, edit it for their project requirements, and drop it directly into their project manual.
The easier you make that process, the more likely your product gets specified.
Part 1 — General
This section covers the administrative and performance framework for your product:
- Scope of the section — what your product is and what work it covers
- Related sections the architect should coordinate with
- Reference standards your product complies with — ASTM, ANSI, UL, or other applicable industry standards
- Submittal requirements — what documentation the architect should require from the contractor, including product data sheets, samples, test reports, and installation instructions
- Quality assurance language — installer qualifications, pre-installation meetings, mock-up requirements if applicable
- Warranty terms — both manufacturer warranty and any required installer warranty
Part 2 — Products
This is the heart of the basis of design specification. It needs to be specific enough to establish your product as the benchmark while being written in language that describes performance requirements rather than just catalog numbers:
- Manufacturer name and contact information
- Product name, model number, and available configurations
- Materials and composition — what your product is made of, to what standard
- Performance requirements — fire ratings, acoustic ratings, structural performance, moisture resistance, thermal values, or whatever metrics are relevant to your product category
- Finish options and available configurations
- Acceptable substitutions language — or direction to the architect on how to evaluate substitution requests
The performance requirements section is the most important part of a basis of design specification. These are the numbers a substitution has to match. If your spec doesn’t include them, there’s no measurable standard for the architect to apply when evaluating a competitor’s request to substitute.
Part 3 — Execution
This section documents how your product gets installed correctly:
- Examination requirements — what substrate or site conditions must be verified before installation begins
- Preparation requirements — surface prep, priming, acclimation, or other pre-installation steps
- Installation methods — sequence, fastening, adhesive, tolerances, and any manufacturer-required procedures
- Field quality control — inspection requirements, testing, and acceptance criteria
- Protection requirements — how the installed product should be protected until project completion
- Cleaning requirements at substantial completion
A complete Part 3 serves two purposes. It tells the contractor how to install your product correctly. And it gives the architect language to hold the contractor accountable if installation doesn’t meet your requirements.
The Most Common Mistakes Manufacturers Make With Guide Specifications
Writing marketing copy instead of technical language. A guide specification is not a brochure. Architects are trained to read specifications as technical documents. Language like “industry-leading performance” or “superior quality” means nothing in a spec context and signals to a specifier that the document wasn’t written by someone who understands how specifications work.
Leaving performance requirements vague. If your spec says “high acoustic performance” instead of “STC 52 minimum” or “impact sound rating FIIC 51 minimum,” you have not written a measurable standard. A competitor can claim to meet “high acoustic performance” with no way to verify it. Specific numbers protect your product.
Not following the 3-part format. Architects may drop manufacturer guide specs directly into their project manuals. If your document isn’t formatted in 3-part structure, it creates editing work for the specifier. Editing work is friction. Friction reduces the likelihood your product gets specified.
Outdated reference standards. ASTM standards, building codes, and industry standards are updated regularly. A guide specification referencing superseded standards sends a signal that your technical documentation isn’t maintained — and raises questions about whether your product data is current.
Missing submittal requirements. If your guide spec doesn’t tell the architect what submittals to require, the contractor may not provide product data, installation instructions, or samples. Without those submittals, quality control breaks down in the field — and your product may be installed incorrectly, creating warranty and liability issues that reflect on your brand.
No installer qualification language. For products that require trained or certified installers, leaving qualification requirements out of the specification opens the door to incorrect installation by unqualified contractors. Your warranty may not cover failures resulting from improper installation — but that distinction matters a lot less when the project is in dispute and your product’s name is on the spec.
How Architects Find and Use Manufacturer Guide Specifications
Understanding how architects actually encounter and use manufacturer specifications helps you write one that works.
Most architects find manufacturer specifications through one of three paths: manufacturer websites, building product databases, or direct outreach from manufacturer representatives. Of these, the website and database paths are the most important for search visibility — because they happen before any sales conversation.
When an architect is in the middle of writing a project manual and needs a specification for a product category, they search. They may search Google directly. They may search a product database. They may ask an AI tool. What they’re looking for is a guide specification they can download, edit, and use.
If your guide specification is not findable, not downloadable, or not formatted correctly when they find it, you’ve lost the specification opportunity before your sales team was ever involved.
This is why the technical quality and findability of your guide specification is a direct driver of how often your product gets specified — and ultimately, how often it gets purchased.
Basis of Design and Substitution Requests
One of the most practical implications of being named basis of design is how it shapes the substitution process during bidding and construction.
When a contractor wants to substitute a different product, they typically submit a formal substitution request to the architect. The architect evaluates whether the proposed product meets the performance requirements established in the specification.
If your specification is well written with clear, measurable performance requirements, the architect has an objective framework for that evaluation. Products that don’t meet your numbers don’t get approved. Products that do meet your numbers may be approved — but they had to prove it against your standard.
If your specification is vague, that evaluation becomes subjective. The architect may approve substitutions they wouldn’t have approved with clearer language. Your competitive position weakens every time a substitution goes through on a project where your product was the basis of design.
A well-written basis of design specification is not just about getting specified. It’s about staying specified through the construction phase.
A Note on Specification Packages for Architects
While this post is written primarily for building product manufacturers, it’s worth noting that architects — particularly those in solo practice or small firms — often rely on professionally written specification templates as a starting point for their project manuals.
When a manufacturer’s guide specification is well written, clearly formatted, and easy to edit, architects incorporate it directly. When it isn’t, they fall back on generic templates that may not name any manufacturer at all — or may name a competitor whose documentation was easier to work with.
If you’re a manufacturer investing in the quality of your guide specification, you’re also making it easier for the architects using downloadable specification packages to incorporate your product into their projects. The two documents work together — your guide spec provides the product-specific content, and the architect’s project specification provides the project-specific framework.
The Bottom Line for Building Product Manufacturers
A basis of design specification is not a marketing document. It is a technical instrument that determines whether your product gets built into projects — and whether it stays in those projects when substitution pressure hits during bidding and construction.
The architects who specify your product are looking for two things: a product that performs, and documentation that makes it easy to specify correctly. The first is your engineering team’s responsibility. The second is your technical writing team’s — or your specification consultant’s.
A well-written, properly formatted, current, and technically complete guide specification is one of the highest-return investments a building product manufacturer can make in their specification and sales program. It works while your sales team sleeps. It gets your product into project manuals in markets your reps have never visited. And it establishes your product as the standard that every competitor has to measure up to.
That’s what a basis of design specification does. And that’s why it’s worth getting right.
Frequently Asked Questions
What does “basis of design” mean in a specification? Basis of design means a specific manufacturer’s product has been named as the quality and performance standard for that specification section. Any proposed substitution must demonstrate it meets or exceeds the named product’s performance in all measurable respects.
Can a contractor substitute a basis of design product? Yes, substitutions are typically permitted unless the specification is written as proprietary with no substitutions allowed. However, the contractor must submit a formal substitution request and demonstrate compliance with all performance requirements. A well-written basis of design specification makes that evaluation objective and measurable.
How is a basis of design specification different from a proprietary specification? A proprietary specification names one product and permits no substitutions. A basis of design specification names one product as the performance benchmark but allows substitutions that can be demonstrated to meet the same criteria. Basis of design is more common on competitively bid projects.
How do I get my product named as basis of design? The path to being named basis of design typically runs through your manufacturer’s representative, direct architect outreach, product presentations, and the quality of your technical documentation. Architects specify products they trust and can document easily. A well-written guide specification in 3-part format is a foundational requirement.
How often should a manufacturer update their guide specification? Any time a product line changes, reference standards are updated, or installation requirements are revised. At minimum, guide specifications should be reviewed annually. An outdated spec with superseded standards or discontinued products creates problems for architects who use it and reflects poorly on your technical credibility.
Does every building product need a basis of design specification? Any product that is specified by architects — rather than selected entirely by contractors or owners — benefits from a manufacturer guide specification written for basis of design use. If architects are making decisions about your product category, you need documentation that supports those decisions.
Written by
Michael Chen