How to Write a Winning Horizon Europe Proposal in 2026: A Complete Guide

Writing a competitive Horizon Europe proposal is one of the most demanding professional tasks an institution can undertake. With overall success rates of 10–15% across most calls — and as low as 5–8% in highly competitive thematic areas — the quality gap between funded and rejected proposals is often measured in precision, not effort.

Before You Start Writing: Strategic Positioning

A well-written proposal built on the wrong concept will not be funded. Before drafting a single sentence, experienced proposal writers conduct a 'call alignment audit' — mapping every Expected Outcome and Expected Impact listed in the call text to concrete deliverables in the proposed project. If the mapping is weak, the concept needs to be rethought, not written up.

• —Read the Work Programme and specific call text in full — not summaries.
• —Identify all Expected Outcomes (what the funded projects should produce) and Expected Impacts (the broader changes they should contribute to).
• —Map your project concept point-by-point against these expectations.
• —Where gaps exist, decide whether the concept can be adapted or whether a different call is a better fit.

Work Package Architecture

The work package (WP) structure is the skeleton of a Horizon Europe proposal. It defines how the project is organised, who does what, and how the budget is distributed. Evaluators assess work packages for logical coherence, appropriate granularity, and realistic timelines.

• —WP1 is typically Project Management — administration, reporting, risk management, ethical compliance.
• —Research/technical WPs should follow a logical progression: analysis → development → validation → demonstration.
• —Dissemination, exploitation, and communication must have their own dedicated WP (often WP last).
• —Task-to-deliverable-to-milestone mapping must be explicit, numbered, and internally consistent across all proposal sections.
• —Each partner's role should be visible in at least one WP with a justified budget allocation.

The Impact Section: Your Most Important Pages

Under the standard Horizon Europe evaluation scheme, Impact represents 40% of the total score for Research & Innovation Actions and Innovation Actions. Yet it is consistently the weakest section in submitted proposals — filled with generic statements about 'contributing to European competitiveness' and 'advancing science'.

• —Quantify: How many organisations, citizens, or sectors will benefit? By how much? Over what timeframe?
• —Specify target groups: Not 'SMEs' but 'SMEs in the EU manufacturing sector with 10–250 employees'.
• —Describe pathways to impact: The theory of change from project outputs to societal outcomes must be explicit.
• —Exploitation plan: Who will use the results, how, and under what business model? Evaluators want to see commercial or policy uptake, not just academic dissemination.
• —Address all three impact dimensions: scientific/technological, economic/market, and societal/policy.

Budget Construction

A credible, well-justified budget signals financial management competence. Inflated budgets, unjustified staff costs, or inconsistencies between the budget and the work plan raise immediate evaluator concerns.

• —Staff costs: Calculate on actual salary rates × % time on project. Justify every significant staff involvement by the tasks they perform.
• —Travel: Justify each trip explicitly — location, purpose, frequency, who travels.
• —Equipment: Apply correct depreciation unless equipment is purchased exclusively for the project.
• —Subcontracting: Must be justified in the work plan and procured competitively.
• —Indirect costs: Applied as a flat rate of 25% on all direct eligible costs except subcontracting.

Common Proposal Writing Mistakes

• —Describing what you will do (methodology) without explaining why it matters (impact).
• —Treating the proposal narrative and the budget as separate documents — they must be fully consistent.
• —Vague or missing exploitation plans for innovation results.
• —Consortium imbalance — one dominant partner, others with token roles.
• —Submitting without independent external review by someone who has not been involved in writing.
• —Leaving portal submission to the final hours — technical issues regularly prevent last-minute submissions.