The competent professional standard comes from the BEIS Guidelines on the Meaning of Research and Development for Tax Purposes, which define R&D for all UK tax relief purposes. The guidelines are not a document most CTOs will have read, but understanding what they say about the competent professional standard is directly relevant to how the technical narrative in your Additional Information Form should be structured.
What the Competent Professional Standard Actually Means
The BEIS Guidelines define R&D as activity that seeks to achieve an advance in science or technology. The advance must go beyond what a competent professional working in the relevant field would already know. The competent professional is not a world-leading expert; they represent the ordinary skilled practitioner in the discipline.
The test is applied at the start of the project. At the point when your team began the work, what would a competent professional in the field have already known? If your project sought to solve a problem that was already solved and the solution was publicly available, it does not qualify as R&D. If the solution was genuinely unknown at the outset, even if it turned out to be straightforward in hindsight, it may qualify.
This standard is the most commonly contested point in HMRC R&D enquiries. HMRC's enquiry officers have challenged claims by asserting that the technical uncertainty was not genuine because a competent professional could have resolved it with standard knowledge. Defending those challenges requires evidence of the state of knowledge in the field at the relevant time.
What Your CTO Actually Does in the Claim Process
There is no formal requirement for your CTO or any other named individual to sign the R&D claim documents. The company tax return is signed by a director or officer. The Additional Information Form is submitted through HMRC's online portal under the company's Government Gateway account.
What the CTO (or equivalent senior technical person) should do:
- Write or review the project narratives in the AIF. These must describe the technical uncertainties at the start of each project, what knowledge existed at baseline, what work was done to resolve the uncertainty, and why the outcome was not known in advance.
- Confirm the time apportionment for qualifying employees. The CTO is typically best placed to verify that the percentages attributed to qualifying R&D work for each team member are accurate and defensible.
- Retain any technical records, such as design documents, sprint retrospectives, code commit logs, or prototype test results, that could be produced in a compliance check.
A CTO who delegates the entire AIF narrative to an adviser who does not understand the technology is not serving the claim well. HMRC's reviewers are increasingly experienced at identifying generic narratives that do not reflect a real understanding of the technical challenge. The best AIF narratives come from people who actually did the work.
What Qualifications Count as Competent Professional
The guidelines do not require a formal academic qualification. A person who is competent through experience alone can be the relevant benchmark. A lead developer with ten years of experience in distributed systems is a competent professional in distributed systems for R&D purposes, whether or not they hold a computer science degree.
What matters is whether the person understands the current state of published knowledge in the field well enough to identify what constitutes an advance beyond it. In practice, this means being familiar with current academic research, relevant industry standards, and the existing commercial solutions in the problem space.
For HMRC enquiry purposes, a CTO or technical lead who can describe what approaches were tried before the qualifying R&D began, what was already known in the industry, and why the problem had not been solved before is demonstrating exactly the kind of competence that supports a valid claim.
When You Need an External Expert Opinion
For standard R&D claims, internal technical staff providing the AIF narrative is sufficient. An external expert opinion becomes useful in two specific situations:
HMRC challenges the technical uncertainty. If HMRC opens a compliance check and argues that your activities were not genuinely uncertain, an opinion from an independent expert with academic or industry credentials can provide an objective view of the state of the art at the project start date. Tribunals have given weight to expert opinions from respected practitioners in the relevant field.
Highly specialised or novel fields. Where the R&D involves a highly specialised domain, for example a new approach in computational biology or a novel machine learning architecture, an external academic or industry expert may be better placed than HMRC's own technical advisers to assess the state of the art. Commissioning an opinion proactively, before an enquiry, can reduce the risk of a challenge.
The external expert should be independent of the company, credentialed in the relevant field, and be willing to provide a written opinion that is defensible at tribunal if needed. See the qualifying expenditure guide for what documentation supports a claim at the cost level, and the enquiry triggers post for what HMRC looks for when reviewing technical narratives.
Solo Founder or Small Team: When There Is No CTO
Many early-stage R&D companies do not have a dedicated CTO. The founder-developer, technical co-founder, or lead engineer performs all of the functions described above. This is entirely acceptable. The competent professional test asks about the state of the field, not about the seniority or job title of the person performing the work.
A solo founder with deep technical expertise in their domain can write compelling, defensible AIF narratives that satisfy HMRC's requirements. What they cannot do is delegate the technical writing to someone who does not understand the work. The person writing the narrative needs to know enough about the field to describe the baseline accurately. Use our eligibility checker as a starting point, then get a specialist to review the AIF before submission.
Frequently Asked Questions
The BEIS Guidelines define a competent professional as a person familiar with the state of knowledge in the relevant field at the start of the R&D project. They represent the ordinary skilled practitioner, not a world expert. The test is used to identify whether the uncertainty your team faced was genuine or whether it was already solved in publicly available knowledge.
There is no formal requirement for any named individual to sign R&D claim documents. The company tax return is signed by a director or officer. The AIF is submitted through the company's Government Gateway account. The CTO or technical lead should write or review the project narratives in the AIF to ensure they accurately describe the technical uncertainties.
Qualifications are relevant but not the primary test. Competence can come through experience, not just formal qualification. What matters is whether the person understands the current state of published knowledge well enough to identify what constitutes an advance beyond it.
An external consultant can provide technical validation of a claim, but they should not replace the internal technical narrative. HMRC expects the AIF to reflect the actual experience of the company's technical staff. An external expert can supplement internal narratives in contested cases, but the primary account should come from people who did the work.
HMRC may argue that the technical uncertainty was not genuine because a competent professional could have resolved it with standard knowledge. Defending this requires evidence of the state of knowledge at the start of the project, such as published papers, prior art searches, or documentation showing what approaches were attempted and why they failed.
Get the Technical Narrative Right from the Start
Uplift Tax works with HMRC-registered specialists who know how to structure AIF narratives to satisfy the competent professional test. The assessment is free.
Request Your Free Assessment