Qualifying activities

How do I know if I'm doing R&D?

Reviewed 31 August 2026

Knowledge bank Qualifying activities

Short answer

Four things have to be true at once. There is a project. That project seeks an advance in a field of science or technology. The advance is in the overall knowledge or capability of that field, not just in your company. And getting there required resolving uncertainty that a competent professional working in the field could not readily have resolved. If any one of those fails, the work is not R&D for tax purposes, however difficult, expensive or commercially valuable it was.

Applies to

Schemes
Merged scheme · ERIS · Legacy SME · Legacy RDEC
Periods
1 April 2023 onwards
Claimants
All

Where the definition comes from

The definition is not really in the tax legislation. Corporation tax law starts with the accounting meaning of research and development, then hands the substance over to guidelines issued by the Secretary of State. Those guidelines — the Guidelines on the Meaning of Research and Development for Tax Purposes — are the test. They are short, numbered, and the tribunals read them closely: the High Court has described the R&D code as detailed and meticulously drafted, leaving little room to read in a purpose the words do not carry.

Two practical consequences. First, the accounting treatment of your development spending has almost no bearing on whether it is R&D for tax. Second, arguing that your work was clearly innovative and therefore ought to qualify does not work. The guidelines ask specific questions, and you have to answer those questions.

The four parts of the test

1. Is there a project?

A project is a number of activities conducted to a method or plan in order to achieve an advance. That wording does real work. It means R&D is not an atmosphere of general technical improvement across your business; it is a bounded piece of work with an aim.

It also means the R&D project and the commercial project are usually not the same thing. A commercial project to launch a product includes procurement, design, market testing, regulatory work, manufacturing setup, and much more. The R&D project inside it is the part aimed at resolving the scientific or technological uncertainty, and it may be a small fraction of the whole.

2. Is it in a field of science or technology?

Science is the systematic study of the nature and behaviour of the physical and material universe. Technology is the practical application of scientific principles and knowledge.

Work in the arts, humanities and social sciences, including economics, is not science for this purpose. Neither is work whose only novelty is commercial, organisational or aesthetic. Mathematics is a special case: for accounting periods beginning on or after 1 April 2023, a mathematical advance is treated as science in its own right, whether or not it describes the physical world. That change matters to quantitative finance, cryptography, optimisation and parts of machine learning, and it is one of the few genuine widenings of the definition in twenty years.

3. Does it advance the field, not just your company?

This is the part most claims fail on. The advance has to be an advance in the field’s overall knowledge or capability—what is publicly available, or readily deducible from what is publicly available, to a competent professional. Your own starting point is irrelevant.

So a system that is new to you, new to your competitors, or new to your industry is not automatically an advance. Taking existing science or technology and deploying it in a new context with only minor or routine changes is not an appreciable improvement, and neither is work that simply brings you into line with what the field can already do.

The advance does not have to be achieved. A failed project is still R&D, and failure is often the cleanest evidence that the uncertainty was real. Nor does it matter that someone else has already done it if they did not publish it—work to reach an advance that exists only as somebody’s trade secret can still be an advance.

4. Was there uncertainty a competent professional could not readily resolve?

Scientific or technological uncertainty exists when knowledge of whether something is possible or feasible, or of how to achieve it in practice, is not readily available or deducible by a competent professional working in the field.

“Readily deducible” means capable of being worked out from what is already known without significant effort. It does not mean easy. And the uncertainty has to be technological: not knowing whether customers will buy it, whether the budget will hold, or how long the work will take is not the kind of uncertainty that counts.

The competent professional is the yardstick for parts three and four, which is why identifying yours — by name, in the right field — is the first practical step in preparing any claim.

When does the R&D start and stop?

R&D begins when work to resolve the uncertainty starts, and ends when the uncertainty is resolved, or work to resolve it stops. It also ends when the knowledge sought is codified in a form a competent professional could use, or when a prototype or pilot with all the functional characteristics of the final product is produced.

That gives you two boundaries. Work before the uncertainty was identified — scoping the commercial opportunity, deciding to build something — is outside. So is work after it was resolved: proving out a solution that already works, testing for regulatory certification once functionality is settled, scaling up to production. Both ends are routinely over-claimed.

Position for accounting periods beginning before 1 April 2023

The earlier guidelines, issued in 2004 and updated in 2010, ask the same four questions in almost the same words, and the case law decided under them applies equally to the current ones.

The one substantive difference is mathematics. Under the earlier guidelines, a mathematical advance was only within scope where it advanced the representation of the nature and behaviour of the physical and material universe. Pure mathematical work was outside. For accounting periods beginning before 1 April 2023, that older, narrower position still applies, and a claim for periods on either side of the boundary must be split.

Worked example

Illustrative. A company making industrial ovens sets out to build a model that holds temperature across the chamber to within half a degree, against an installed base that manages three degrees.

WorkstreamR&D?Why
Deciding there is a market for a tighter-tolerance ovenNoCommercial, not technological
Reviewing published work and vendor data on airflow and sensor placementYes — indirectEstablishing the baseline for the project
Modelling and rig-testing a new airflow geometry that existing thermal models do not predict wellYesResolving a technological uncertainty
Selecting a controller from a catalogue and configuring it to specNoRoutine application of existing technology
Redesigning the door seal to hold the new tolerance, where no off-the-shelf seal performsYesAppreciable improvement, uncertain outcome
Testing the finished oven against food safety regulationsNoUncertainty already resolved
Restyling the control panelNoAesthetic

The commercial project runs for eighteen months. The R&D project inside it runs for about seven, and stops the day the rig holds tolerance repeatably — not the day the oven ships.

Where claims go wrong

  • Claiming the commercial project. The single most common error, and the one that makes a claim indefensible in an enquiry: the costs of an eighteen-month product launch are claimed because seven months of it was R&D. HMRC’s opening question is usually a request to describe the project, and an answer that describes a product is a bad start.
  • An advance stated as the product. “We developed a new platform” is not an advance in science or technology; it is a thing you built. The advance is the capability the field lacked. If you cannot say what the field could not do before, you do not yet have a claim.
  • Confusing difficulty with uncertainty. Long, expensive and frustrating work is not evidence of technological uncertainty. Plenty of hard projects are hard for reasons a competent professional would have predicted exactly.
  • Writing the technical narrative backwards. Deciding to claim, then constructing uncertainties to fit the work that was done, produces documents that do not survive contact with a tribunal. Uncertainty has to have existed and been recognised at the time.
  • Ignoring the boundaries. Claiming through to launch, or from the first day of the commercial project, adds cost and risk to the whole claim. An over-broad boundary invites HMRC to test the entire claim rather than the disputed part.

Last reviewed 31 August 2026

Get in touch

Want this checked against your own project?