Short answer
Some of the work can, on the same test that applies to a pharmaceutical company or a software house: a project must seek an advance in overall technological capability and run into a problem a competent professional cannot readily resolve. What makes motorsport claims difficult is that much of what a race team does is setting up, optimising and choosing between parts that already exist — which the guidelines defining R&D put outside the relief in terms. The claim lives in the design and development work behind the parts, not in the campaign that runs them.
Applies to
- Schemes
- All periods · Merged scheme · ERIS · Legacy SME · Legacy RDEC
- Periods
- 1 April 2023 onwards
- Sectors
- Motorsport & Automotive
This note covers race teams, series entrants, specialist suppliers, tuners, vehicle manufacturers and automotive tier one and tier two suppliers.
Where the R&D usually is
The work that qualifies has a common shape: somebody had to design something because nothing available would do the job, and did not know at the outset whether their approach would work. That covers new component design — a fuel or oil system that surges under loads a road-derived design was never built for, a suspension component whose geometry has to do something no published geometry does. It covers materials and process development, where a part must be lighter, stiffer or more heat-tolerant than existing methods produce. It covers control, electronics and data systems, such as establishing undocumented interface behaviour so a mandated control unit can drive an engine correctly.
And it covers integration, the one most often missed. The guidelines are explicit that combining standard components can still involve uncertainty: there is uncertainty “if a competent professional working in the field cannot readily deduce how the separate components or sub-systems should be combined to have the intended function”. Where fitting one developed component destabilises something else, and the cause is not obvious, the work to find and fix it can be part of the same project.
One point helps this sector: an advance can still be an advance where somebody else has made it but kept the details secret. Rival teams do not publish their solutions, so “someone at the front has probably solved this” is not by itself a reason to stand down.
Where it usually is not
The guidelines deal with the rest of a race programme directly, in wording an HMRC officer will quote back.
Fine-tuning is out: “improvements, optimisations and fine-tuning which do not materially affect the underlying science or technology do not constitute work to resolve scientific or technological uncertainty”. That covers suspension setup within known adjustment ranges, mapping within an established strategy, and gear ratio selection. It is skilled, it wins races, and it is not R&D. Testing components to find the best one goes the same way, as do routine engine refreshes. So does adapting a road part for competition with minor changes, because deploying existing technology in a new context “with only minor or routine changes” is expressly not an appreciable improvement.
Bodywork is out where the object is appearance, because cosmetic and aesthetic qualities “are not of themselves science or technology” — though aerodynamic development is not, because there the object is measurable.
So is running the campaign. The guidelines list “the production and distribution of goods and services” and “general support services (such as transportation, storage, cleaning, repair, maintenance and security)” among activities that do not directly contribute. Transporting cars to circuits, preparing them between races and maintaining them through a season are not qualifying activities, whatever share of the budget they represent.
Racing inside a regulated envelope
This is the judgement that decides most motorsport claims. Where a technical regulation fixes the component — a control tyre, a specification control unit, a homologated engine — what is left to the team is very often setup and optimisation within known limits. That is the fine-tuning the guidelines exclude, and a claim describing a season of chassis, suspension and engine work in a tightly regulated series is, on its face, a claim about optimisation.
The opposite case is real but narrower. Where a regulation creates a constraint no existing solution meets — a weight, packaging, fuel flow or emissions limit forcing a different technical approach — designing something that meets it can be a genuine advance. The question is not whether the regulations made the work difficult, but whether a competent professional could have said at the outset how to satisfy them. If they could, the difficulty was competitive rather than technological.
When development stops and the season starts
R&D ends when the knowledge is codified in a usable form, or when a prototype with all the functional characteristics of the final product exists. For prototypes, the guidelines go further: once modifications reflecting the test findings have been made and further testing satisfactorily completed, “the uncertainty has been resolved, and further work will not be R&D”. Development testing of a new component therefore qualifies; running it race after race to confirm it keeps working does not. The exception is in the guidelines too — new problems involving technological uncertainty can emerge after something is in use, though they are distinguished from “routine fault fixing”. A part failing in a way nobody can explain may restart a project. A part wearing out does not.
Sponsors, customers and who owns the claim
Sponsorship and prize money are not payment for R&D. A sponsor buys exposure, not a development programme, so sponsorship is not consideration for the technical work and does not make that work somebody else’s.
Customer contracts are the real question. A supplier designing to a customer’s specification, and a team doing development funded by a manufacturer, must establish who is treated as carrying out the R&D before either claims — and that turns on who decided what and who bore the risk, not on what the contract is called. See contracted-out R&D.
Costs that behave differently in this sector
Most cost rules apply here as anywhere, and the general position is on what costs qualify. Three catch motorsport and automotive businesses specifically.
Materials that end up in something you sell are excluded. Where R&D produces an item later transferred for consideration “in the ordinary course of the relevant person’s business”, the cost of the consumable items forming part of it is not qualifying expenditure. A manufacturer that develops a component and sells the production run has qualifying material cost in its test articles and non-qualifying material cost in the parts sold. Where only part of a batch is sold, an apportionment applies, so material scrapped or kept back for further trials stays in the claim.
Overseas testing is not automatically restricted — it depends on who is doing it. For accounting periods beginning on or after 1 April 2024, the restriction bites on payments to contractors for R&D undertaken abroad and on externally provided workers outside UK PAYE. It does not reach a company’s own employees, so a team’s own engineers testing at a foreign circuit are not caught. Where it does apply, expenditure can still qualify if conditions necessary for the work are not present in the UK — but cost and the availability of workers are expressly excluded, and are the only exclusions.
Race operations staff are not R&D staff. Engineering time on development qualifies to the extent it is properly apportioned; time spent running the cars at events does not, and an apportionment that quietly includes race weekends is easy for HMRC to take apart.
Worked example
Illustrative. A suspension manufacturer develops a new rear linkage geometry to solve a problem no available linkage solves, then sells the validated parts to teams.
| Cost | Amount | In the claim? | Why |
|---|---|---|---|
| Engineering time on design, simulation and rig testing | £68,000 | Yes | Directly resolving the uncertainty |
| Material consumed in test articles, destroyed or retained | £14,000 | Yes | Not transferred to a customer |
| Material in the validated linkages sold to teams | £9,000 | No | Consumable items forming part of a product sold |
| Simulation software licences, apportioned to the project | £4,000 | Yes | Apportioned to qualifying use |
| Race weekend support, transport and trackside servicing | £22,000 | No | Support services, not R&D |
Qualifying expenditure is £86,000 of the £117,000 spent. The £9,000 of material in the parts sold is the line most often missed because, in the ledger, it looks identical to the £14,000 that does qualify.
Where claims go wrong
- Treating the car, or the season, as the project. An R&D project “may itself be part of a larger commercial project, but that does not make the parts of the commercial project that do not address scientific or technological uncertainty” into R&D. A claim built on the racing budget, with development described as context, fails at the first question an officer asks: the advance cannot be stated and the uncertainty cannot be dated. Inside a season there may be two or three genuine technical projects, and those are the claim.
- Presenting setup and tuning as development. Suspension setup, linkage and yoke testing and engine tuning inside a series’ technical envelope are what the guidelines call optimisation and fine-tuning. We have assessed this fact pattern on a real claim and concluded it does not reach the threshold — a claim worth declining rather than stretching, and the one most likely to draw an enquiry.
- Losing the material split. Consumables used in testing and consumables that leave the building in a customer’s part are usually bought on the same purchase orders and sit in the same nominal code. If the split is not made when costs are gathered, it will not be made at all.
- No contemporaneous record of the uncertainty. The knowledge sits with a few engineers, the season moves on, and by the time an enquiry arrives, nobody can date when a problem was identified or solved. A dated note from the engineer responsible, written when work starts, beats a reconstruction a year later — see record-keeping requirements.
Last reviewed 14 September 2026