A common question is whether quality control (QC) testing counts for the federal R&D tax credit under Section 41. The short answer is that routine quality control testing — verifying that a known product meets established specifications — generally is not qualified research, because it does not involve eliminating a technical uncertainty through a process of experimentation. However, testing performed to resolve a technical uncertainty during development, through an evaluative process of alternatives, may warrant review. This page explains why "we test every batch" is not automatically R&D. It is educational and is not individualized advice. For the foundational framework, see our page on qualified research.
Why Routine QC Is Generally Not Qualified Research
Routine quality control testing is performed to verify that a product conforms to established specifications. The specification is known, the test method is known, and the expected result is known. There is no technical uncertainty about the capability, method, or appropriate design of the business component — the testing is verification, not experimentation. Because the elimination-of-uncertainty element and the process-of-experimentation element are generally not satisfied, routine QC testing generally does not constitute qualified research.
This is true even if the testing is rigorous, uses sophisticated equipment, or is performed by qualified engineers. The question is not whether the testing is sophisticated, but whether it is part of an evaluative process of alternatives directed at eliminating a technical uncertainty.
Post-Production Inspection
Section 41 and the Treasury Regulations address research conducted after commercial production begins. Post-production inspection — testing or inspecting products on a production line to verify quality — generally falls within the post-commercial-production exclusion. Even if the inspection discovers problems and the problems are solved on the line, routine production troubleshooting generally is not a process of experimentation directed at developing or improving a business component. For more on this boundary, see our page on qualified research.
When Development-Stage Testing May Warrant Review
Testing performed during the development phase — before commercial production — may warrant review when it is part of a process of experimentation directed at eliminating a technical uncertainty. For example, if a company is developing a new product and is uncertain whether a specific design can achieve a performance target, testing alternative designs to evaluate which achieves the target may be part of qualified research. The key distinctions are:
- Uncertainty — there is a genuine question about capability, method, or appropriate design.
- Alternatives — the testing evaluates one or more alternatives.
- Evaluation — the testing is an evaluative process, not merely verification against a known standard.
- Pre-production — the testing occurs during development, not after commercial production begins.
For a deeper treatment of this distinction, see our page on routine testing vs. R&D experimentation.
Hypothetical Example
Consider a food manufacturer that produces a baked product to an established recipe and tests every batch for moisture content to verify it meets the specification. This routine QC testing — verifying conformance to a known standard — generally is not qualified research, because there is no technical uncertainty and no process of experimentation.
Now consider the same manufacturer developing a new product line with an alternative flour blend, where the company is uncertain whether the blend can achieve the required texture. The company tests several alternative blends, evaluates the results, and modifies the formulation based on the findings. This development-stage testing — evaluating alternatives to resolve a technical uncertainty — may warrant review as qualified research, provided the other elements are met.
This example is illustrative only and does not state that the testing definitely qualifies.
IRS and Treasury Guidance
The Treasury Regulations (§1.41-4) describe a process of experimentation as an evaluative process designed to evaluate alternatives to resolve a technical uncertainty. Routine quality control — which evaluates conformance to a known standard rather than evaluating alternatives to resolve an uncertainty — generally does not fit this framework. The Instructions for Form 6765 identify routine testing and inspection among the activities that are generally not qualified research.
Documentation That May Help
For development-stage testing that may warrant review, records that can help include test plans describing the uncertainty and alternatives, test results, records of how results informed design changes, and records connecting the testing to specific business components. For routine QC, the distinction from qualified research is itself the documentation point — records showing that testing was routine verification, not experimentation, help clarify the boundary. For more, see our page on R&D tax credit documentation.
Key Takeaway
Routine quality control testing — verifying that a known product meets established specifications — generally is not qualified research, because it does not involve eliminating a technical uncertainty through a process of experimentation. Testing performed to resolve a technical uncertainty during development, through an evaluative process of alternatives, may warrant review. "We test every batch" is not automatically R&D. Because these determinations are fact-specific, professional review is appropriate before claiming the credit.