It’s a common assumption that if something feels new, innovative, or technically complex, it must qualify as R&D for UK tax purposes. Novelty and complexity alone are not the test. The criteria is narrower and more technical.

As per the R&D definition set out in the guidelines issued by DSIT (Department for Science, Innovation and Technology) a project qualifies if it seeks to achieve an Advance in science or technology and involves overcoming scientific or technological uncertainty related to the Advance.

Two concepts sit at the core of the definition:

SCIENTIFIC/TECHNOLOGICAL ADVANCE

The project must seek to advance the overall knowledge or capability in a field of science or technology—not just represent an internal improvement for the business.

SCIENTIFIC/TECHNOLOGICAL UNCERTAINTY

There must be uncertainty that a competent professional in the field cannot readily resolve using existing publicly available knowledge or standard practices.

These are the tests that matter. Other descriptors—such as “new”, “innovative”, or “complex”, only have relevance if they directly relate to these criteria.

WHY “NEW” IS NOT SUFFICIENT

Something being new to a business, team, or product does not in itself indicate R&D. Many activities involve first-time implementation, adoption of unfamiliar tools, or development of new features, but still rely on established knowledge and proven approaches.

The distinction lies in whether the work extends the boundaries of what is known or achievable in the wider field, or is readily deducible by a competent professional working in the field. If it does not, it is unlikely to meet the definition, regardless of how novel it feels internally.

WHY “COMPLEX” IS NOT SUFFICIENT

Complexity alone does not imply the presence of a scientific/ technological uncertainty.

Projects can be large, intricate, and resource-intensive while still being fully achievable using existing techniques, architectures, and best practices. In such cases, a competent professional would be able to determine a path to completion without needing to resolve unknowns at the technological level.

The R&D test is not about how hard something is to deliver, but whether there is genuine uncertainty in how it can be achieved.

THE IMPORTANCE OF SCIENTIFIC/TECHNOLOGICAL UNCERTAINTY

Scientific/Technological uncertainty exists where the solution to a problem is not readily deducible by a competent professional. This goes beyond routine problem-solving, debugging, or overcoming implementation challenges.

It typically involves situations where:

  • Existing knowledge does not provide a clear or reliable solution.
  • Multiple approaches must be evaluated through experimentation.
  • The outcome cannot be predicted in advance with confidence.
  • This is the key differentiator – without uncertainty, there is no R&D for tax purposes.

VIEWING PROJECTS THROUGH THE “COMPETENT PROFESSIONAL” LENS

To assess eligibility, it is important to consider the perspective of a competent professional working in the relevant field. If such a professional could reasonably determine how to achieve the desired outcome using current knowledge, tools, and techniques, the work is unlikely to qualify—even if it is time-consuming or technically demanding.

If, however, the outcome could not be readily achieved without experimentation, iteration, or the development of new approaches, then the project is more likely to fall within the R&D definition.

COMMON PITFALLS IN R&D CLAIMS

In practice, several recurring issues weaken R&D claims:

  • Equating product innovation with technological advancement.
  • Commercially new features or offerings do not necessarily advance underlying technology.
  • Confusing difficulty with uncertainty.
  • Challenging work, learning curves, or engineering effort do not automatically indicate R&D.
  • Overlooking the real R&D activity.
  • The most technically significant work is often embedded in problem-solving and experimentation, rather than in visible product outcomes.

FRAMING R&D CORRECTLY

Strong R&D claims focus on the underlying technical challenges rather than the end product. In particular, they clearly articulate:

  • What the baseline level of knowledge was (the competent professional’s take on this).
  • What advance in science or technology was sought.
  • Why this advance was not readily achievable using existing knowledge
  • Where the technological uncertainties lay.
  • How those uncertainties were systematically addressed.

This requires input from personnel directly involved in the technical work and an accurate understanding of where genuine uncertainty existed.

Summary

“New” and “complex” are intuitive but unreliable indicators of R&D eligibility. The project activities must be considered in light of the R&D definition/on advancement and uncertainty as explained above.

Keeping that distinction clear not only strengthens claims, but also helps organisations better recognise the R&D eligible technical work taking place within their teams.