By Julien Sudre, grant writer and founder of Grant360. Originally published 8 December 2025. Updated: 23 September 2026.
To write a competitive Horizon Europe proposal, answer the call topic precisely, show what is new and feasible about your approach, explain how the results can lead to the expected outcomes, and give each partner a credible role in a realistic work plan. Build the argument around the three evaluation criteria: Excellence, Impact, and Quality and efficiency of implementation. A clear document helps evaluators assess that argument, but no writing technique guarantees funding. The European Commission explains how proposals are evaluated.
This guide is written by an experienced grant writer who has worked on more than a hundred applications. It concentrates on the decisions that make a collaborative Horizon Europe proposal more convincing. The details depend on the action type and topic: before drafting, consult the documents attached to your call in the Funding & Tenders Portal. For a fuller explanation of each section, see our complete guide to Horizon Europe grant writing.
How do you align a proposal with the call without copying it?
Translate the call into a set of commitments you can demonstrate. List each relevant expected outcome and scope requirement, then state which objective, activity, partner and result addresses it. Use the call's terminology when accuracy requires it, but explain how your project contributes rather than repeating the topic text.
Suppose a topic calls for solutions tested with public authorities across different regions. Naming several regions in the consortium is insufficient. Specify what will be tested in each place, why those settings differ, who will assess the result, and what the comparison will teach the project. Include any requirements specific to the action type, eligibility rules and submission stages; these are stated on the call page and in the Horizon Europe Programme Guide.
A useful writing check: can you point to a paragraph or table that provides evidence for every central commitment you claim to meet? If a requirement has no place in the proposed activities, revise the design before polishing the prose.
How do you make the Excellence section convincing?
State a small number of assessable objectives, identify the precise gap in existing knowledge or technology, and explain why your methods can close it. Use evidence to support novelty and feasibility: relevant publications, benchmark results, preliminary tests, validated needs, or clearly labelled assumptions. The Commission's standard application form for Research and Innovation Actions (RIAs) and Innovation Actions (IAs) shows the questions applicants must address under Excellence.
For example, "improve energy efficiency" tells the reader little. "Measure energy consumption against the current process in three industrial settings, using the same protocol and a predefined performance target" supplies a testable objective. Any numerical target should have a defensible baseline or rationale; an impressive percentage without evidence weakens the case.
Explain the method at the level needed to judge it: what will be compared, what data will be collected, which limitations are expected and how they will be handled. Address open science, interdisciplinarity, the gender dimension in research content and other cross-cutting topics where relevant, according to the applicable call documents. Avoid generic statements that do not affect the project design.
How do you demonstrate impact rather than list activities?
Show how project results could be taken up by specific users and contribute to the topic's expected outcomes. Connect those outcomes to the wider expected impacts in the work programme, while separating what the consortium can achieve from effects that depend on later adoption or policy decisions. The Commission's application form explicitly asks for pathways towards outcomes and impacts and for measures to maximise them.
Write an impact pathway in plain language: result -> intended user -> action required for uptake -> change expected -> evidence to be collected. If a project develops a decision tool for municipalities, for instance, explain which officials will test it, what decision it could improve, what training or integration is needed, and how adoption will be measured. A conference presentation may disseminate a result; it does not by itself demonstrate that anyone will use it.
Quantify where the assumptions permit it. Name the baseline, target, timeframe and source. If you have interviewed potential users or analysed adoption barriers, describe the method and sample accurately. Distinguish communication about the project, dissemination of its results and exploitation through their use. Avoid attaching unrelated European policy priorities to the proposal merely to sound strategic; demonstrate the link to the particular topic.
How do you prove the consortium can deliver?
Make the work plan, partner roles, schedule and resources support the objectives and impact pathway. A work package should have a clear purpose, tasks with responsible partners, meaningful deliverables, decision points and a realistic allocation of effort. The official RIA/IA application template sets out the implementation tables, including work packages, deliverables, milestones and risks.
Check dependencies before fixing dates. If regulatory approval or recruitment is needed before a pilot, reflect that in the schedule and risk plan. If an organisation is expected to lead exploitation, assign it time and a concrete role. A partner's name, country or reputation is no substitute for the capacity required by the work.
For each major risk, state what could happen, its likely consequences, the person or partner responsible and the response. Examples include poor recruitment, data access delays, a prototype missing a threshold, or low user adoption. Governance should explain who makes decisions and how disagreements or delays are resolved, at a scale appropriate to the consortium.
How do you make the proposal easy to evaluate?
Use a consistent set of objectives, figures and terms across the application. Give each section an immediate answer to its evaluation question, then supply the explanation and evidence. Tables and diagrams are useful when they clarify a relationship that prose would make harder to follow. The Commission's evaluation form for RIAs and IAs is a practical final check against the criteria.
For a multi-author draft, appoint an editor to reconcile the sections. Compare the objectives against the methodology, work packages, deliverables, impact indicators and budget; compare numerical information against Part A of the submission. Ask a reader unfamiliar with the project to explain its central idea and trace one expected outcome from the call to the planned evidence. If they cannot, identify the missing link rather than simply shortening sentences.
Clarity makes the evidence easier to find. It cannot turn a weak or ineligible project into a competitive application. The European Research Executive Agency's advice to applicants likewise emphasises the specific evaluation criteria, relevance, credible long-term impact and a clear contribution to the work programme.
What should you check immediately before submission?
Confirm that the final version uses the documents and forms for the specific call, answers each applicable criterion, respects the call's page and formatting rules, and matches the administrative information entered online. Validate the application in the portal and submit it before the deadline; the Funding & Tenders Online Manual explains the submission process.
Conduct one last review with these questions:
- Does each important claim have a source, result, method or explicit assumption behind it?
- Can each expected outcome be traced to an activity and an intended user?
- Do the schedule, partner effort and budget support the promises made in the text?
- Are figures, terminology and partner roles consistent across the whole application?
- Does the submitted version follow the current call-specific requirements?
Conclusion: What makes a Horizon Europe proposal competitive?
It is a proposal whose relevance, method, impact pathway and delivery plan reinforce one another. Start with the call; design the project around its requirements; substantiate your claims; and make the result straightforward to evaluate. Funding remains competitive and depends on the quality of other submissions as well as your own, so "winning" should be treated as a goal rather than a promise.
For a wider treatment of proposal design and the three criteria, read the complete Horizon Europe grant writing guide. If you are organising a collaborative draft, Grant Genius is Grant360's proposal writing application; its product page describes its current features.