Tracking qualifying R&D activity comes down to five steps. Identify projects that meet the IRS four-part test, log the technical uncertainty and process of experimentation (POE) as it happens, capture employee time, supplies, and contract research tied to the qualifying research activity, and centralize contemporaneous documentation throughout the year. Companies that follow these steps tend to claim more accurate credits with stronger support, which is exactly what the R&D tax credit rules call for.
Most businesses lose value not because they fail to perform qualifying work, but because the supporting details get lost between project teams, payroll, and accounting. The five steps below help you change that.
Step 1: Identify Which Projects Likely Meet the IRS Four-Part Test
Start by reviewing your active and recent projects against the four-part test outlined in Section 41 of the Internal Revenue Code. To qualify, a project needs a permitted purpose tied to the function, performance, reliability, or quality of a product or process. It also needs to rely on principles of a hard science, such as engineering, computer science, biology, or chemistry. There must be technical uncertainty at the outset, and the team must work through that uncertainty using a process of experimentation.
A practical way to apply the test is to walk through each project with the people closest to the work. Ask what problem they were solving, what they did not know at the start, and how they tested possible solutions. Many companies are surprised to learn that certain product improvements, software development activities, and process engineering efforts may qualify when they satisfy the applicable requirements
Step 2: Build a Simple System for Logging Technical Uncertainty
Technical uncertainty is one of the most overlooked pieces of R&D credit documentation. The IRS wants to see that your team did not already know how to achieve the result when the project began, and that you used experimentation to get there.
A simple log goes a long way. For each qualifying project, capture the question your team was trying to answer, the alternatives you considered, the tests or iterations you ran, and what you learned from each one. Existing tools usually do the job. Project management software, engineering tickets, lab notebooks, design files, and meeting notes can all serve as evidence when they are organized and connected to the project.
Step 3: Track Time and Wages Tied to Qualifying R&D Activity
Wages are often the largest category of qualified research expenses, so accurate time tracking has a direct effect on the credit. Companies that wait until year-end to reconstruct time tend to leave money on the table or weaken the support behind their claim.
Which Employee Roles Typically Qualify?
Three categories of employee activity may count: direct research, direct supervision of research, and direct support of research. Activities performed by engineers, software developers, scientists, product designers, project managers, technicians, and quality assurance staff may qualify when they are engaged in qualified research activities. Roles in administration, marketing, sales, and general management usually do not.
How the 80% Rule Affects Wage Calculation
If an employee spends 80% or more of their time on qualified research, 100% of their qualifying wages may be included in the credit calculation. If their qualified time is below that threshold, only the portion of wages tied to qualified activity counts. Building this percentage from contemporaneous records, rather than year-end estimates, produces a more defensible position.
Step 4: Keep Records of Supplies, Contract Research, and Cloud Computing Costs
Wages are only part of the picture. Qualifying expenses also include the materials and outside work that support the research.
The Three Qualified Expense Categories Beyond Wages
Supplies cover tangible items consumed or used during the research, such as prototype materials, test components, and pilot run inputs. Land, depreciable property, and general office supplies do not qualify. Contract research generally allows 65% of amounts paid to third parties performing qualified research on your behalf, provided your company retains rights to the results and bears the financial risk. Cloud computing and rental costs for hosting and computing resources used in qualified software development may also be included when properly documented.
For each category, keep invoices, purchase orders, contracts, and a clear connection between the expense and the qualifying project.
Step 5: Centralize Documentation Before Year-End, Not After
Year-end reconstruction is the most common reason R&D credit claims are weakened under review. By the time the tax return is being prepared, the people who performed the work may not remember the details, and project records can be scattered across teams.
A better approach is to centralize documentation throughout the year. Pick one location for project summaries, time data, expense records, and technical notes. Assign someone to update it on a regular cadence, even if briefly. When the credit study begins, the information is ready to support the calculation rather than being recreated from memory.
Partner with Navatus to Turn Your R&D Work Into a Defensible Credit
Navatus offers focused R&D tax credit services for businesses and accounting and advisory firms, including eligibility reviews, federal and state research credit studies, documentation and support packages, and audit support. We handle data gathering, technical interviews, and credit calculations, and coordinate with your CPA firm or internal tax team to keep the filing process smooth. If you want a clearer way to evaluate, document, and pursue your credit opportunities, we can help you build a process that works year after year.
Schedule a consultation with our R&D credit team today.
References: