A practical Nexuswelt article for proposal teams preparing for the final phase of Horizon Europe 2025–2027

As Horizon Europe moves through its final implementation phase, proposal teams should not assume that older proposal habits will still work in the same way. The current environment is more selective, more structured, and more strategic. In several areas of the programme, the decisive filtering happens early. In others, the proposal has to show much clearer logic on implementation, impact, deployment, and wider European value.

The European Commission adopted the Horizon Europe 2026–2027 main work programme in December 2025. Together with the second Horizon Europe Strategic Plan for 2025–2027, this gives applicants a much sharper signal about how proposals should now be positioned: stronger alignment with expected outcomes and impacts, clearer policy and industrial relevance, and more disciplined explanation of why the consortium, timing, and project architecture make sense.

Below are seven proposal shifts that matter now, followed by practical writing tips, frequent weaknesses to avoid, and a proposal-preparation checklist that teams can use before submission.

1. First stage is no longer a light pre-step

For two-stage topics, the short proposal is not a soft opening. It is a real selection document. Under the Horizon Europe General Annexes, first-stage applications are very short, which means teams now have much less room for background-heavy explanation or broad descriptive storytelling.

In practice, the first stage already has to prove four things quickly: why this problem matters, why this project is the right response, why now is the right moment, and why this consortium deserves to move forward. If one of these elements remains vague, the proposal may never get the chance to develop further in the second stage.

What to do in practice

• draft the first stage as if the evaluator will only remember six lines from the whole proposal. Your opening page should make the challenge, intervention logic, expected change, and consortium fit immediately visible.
• before finalising Stage 1, test whether an outsider can answer the following in under two minutes after reading your summary: What is the concrete gap? What will this project do differently? Who needs the result? Why is this team credible? If the answer is not immediate, the proposal is probably still too generic.

2. Blind evaluation changes what can actually persuade

In selected topics, the Commission continues to use blind first-stage evaluation. That means applicants must not disclose organisation names, acronyms, logos, or personnel names in the abstract and Part B of the first-stage proposal where blind evaluation applies.

This changes proposal behaviour. Teams cannot rely on brand recognition, institutional prestige, or a famous coordinator to create confidence. Instead, the proposal has to persuade through its internal logic: problem definition, methodological strength, implementation design, expected outcomes, and coherence.

What to do in practice

• remove all prestige-based shortcuts from the draft and check whether the logic still stands on its own. A proposal that only sounds convincing because the evaluator recognises a partner name is much weaker than it looks.
• replace identity-based claims with evidence-based claims. Instead of implying that the consortium is excellent because it is well known, show concrete capability through assets, access, methodological role, pilot environment, technical positioning, or route to deployment.

3. There is less tolerance for generic writing

Compressed proposal formats increase the cost of imprecise writing. The less space available, the less tolerance there is for broad claims, vague ambition, or policy language that is not translated into operational project logic.

Strong proposals now get to the point faster. They show the problem, the intervention, the expected result, the users or adopters, and the wider European relevance without making the evaluator work to connect the dots.

What to do in practice

• cut every paragraph that only repeats the call text in slightly different words. Evaluators already know the work programme. What they need from the proposal is your specific response to it.
• scan the proposal for weak phrases such as “contribute to competitiveness”, “support the transition”, “foster innovation”, or “enable uptake”. Each of these should be followed by a concrete explanation: by whom, through what route, in what environment, and with what measurable effect.
• give each work package a one-line strategic function. For example: “WP3 validates technical performance in real operating conditions” or “WP5 creates the regulatory and market pathway for uptake”. This makes the logic easier to follow.

4. Lump sum makes weak implementation logic more visible

Lump sum funding does not remove the need for serious budget logic. On the contrary, it makes the coherence between planned work and estimated resources more visible. Evaluators look at whether the estimated resources are reasonable and aligned with the proposed activities and deliverables.

That means overloaded work packages, vague task descriptions, unrealistic effort distribution, or cost estimations that do not match the real work become easier to spot. A proposal with beautiful objectives but weak operational design is vulnerable.

What to do in practice

• build the budget from the work, not the other way around. First define the actual activities, responsibilities, outputs, dependencies, and review points. Then estimate the effort that genuinely follows from that structure.
• check every work package for three things: is it internally coherent, are the outputs realistic for the effort requested, and is there a clear connection between the tasks, the deliverables, and the partner roles?
• make the implementation section easy to trust. Avoid artificial complexity. A simpler but credible work plan is usually stronger than a dense plan that tries to look impressive but is hard to believe.

5. Widening countries matter strategically

Widening participation and spreading excellence remain highly relevant in the final phase of Horizon Europe. The programme still places importance on access to excellence, stronger integration of underrepresented research and innovation ecosystems, and better European balance in participation.

For applicants, this matters beyond WIDERA-only calls. Widening-country partnerships can strengthen geographic relevance, ecosystem reach, piloting capacity, policy connection, implementation access, or long-term deployment pathways. But they need to be positioned strategically, not decoratively.

What to do in practice

