Why technical evidence matters

The technical evidence behind an R&D tax relief claim helps turn a project description into a clear explanation of why the work meets the tax definition of research and development. It shows what the business was trying to achieve, what could not readily be worked out and how the project team approached the problem.

Evidence does not mean creating a large file of documents for its own sake. Nor is there a separate, prescribed record-keeping system that every claimant must follow. The records available will differ between a small company with one project and a larger business running several workstreams. What matters is that the information is relevant, proportionate and connected to the position being claimed.

A claim needs more than a description of the finished product

Commercial materials often explain what a product, process or service does and why a customer might value it. That context can be useful, but it does not by itself explain R&D for tax purposes. A new or commercially distinctive result is not automatically evidence of an advance in science or technology.

The technical account needs to go further. It should describe the knowledge or capability available when the project began, the advance the company sought and the scientific or technological uncertainty faced — in plain English, what a suitably experienced professional in the field could not readily work out using available knowledge or standard practice.

Evidence supports the competent professional’s explanation

The company’s competent professionals are central to the technical position. They understand the field, the project decisions and why the solution was not straightforward. Their explanation should establish the technical reasoning; records help support and illustrate it.

Useful evidence might include:

• project plans, technical specifications and design notes;
• research into the existing state of knowledge or capability;
• test results, prototypes, calculations and trial data;
• records of failed approaches, changes in direction or unresolved problems;
• technical meeting notes, issue logs and progress reports; and
• relevant correspondence with employees, contractors or external specialists.

No single item proves that a project qualifies. Taken together, however, the records can show how the project developed and why particular activities were required. Evidence created during the work will often provide a clearer account than information reconstructed much later.

Unsuccessful work can still be relevant

Technical evidence is not only about successful outcomes. A project may still contain qualifying R&D where an uncertainty is not resolved or the intended result is not achieved. Failed tests, abandoned routes and unexpected results can help explain the nature of the uncertainty and the systematic work undertaken to address it.

The key distinction is between evidence of technical uncertainty and evidence of ordinary commercial difficulty. Delays, budget pressures, customer changes or resource constraints may affect a project, but they do not establish scientific or technological uncertainty. The records should help separate the two.

Technical and financial evidence should align

A claim also needs a clear connection between qualifying activities and the expenditure included. Payroll records, invoices and accounting data can establish that costs were incurred, but they may not show how an employee’s time or a contractor’s work related to resolving an uncertainty.

The method used to identify and allocate costs should therefore reflect how the business actually delivered the project. Contemporaneous time records may be available, but they are not the only possible source. Project plans, role descriptions, work records and informed input from those involved may also help establish a reasonable basis. The approach should be consistent, explainable and tailored to the company’s circumstances.

The additional information form makes clarity essential

The additional information form requires companies to explain the relevant field of science or technology, the starting knowledge, the intended advance, the uncertainties and how the project sought to overcome them. It also requires qualifying expenditure to be linked to the projects described.

These questions should be answered directly and with enough detail to explain the position. Referring elsewhere to a separate report does not replace the information required within the form. Preparing the technical evidence early makes it easier to produce an account that is complete without becoming unnecessarily long.

A practical approach to evidence

Businesses do not need to redesign every project system around a future claim. A practical starting point is to identify the information already produced by technical and finance teams, consider where important decisions are recorded and address any gaps while the project is active. The level of formality should remain proportionate to the size and nature of the work.

Knight R&D works with each client’s competent professionals and finance team to understand the records available, explain the legislative requirements and structure the information clearly. This keeps the technical judgement with the business while helping ensure that the claim reflects both the work undertaken and the expenditure included.