One of the most important distinction pages for the R&D tax credit is the difference between routine testing and R&D experimentation. The short answer is that routine testing — quality assurance, inspection, and validation against known specifications — generally is not qualified research, because it does not involve eliminating a technical uncertainty through a process of experimentation. R&D experimentation — evaluating alternatives to resolve a technical uncertainty, often using prototypes and systematic testing before commercial production — may be qualified research. This page explains the distinction with examples. It is educational and is not individualized advice. For the foundational framework, see our page on qualified research.
Routine Testing
Routine testing is testing performed to verify that a product, process, or component conforms to established specifications. The characteristics of routine testing include:
- Known specification — the target or standard is established and known.
- Known test method — the procedure for testing is established and known.
- Expected result — the expected outcome is known (pass or fail against the specification).
- Verification, not evaluation — the testing verifies conformance, it does not evaluate alternatives.
- No technical uncertainty — there is no question about the capability, method, or design of the business component; the question is whether a particular unit meets the known standard.
Routine testing includes quality assurance testing, incoming inspection, in-process inspection, final inspection, batch testing, and routine validation. These activities, by themselves, generally are not qualified research because the elimination-of-uncertainty and process-of-experimentation elements are generally not satisfied.
R&D Experimentation
R&D experimentation is testing performed to evaluate alternatives and resolve a technical uncertainty about a business component. The characteristics of R&D experimentation include:
- Technical uncertainty — there is a question about the capability, method, or appropriate design of the business component that is not established at the outset.
- Alternatives — the testing evaluates one or more alternatives (different designs, materials, configurations, or approaches).
- Evaluative process — the testing is an evaluative process capable of evaluating more than one alternative, not merely verifying conformance.
- Reliance on scientific or engineering principles — the process fundamentally relies on principles of the physical or biological sciences, engineering, or computer science.
- Development context — the testing occurs during the development of a business component, typically before commercial production.
R&D experimentation may include prototype testing, pilot runs, material substitution testing, process-improvement testing, and design-iteration testing. These activities may be qualified research, provided all four elements of the four-part test are satisfied.
The Key Distinction
The key distinction is not the type of testing (lab vs. field, destructive vs. nondestructive, sophisticated vs. simple) but the purpose and nature of the testing:
- Routine testing asks: "Does this unit meet the known specification?"
- R&D experimentation asks: "Which of these alternatives can achieve the uncertain result?"
If the testing is verifying conformance to a known standard, it is generally routine testing. If the testing is evaluating alternatives to resolve a technical uncertainty, it may be R&D experimentation. The same physical activity — running a test, collecting data, analyzing results — can be routine testing or R&D experimentation depending on the purpose and context.
Indicators of Experimentation
Several indicators tend to distinguish experimentation from routine testing:
- Prototypes — building and testing prototypes to evaluate alternatives suggests experimentation.
- Systematic testing of alternatives — testing multiple options against a target suggests experimentation.
- Iteration based on results — modifying the approach based on test results suggests experimentation.
- Pre-commercial-production timing — testing during development, before commercial production, suggests experimentation.
- Technical uncertainty documented — records identifying a question about capability, method, or design suggest experimentation.
The absence of these indicators does not automatically disqualify testing, and the presence of one or two does not automatically qualify it. The question is whether, on the whole, the testing is part of an evaluative process of alternatives directed at eliminating a technical uncertainty.
Hypothetical Examples
Routine testing example: A manufacturer produces a standard product to an established specification and tests each batch to verify that it meets the specification. The test method is established, the specification is known, and the expected result is known. This is routine quality control, not R&D experimentation.
R&D experimentation example: The same manufacturer is developing a new product and is uncertain whether an alternative material can achieve a required performance target. The company tests several alternative materials, evaluates the results, and modifies the design based on the findings. This is R&D experimentation — evaluating alternatives to resolve a technical uncertainty — and may warrant review as qualified research, provided the other elements are met.
These examples are illustrative only and do not state that any particular activity definitely qualifies.
Documentation That May Help
Records that can help distinguish routine testing from R&D experimentation include test plans describing the purpose (verification vs. evaluation of alternatives), records of the technical uncertainty, records of alternatives evaluated, records of how results informed design changes, and records showing when commercial production began. For more, see our page on R&D tax credit documentation.
Key Takeaway
The key distinction between routine testing and R&D experimentation is whether the testing evaluates alternatives to resolve a technical uncertainty (experimentation) or verifies conformance to known specifications (routine testing). Prototypes, systematic testing of alternatives, iteration based on results, and development before commercial production are indicators of experimentation. Because the distinction is fact-specific, professional review is appropriate before claiming the credit.