FastGrowth All articles
Finance & Cash Flow

Memory Is Not a Filing Cabinet: The 60-Day R&D Evidence Sprint for UK Founders

FastGrowth
Memory Is Not a Filing Cabinet: The 60-Day R&D Evidence Sprint for UK Founders

Photo: Utopai Studios, CC BY 4.0, via Wikimedia Commons

Most UK scale-ups do not set out to make a wobbly R&D claim. They set out to file the paperwork, get the relief and get back to building the business. Then a compliance letter lands, and suddenly the technical narrative has to be reconstructed from old Slack threads, half-finished sprint notes and the memory of whoever was leading the project two years ago.

That is the moment founders discover the uncomfortable truth: HMRC is not really buying your story. It is buying the trail that proves the story was true at the time. If the trail does not exist, a 60-day sprint is not about dressing up a claim. It is about finding out whether there is a defensible claim at all — and walking away from the ones that cannot be evidenced.

Why the story fails before the numbers do

R&D tax relief reviews tend to go wrong in a predictable order. The cost schedule looks fine. The accountant has done the maths. Then HMRC asks who identified the scientific or technological uncertainty, what competent professionals worked on it, what alternatives were explored, and why the work was not routine engineering or standard software development.

That is where the narrative collapses. A sentence like we improved the platform is not evidence. A project card that says we did not know whether the new ingestion layer could handle peak load without breaking data integrity, and we tested three architectures before finding one that worked, is much closer. The difference is specificity, dates and named people.

Days 1–10: appoint a claim owner and freeze the file

The first mistake is letting the claim live in an accountant's inbox. Give it an internal owner — usually a finance lead working with a technical lead — and create one indexed claim file. Every document should have a date, a project name and a person attached to it.

This is also the week to check pre-notification. If this is your first R&D claim, or you are claiming after a gap, HMRC generally needs notification within six months of the end of the accounting period. For a period ending 31 December 2026, that clock runs to 30 June 2027. Miss it and the claim can be invalid before anyone argues about the science. Do not leave pre-notification until the return is being filed.

Days 11–25: turn projects into uncertainty logs

Build one-page project cards. For each project, capture the baseline before the work started, the uncertainty that could not be resolved by existing knowledge, why routine methods were not enough, the experiments attempted, and the outcome — including failures. Failures are useful. They show the work was genuinely uncertain rather than a tidy story written backwards.

Name the competent professional on each project. That means someone with relevant technical experience, not simply the most senior person available. Record their role, qualifications or equivalent experience, and the specific decisions they made. If the R&D adviser wrote the technical narrative without input from that person, expect trouble.

This is also where you separate advance in science or technology from ordinary product work. A new pricing page, a customer portal refresh or a routine cloud migration is not R&D just because it is difficult. The test is whether you were trying to resolve a technological uncertainty by advancing capability beyond what was readily available to competent professionals.

Days 26–40: rebuild the time and cost trails

HMRC wants to see how people and costs connect to projects. Pull together timesheets, sprint boards, ticket logs, git commits, calendar blocks, lab notebooks and project plans. Not every founder has clean timesheets, but most have something better than a round-number guess. Use named individuals, hours or percentages, and project codes.

Supplier costs need the same treatment. Cloud bills, subcontractor invoices, testing services and specialist materials should be tied to the project through contracts, statements, invoices and a sensible apportionment method. If 30 per cent of a cloud bill relates to R&D, show how you got to 30 per cent. Do not round up because the claim looks better that way.

If the records genuinely do not exist, reduce the claim or exclude the cost. A smaller claim that survives is worth more than a larger one that triggers an enquiry, penalties and a lot of founder time.

Days 41–50: red-team the claim

Ask someone sceptical to review the file as if they were HMRC. Give them the technical narrative, the cost schedule and the project cards, and ask three questions: what was uncertain, who was competent to resolve it, and what evidence proves the work happened when you say it did?

Check for consistency. The project dates in the narrative should match the time records. The people named in the technical write-up should appear in the cost schedule. The senior officer endorsement should come from someone who can actually stand behind the claim. If your adviser is named on the additional information form, make sure their details and role are accurate.

Days 51–60: submit, shrink or walk away

By day 60 you should have a decision, not another workshop. Submit with the additional information form, keep the claim file intact and store it somewhere the finance team can find it in three years. Or shrink the claim to the projects that can be evidenced. Or walk away.

Walking away is not failure. If the uncertainty was vague, the work was routine, the time records are guesswork and the supplier costs cannot be tied to a project, the claim is a liability dressed up as cash. HMRC does not need a perfect story. It needs a boring, dated, named trail that shows the claim was built as the work happened — not reconstructed after the letter arrives.

This is practical finance work, not tax magic. Get the evidence in order, keep the founder time contained, and treat the claim as something you may have to defend. That is the version of R&D relief that actually helps a scale-up sleep at night.

All Articles

Related Articles

The Guarantee You Forgot You Signed: A 30-Day Personal Exposure Map for UK Founders

The Guarantee You Forgot You Signed: A 30-Day Personal Exposure Map for UK Founders

The Bench That Bites Back: A 45-Day Off-Payroll Reality Check

The Partner You Call a Channel Is Probably a Cost Centre: A 45-Day Margin Audit

The Partner You Call a Channel Is Probably a Cost Centre: A 45-Day Margin Audit