A solid Horizon Europe proposal is not judged solely by the quality of its idea. It is evaluated based on how clearly that idea is presented against the structure evaluators are required to use. This is one of the most important points, and one that applicants often underestimate.
Many consortia still write their proposals as if evaluators would read them like a report, gradually uncovering the project’s strengths. In practice, evaluators review several proposals under time pressure and rely heavily on the official evaluation form to guide both their reading and scoring.
The consequence is simple: a good project is not enough on its own. To obtain a good score, the proposal must be written so that evaluators can identify, verify and quickly justify its strengths.
Evaluators read with the evaluation form in mind
Evaluators don’t “discover” your proposal; they navigate it using the evaluation form as a map. The process is structured around three criteria: Excellence, Impact, and Quality and Efficiency of Implementation.
Your task is not to deduce what applicants intended to say, but to score what is explicitly written. Therefore, even strong proposals lose points if key information is vague or buried in dense text. If evaluators cannot quickly find the evidence they need, it will have little effect on the final score. For this reason, the most effective approach is to use the evaluation form itself as a framework for drafting.
Use the evaluation criteria as your drafting framework
The form specifies exactly what must be analyzed: the strength of the concept, the credibility of the methodology, the viability of the pathway to impact, the quality of the work plan, the consortium’s complementarity and risk management. These are the exact filters through which your proposal will be read.
Your proposal should address these points directly and visibly. In many cases, it helps to use terminology that mirrors the language of the form itself. When evaluators immediately recognize the link between your text and the evaluation criteria, the proposal becomes easier to evaluate and to reward.
What evaluators look for in each section
- Excellence: They focus on whether the project is conceptually solid and methodologically credible. They look for a clearly defined challenge, deep knowledge of the state of the art, and objectives that are specific, realistic, and aligned with the call.
- Impact: Evaluators want to know who benefits, what changes will result from the project, and how those changes will realistically occur. General statements won’t convince unless accompanied by a clear pathway to impact, with concrete actors and defined adoption routes.
- Implementation: They assess whether the project can actually be executed as proposed. They review the work plan, timeline, resources, and governance. A compelling section shows that the project’s ambition is backed by a credible execution plan.
How to write so evaluators score you efficiently
The most powerful proposals are written for evaluation, not just for presentation. This means making the evaluator’s job easier: key messages should appear at the start of paragraphs and objectives should be clearly numbered.
Coherence is also vital. A common weakness is contradictions between sections, such as describing different beneficiaries or assumptions from one section to another. Even small inconsistencies can undermine credibility and reduce the score.
A final check before submission
Before submission, review the proposal line by line against the evaluation form. For each question, you should be able to point to a paragraph, figure, or clearly defined section that directly answers it.
It is also helpful to ask someone outside the process to act as a mock evaluator. Their questions often reveal where the proposal needs clearer language or better alignment with scoring criteria. In the end, the most competitive proposals allow evaluators to recognize quality immediately and justify a high score with complete confidence.
Roberto Horcajada, Senior Project Manager – European Funds at Euro-Funding.
