In this article: Learn why SME interviews are essential to strong R&D tax credit documentation, audit readiness, and identifying potentially qualifying work.
The difference between a defensible R&D tax credit claim and a vulnerable one often comes down to how well a company documents the technical story behind its projects.
Most companies pursuing the Credit for Increasing Research Activities, or the R&D tax credit, are focused on solving technical problems and developing new products, software, or processes, while the individuals performing the work are typically engineers, developers, and technical specialists, not tax or documentation experts.
As a result, some of the most important technical details supporting an R&D tax credit claim never make it into formal documentation. That is why Subject Matter Expert (SME) interviews matter.
Conducting structured project interviews with SMEs is one of the most effective ways to create accurate, technically detailed, and audit-defensible R&D tax credit documentation. While timesheets, financial records, project plans, and technical artifacts all play important roles, interviews often provide the missing context needed to clarify technical uncertainty, experimentation, and business-component development under IRC §41 and related state incentives. State-level eligibility, filing requirements, and substantiation expectations vary by jurisdiction.
Why are standard project records often insufficient for R&D tax credit documentation?
Most businesses do not maintain documentation designed for R&D tax credit purposes.
Engineering teams may maintain CAD files, source code repositories, testing data, prototype drawings, tickets, or meeting notes, but these records are typically created to support project execution rather than document the technical uncertainty and experimentation required for an R&D tax credit claim.
For example, a project file may show that a company designed a new component or released a software feature, but it may not explain:
- What technical questions existed at the outset
- Why standard approaches were insufficient
- Which alternatives were evaluated
- What testing or iterative development occurred
- Why certain approaches succeeded or failed
- How the team resolved technical challenges
This creates a documentation gap: critical technical details can remain buried in fragmented records or in undocumented institutional knowledge, causing otherwise legitimate R&D activities to appear unqualified during an Internal Revenue Service (IRS)- or state-level review.
How do SME interviews help identify potentially qualified R&D activities?
Project documentation may capture what was developed, but not necessarily why development was technically challenging.
During interviews, SMEs can explain the underlying technical obstacles that drove experimentation and iterative development. These conversations uncover details that are absent from project records but critical for demonstrating qualification under the IRS’ four-part test.
For example, an engineer might explain that:
- Prior design assumptions produced unacceptable thermal behavior.
- Material properties changed unpredictably during production.
- Existing manufacturing tolerances caused repeatability failures.
- Existing methods produced inconsistent outputs under real-world conditions.
- Commercial software tools could not achieve the required functionality.
- Infrastructure limitations affected software scalability.
These explanations help establish that the work involved more than routine implementation or standard engineering practices.
SMEs also clarify that teams evaluated multiple alternatives before specifying a final approach. This is especially important because experimentation and iterative evaluation are central components of qualified research activities.
How do SME interviews help document technical uncertainty?
One of the most common weaknesses in poorly prepared R&D documentation is the use of vague or generic descriptions of uncertainty.
Statements such as “the company wanted to improve efficiency” or “the team developed a new process” are insufficient on their own. Audit-ready documentation requires a more precise explanation of what was technically unknown at the start of the project.
SME interviews allow documentation specialists to ask follow-up questions that refine broad project descriptions into defensible technical uncertainties.
How do SME interviews help document the process of experimentation?
Experimentation is rarely documented in a single centralized location. Development iterations often occur across meetings, simulations, prototype revisions, testing cycles, production runs, field observations, and software releases. SMEs are typically the individuals best positioned to connect these activities into a clear technical narrative.
During interviews, companies frequently uncover potentially qualifying activities, such as:
- Simulation and modeling
- Comparative testing of alternatives
- Material, component, and performance evaluation
- Prototype fabrication, revision, and testing
- Trial-and-error development
- Batch testing, reformulation, and parameter refinement based on observed outcomes
- Pilot-scale production evaluation
- Software iteration cycles
These activities are strongest when documented as part of a systematic process that identifies the uncertainty, evaluates one or more alternatives, and explains how testing results informed the final technical approach.
Importantly, SME interviews also help separate potentially qualified research from activities that are generally excluded from the credit, including routine quality control, ordinary troubleshooting, cosmetic changes, duplication, post-production support, and administrative or commercial work unrelated to technical uncertainty.
This distinction strengthens audit defense by keeping project narratives technically focused and aligned with applicable tax rules.
How do technical interviews strengthen credible and defensible documentation?
Strong R&D documentation should reflect how technical teams actually speak about their work.
Documentation developed solely from generalized templates or accounting records can appear broad, repetitive, or disconnected from the actual project work. In contrast, documentation informed by SME interviews contains more credible technical detail, project-specific terminology, and realistic descriptions of development challenges.
This level of specificity is especially important during IRS examinations or state-level reviews.
When project descriptions include detailed explanations of technical obstacles, evaluated alternatives, and iterative development processes, they are generally more persuasive than high-level summaries that lack engineering or technical substance.
Additionally, interviews can help identify contemporaneous supporting records that might otherwise be overlooked, including:
- Customer technical specifications
- Design drawings and prototype records
- Software repositories, change logs, and simulation outputs
- Testing reports and manufacturing trial documentation
- Meeting notes and internal technical communications
Together, these materials create a more comprehensive audit defense file.
The importance of SME interviews across engineering, manufacturing, and software development
Some businesses incorrectly assume that R&D tax credits apply only to laboratories or formal research environments.
In reality, potentially qualified research may occur across a wide range of industries, including:
- Engineering, architecture, and construction
- Manufacturing and process engineering
- Software development
- Aerospace, defense, automotive, and medical device development
- Food and beverage development
- Agriculture
- Energy and environmental technologies
In each of these industries, SMEs often hold the technical knowledge necessary to explain why a project involved uncertainty, evaluated alternatives, and experimentation.
Without interviews, many of these project-specific details may never be fully documented.
Strong documentation starts with the people performing the work
At its core, the R&D tax credit is intended to support businesses that invest in qualified research and technical problem-solving. The individuals closest to that work are often the engineers, developers, technicians, scientists, designers, and project leaders actively addressing those challenges every day. SME interviews provide a structured way to capture their knowledge and translate it into organized, supportable documentation.
For businesses pursuing federal or state R&D tax credits, project interviews are not merely administrative exercises. They are one of the most effective tools available for developing accurate, technically grounded, and audit-ready project documentation when used alongside contemporaneous records.
When performed correctly, SME interviews help ensure that the technical complexity behind development activities is clearly documented and connected to the requirements of IRC §41.
Connect, learn, and explore R&D tax credit opportunities
Discuss potential R&D credit eligibility and documentation practices with a qualified tax professional.
Schedule a complimentary R&D consultation with Randy Eickhoff, CPA, Founder & Head Coach of Acena Consulting, for expert guidance.
Visit our Acena Events page to sign up for our newsletter and stay abreast of all upcoming events.
Follow Acena on LinkedIn for the latest industry-specific incentives and tax policy updates.
//
Edited by Laura Whittenburg, MSBME, Sr. Technical Writer
Photo: “Taxes” by James Morris, CC BY 2.0
