Horizon impact pathways: connect every result to an uptake actor and barrier

A Horizon Europe proposal can contain strong research and still present a weak pathway to impact. The common failure is not always a lack of ambition. It is the missing chain between what the project will generate and what a defined user will actually do differently because that result exists.

The European Commission's current full Horizon Europe RIA/IA and CSA application forms separate three levels. Results are generated during implementation. Outcomes are expected medium-term effects supported by the uptake, diffusion, deployment or use of those results by direct target groups. Impacts are wider long-term effects on society, the economy or science, enabled by those outcomes.

That distinction matters because a deliverable is not automatically an outcome and an outcome is not automatically an impact. A validated model, dataset, demonstrator, protocol or policy recommendation may be a valuable result. The proposal must still explain who will use it, for which decision or process, under what conditions and at what scale.

The current full RIA/IA and CSA forms ask applicants to describe the unique contribution their results would make to the expected outcomes in the topic and the wider impacts in the destination. They also ask for specific target groups rather than a generic statement that society, industry or policymakers will benefit.

A credible target group is operationally defined. Instead of 'public authorities', identify the type of authority, its mandate, the decision cycle it controls and the role able to adopt the result. Instead of 'industry', identify the relevant operators, technology integrators, buyers, standards bodies or investors and the conditions under which each would act.

Both forms also ask applicants to identify requirements and potential barriers beyond the project's immediate scope and duration. Examples include other research, regulation, markets and user behaviour. These are not the same as internal project-management risks. They are conditions that determine whether a sound result can travel into use.

PRINCEPS recommends one uptake-chain row for each material result, with seven fields:

1. Result — the specific knowledge, method, dataset, tool, demonstrator, standard input, service model or other asset the project will generate.

2. Uptake actor — the precisely defined organisation, professional group, community or decision-maker expected to use it.

3. Use decision — the procurement, policy, operational, research, investment, clinical, regulatory or community decision the result is meant to support.

4. Uptake mechanism — the demonstration, validation, licensing, standardisation, training, procurement, policy-engagement, open-access or commercialisation route that moves the result into use.

5. Observable outcome — the measurable change expected among the target users during or shortly after the project.

6. Barrier and assumption — the external condition that can prevent or delay uptake, including regulation, affordability, infrastructure, trust, skills, evidence thresholds or competing incentives.

7. Mitigation and owner — the project measure, responsible partner, decision point and post-project route for responding if the assumption proves wrong.

This is a PRINCEPS proposal-control method, not an official European Commission template. It is a detailed extension of PRINCEPS' earlier communication, dissemination and exploitation lesson to test adoption result by result; it is not a replay of that earlier overview. Its purpose is to expose gaps that a broad impact paragraph can conceal.

The Commission distinguishes dissemination from exploitation. Dissemination makes results available to people who can use them. Exploitation concerns actual use, including developing or improving a product, process or service, contributing to standards, shaping policy or enabling wider uptake. Communication supports visibility and engagement but does not by itself prove use.

The practical implication is that each channel should have a job. A scientific paper may support validation and scientific uptake. A standards workshop may move a technical method towards codification. A regulator briefing may support a policy or approval decision. A business case and demonstrator may support procurement or investment. Listing channels without the intended user decision leaves the pathway incomplete.

African partners should be positioned as uptake actors and implementation owners where that matches their role, not only as sites, data sources or dissemination audiences. A ministry, city, university, operator, association or community organisation may control adoption conditions that no European partner can substitute. The proposal should make that authority, resource requirement and benefit visible.

Before submission, reconcile the uptake-chain rows with the work programme outcome wording, work packages, deliverables, milestones, exploitation measures, intellectual-property choices, communication activities, budget and risk logic. Every quantitative claim should state its baseline, unit, timeframe, attribution boundary and source or estimation basis.

This analysis is strategic and editorial. It does not guarantee evaluation success, funding, adoption, commercialisation or policy change. The live topic, destination, application form, General Annexes, Model Grant Agreement and submission system remain controlling.

Editorial note: This is PRINCEPS analysis for general information. It does not replace the official work programme, topic conditions, submission system, grant rules or professional advice specific to an application.