Keep the records that explain your R&D

A test result in one folder, a design decision in a chat, and the cost in a spreadsheet can all describe the same R&D project. The challenge at claim time is putting them back together.

Start with the records your team already creates. A small amount of context added while the work is fresh can save a long reconstruction at year-end. The aim is to preserve the reasoning behind each experiment while people still remember it.

Give the investigation a place to live

Create one project note or experiment index that points to the existing work. You can keep it in a shared document, your issue tracker, or the place your team normally records technical decisions.

Include the question you are investigating, the relevant constraints, who is involved, and links to the main attempts. Use a project name that engineering and finance can both recognize.

For example, a materials team investigating how a formulation behaves across a wider temperature range could link its sample recipes, test conditions, measurements, and the decision to change the next batch. A software team can make the same connections between a design note, test output, and an issue or pull request.

Keep the result with the decision

When a result changes the next design, add a few lines explaining the connection. A useful note answers four questions:

• What approach did we test, and why?
• What conditions and measurements did we use?
• What did the result tell us?
• What are we changing or investigating next?

"Test failed; retry next week" is hard to interpret later. "The coating cracked after repeated heating; we are testing a different mix to investigate whether the expansion mismatch caused it" gives the next person something to follow.

Retain the underlying files and the setup as well as the summary. At an existing project meeting, check that the links still work and that someone else can follow the sequence.

Keep the cost records connected

Technical records explain the investigation. Financial records explain the amount claimed. Keep enough detail to connect the two.

The CRA’s claim preparation guidance calls for records that show the work, its contributors, when it happened, and the associated cost calculations. Its examples include technical drawings, source code, meeting records, test results, time and payroll records, contracts, invoices, and proof of payment. It recommends maintaining records throughout the work.

For your own project, keep the basis for employee time allocations, the relevant contractor invoices and work descriptions, material purchases and usage, and any related funding. An issue count or commit count can help locate activity; it does not measure hours by itself.

Use the same project names in the technical index and finance schedules. Cedar reconciles those records to the claim, checks the treatment of assistance, and prepares the expenditure calculations.

Identify gaps before drafting

For work already completed, make an inventory before asking everyone to rewrite their year. Find the original project files, then speak with the contributors about any missing context. Clearly date explanations added later and identify the records they relate to.

Cedar’s platform helps organize project information, evidence, and follow-ups in one place. Your senior claim preparer uses that material to assess the work, write the report, and connect it to the costs. If CRA reviews the claim, Cedar leads the technical and financial response, prepares the supporting documents, and attends review meetings with your team. That review work is included in our service.

Talk to Cedar about the records you have. We’ll use them to scope and prepare your claim, following up with your team where more detail is needed.