Horizon Europe proposal writing: what evaluators actually need to see
Horizon Europe proposal writing is often treated as a writing problem.
It is not.
At least, not only.
The work starts earlier, when the consortium reads the Horizon Europe work programme 2026 and decides what the topic is really asking for.
Of course the text matters. Clarity matters. Structure matters. The evaluator has limited time, many proposals to read, and very little patience for confusion dressed as ambition.
But the strongest proposals are not strong because they use better adjectives.
They are strong because the thinking underneath is visible.
The evaluator can see why the project matters, why this consortium should do it, why the method is credible, why the impact path is believable, and why the work plan will not collapse the first time reality behaves differently from the Gantt chart.
That is the real work.
Writing only reveals whether the work has been done.
Evaluators need orientation
A Horizon Europe evaluator should not have to guess what the project is.
This sounds basic, but many proposals make the reader work too hard.
They start with policy language, technical vocabulary, stakeholder references, acronyms, and consortium ambition before giving a simple answer to a simple question:
What problem are you solving, for whom, and why now?
If this is not clear early, everything else becomes harder to believe.
The proposal may still contain good content, but the evaluator is forced to assemble the logic piece by piece. That is risky.
A good proposal gives orientation quickly.
Not with a generic executive summary. With a clear strategic frame.
This is the problem. This is why the current situation is insufficient. This is what the topic asks for. This is why our approach fits. This is what will be different if the project works.
After that, complexity is allowed.
Before that, complexity is noise.
Excellence is not a technology brochure
Many proposals treat the excellence section as a place to show how advanced the idea is.
That is only part of it.
Excellence should also show why the approach is necessary, why the current state of the art is not enough, and why the project’s choices are credible.
The evaluator needs to see the logic of the innovation.
What is new? What is difficult? What has already been tested? What is uncertain? What assumptions are you making? What alternatives did you reject? Why is this methodology appropriate?
A proposal that hides uncertainty can sound immature.
Real innovation has risk. Horizon Europe does not expect magic. It expects a serious way to manage uncertainty.
So the question is not: can we describe something impressive?
The question is: can we show that we understand what has to be proven?
Impact is not a promise at the end
Impact is where many proposals become theatrical.
They promise transformation. They mention Europe. They list target groups. They describe dissemination. They add a few numbers. They say the project will support competitiveness, sustainability, resilience, inclusion, digital transition, or strategic autonomy.
Maybe all of this is true.
But evaluators need more than aspiration.
They need a path.
Who will use the result? What behavior, decision, process, market, policy, or system could change? What has to happen during the project to make that change possible? Who owns the relationship with users, buyers, regulators, public authorities, industry, communities, or patients? What barriers exist? What will still be missing at the end?
Impact is not the moment when the proposal becomes inspirational.
It is the moment when the proposal becomes accountable.
This is also where exploitation strategy matters. In From lab to launch, I wrote about the discomfort many partnerships feel when research has to face the market, users, or real adoption. That discomfort should not be hidden. It should be designed into the project.
The consortium must be necessary
A Horizon Europe consortium is not a collection of impressive institutions.
It is a machine for doing the work.
Every partner should have a reason to be there that the evaluator can understand without generosity.
This partner controls a pilot environment. This one has the scientific method. This one understands regulation. This one reaches users. This one manages data. This one connects to procurement. This one brings industrial validation. This one knows how to translate results into policy or market uptake.
If the roles are vague, the consortium looks decorative.
This is a problem because evaluators are very good at sensing decorative partners.
They have seen too many proposals where everyone contributes to everything, supports everyone, participates in all phases, and somehow nobody is clearly responsible for the difficult parts.
Good proposal writing makes responsibility visible.
Not aggressively. Clearly.
Who decides? Who leads? Who validates? Who challenges? Who implements? Who carries the risk if a work package becomes complicated?
If the proposal cannot answer this, the work plan is not ready.
Implementation should feel boring in the best way
The implementation section should not be exciting.
It should be reassuring.
This is where the evaluator needs to feel that the consortium has turned ambition into manageable work. Work packages are not containers for text. They are decisions about sequence, dependency, responsibility, and control.
A good implementation plan answers practical questions.
What has to happen first? Which tasks depend on which evidence? Where are the decision points? What happens if validation fails? How does data move? How do stakeholders enter? How does the project avoid producing deliverables that are formally complete but strategically useless?
Risk management is part of this.
Not the usual table where every risk is medium and every mitigation is “continuous monitoring.”
Real risks.
The partner may not recruit enough users. The pilot may be delayed. The technology may not reach the expected maturity. A regulatory assumption may change. A stakeholder group may resist adoption. A dataset may be incomplete. A market path may turn out to be weaker than expected.
These risks do not make the proposal weaker.
Pretending they do not exist does.
The proposal should sound like one organization
Many Horizon proposals are written by many people.
That is normal.
The problem is when they read like many people who never really agreed.
Different terminology. Different levels of ambition. Repeated explanations. Contradictory numbers. Impact claims that do not match tasks. Tasks that do not match deliverables. Deliverables that do not match milestones. A budget that tells a different story from the work plan.
Evaluators notice this.
They may not call it a writing problem. They may call it lack of coherence, weak implementation, unclear methodology, insufficient impact pathway, or inadequate consortium integration.
But often the root is simple.
The proposal was assembled before the project was truly designed.
Good proposal writing includes editorial control, but also strategic control. Someone has to protect the logic of the whole document.
Not polish sentences at the end.
Protect the argument from the beginning.
Do not confuse European language with European logic
There is a difference between using EU vocabulary and understanding the programme logic.
A proposal can mention all the right priorities and still fail to show how it contributes to them.
It can talk about stakeholders without giving them a real role. It can talk about exploitation without a credible user path. It can talk about interdisciplinarity while each discipline remains in its corner. It can talk about open science while treating data as an afterthought. It can talk about gender, ethics, sustainability, or inclusiveness as compliance paragraphs instead of design constraints.
This is where evaluators become skeptical.
They do not need the proposal to sound European.
They need it to behave like a European project.
Collaborative. Accountable. Policy aware. Impact oriented. Operationally credible. Honest about uncertainty. Clear about who benefits and who carries responsibility.
Use the criteria without becoming mechanical
The three main evaluation areas are familiar: Excellence, Impact, and Quality and efficiency of the implementation.
The danger is that teams treat them as boxes.
Excellence becomes the science chapter. Impact becomes the optimistic chapter. Implementation becomes the project management chapter.
But evaluators do not read them as isolated islands. They read across them.
If the excellence section promises a difficult validation, the implementation section must show time, budget, roles, and risks for that validation. If the impact section promises uptake by a specific market or public authority, the consortium must include a credible route to that actor. If the work plan depends on data, the methodology must explain what kind of data, from whom, with which constraints.
The sections may be separate in the template. The logic cannot be separate in the project.
The best writing removes doubt
In the end, Horizon Europe proposal writing has one main job.
Reduce evaluator doubt.
Doubt about the problem. Doubt about the fit with the topic. Doubt about the ambition. Doubt about feasibility. Doubt about impact. Doubt about the consortium. Doubt about whether the budget and work plan tell the same truth.
You cannot remove all doubt. You should not try. Innovation without uncertainty is usually not innovation.
But you can show that the consortium understands the doubt and has designed the project around it.
That is what evaluators need to see.
Not a perfect story.
A credible one.
Because a Horizon Europe proposal is not a brochure for a beautiful idea.
It is a governance document for a project that has not happened yet.
The writing matters because it is the first evidence of how the consortium thinks.