• never include a widening-country partner only to signal diversity. Explain the functional role. Does this partner strengthen access to users, to a regional ecosystem, to demonstration conditions, to deployment settings, or to a specific policy or market environment?
• where widening dimension matters, connect it directly to project outcomes. For example, show how consortium composition improves access to underrepresented innovation ecosystems, increases replication potential, or strengthens adoption across Europe rather than in a single region only.

6. Impact needs a pathway, not bigger promises

One of the most common proposal weaknesses is treating impact as a place for ambitious language instead of a place for credible pathways. Horizon Europe proposals are stronger when they explain who will use the results, under what conditions, through which route, and what must happen for uptake to become realistic.

This means impact writing should connect project results to exploitation, deployment, procurement, regulation, standardisation, industrial integration, policy use, investor interest, or market entry, depending on the topic. The stronger the pathway, the more believable the impact.

What to do in practice

• write impact backwards. Start with the target change you want to see after the project. Then identify the actors who must adopt or use the result. Then identify the conditions, barriers, incentives, and actions needed to get there.
• distinguish clearly between outputs, outcomes, and impacts. Outputs are what the project produces. Outcomes are what changes when those results start being used. Impacts are the wider medium- and long-term effects. Many proposals lose clarity because they mix these levels.
• include exploitation and uptake logic early in the proposal, not only in a later “impact” section. Evaluators should already feel, while reading excellence and implementation, that the project is built for use.

7. Strategic relevance is more visible and more necessary

In the final years of Horizon Europe, proposals are being read in a more explicitly strategic context. The Strategic Plan 2025–2027 connects funding more tightly to wider European priorities such as resilience, sustainability, competitiveness, industrial leadership, societal preparedness, and digital transformation.

That means proposals need to make their wider relevance visible. Evaluators should not have to guess why the project matters at European level. The proposal should say where the larger relevance sits: industrial, societal, public-sector, security-related, regulatory, market-facing, or deployment-oriented.

What to do in practice

• include one short paragraph that answers this directly: what European need, vulnerability, bottleneck, or opportunity does this project address that goes beyond the narrow technical topic?
• explain why the timing matters now. Is there a policy window, a deployment gap, an urgent capability need, a market inflection point, or a new regulatory context? Strategic timing often strengthens both relevance and urgency.

Quick review table for internal proposal checks

Use this during drafting or before submission to spot weaknesses early.

Practical proposal tips for teams writing now

• Start with a one-page proposal logic sheet before writing the full draft. Summarise the call fit, core problem, strategic objective, expected outcomes, main user groups, and consortium logic on one page. If that one page is weak, the full proposal will usually stay weak.
• Create a red-flag review before submission. Ask one person not involved in drafting to identify where the proposal still sounds generic, where responsibilities are blurred, where impact is asserted but not explained, and where budget logic looks artificial.
• Use consistency checks across sections. The same project logic should appear in the abstract, objectives, work packages, outcomes, impact pathway, and consortium roles. If those parts describe the project differently, evaluator confidence drops.
• Treat partner roles as decision architecture. Each partner should have a visible reason for being there. Avoid partner descriptions that sound ceremonial or generic. The evaluator should understand why this organisation is necessary to the project logic.
• Write with evaluation criteria in mind, not internal project language. Many proposals are drafted as technical notes for the consortium. They become stronger when rewritten as decision documents for evaluators.
• Do not leave exploitation, dissemination, standardisation, regulation, or user uptake until the end. These are not add-ons. In many topics they are part of what makes the project credible in the first place.

Frequent weaknesses that still appear in otherwise good proposals

• Strong topic idea, weak intervention logic: the challenge is real, but the proposal does not clearly explain how the work changes the situation.
• Ambitious objectives, but tasks are too descriptive: the work packages describe discussion, coordination, or analysis without showing how they lead to robust outputs.
• Impact language without actors: the proposal claims European relevance but does not identify who will adopt, use, procure, regulate, or scale the result.
• Too much consortium description, too little project justification: the draft spends valuable space presenting the partners instead of explaining the action.
• Budgets that look negotiated rather than reasoned: resources appear distributed to satisfy partners, not to reflect real workload.
• Late-stage editing that creates contradictions: the summary, objectives, and work packages no longer describe exactly the same project.

Fast pre-submission checklist

☐ The opening page explains the problem, the project response, the timing, and the consortium logic in plain language.

☐ The proposal can still persuade even if evaluator does not know the partner names or institutions.

☐ Each work package has a clear function, realistic outputs, and visible links to outcomes and implementation.

☐ The budget follows the actual work rather than internal negotiation between partners.

☐ The impact section names the users, adopters, buyers, regulators, or standardisation actors that matter.

☐ The widening dimension, if relevant, has a strategic function and is not only symbolic.

☐ The same project logic is consistent across abstract, objectives, work packages, outcomes, and implementation.

☐ The proposal contains no vague filler phrases that could be replaced by evidence, numbers, users, or deployment logic.

Official sources to embed in the webpage article

•  Horizon Europe work programmes
  
•  Horizon Europe Strategic Plan 2025–2027
  
•  Horizon Europe 2026–2027 General Annexes
  
•  Horizon Europe 2025 General Annexes
•  Widening participation and spreading excellence
  
• Lump Sum Funding: What do I need to know?
  
•  How to manage your lump sum grants