On 6 August 2026 the First-tier Tribunal dismissed Tanglewood Care Services Limited v HMRC [2026] UKFTT 1137 (TC). A care-home operator had claimed enhanced SME R&D relief of £880,286 for a project titled “Managing outbreak & effects of a Global Pandemic in a residential care home (Covid-19)”. Judge Stapenhurst and Mr Julian Sims held the activities were operational risk management, not research and development under the BEIS Guidelines. The appeal failed. The claim came out of the CT computation.
If you sign R&D claims — or you sit over a board that still treats R&D as a year-end plug from an external claim specialist — read this before the next Additional Information Form goes in. The Tribunal did not mock the operational effort. It refused to convert pandemic management into science.
Sources: the judgment, Claritax, HMRC’s R&D relief guidance, CIRD81900 (BEIS Guidelines), the DSIT Guidelines, Part 13 CTA 2009 and GfC3.
What Tanglewood actually claimed
Tanglewood runs residential nursing care facilities. For the period ended 31 January 2021 it originally filed without R&D, then amended on 9 September 2022 to claim enhanced expenditure of £880,286 on a single Covid-response project: a “novel system” of PPE, testing, visitor restrictions, cohorting, cleaning, distancing, staff segregation, track-and-trace, admissions controls and vaccination. Uncertainties included asymptomatic transmission and the optimal mix of measures in a care home.
HMRC’s case was simpler. The company applied existing infection-control knowledge to its own operations. Hard, valuable work — not an advance in overall scientific or technological knowledge or capability.
The four tests the Tribunal actually ran
The period sits under the older BEIS Guidelines (2010), not the post-April 2023 DSIT rewrite. Architecture: s.1138 CTA 2010 → s.1006 ITA 2007 → SI 2004/712 → the Guidelines. The fight was (i) advance, (ii) scientific or technological uncertainty, (iii) system uncertainty, and (iv) the competent professional.
1. Advance in overall knowledge or capability. Paragraphs 3 and 6 require a field-level advance, not merely progress relative to the company’s own starting point. The Tribunal accepted a project to minimise transmission while maintaining care. It rejected a field-level advance. The objective was how best to deploy known infection-control measures inside Tanglewood’s homes. Adaptation inside one operator’s estate is not enough.
2. Scientific or technological uncertainty. Paragraphs 13–14 require uncertainty about possibility, feasibility, or how to achieve something in practice that a competent professional cannot readily resolve. Most of Tanglewood’s “uncertainties” were staffing, visitor policy, admissions, wellbeing, PPE procurement and running homes in an emergency. Real problems — operational and managerial, not Guidelines-type scientific or technological uncertainty.
3. System uncertainty is not a free pass. Paragraphs 29–30 allow uncertainty from combining known components. The Tribunal agreed system-uncertainty projects can qualify in principle. It still needed evidence that a competent professional could not readily deduce the combination. Assembling known measures into an evolving operational pattern is not automatically system uncertainty.
4. Competent professional evidence. Witnesses were experienced care-home operators — honest and operationally expert. None claimed expertise in virology, epidemiology or infection science. Without that, the Tribunal could not test the field baseline, whether uncertainties were readily deducible, or whether any advance went beyond Tanglewood’s own operations. It reinforced AHK Recruitment Ltd v HMRC [2020] UKFTT 232 (TC): someone must speak authoritatively to the state of knowledge in the field.
Paragraphs 119–121: operational decision-making, risk management and adaptation of existing guidance. Not R&D for Part 13 CTA 2009. Appeal dismissed.
Why this is a live CFO controls issue in 2026
Do not dismiss Tanglewood as a Covid claim that was always going to fail. The facts are older; the control failure is current. HMRC’s posture has hardened through claim notification, the Additional Information Form, the merged scheme from periods beginning on or after 1 April 2024, and heavier enquiry selection. The legal spine — field advance, scientific or technological uncertainty, competent professional — still sits under the DSIT Guidelines for later periods. Soft system-uncertainty narratives without technical evidence remain a write-off risk.
Three board-level traps show up again and again:
Trap A — “We did something new to us.” New to the company is not enough. Paragraph 22 of the BEIS text is blunt: routine adaptation of an existing process is not an advance even if it is completely new to the trade. Your internal first-time deployment of known tech is usually a capital/opex story, not an R&D story.
Trap B — “System uncertainty” as marketing language. Combining known components can qualify. It qualifies when a competent professional cannot readily deduce the combination that delivers the intended function, and when the work is a planned investigation to resolve that uncertainty. It does not qualify because a consultant’s template uses the phrase “system uncertainty” twelve times.
Trap C — Outsourced claim packs with no technical owner. If the only people who can defend the claim are the agent who sold it and the FD who booked the credit, you are already in Tanglewood territory. Finance can own the tax mechanics. A competent professional in the relevant scientific or technological field must own the advance and the uncertainty narrative — in contemporaneous project records, not in a retrospective essay.
What “good” looks like on an R&D file
Before sign-off, every claim needs four artefacts:
1. Field and baseline. Which field? What was publicly available or readily deducible at the start? Cite standards, papers, prior art — not “we had never done this.”
2. Uncertainty that survives cross-examination. Possibility, feasibility, or how to achieve it in practice? Why not readily resolvable? Separate commercial risk and ops chaos from scientific or technological uncertainty.
3. Competent professional on the record. Named person, discipline, role, and a written view on baseline, uncertainty and advance. If your only witnesses are ops managers describing process change, re-scope before HMRC does.
4. Boundaries and cost trail. Start/end around the uncertainty, not the commercial programme. Map staff, EPWs, consumables and software to uncertainty work — not to “everything in the pandemic / transformation / ERP cutover.”
Under the merged scheme, AIF content must match the technical file. Use HMRC’s main guidance, DSIT Guidelines and CIRD — not the agent brochure.
CFO checklist — lock this month
1. Inventory open R&D credits and contingent claims. By entity, period, scheme (old SME / RDEC / merged / ERIS), amount in CT return, amount not yet claimed, and agent. Flag any claim whose technical owner is “the adviser.”
2. Kill or re-scope soft Covid / ops / pure process claims still in enquiry or amendment. If the narrative is “we adapted known measures under pressure,” Tanglewood is the blueprint HMRC will use. Do not fund a bad fight for optics.
3. Require a competent-professional memo before sign-off. No memo, no claim. The memo must address baseline knowledge, uncertainty, advance sought, and why failure (if any) still left qualifying activity.
4. Align board reporting with tax risk. R&D cash is not free equity. Book it as contingent until the technical file would survive Tribunal language like paragraphs 119–121 of Tanglewood. Audit committee should see claim concentration and enquiry exposure, not just the P&L credit.
5. Separate genuine product/process R&D from transformation theatre. ERP rollouts, shared-service redesign, “AI enablement” of existing workflows and customer-journey optimisation are usually commercial projects with a thin tech wrapper. Apply the same four tests. Most will fail cleanly — which is a control success, not a missed opportunity.
6. Watch PE portfolio companies. Underwriting that capitalised “R&D intensity” or exit multiple support from soft claims needs a re-cut. A post-deal HMRC clawback is a locked-box and warranty problem, not a tax footnote.
Bottom line
Tanglewood is not a case about care homes. It is a case about evidence. The Tribunal was prepared to respect operational ingenuity under extreme pressure. It was not prepared to relabel that ingenuity as an advance in science or technology without a field baseline, scientific or technological uncertainty, and a competent professional who could speak to both.
If your next R&D claim cannot answer those three points in plain English, with names and documents, do not file it. The cheaper control is a smaller, defensible claim. The expensive control failure is an £880k enhancement that becomes a closure notice, a CT restatement and a board conversation you did not budget for.