{"id":46561,"date":"2026-08-26T09:00:49","date_gmt":"2026-08-26T07:00:49","guid":{"rendered":"https:\/\/nexuswelt.com\/?p=46561"},"modified":"2026-08-26T21:27:59","modified_gmt":"2026-08-26T19:27:59","slug":"horizon-europe-impact-section-scoring","status":"publish","type":"post","link":"https:\/\/nexuswelt.com\/de\/horizon-europe-impact-section-scoring\/","title":{"rendered":"Horizon Europe Impact Section: How to Write It So Evaluators Score It High"},"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

Impact is where technically excellent proposals lose. A consortium that scores well on Excellence and Implementation and only three out of five on Impact will usually not be funded, because in a field this competitive the threshold is not the problem – the ranking is.<\/span><\/span><\/p>

The difference between a three and a five is rarely ambition. It is causal logic: whether an evaluator can follow a plausible chain from what you will do, through what will exist because of it, to who will change their behaviour as a result. This article covers how to build that chain, how the 2026 template changed what belongs in the section, and what separates a scoring impact section from a plausible-sounding one.<\/span><\/span><\/p>

How Impact is scored<\/b><\/span><\/span><\/span><\/h2>

Every collaborative proposal is assessed against three criteria – Excellence, Impact and Implementation – each scored from zero to five, each with a threshold below which the proposal is rejected regardless of the other scores. For innovation actions, Impact carries additional weight in the ranking formula, which is worth knowing before deciding how to allocate writing effort.<\/span><\/span><\/p>

Evaluators assess two things under Impact: the credibility of the pathways from your activities to the expected outcomes and wider impacts, and the magnitude and importance of those impacts. Credibility comes first. An enormous claimed impact with no plausible route to it scores worse than a modest one with a convincing chain.<\/span><\/span><\/p>
Score<\/b><\/span><\/span><\/span><\/td>What it looks like<\/b><\/span><\/span><\/span><\/td>Why it happens<\/b><\/span><\/span><\/span><\/td><\/tr><\/thead>
5<\/b><\/span><\/span><\/td>A specific, evidenced causal chain; named users; realistic magnitude; measures that clearly serve the pathway<\/span><\/span><\/td>The consortium designed the impact logic before writing, and the work plan reflects it<\/span><\/span><\/td><\/tr>
4<\/b><\/span><\/span><\/td>Credible pathway with one or two soft links or unevidenced assumptions<\/span><\/span><\/td>Usually a single weak step – often the transition from result to user<\/span><\/span><\/td><\/tr>
3<\/b><\/span><\/span><\/td>Plausible but generic. Societal benefits described in broad terms without a credible route to them<\/span><\/span><\/td>The section was written after the technical work was designed, as narrative rather than logic<\/span><\/span><\/td><\/tr>
Below 3<\/b><\/span><\/span><\/td>Claims without mechanism, or impacts unrelated to the topic’s expected outcomes<\/span><\/span><\/td>The topic text was not used as the anchor<\/span><\/span><\/td><\/tr><\/tbody><\/table>

The three is the dangerous score. It passes the threshold, feels acceptable when you read it back, and quietly removes you from the funded range.<\/i><\/span><\/span><\/p>

Start from the topic, not from your project<\/b><\/span><\/span><\/span><\/h2>

The single most common structural error is writing the impact you would like your project to have, then attempting to connect it to the call. The order has to be reversed.<\/span><\/span><\/p>

Each topic states expected outcomes, and sits within a destination with wider expected impacts. Those are the targets your section must hit. But repeating them verbatim is not the answer either – evaluators read the same restated sentences in every proposal on their pile.<\/span><\/span><\/p>

What scores is restating them implicitly through your own specific results. If a topic expects improved decision-making by public authorities, the section should identify which of your outputs – a validated decision-support tool, a dataset, a guideline – produces that improvement, which authorities could realistically adopt it, and under what conditions they would.<\/span><\/span><\/p>

Outputs, outcomes, impacts: keep them distinct<\/b><\/span><\/span><\/span><\/h2>

\"\"<\/p>

Most weak sections list outputs and then assert impacts, skipping the outcome entirely. The outcome is the load-bearing step: it is where a real person outside the consortium does something differently. If you cannot name that person and that change, the chain is broken and an evaluator will see the gap.<\/span><\/span><\/p>

Building the pathway<\/b><\/span><\/span><\/span><\/h2>

For each significant result, write the chain explicitly:<\/span><\/span><\/p>

  1. The result – what will exist that does not exist now, described concretely.<\/span><\/span><\/li>
  2. The user – who takes it up, named by type and where possible by example.<\/span><\/span><\/li>
  3. The barrier – what currently prevents that uptake, and what in your project removes it.<\/span><\/span><\/li>
  4. The mechanism – through what route the result reaches that user: licensing, standardisation, policy channel, open publication, further research, training.<\/span><\/span><\/li>
  5. The condition – what has to be true for the mechanism to work, including things outside your control.<\/span><\/span><\/li>
  6. The evidence – why this is plausible: preliminary data, letters of intent, comparable adoption rates, prior funded work.<\/span><\/span><\/li><\/ol>

    Naming a condition outside your control strengthens the section rather than weakening it. It signals that the consortium understands the environment it is operating in. A pathway with no stated assumptions reads as one nobody stress-tested.<\/span><\/span><\/p>

    What changed in the 2026 template<\/b><\/span><\/span><\/span><\/h2>

    The 2026\u20132027 impact section was streamlined. Applicants are no longer required to describe general scientific, economic and societal impacts in the abstract, or to quantify the scale and significance of expected contributions. For the wider context, see our overview of what changed in the 2026\u201327 work programme<\/a>.<\/span><\/span><\/p>

    Two consequences follow, and they pull in opposite directions from how the change is usually read.<\/span><\/span><\/p>