Hardwood SpecificationMATERIALS / RECORDS / COORDINATION(844) 524-3286
Define the requirement

Performance versus prescriptive hardwood specifications

Choose a writing approach that makes evidence and decision authority clear.

An unlettered specification binder and coordinated drawings beside a plain wood sample.
Illustrative context

Coordinate drawings, specification notes and the material reference.

Illustrative specification workspace. Blank records and samples do not establish product approval or acceptance criteria.

A performance requirement states an outcome and its verification method. A prescriptive requirement identifies the material or method. Many hardwood packages need both.

Separate the outcome from the selection

Begin with the use and the reason for each requirement. A visible surface may need an agreed appearance range, while an interface needs an identified profile and compatible attachment system. Avoid putting broad promises such as premium quality into the same field as measurable dimensions. They cannot be checked in the same way. Write the desired outcome first, then decide which material selections must be fixed to achieve the coordinated design. This makes a reviewer able to identify what can change and what requires a formal decision.

Name evidence before requesting it

Every performance statement needs an evidence path. Identify the document, sample, test report or professional review that will establish whether the proposed product addresses the requirement. A supplier brochure is useful product information but does not automatically establish project suitability. If a rating is required, record the exact requested rating and applicable configuration without assuming that a species name carries that rating. For prescriptive items, request the supplier's exact product designation, drawing and current instructions so the specified choice can be traced to an orderable item.

Resolve conflicts before issue

Mixed specifications can contradict themselves when a named system is paired with an unrelated installation detail. Review the product, interface and evidence requirements together before issuing the package. If the manufacturer instructions and a project detail differ, record the discrepancy and assign it to the responsible reviewer instead of silently selecting one. The brief should identify which matters are unresolved and what stops procurement. A completed drafting checklist means the questions were addressed in the record; it does not establish technical approval or authorize construction.

  • State the intended use
  • Identify fixed selections
  • Define evidence and reviewer
  • Record unresolved conflicts

Write a requirement that can actually be evaluated

Words such as premium, durable and high quality describe an intention but do not tell a supplier or reviewer how to evaluate an offer. A performance requirement identifies the result and the evidence needed to demonstrate it. A prescriptive requirement identifies the product, material or method to be used. Many useful specifications combine both, provided they do not contradict each other.

For hardwood, the distinction is practical. Naming a species is a material selection; it does not by itself define appearance, machining, moisture condition, fastening or suitability for every exposure. Requiring a particular profile drawing is prescriptive. Requiring a documented project-specific performance result needs the applicable evaluation basis and acceptance criteria, not a broad claim copied from a species description.

Match the requirement to its proof

Scroll sideways to read all columns. Keyboard: focus the table and use the arrow keys.

Match the requirement to its proof
Requirement typeA useful evidence requestWeak substitute
Product identityExact material and supplied product descriptionTrade name alone
GeometryReferenced drawing with actual dimensions and tolerancesMarketing rendering
AppearanceDefined sample range and review conditionsPremium grade without a definition
PerformanceApplicable report, scope and acceptance criterionUnqualified durability claim
ExecutionCoordinated instructions and assigned responsibilityInstall properly

The evidence request should be proportionate to the decision. Do not ask for a test report that cannot answer the stated question. Conversely, do not use an attractive sample as proof of structural, fire or exposure performance. The record should make clear which kind of approval each document supports.

Avoid a specification that defeats its own objective

A hybrid requirement can become inconsistent if it demands one exact product and also requires a result that product has not demonstrated. It can also leave a gap if it requests an outcome but assigns no responsibility for selecting the means. Review the clauses together instead of checking each sentence in isolation.

Consider an illustrative appearance requirement: the owner wants visible grain and accepts natural variation within an approved sample range. Adding a demand for perfectly uniform colour across every board would conflict with that stated intent unless the supplied treatment and selection scope can actually achieve it. Resolve the priority before requesting prices or samples.

Keep unresolved requirements visible in the draft

An incomplete field should read unresolved, with the question and responsible respondent attached. Do not fill a tolerance, test standard or exposure rating merely because the specification builder has a space for it. A precise unsupported number is harder to detect than an honest blank.

The USDA Wood Handbook supplies background on material behavior, not a completed project specification. The builder organizes the requirements chosen for the project. Use product identification, appearance grading and tolerances and verification to make the individual clauses reviewable before the draft is issued.

Evidence & scope

USDA Forest Products Laboratory — Wood Handbook ↗

General wood science context; chapters on lumber, moisture, fastening and finishing. Not a project specification or product approval.

Original planning guidance. References support their stated technical scope; examples and workflows do not establish product approval.