EU innovation grants for UK companies: why bids fail on work packages, cost realism and evidence

EU innovation grants for UK companies can look straightforward on paper: assemble partners, write a proposal, submit. In practice, many Horizon Europe bids are lost on operational detail, not on the novelty of the idea. Evaluators need to see that the work plan is deliverable, the costs are credible, and the consortium can evidence both capability and impact. This article focuses on the hidden execution issues that routinely score proposals down. 

The operational reality behind evaluation 

Horizon Europe proposals are assessed against award criteria set out in the call, and the implementation side of the case matters more than many teams expect. A proposal can be technically strong and still fail if the work packages cannot be executed or evidenced. This is why bid teams should treat the work plan and budget as the backbone, with the narrative built around it. 

Eight reasons EU bids fail, and what to do instead 

1) Work packages read like intentions, not a plan 

Failure mode: 

• Work packages are labelled “integration”, “validation”, “pilot”, but outputs are undefined. 

• Deliverables lack acceptance criteria, owners and dates. 

Fix: 

• Write deliverables as testable artefacts: specifications, datasets, prototypes, validated methods, deployed pilots, adoption playbooks. 

• Include a clear “definition of done” for each deliverable and milestone. 

2) Cost realism does not match the work plan 

Failure mode: 

• Person-months are allocated because partners “need budget”, not because tasks require effort. 

• Subcontracting is inserted late, with no rationale or procurement story. 

• Travel, equipment and third-party costs appear without linkage to activities. 

Fix: 

• Build the budget from the task list. If a task is not in the plan, it should not be in the budget. 

• Add a short cost logic for each work package: roles, effort, key resources, and why they are necessary. 

3) Partner roles are not evidenced 

Failure mode: 

• Partners are selected for brand value, not operational fit. 

• The proposal makes capability claims without concrete proof. 

Fix: 

• Use a one-page evidence pattern per critical partner: relevant projects, named facilities, methods, pilot sites, standards experience, and delivery leadership. 

• Make the link between partner capability and the specific tasks they own. 

4) Impact is asserted, but not measurable 

Failure mode: 

• Impact is written as aspiration: “growth”, “jobs”, “sustainability”, “EU leadership”. 

• There is no measurement plan, baseline, or pathway to adoption. 

Fix: 

• Define 3 to 6 impact metrics tied to the call expected outcomes. 

• State baseline, target, measurement method, and who owns data collection. 

5) Governance is thin, so delivery risk is obvious 

Failure mode: 

• Decision rights are unclear. 

• Risk management is generic. 

• There is no escalation route when partners miss deadlines. 

Fix: 

• Define governance as a system: steering group cadence, technical working groups, change control, and dispute resolution. 

• Show how you will manage dependencies across work packages. 

6) Ethics, data and security are left to the last week 

Failure mode: 

• Ethics self-assessment is treated as a tick-box. 

• Data management and security obligations are vague. 

• The consortium has not agreed who owns what data and under what terms. 

Fix: 

• Identify ethics and data risks early, assign owners, and reflect them in the work plan. 

• Draft the data management approach at bid stage so it is consistent with exploitation plans. 

7) Exploitation and IP arrangements are inconsistent 

Failure mode: 

• The exploitation plan assumes freedom to operate, but IP ownership and access rights are not defined. 

• Foreground and background IP are discussed in generalities. 

Fix: 

• Align exploitation routes to a credible collaboration agreement structure: background access, foreground ownership, licensing intent, and publication rules. 

• Make it realistic for the partners you have, not the partners you wish you had. 

8) Reporting and audit readiness are ignored pre-award 

Failure mode: 

• No one has thought about how effort, deliverables and costs will be evidenced. 

• The delivery team has no internal process for collecting proofs of work. 

Fix: 

• Build an “evidence pack” plan alongside the proposal: what documents you will keep, who stores them, and how reporting will be produced. 

• If the action uses lump sums, plan how you will evidence work package completion and deliverables, because reviews focus on technical implementation. 

A CFO sign-off checklist for EU bids 

Use this checklist before approving the final submission: 

• Does every cost line map to a task and deliverable? 

• Are person-months defensible, and do they align with named roles and methods? 

• Do subcontracting plans have a rationale and a procurement approach? 

• Can we evidence partner capability for the tasks they own? 

• Are impact metrics defined with baselines, targets and owners? 

• Is the governance model specific, including change control and escalation? 

• Do we have a draft evidence pack plan for reporting and reviews? 

Where specialist support typically fits in 

In practice, specialist advisers such as FI Group by EPSA are often used to challenge the work plan, test cost realism, and help teams set up evidence and reporting processes that reduce delivery friction after award. Their EU innovation grants funding page summarises the support model used across major EU and UK innovation programmes. 

FAQs 

What is a “work package” and why is it so important? 

A work package is a structured set of tasks with outputs, owners and timing. In EU bids, it is the unit that connects technical ambition to delivery evidence. 

How do evaluators judge whether costs are realistic? 

They look for internal consistency: tasks, effort, resources and partner roles should align. Large unexplained variances or vague tasks raise implementation risk. 

What counts as “partner evidence” in a proposal? 

Relevant delivery proof: prior comparable projects, facilities, methods, certifications, pilot access, and named delivery leads who match the work package. 

What does “reporting readiness” involve? 

Having a practical system for capturing proofs of work, deliverables, milestones and costs, so reporting can be completed without rebuilding the story each period. 

Can we fix these issues after we submit? 

Rarely. Once submitted, you cannot change the work plan or budget. If the operational backbone is weak, the score will reflect it.