By Julien Sudre, grant writer and founder of Grant360 and Innotrope. Originally published 8 December 2025. Updated: 23 September 2026.
Horizon Europe proposals fail for different reasons: some are ineligible or miss a submission requirement; others pass those checks but do not score highly enough, or score well without reaching the funding cut-off. In the proposal itself, recurring weaknesses include poor fit with the call, unclear objectives, an unconvincing route to impact, and a work plan or consortium that does not support the promised results. The remedy is to identify which weakness applies, then connect the call requirements, evidence, activities, partners and budget in one coherent case. The European Commission describes the evaluation and selection process.
This guide draws on the author's experience writing more than a hundred grant applications and his own review of all the Evaluation Summary Reports (ESR) received for all his applications. It focuses on collaborative Horizon Europe proposals; always check the conditions and evaluation form attached to your particular topic in the Funding & Tenders Portal. The examples below illustrate diagnostic questions, not a formula that guarantees funding.
Why does poor fit with the call weaken a proposal?
A proposal can be scientifically strong and still answer the wrong question. Check the topic's expected outcomes, scope, action type and specific conditions before shaping the project. For each central requirement, identify where the proposal explains the contribution and what work will produce it. The European Research Executive Agency's applicant advice recommends examining the specific call criteria and the project's contribution to the work programme's expected outcomes and impacts.
For example, if the topic asks for testing in real operational settings, a laboratory validation plan alone may leave a gap. Add an appropriate pilot and partner where the topic calls for one, or choose a different topic that fits the project. Copying an expected outcome into the Impact section without a matching activity does not resolve the mismatch.
What to do: Build a simple requirement map with columns for the call text, proposed response, responsible partner, planned evidence and section of the application. Treat missing rows as project design questions rather than wording problems.
Why do vague objectives and weak evidence cost points?
Objectives are hard to assess when they do not say what will change or how success will be checked. Replace broad intentions such as "increase resilience" with a defined result, context and method of verification. Support claims of novelty and feasibility with relevant research, preliminary results, user evidence or clearly stated assumptions. The Commission's standard application form for Research and Innovation Actions (RIAs) and Innovation Actions (IAs) sets out what applicants must explain under Excellence.
For instance, "improve flood response" could become "test whether the proposed forecasting method reduces alert time against the current procedure at three pilot sites." The target, baseline and method should be realistic for the project. A precise objective is useful only when the methods, data access and resources can support it.
What to do: For each objective, ask what evidence would demonstrate progress, who will produce it, and when. If the answer is unclear, revise the objective or the methodology.
Why does an Impact section fail even when the research is good?
An Impact section is weak when it describes outputs and promotional activities without showing how anyone will use the results. Identify users, their needs, barriers to adoption and the steps by which project results could contribute to the topic's expected outcomes. Distinguish the changes the consortium can plausibly influence from wider impacts that depend on later decisions. The official application form asks for pathways towards outcomes and impacts and for measures to maximise those effects.
A new software tool, for example, is a result. Training a group of public authorities and validating it in their decision process may be part of the pathway to uptake. Reduced processing time across many authorities would be a broader effect that requires assumptions about adoption and scale. A conference talk can help disseminate results, but it is not evidence of uptake by itself. Explain exploitation as the use of results, and communication as engagement with audiences about the project.
What to do: Draw a chain from each significant result to its intended user, the action needed for uptake, the measurable change and the supporting evidence. State baselines, timeframes and assumptions for numerical estimates.
Why do work plans and risk tables lack credibility?
A work plan becomes unconvincing when tasks do not support objectives, dependencies are impossible, deliverables do not mark useful progress, or resources are insufficient for the proposed activities. Risk tables are equally weak when every risk is generic and every response says "monitor closely." The Commission evaluates Quality and efficiency of implementation as one of the main criteria and provides work plan, milestone and risk tables in its RIA/IA template.
Suppose a pilot depends on ethical clearance and access to patient data. A schedule that starts recruitment before either is secured needs revision. The risk description should identify the potential delay, its effect on the pilot, who owns the response and an actionable alternative. Likewise, a task should have enough partner effort in the budget to be plausible.
What to do: Trace each objective into work packages, tasks, deliverables and effort. Then trace key results forward into the Impact section. Check each milestone against its prerequisites and each risk against a concrete response.
Why can consortium design undermine an otherwise strong idea?
A consortium is weak when it lacks a capability required to deliver the work, includes partners whose roles are unclear, or assigns responsibilities without corresponding effort. Explain what each participant will do and why its expertise or access matters. The Commission's evaluation form for RIAs and IAs addresses the capacity of participants and the consortium as a whole under implementation.
If a project promises clinical validation, show who can recruit participants, run the protocol, analyse results and manage relevant obligations. A prestigious institution in an advisory role does not automatically fill a missing operational capacity. Likewise, an end-user organisation should have a genuine task if its involvement is central to the proposed impact pathway.
What to do: For each partner, list its indispensable contribution, tasks, deliverables, effort and decision rights. Revisit partners whose contribution cannot be explained and identify capabilities the team still lacks.
Why do inconsistencies and rushed reviews create avoidable weaknesses?
Contradictory figures, partner roles or timelines make it difficult to verify the proposed plan. Compare the administrative entries in Part A with the narrative and tables in Part B, including budget figures, work package leads, effort and participant information. The official submission manual explains how proposals are prepared and submitted through the portal.
Do not rely on a universal rule such as "start exactly three months before the deadline": the lead time depends on the topic, consortium and evidence available. Reserve enough time for partners to confirm their roles, reviewers to challenge the proposal, and the coordinator to resolve conflicting versions. A review by somebody who did not draft a section can reveal gaps that its author no longer sees.
What to do: Assign one owner to the definitive figures and terminology, freeze a version for review, and keep a list of issues with owners and resolution dates. Validate the portal submission before the deadline and check the requirements of the current call.
How should you use an Evaluation Summary Report after rejection?
Treat an Evaluation Summary Report (ESR) as evidence about the assessed proposal, then distinguish between an eligibility problem, a weakness under an evaluation criterion and an above-threshold proposal that missed the funding cut-off. A score alone does not tell you which revision is needed. Read comments in the context of the criteria and thresholds for the actual call; see the Commission's explanation of project selection.
For every substantive comment, note the root cause and the places that must change. "Impact pathway insufficiently credible" might require more than a better paragraph: you may need user commitments, a revised pilot, a partner responsible for uptake and adjusted resources. If resubmitting to another topic, reassess the fit from the beginning instead of assuming the previous proposal only needs editing.
What to do: Make a four-column revision log: evaluator observation, likely cause, proposed change, and evidence that the revised submission now contains. Ask a fresh reviewer whether the response is convincing.
Conclusion: What are the main reasons Horizon Europe proposals fail?
Proposals may fail a formal requirement, score below a threshold, or reach the required score without receiving funding. Among weaknesses applicants can address, the most consequential are poor alignment with the topic, claims unsupported by evidence, unclear impact pathways, work plans that do not match the ambition, missing consortium capabilities and unresolved inconsistencies. Diagnose the reason first, then revise the project logic and its evidence rather than polishing language alone.
For the full writing process, read Horizon Europe grant writing complete guide. For a shorter drafting checklist, see How do you write a winning Horizon Europe proposal?.