By Max Fellows, Founder of allpoints
Have you heard of the R&D grant? When you run an event agency, production house, tech service or supplier, you probably don’t think of your team as a research and development department. You’re creating experiences, solving client problems, working around briefs, bringing different ideas, innovations and technologies together and finding ways to deliver ideas that haven’t necessarily been done before.
Occasionally, the heavy lifting behind the scenes isn’t just creative problem-solving; it’s actual research and development. If your team is already spending time and money to beat complex hurdles, those efforts might actually qualify for R&D tax relief.
What does R&D actually mean?
For tax purposes, R&D (Research and Development) has a much tighter definition than simply doing something innovative. HMRC looks for projects seeking an advance in science or technology while tackling scientific or technological uncertainty that couldn’t readily be resolved by a competent professional in that field.
For event agencies and event businesses, that distinction is important.
Creating a completely original activation, designing an incredible experience or finding a clever new way to engage an audience does not automatically make a project R&D. The creative idea itself isn’t the qualifying part.
The question is what had to happen technically, or from a research perspective, to make that idea possible.

Where could R&D appear within an event project?
Think about the projects where the initial response from your production or technology team wasn’t simply “we know how to build that”, but closer to “we’re going to have to work out whether this is actually possible.”
While much of the focus is often on the “development” of physical or digital solutions, the “research” element is just as crucial. This involves proprietary research, conducting systematic testing, gathering original data, or undertaking scientific exploration to uncover new technical knowledge that isn’t currently available in the public domain. If your team had to run controlled experiments, rigorously test new material properties under unique event conditions, or carry out formal investigations just to understand if a solution was theoretically possible, this essential groundwork is a vital part of a qualifying R&D project.
That could include projects where your team has had to:
- Develop or significantly adapt software because existing technology couldn’t achieve the required functionality.
- Find a new technical way of connecting platforms, systems or data where the solution wasn’t readily apparent.
- Develop technology for immersive, interactive or hybrid experiences that required substantial testing and experimentation.
- Overcome engineering or technical limitations within the physical delivery of an experience.
- Create new technical processes to improve areas such as performance, scalability, data handling or energy use, where the solution requires more than applying established methods.
Software integration can potentially qualify, for example, where combining existing technologies presents a technological uncertainty and a competent professional couldn’t readily determine how to make them work together as required. Simply connecting two existing platforms in a conventional way would be very different.
That distinction is where many agencies need to look more closely.

Six questions worth asking after a complex and technically difficult project
Rather than asking your finance team, “Did we do any R&D this year?”, start with the people who actually delivered the work.
Ask:
- What were we trying to achieve technically?
- What stopped us from using an existing or readily available solution?
- What research was carried out to uncover a new learning?
- Did we have to conduct original experiments or systematically gather new data because existing industry knowledge couldn’t provide the answer?
- What did our technical team genuinely not know how to solve at the beginning?
- What testing, development or iteration did we undertake to get there?
If there are strong answers to those questions, there may be something worth exploring.
Equally, there may not be. R&D tax relief shouldn’t become an exercise in retrospectively making an ordinary project sound more complicated than it was. If existing knowledge, products or standard processes could readily solve the problem, it is unlikely to meet HMRC’s definition.

What costs could be relevant?
Where a project does qualify, the associated expenditure can extend beyond the most obvious development costs.
Depending on the circumstances, qualifying expenditure can include areas such as employee costs, software, consumable items, data licences, cloud computing and certain contractor or externally provided worker costs. The rules around contracted-out R&D changed for accounting periods beginning on or after 1 April 2024, so agencies working across clients, production partners and specialist suppliers need to be particularly careful about who decided the R&D grant was required and where the work took place.
Good project records therefore matter. Technical briefs, development notes, testing, iterations and evidence of the problems encountered can all help build a much clearer picture of what happened during the project than trying to reconstruct the story months later.

Don’t wait until year-end to think about it
There are also deadlines attached to R&D grant claims. Businesses making their first claim, or those that haven’t made a qualifying recent claim, may need to notify HMRC within six months of the end of the relevant period of account. An additional information form must also be submitted before, or on the same day as, the relevant Company Tax Return.
For agency and business owners, the bigger lesson is to make R&D part of the project review process rather than something left entirely to the finance team at year-end.
When a job has required your team to push beyond what was technically straightforward, document it, because while your client may remember the finished experience, some of the most valuable innovation could have happened behind the scenes while your team was figuring out how to make it work.








































