R&D Tax Credit Documentation for A/E Firms:
How to Prepare the CPA Handoff
The R&D Tax Credit filing requires roughly ten items. Most of them already exist in the firm's project files, payroll records, and accounting system. One of them — the labor report — is the piece most firms don't have ready in a usable format. Here's what all ten items are, where each one comes from, and how to organize the handoff so the CPA can file without a reconstruction exercise.
The Full Documentation Picture — and Where BaseBuilders Fits In
The R&D Tax Credit is not a simple line item on a return. It is a defensible claim — one that requires documentation connecting the firm's technical work to the IRS qualification criteria, tying qualifying labor to specific employees and projects, and organizing the full package in a way a CPA can use to prepare the credit calculation and defend it in an audit.
That documentation package has roughly ten components. Most of them already exist in some form in the course of running a normal A/E practice — project records, payroll data, accounting files, contracts, correspondence. The challenge is not that the documentation doesn't exist. It is that it has never been organized with the R&D credit in mind, which means the CPA has to locate it, evaluate it, and organize it as part of the filing engagement.
The more organized the handoff, the less the CPA charges to prepare the filing. The more complete the documentation, the more defensible the credit is if the IRS asks to see the support. And the more consistently the documentation is maintained year over year, the lower the annual cost of claiming the credit becomes — because the systems that produce the documentation are already running, and the credit is a byproduct of how the firm manages its work.
BaseBuilders owns one item in the documentation package cleanly: the labor report. That item is the one most commonly missing at tax time and the one most likely to require expensive CPA reconstruction when the underlying tracking hasn't been maintained. The other nine items come from sources the firm already has — assembled with CPA guidance and organized for the handoff.
This article covers all ten. Where each item comes from, what the CPA needs it to contain, and how to organize it for a handoff that minimizes follow-up questions and maximizes credit accuracy.
→ Read: R&D Tax Credit for A/E Firms: The Complete Guide
Check with your CPA; BaseBuilders is not a tax advisor, does not play one on TV, and tax laws are constantly changing.
The R&D Tax Credit documentation package has roughly ten components.
Most of them already exist in the firm's project files, payroll records, and accounting system. The challenge is not that the documentation doesn't exist — it is that it has never been organized with the credit in mind.
The more organized the handoff, the less the CPA charges to prepare it.
The Ten Documentation Items — What They Are and Where They Come From
Item 1: Qualified Research Project List
A list of projects active in the tax year that involved qualified research activities — work that satisfies the IRS four-part test. For each project, the list should include the project name, the client, the project type, the phases active during the tax year, and a brief description of the technical uncertainty the project was addressing.
This list comes from the firm's own knowledge of its work. The principal who managed the projects knows which ones involved genuine technical problem-solving under conditions of uncertainty — structural systems that required iterative evaluation, MEP configurations that required modeling to optimize, site designs that required engineering analysis to resolve constraints. The CPA uses this list as the starting point for the technical narrative development.
BaseBuilders' project management records — active projects, phases, and timeline — support this list. Custom project fields configured for R&D purposes can store the technical uncertainty description directly in BaseBuilders alongside the project data, eliminating the need to reconstruct the narrative from memory at tax time.
Item 2: Technical Narratives
Written descriptions of the qualified research activities performed on each listed project — explaining what technical problem was being solved, what uncertainty existed at the outset, what alternatives were evaluated, and how the firm arrived at its solution. These are the documents that connect the firm's work to the IRS four-part test at the project level.
Technical narratives are typically prepared by the CPA in consultation with the firm's technical principals — the CPA structures the narrative to address the IRS criteria, and the principal provides the technical content. The quality of the narrative depends on how well the principal can describe the technical problem-solving that occurred during the project.
The more specific the principal's recollection — and the better the project records that support it — the stronger the narrative. Firms that maintain project-level notes on design alternatives evaluated, technical approaches considered and rejected, and engineering problems solved have richer source material for the CPA than firms that are working from memory alone.
Item 3: Evidence of Experimentation
Documentation demonstrating that the firm evaluated alternatives, compared technical approaches, and iterated toward a solution — evidence that a genuine process of experimentation occurred rather than the application of established methods to a known problem.
This evidence already exists in the firm's project records. Design meeting notes that reference alternative configurations considered. Email correspondence discussing competing structural approaches and the reasons one was selected over another. Calculation records showing multiple system configurations evaluated. Model outputs comparing the performance of alternative envelope configurations. Sketches showing the evolution of a design solution.
The firm does not need to create this documentation for R&D purposes. It needs to preserve it and be able to locate it. Firms that maintain organized project files — meeting notes, correspondence, calculation records, model outputs — have strong evidence of experimentation. Firms that rely on oral communication and don't maintain written records of design decisions have weaker support for their decisions.
Item 4: The Labor Report
The seven-column export from BaseBuilders showing who worked on qualifying projects, in which phases, performing which activities, for how many hours, at what direct labor cost. This is the item BaseBuilders generates cleanly — a structured, auditable, date-level record of the qualifying labor from which the credit is calculated.
The labor report is covered in detail in the companion article. The key point for the CPA handoff is format consistency: the same seven-column structure, the same activity list, the same direct labor rates, run for the same date range every year. When the CPA receives the same format each year, the review and reconciliation process becomes faster and more efficient over time.
→ Read: The R&D Tax Credit Labor Report: What Your CPA Actually Needs from Your A/E Firm
Item 5: Payroll Records
The W-2s and payroll records for employees who performed qualifying research activities during the tax year — the source documents the CPA uses to reconcile the Direct Labor column in the labor report against the firm's actual payroll.
These records come from the firm's payroll system or payroll service provider. They are already maintained for tax and employment law compliance purposes. For R&D credit purposes, the CPA needs the records for the specific employees identified in the labor report — not the full payroll register for every employee.
When direct labor rates in BaseBuilders are kept current — updated when employee compensation changes — the reconciliation between the labor report and the payroll records is straightforward. When rates are stale, the CPA has to adjust the labor report figures against actual payroll data, which takes additional time.
Item 6: Contractor and Consultant Costs
If the firm engaged independent contractors or outside consultants to perform qualified research activities — engineering subconsultants performing design analysis, specialty consultants contributing to technical problem-solving — 65% of those costs may be includable as qualified research expenses.
These records come from the firm's accounts payable and subconsultant management records. The firm needs to identify which consultant engagements involved qualified research activities, separate those costs from consultant costs related to non-qualifying work, and provide the CPA with the qualifying portion.
For A/E firms where subconsultants perform significant technical design work — structural engineers on architecture-led projects, MEP engineers on civil-led projects — this category can be meaningful. For firms where subconsultants are purely pass-through or where their work is primarily CA-phase administration, the qualifying portion may be small or zero.
Item 7: Supply Costs
Costs of supplies used directly in the qualified research activities. For A/E firms, this category is typically minimal — it covers physical materials consumed in the design process, not software subscriptions, office supplies, or equipment purchases. Physical model materials, specialty printing for design analysis, and similar consumables used directly in technical evaluation may qualify.
The CPA will identify whether any supply costs are worth including. Most A/E firms find this category immaterial and do not pursue it, but the firm should be prepared to provide supply cost records if the CPA determines they are worth including.
Item 8: Prior-Year Qualified Research Expense History
The qualified research expense totals from prior years — relevant because the standard R&D credit calculation is incremental, comparing current-year qualified research expenses against a base amount derived from historical QRE data. The higher the base amount, the lower the incremental credit.
For firms claiming the credit for the first time, the CPA will establish the base amount methodology. For firms that have claimed the credit in prior years, the prior-year QRE history is already on file with the CPA. The firm does not need to reconstruct this — the CPA maintains it as part of the ongoing credit relationship.
Item 9: Documentation of Non-Qualifying Activities
Records supporting the exclusion of non-qualifying work from the credit calculation — documentation that the firm's Bidding, CA, and administrative hours were excluded from the labor report and the qualified research expense total.
The Phase and Activity columns in the BaseBuilders labor report support this documentation directly. The full export shows all time entries with phase and activity labeled. The CPA's analysis of what was included and excluded — and why — is visible in the data. If the IRS asks why CA hours were excluded, the labor report shows what those hours were logged as, and the CPA's analysis explains the qualification determination.
Item 10: Signed Declarations
The return preparer's declaration and the taxpayer's declaration attesting to the accuracy of the R&D Tax Credit claim. These are administrative requirements — required forms that the CPA prepares and the firm's authorized signer executes as part of the tax return.
Nothing about this item requires the firm to make any advance preparations. It is the final step in the filing process, handled by the CPA during return preparation.
Most of the ten documentation items already exist in the firm's project files, payroll records, and accounting system.
The CPA's job is to organize and present them correctly. The firm's job is to maintain them consistently and make them accessible.
The labor report is the one item that requires a configured system to produce — and BaseBuilders is that system.
How to Organize the Handoff
The difference between a CPA handoff that takes one meeting and one that takes weeks of follow-up is almost entirely a function of organization — whether the documentation is assembled before the handoff meeting or reconstructed during it.
The annual handoff package
Assembling the handoff package once a year — at the same time as the labor report is generated, before the CPA meeting — produces a consistent, efficient filing process. The package for a well-prepared A/E firm includes:
The labor report CSV from BaseBuilders, generated for the prior tax year's date range using the saved R&D column set.
The qualified research project list — updated for the prior tax year, with technical uncertainty descriptions for each qualifying project. If custom project fields in BaseBuilders were used to maintain these descriptions during the year, they can be exported directly.
The evidence of experimentation — meeting notes, correspondence, calculation records, and model outputs from qualifying projects during the tax year. These do not need to be comprehensive — a representative selection of documents that illustrate the evaluation process for each qualifying project is sufficient.
Payroll records for the employees identified in the labor report — typically W-2s and the firm's payroll summary for the tax year.
Any qualifying contractor or consultant cost records — invoices or payment records for subconsultants who performed qualifying technical work during the tax year.
The CPA meeting
The handoff meeting with the CPA has two purposes: delivering the documentation package and walking the CPA through the technical narratives. The CPA needs to understand the technical problem-solving that occurred on each qualifying project well enough to write accurate, defensible narratives. The more specifically the principal can describe the alternatives evaluated and the technical uncertainty involved, the less time the narrative development takes.
A principal who can say "on this project we evaluated three structural configurations before selecting the moment frame because the shear wall approach created a layout conflict we couldn't resolve within the owner's program" is giving the CPA a narrative. A principal who says "we did normal structural design work" is giving the CPA a starting problem.
The better the project records — and the more consistently the qualifying work was documented during the project rather than reconstructed at tax time — the more efficient the narrative development process.
Year-over-year efficiency
The first year of claiming the R&D Tax Credit involves the most CPA time — establishing the base amount, developing the qualification framework, documenting the credit methodology, and building the technical narratives for the initial project set. Every subsequent year is more efficient because the framework exists, the format is established, and the CPA is refining a process rather than building one from scratch.
The labor report contributes directly to this efficiency. When the CPA receives the same seven-column format every year, with the same activity list and the same direct labor rate structure, the review and reconciliation is a confirmation exercise rather than a learning exercise. The credit gets filed faster. The CPA's fee is lower. The firm's time investment in the handoff is smaller.
The first year of claiming the R&D Tax Credit is the most work — for the CPA and for the firm.
Every subsequent year is more efficient because the framework exists, the format is established, and the systems that produce the documentation are already running.
The annual labor report from BaseBuilders is the same format every year. The CPA's review gets faster every time.
Maintaining the Documentation Between Filings
The most common mistake firms make after claiming the R&D Tax Credit for the first time is treating the documentation as a tax-time exercise rather than an ongoing practice. The documentation is assembled at tax time, the credit is filed, and the project records that supported it are not maintained with any particular rigor until the next filing cycle.
That approach works adequately in years when nothing is audited. It creates problems when the IRS requests documentation for a credit claimed two or three years earlier — when the principals who worked on the qualifying projects may have moved on, the project files may be incomplete, and the technical narratives prepared by the CPA are the primary remaining record of what the work involved.
Maintaining project-level documentation during the year
The most valuable R&D documentation maintenance practice is capturing the technical problem-solving record at the project level as the work happens — not reconstructing it at tax time.
Meeting notes that record design alternatives discussed and decisions made. Email correspondence about competing technical approaches. Calculation records showing the analysis that supported a system selection. Model outputs comparing the performance of alternative configurations. These documents exist naturally in the course of delivering A/E services. Maintaining them in organized project files — accessible and complete — is the only practice required.
Custom project fields in BaseBuilders support this practice directly. A project field labeled "Technical Uncertainty Summary" can capture, at project setup or during early design phases, a brief description of the technical problem the project is addressing and the alternatives being evaluated. A field labeled "Qualifying Activities" can note which phases and activities involved qualified research. These entries take minutes to complete and produce the source material the CPA needs for technical narratives — available at tax time without a reconstruction exercise.
Keeping direct labor rates current
Direct labor rates in BaseBuilders should be updated whenever employee compensation changes — salary adjustments, role changes, new hires. Stale rates produce a Direct Labor column that doesn't reconcile cleanly to payroll records, which creates additional CPA work at filing time and potential adjustment to the credit calculation.
A rate update process tied to the firm's regular compensation review cycle — annual salary adjustments updated in BaseBuilders at the same time they take effect in payroll — keeps the labor report accurate without requiring a separate maintenance exercise at tax time.
Saving the report template
Once the R&D labor report column set is configured and saved in BaseBuilders, no maintenance is required for the report itself. The saved template runs the same column set every year. The activity list updates only if the firm changes its activity configuration — which should happen in consultation with the CPA if it affects the qualifying determination.
The annual report generation is a query, a template selection, and an export. The maintenance that supports it is the routine practice of logging time accurately against projects, phases, and activities — which the firm is doing anyway for project financial management.
The audit preparedness posture
R&D Tax Credit claims can be audited. The standard statute of limitations for a credit claim is three years from the filing date, though larger credits or amended returns may carry longer exposure periods. Maintaining the documentation package for the credit — project lists, technical narratives, evidence of experimentation, labor reports, and payroll reconciliations — for at least the duration of the audit exposure period is prudent practice.
The CPA will typically maintain the technical narratives and the credit calculation workpapers as part of the ongoing tax file. The firm should maintain the project-level documentation — meeting notes, correspondence, calculation records, and the BaseBuilders labor report export — in an accessible form for the same period.
A firm that receives an IRS inquiry about a prior-year credit claim and can produce a clean labor report, organized project files with evidence of experimentation, and technical narratives that connect the documented work to the IRS qualification criteria is a firm that resolves the inquiry efficiently. A firm that has to reconstruct the documentation from incomplete records is a firm that pays significantly more in CPA fees to reach the same resolution.
→ Read: A/E Accounting for Architecture and Engineering Firms
→ Read: Financial Metrics for A/E Firms
Related Articles
Time Tracking Software for Architecture and Engineering FirmsCut Your Billing Time by 60% Within 90 Days — Or We Refund Every Penny
We're so confident BaseBuilders will transform your billing process that we're putting our money where our mouth is.
BaseBuilders’ easy-to-use software is specifically designed to help small to mid-sized firms track time, manage projects, stay on top of expenses, and more. We’ll handle the invoicing for you so you can focus on growing your firm and designing wonderful spaces.