What actually counts as qualified research? A plain-English guide to the four-part test

Ask three advisors whether a project qualifies for the research credit and you may get three different answers. That is rarely because the law is vague. It is usually because the four-part test is being applied loosely, in the hope that enthusiasm can substitute for analysis. It can't, and when a claim is examined, it doesn't.

The test itself is short. Each part is a filter, and a project must pass all four. What follows is each part in plain English, with the questions we teach claimants to ask of their own work.

The statutory frame

The credit rewards qualified research, and the statute defines that term by reference to four requirements. Two things are worth noticing before reading them. First, the unit of analysis is the business component, meaning a product, process, technique, formula, invention or piece of software, not the company as a whole. Second, the test is conjunctive: failing any single part means the activity does not qualify, however impressive it is otherwise.

Part one: permitted purpose

The work must be intended to create or improve the functionality, performance, reliability or quality of a business component. This is the easiest part to pass and the most commonly misread. It does not require novelty to the world; improving your own product counts. But it does require a development objective. Routine production, cosmetic changes and market research sit outside it.

Part two: technological in nature

The work must fundamentally rely on principles of the physical or biological sciences, engineering or computer science. The question to ask is not "did we use technology?", because every business does, but "does resolving our problem depend on hard science?" Configuring purchased software with vendor documentation generally does not. Building or materially re-architecting software generally does.

The question is not whether you used technology. It is whether resolving your uncertainty depended on it.

Part three: elimination of uncertainty

At the outset, you must have been uncertain about capability, method or appropriate design. The key word is outset: uncertainty is judged before the work starts, not after it succeeds. This is where contemporaneous records earn their keep. A design document that states what was unknown in March is worth more than a memo reconstructing it in December.

Part four: process of experimentation

Substantially all of the activity must constitute a process of experimentation: evaluating alternatives through modelling, simulation, systematic trial and error, or other scientific means. A plan, hypotheses, alternatives considered and results recorded: this is the part examiners probe hardest, because it leaves the clearest evidence trail when it genuinely happened.

The test at a glance

Part	The question it asks	Where claims fail
Permitted purpose	Is there a development objective for a business component?	Routine work dressed up as development
Technological in nature	Does the work rely on hard science?	Configuration presented as engineering
Uncertainty	Was capability, method or design unknown at the outset?	Uncertainty reconstructed after the fact
Experimentation	Were alternatives systematically evaluated?	No evidence trail of the process

Applying it honestly

The discipline we teach is simple: write down, per project, one sentence for each part of the test, before anyone calculates anything. If a sentence cannot be written without hedging, the project probably belongs outside the claim, and the claim is stronger for its absence. Credits built this way are smaller on paper and larger in practice, because they survive contact with review.

The same habit transfers across borders. The UK, Australian and Canadian schemes each frame eligibility differently, but all of them reward the same underlying thing: documented technical uncertainty, addressed systematically. Learn the discipline once and every jurisdiction gets easier.

This is educational material, not tax advice. Rules change and facts matter; take advice on your own position before relying on any general guidance, ours included.