{"id":46661,"date":"2026-09-02T09:00:23","date_gmt":"2026-09-02T07:00:23","guid":{"rendered":"https:\/\/nexuswelt.com\/?p=46661"},"modified":"2026-08-20T15:53:21","modified_gmt":"2026-08-20T13:53:21","slug":"stakeholder-engagement-eu-projects","status":"publish","type":"post","link":"https:\/\/nexuswelt.com\/de\/stakeholder-engagement-eu-projects\/","title":{"rendered":"Stakeholder Engagement in EU Projects: Turning Results into Uptake"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Munich, 2 September 2026 \u00b7 Nexuswelt Group<\/span><\/span><\/span><\/p>

A project can finish every deliverable, publish well, hold every planned workshop, and produce nothing that anybody outside the consortium uses. This is the most common form of failure in EU-funded work, and it does not appear in any report as a failure.<\/span><\/span><\/p>

Uptake requires that people outside the project were involved before the results existed. That is what stakeholder engagement is for. It is not awareness-raising with a different name, and treating it as such is why so many technically successful projects end with a dissemination record and no adopters.<\/span><\/span><\/p>

Awareness is not acceptance, and acceptance is not uptake<\/b><\/span><\/span><\/span><\/h2>

These three words are used interchangeably in most project documents. They describe different states, they require different work, and only the last one supports an impact claim.<\/span><\/span><\/p>

\"Stakeholder<\/p>

Most engagement plans stop after the second row. The gap between understanding and acceptance is where projects lose their impact, and it cannot be closed by producing more material.<\/i><\/span><\/span><\/p>

Consultation is not engagement<\/b><\/span><\/span><\/span><\/h2>

There is a hierarchy of involvement, and where a project sits on it determines what it can credibly claim.<\/span><\/span><\/p>
Level<\/b><\/span><\/span><\/span><\/td>What happens<\/b><\/span><\/span><\/span><\/td>What it can produce<\/b><\/span><\/span><\/span><\/td><\/tr><\/thead>
Informing<\/b><\/span><\/span><\/td>You tell them what you are doing<\/span><\/span><\/td>Awareness<\/span><\/span><\/td><\/tr>
Consulting<\/b><\/span><\/span><\/td>You ask their opinion, then decide<\/span><\/span><\/td>Better-informed decisions, and often resentment if the input visibly changed nothing<\/span><\/span><\/td><\/tr>
Involving<\/b><\/span><\/span><\/td>They participate in shaping the work at defined points<\/span><\/span><\/td>Understanding and some acceptance<\/span><\/span><\/td><\/tr>
Co-creating<\/b><\/span><\/span><\/td>They help produce the result, and their knowledge is treated as equivalent input to technical expertise<\/span><\/span><\/td>Acceptance, co-ownership, and a realistic route to uptake<\/span><\/span><\/td><\/tr><\/tbody><\/table>

In some parts of Horizon Europe this is not optional. The multi-actor approach requires genuine and sufficient involvement of relevant actors in co-creation, from proposal drafting through to the end of implementation, and it is applied across a substantial share of topics in the clusters where it applies. Communicating results or running consultation activities does not satisfy it.<\/span><\/span><\/p>

The Commission’s own definition distinguishes actors – who are partners inside the consortium – from stakeholders and end users, who are external and targeted by the project. Both matter, but only actors are integrated as beneficiaries. The <\/span><\/span>official description of the multi-actor approach<\/u><\/span><\/span><\/span><\/a> sets out the requirements in detail.<\/span><\/span><\/p>

Mapping stakeholders properly<\/b><\/span><\/span><\/span><\/h2>

Most stakeholder maps are a list of categories drawn up in an afternoon: industry, policymakers, academia, civil society. That is not a map, it is a table of contents.<\/span><\/span><\/p>

A usable map answers five questions for each group:<\/span><\/span><\/p>

  1. Who exactly – named organisations or precisely defined roles, not sectors.<\/span><\/span><\/li>
  2. What decision do they control that matters to your result? If they control no relevant decision, they are an audience, not a stakeholder.<\/span><\/span><\/li>
  3. What is in it for them? A stakeholder with no interest in the outcome will not engage regardless of how well you communicate.<\/span><\/span><\/li>
  4. What would stop them adopting, specifically – cost, regulatory approval, integration with existing systems, skills, procurement rules, internal authority.<\/span><\/span><\/li>
  5. Who do they trust? Uptake usually travels through an intermediary rather than directly from a research consortium.<\/span><\/span><\/li><\/ol>

    That last question is the one most maps omit and the one that most often determines whether anything happens. A regional authority is more likely to adopt a method recommended by its national association than one presented by a project it has never heard of.<\/span><\/span><\/p>

    Timing: the engagement curve<\/b><\/span><\/span><\/span><\/h2>

    Engagement effort is usually distributed backwards. Projects run a kick-off workshop, go quiet through the technical work, and then attempt intensive outreach in the final six months – at the point when nothing about the result can still be changed in response to what they hear.<\/span><\/span><\/p>
    Phase<\/b><\/span><\/span><\/span><\/td>What engagement is for<\/b><\/span><\/span><\/span><\/td>What it looks like<\/b><\/span><\/span><\/span><\/td><\/tr><\/thead>
    Proposal stage<\/b><\/span><\/span><\/td>Establishing that the need is real and the intended users are interested<\/span><\/span><\/td>Letters of intent that mean something; named organisations; evidence in the impact section<\/span><\/span><\/td><\/tr>
    Early project<\/b><\/span><\/span><\/td>Validating the problem definition and the specification<\/span><\/span><\/td>Requirements workshops where the specification can still change as a result<\/span><\/span><\/td><\/tr>
    Mid project<\/b><\/span><\/span><\/td>Testing and adjusting; building trust through visible responsiveness<\/span><\/span><\/td>Pilots, living labs, iterative feedback with documented changes<\/span><\/span><\/td><\/tr>
    Late project<\/b><\/span><\/span><\/td>Preparing adoption, removing barriers, transferring ownership<\/span><\/span><\/td>Training, procurement conversations, standards submissions, intermediary handover<\/span><\/span><\/td><\/tr>
    Post project<\/b><\/span><\/span><\/td>Continuation without the consortium<\/span><\/span><\/td>A named owner outside the project; a maintained resource; an intermediary carrying it forward<\/span><\/span><\/td><\/tr><\/tbody><\/table>

    The test for whether early engagement is real: has anything about the project changed because of what a stakeholder said? If nothing ever changes, the engagement is theatre, and stakeholders learn that quickly.<\/span><\/span><\/p>

    Why stakeholders disengage<\/b><\/span><\/span><\/span><\/h2>