Documenting alternatives considered during R&D is central to substantiating the process-of-experimentation element of qualified research under Section 41. The Treasury Regulations describe a process of experimentation as an evaluative process designed to evaluate one or more alternatives to resolve a technical uncertainty. This page explains how to document alternatives in a way that can help support a credit claim. It is educational and is not individualized advice. For the underlying framework, see our page on process of experimentation.
Why Documenting Alternatives Matters
The process-of-experimentation element looks for an evaluative process capable of evaluating alternatives. Records that show what alternatives were considered, why they were considered, and how they were evaluated can help demonstrate that the work was an evaluative process rather than a single predetermined path. The regulations state that a process of experimentation generally should be capable of evaluating more than one alternative. For more, see our page on process of experimentation.
What to Record for Each Alternative
For each alternative considered, useful documentation may include:
- What the alternative was — the specific design, material, method, configuration, or approach considered.
- Why it was considered — what made it a candidate for resolving the uncertainty.
- How it was tested — the testing, modeling, simulation, or evaluation method used.
- What the results were — the outcome of the evaluation.
- What decision was made — whether the alternative was selected, modified, or rejected, and why.
Records that capture all five elements for each alternative tend to be more useful than records that describe only the final outcome.
Documenting Rejected Alternatives
Rejected alternatives are particularly important to document. A record that shows the team considered and rejected several alternatives — and why — can help demonstrate an evaluative process. Rejected alternatives are often forgotten after the fact, which is why contemporaneous records are valuable. A record that says "we considered alternatives A, B, and C; A was rejected because of X; B was rejected because of Y; C was selected because of Z" is more useful than a record that says only "we selected C."
Hypothetical Example
Consider a manufacturer that is developing a new coating and is uncertain which resin system can achieve the required corrosion resistance. The company considers three alternative resin systems. For each, the records show: what the resin system was, why it was considered (e.g., known corrosion resistance in similar applications), how it was tested (salt-spray testing), what the results were (hours to corrosion), and what decision was made (selected, modified, or rejected, and why). This documentation — showing the evaluative process across alternatives — can help support the process-of-experimentation element.
By contrast, a record that says only "we tested a coating and it passed" does not show the evaluative process and is less useful.
This example is illustrative only.
Documentation That May Help
Records that can help support the alternatives element include test plans listing alternatives, test results for each alternative, decision records explaining why alternatives were selected or rejected, and project communications discussing alternatives. Records created during the evaluation, when alternatives were being weighed, tend to be most useful. For more, see our page on R&D tax credit documentation.
Key Takeaway
Documenting alternatives considered during R&D involves recording what alternatives were evaluated, why they were considered, how they were tested, what the results were, and why some were rejected. This supports the process-of-experimentation element. Contemporaneous records, including records of rejected alternatives, tend to be most useful. Because documentation adequacy is fact-specific, professional review is appropriate.