A common question from manufacturers is whether developing product specifications can qualify as research and development for the federal R&D tax credit under Section 41. The short answer is that developing product specifications may constitute qualified research when the work involves a technical uncertainty about what specifications are achievable and a process of experimentation to determine them. Writing specifications from known data or established standards generally is not qualified research. This page explains the framework in general terms. It is educational and is not individualized advice. For the foundational framework, see our page on qualified research.
When Specification Development May Warrant Review
Developing product specifications may warrant review when the work involves a genuine technical uncertainty about what performance, tolerance, material, or reliability targets are achievable, and a process of experimentation to determine them. Under the four-part test, the work must be for a permitted purpose (developing or improving a business component), be technological in nature, be intended to eliminate uncertainty, and be conducted through a process of experimentation.
Common scenarios that may warrant review include:
- Performance specification development — evaluating alternative designs or materials to resolve uncertainty about what performance level a new product can achieve, where the specification is not known in advance.
- Dimensional tolerance development — testing alternative process parameters or tooling to resolve uncertainty about what tolerances can be consistently achieved in production.
- Material specification development — evaluating alternative materials to resolve uncertainty about which material can achieve the required combination of properties.
- Reliability target development — testing alternative designs or processes to resolve uncertainty about what reliability level can be achieved.
In each case, the question is whether the work evaluates alternatives to resolve a technical uncertainty about what specification is achievable, not merely whether a specification was written.
Specifications as a Result of Experimentation
A key insight is that specifications can be the result of experimentation, not just the input to it. When a company is developing a new product and is uncertain what performance, tolerance, or reliability level is achievable, the process of experimentation may be directed at determining the specification itself. The company tests alternatives, measures what is achievable, and sets the specification based on the results. This is different from writing a specification from known data or established standards, where the specification is an input, not an output.
Writing Specifications from Known Data
A central distinction is between developing specifications through experimentation and writing specifications from known data:
- Writing specifications from known data — setting specifications based on established standards, supplier data, or prior experience. There is no technical uncertainty about what is achievable; the specification is selected from known options. This generally is not qualified research.
- Developing specifications through experimentation — determining what specification is achievable by evaluating alternatives and testing, where the achievable level is uncertain at the outset. This may warrant review as qualified research.
The distinction turns on whether there is a genuine technical uncertainty about what is achievable. A company that is simply selecting a specification from a standard or a supplier's data sheet is generally not conducting research. A company that is determining what specification a new product can achieve through experimentation may be.
Hypothetical Example
Consider a manufacturer that is developing a new type of sensor and is uncertain what accuracy level the sensor can achieve across its operating temperature range. The company evaluates alternative sensor designs, tests each across the temperature range, measures the achievable accuracy, and sets the product specification based on the results. This systematic evaluation of alternatives to determine an achievable specification may warrant review as qualified research.
By contrast, if the same manufacturer writes a specification for a new version of an existing product by selecting tolerances from an established standard, that is specification writing from known data, not research.
This example is illustrative only and does not state that the activity definitely qualifies.
Documentation That May Help
Records that can help support specification development claims include test plans identifying the uncertainty and alternative designs or materials, test results showing what performance was achieved, records of how results informed the specification, and records connecting the specification to the specific business component. For more, see our page on R&D tax credit documentation.
Key Takeaway
Developing product specifications may constitute qualified research when the work involves a technical uncertainty about what specifications are achievable and a process of experimentation to determine them. Writing specifications from known data or established standards generally is not qualified research. Because the distinction is fact-specific, professional review is appropriate before claiming the credit.