R&D Documentation Checklist

This is a practical organizational checklist for R&D documentation — organized by project information, technical objectives, uncertainty, alternatives, experimentation, personnel, expenses, evidence, review, and completion. It is not a universal IRS-required checklist.

This page provides a practical organizational checklist for R&D documentation. It is a tool for businesses that want to organize their R&D records in a structured way. It is not a universal IRS-required checklist — there is no single documentation format that every business must maintain — and not every item will apply to every business. The checklist is a starting point that should be adapted to the business's actual activities and facts. It is educational and is not individualized advice. For the broader documentation concepts, see our page on R&D tax credit documentation.

Important: This Is Not an IRS-Mandated Checklist

Before using this checklist, it is important to understand what it is and what it is not. The IRS has published guidance describing the information taxpayers are required to provide for a research credit claim for refund to be considered valid — including identifying the business components, the research activities performed, and the total qualified wage, supply, and contract research expenses. But the IRS does not prescribe a single universal documentation format or checklist that every business must maintain. This checklist is a practical organizational tool, not a statement of IRS requirements. Whether particular records are needed depends on the business's facts and the applicable rules.

1. Project Information

[ ] Project name or identifier
[ ] Business component (product, process, software, technique, formula, or invention)
[ ] Project owner or responsible person
[ ] Start date
[ ] Estimated or actual end date
[ ] Status (in progress, completed, discontinued)

2. Technical Objectives

[ ] Objective statement — what the work is intended to develop or improve
[ ] Specific improvement being pursued (function, performance, reliability, quality)
[ ] Technical problem being addressed
[ ] Connection to the business component

3. Uncertainty

[ ] Description of the technical uncertainty
[ ] Type of uncertainty (capability, method, or appropriate design)
[ ] When the uncertainty existed (at the outset of the work)
[ ] Why the uncertainty existed (what was not established by available information)

4. Alternatives

[ ] Alternatives considered (different designs, methods, materials, configurations, or approaches)
[ ] Why each alternative was considered
[ ] How the alternatives were evaluated

5. Experimentation

[ ] Experiments or tests conducted
[ ] Methods used (modeling, simulation, systematic testing, or other evaluative process)
[ ] Results of each experiment
[ ] How results informed next steps
[ ] Failed tests and their significance
[ ] Iterations and revisions

6. Personnel

[ ] People who performed or directly supported the work
[ ] Roles of each person (direct research, direct supervision, direct support)
[ ] Time or activity records connecting people to projects
[ ] Allocation of time where a person worked on multiple projects or activities

7. Expenses

[ ] Wages connected to the project
[ ] Contractor payments connected to the project
[ ] Supplies used in the project
[ ] Allocation of costs where they support multiple projects or both R&D and non-R&D work
[ ] Connection of costs to specific activities and business components

8. Evidence

[ ] Test results
[ ] Design files and specifications
[ ] Experiment logs
[ ] Meeting notes and technical notes
[ ] Photographs or images
[ ] Prototypes or samples (where applicable)
[ ] Change records or version histories
[ ] Emails or communications (where relevant)

9. Review

[ ] Records reviewed internally (by whom, when)
[ ] Records reviewed by a CPA or other tax professional (if applicable)
[ ] Gaps identified and addressed
[ ] Questions raised and answered

10. Completion

[ ] Outcome recorded (achieved, revised, or discontinued)
[ ] Final results documented
[ ] Remaining evidence preserved
[ ] Record finalized and archived

How to Use This Checklist

This checklist is a starting point, not a prescription. Not every item will apply to every business or every project. A business should adapt the checklist to its actual activities, industry, and workflow. The goal is not to check every box but to ensure that the records, taken together, help substantiate the activities, costs, and business components involved. For more on the documentation framework, see our page on how to document R&D projects.

Contemporaneous Documentation

The checklist is most useful when it is used throughout the project, not just at the end. Records created during the period of research — contemporaneous records — tend to be more useful than records reconstructed after the fact. For more on why timing matters, see our page on contemporaneous R&D documentation.

What This Checklist Does Not Do

This checklist does not establish that a business's activities qualify for any tax credit. It does not determine whether costs are qualified research expenses. It does not replace the professional judgment of a CPA or qualified tax professional. It does not make records "IRS-compliant" by itself. It is an organizational tool; the substantive analysis is a separate step.

Key Takeaway

This R&D documentation checklist is a practical organizational tool covering project information, technical objectives, uncertainty, alternatives, experimentation, personnel, expenses, evidence, review, and completion. It is not a universal IRS-required checklist, and not every item will apply to every business. Used throughout the project, it can help ensure that records are created while the technical context is present. For a template companion, see our page on R&D project documentation template.