Exploitation of Results: Turning EU Project Outputs into Something That Survives the Grant

Munich, 28 October 2026 · Nexuswelt Group

Exploitation is the work package that gets written in the proposal, deferred through the project, and confronted in the final year – when ownership was never settled, the intended users were never consulted, and the consortium is three months from dissolving.

It is also the only part of the project that determines whether anything survives the grant. This article covers what exploitation actually requires, how to identify and mature the results worth exploiting, the ownership questions that have to be settled early, and the free support most consortia never use.

What exploitation actually means

The distinction from dissemination is not pedantry – it is the difference between a section that scores and one that does not.

A credible communication, dissemination and exploitation plan should distinguish these activities and define how each contributes to project outcomes. Listing academic publications as an exploitation strategy is the single most common error in this area. Publications are dissemination. Exploitation is what somebody does with the result afterwards, and a section that lists conferences has effectively been left blank.

Key Exploitable Results: narrow, do not expand

A result is any output of the action – data, knowledge, software, a method, a dataset, a policy recommendation – together with the rights attached to it. Key Exploitable Results are the subset the partners prioritise as having genuine downstream value.

The instinct is to list everything. Resist it. Three well-supported KERs with named owners, identified users and credible routes will outperform twelve unowned ones at final review, and they will produce a better project along the way because the consortium has decided what matters.

A workable rhythm:

1. 1. Month six: identify candidate KERs, provisionally. This is early enough to be wrong and late enough to be informed.
   2. Each reporting period: assess each candidate for maturity, ownership clarity and user interest.
   3. Progressively narrow. A list that grows through the project is a list nobody is managing.

1. Final year: the surviving KERs should each have an owner, a route and a stated next step beyond the grant.

Ownership, settled early

Results are owned by the partner that generates them, with access rights and exploitation arrangements set out in the grant agreement and negotiated in more detail in the consortium agreement. That sounds settled. In practice it is where exploitation most often fails.These responsibilities should be addressed during year-one consortium management, before ownership and access-rights questions become disputes.

The situations that cause trouble:

• Joint ownership arising from genuinely collaborative work, without an agreed regime for how it will be exploited or how revenues are shared.
• Background intellectual property that a partner brought in, without clear access rights for the others to exploit results built on it.
• Results generated by a partner who has no interest in exploiting them and no obligation to let anyone else.
• Software with dependencies whose licences constrain commercial use, discovered when a licence is being negotiated.

All of these are resolvable in year one and expensive in year three. Raise them while the relationships are new and nothing is at stake yet – a conversation about hypothetical revenue is considerably easier than one about actual revenue.

The exploitation routes

Exploitation is not a synonym for commercialisation. Most EU project results are exploited through routes that involve no sale at all.

The post-project problem

Exploitation obligations continue for a defined period after the project’s end date. Most consortia dissolve at the end date. These two facts sit awkwardly together and the gap between them is where results die. Exploitation does not end at project closure. It remains part of the wider EU project lifecycle, with responsibilities for results, maintenance and stakeholder relationships continuing beyond the grant.

What has to be decided before the consortium disperses:

• Who holds each result, in writing, with contact details that will still work in two years.
• Who maintains anything that requires maintenance – a dataset, a piece of software, a platform. “The community” is not an answer unless a community exists.
• Who holds each stakeholder relationship. Relationships built by a project end with it unless someone inherits them.
• How any later uptake gets recorded and shared, since the impact case continues after the final review. Tracking post-project uptake requires clear impact pathways and KPIs that connect results with evidence of actual use.
• What happens to the project website and its content, which typically disappears within two years of the funding ending.

A project that answers none of these has not completed its exploitation work, whatever the final report says.

Free support most consortia never use

The Commission funds a support ecosystem specifically for this, and it is consistently underused. Engaging with it costs nothing and reviewers notice when a consortium has. The European Research Executive Agency’s dissemination and exploitation pages are the entry point.

A line in the periodic report noting which of these you engaged with and what came of it carries more weight than pages of activity counts.

Common failures

• Exploitation described as publications and conferences.
• “Too early to consider” at low TRL. Early-stage research has identifiable downstream users, and evaluators flag this answer explicitly.
• A KER list that grows rather than narrows, indicating nobody is managing it.
• Ownership left to the consortium agreement and then never revisited.
• An exploitation plan written by the communication partner without the technical partners who own the results and know the users.
• Commercialisation assumed as the only legitimate route, when internal use, policy input or standardisation is the realistic one.
• No named owner for results after the end date.
• Waiting for the final year, by which point ownership, maturity and user interest are all unresolved simultaneously.

A year-by-year rhythm

Exploitation planning starts with the Horizon Europe impact section, where the intended users, uptake pathways and expected outcomes must form a credible logic.

How Nexuswelt works on exploitation

Exploitation fails at the design stage more often than at the delivery stage, and by the final year the available options are whatever the earlier decisions left open. Nexuswelt contributes to EU-funded projects as a partner on communication, dissemination, stakeholder engagement and exploitation, working on KER identification, ownership clarity and route design from the proposal onward. The wider treatment of coordinator obligations is in our guide to communication, dissemination and exploitation, and more on the firm is on the Nexuswelt about page. Organisations preparing or implementing Horizon Europe projects can explore Nexuswelt’s support for communication, dissemination, stakeholder engagement and exploitation.

Frequently asked questions