How the European Defence Fund Actually Works
Updated: 2 days ago
The European Defence Fund has become one of the central mechanisms shaping collaborative defence research and development in Europe.
Since the EDF Regulation entered into force in 2021, the programme has created a recurring structure through which companies, research organisations and other eligible entities cooperate across borders on defence technologies and capabilities.
For 2026 alone, the Commission allocated €1 billion to the EDF Work Programme, covering 31 topics across major defence capabilities, critical technologies and defence innovation.
For companies approaching the programme, the key is understanding the full process around the call.
EDF participation begins before proposal submission and continues long after the evaluation result.
Overview
What the EDF Is Designed to Do
The European Defence Fund supports collaborative defence research and development.
Its main objectives include:
strengthening the competitiveness and innovation capacity of the European defence technological and industrial base;
supporting cross-border cooperation;
reducing fragmentation in defence R&D;
contributing to the development of defence capabilities relevant to Member States.
The EDF sits between capability priorities and industrial development.
It can finance work ranging from research and feasibility studies to system design, prototyping, testing, qualification and certification.
The programme therefore covers multiple stages of technology development.
How Annual Work Programmes Are Created
EDF operates through annual Work Programmes.
Each Work Programme defines:
calls;
topics;
budgets;
expected outcomes;
eligible activities;
specific conditions for participation.
The topics reflect commonly agreed defence capability and technology priorities.
This makes the Work Programme the first document a company should study.
A topic description usually gives several signals:
the capability problem;
the expected scope;
activities that can be funded;
expected impact;
technology maturity;
topic-specific conditions.
A company should read these elements before beginning partner outreach.
The right consortium depends on the topic.
Research and Development Actions
EDF distinguishes broadly between research actions and development actions.
Research actions focus on generating new knowledge and defence-oriented research.
Development actions can include:
studies;
design;
system prototyping;
testing;
qualification;
certification;
technologies or assets improving efficiency across the defence product lifecycle.
The distinction matters because funding rates and additional requirements differ depending on the activity.
Under the EDF Regulation, activities before the prototype stage can receive very high funding intensity.
Prototype activities normally have a lower base funding rate.
Testing, qualification and certification can receive higher base rates than prototyping.
Bonuses can apply in certain cases, including participation by eligible SMEs and mid-caps and links with PESCO projects.
The exact funding conditions should always be checked in the relevant call documents.
Who Can Participate
For the standard collaborative structure, an EDF action generally requires a consortium of at least three eligible legal entities established in at least three different Member States or associated countries.
The Regulation also contains independence requirements between the core entities.
Specific exceptions exist for certain action types, including some disruptive-technology and study activities.
Eligibility also depends on ownership and control.
Entities controlled by non-associated third countries may face additional conditions and guarantees linked to:
security of supply;
access to sensitive information;
control of intellectual property.
This makes corporate structure relevant.
A technically strong partner can still create eligibility complications if ownership or control conditions are not understood early.
Ukraine is now fully associated with the EDF, enabling eligible Ukrainian entities to participate together with EU and other associated-country partners under the applicable programme rules.
Companies should still check the conditions of the specific call and topic.
How Consortia Work
EDF is built around multinational collaboration.
A typical consortium can include:
prime contractors;
system integrators;
SMEs;
mid-caps;
research organisations;
universities;
testing organisations;
specialised technology companies.
The coordinator manages the overall proposal and later the grant relationship with the Commission.
Other beneficiaries usually take responsibility for defined tasks or work packages.
A company therefore needs to enter with a clear role.
Useful consortium contributions include:
subsystem development;
software;
sensors;
communications;
integration;
simulation;
testing;
validation;
manufacturing;
operational expertise;
specialist research.
The strength of a consortium comes from the way these capabilities combine around the topic.
Funding Logic
The EDF budget finances the eligible activities defined in the project.
The exact Union contribution depends on the action type and funding rate.
For development actions, some costs may need to be covered through other sources such as participating companies or Member States.
For later-stage development activities, Member State commitment becomes increasingly important.
The Regulation requires specific evidence for some development stages because technologies closer to procurement need a credible path towards acquisition and use.
This is one reason consortium building often includes discussions with:
ministries;
end-users;
national authorities;
industrial partners.
Funding therefore follows capability logic.
A technically attractive project has to show how collaborative R&D contributes to a relevant European defence capability.
From Topic to Proposal
A typical company journey starts with the Work Programme.
Identify a Topic | The company maps its technology and capabilities against the annual topics. |
Build or Join a Consortium | Potential partners begin discussing: concept; technical architecture; work packages; roles; budget; IP; testing; end-user involvement. This process can start months before the submission deadline. |
Develop the Proposal | The consortium prepares the administrative and technical parts required by the call. This normally includes: participant information; technical concept; impact; implementation; work packages; deliverables; milestones; risks; resources; budget. |
Submit Through the Funding & Tenders Portal | The coordinator submits the proposal electronically. |
Evaluation and Selection
Proposals are evaluated against the criteria defined for the call.
The evaluation examines more than the underlying technology.
Depending on the call, evaluators assess areas such as:
relevance to the topic;
excellence;
innovation;
contribution to European defence objectives;
industrial impact;
cross-border cooperation;
implementation quality;
credibility of the consortium.
This is why partner selection matters.
The proposal needs the collective capacity to deliver the action.
After evaluation, the Commission publishes results and invites selected proposals into Grant Agreement Preparation.
A published selection result is therefore followed by another formal stage before the project begins.
Grant Agreement Preparation
Selected consortia enter Grant Agreement Preparation - GAP through the Funding & Tenders Portal.
During this phase, participants finalise the legal, administrative and financial information needed for the grant.
This can include:
legal entity information;
participant roles;
budget details;
banking information for the coordinator;
reporting periods;
prefinancing arrangements;
required declarations.
Before grant signature, each beneficiary signs a Declaration of Honour.
The coordinator signs the Grant Agreement electronically.
The granting authority signs it.
Other beneficiaries then sign their accession forms electronically.
Project Implementation
Once the grant enters into force, the consortium moves from proposal logic to delivery.
The Grant Agreement defines the formal commitments.
The Description of Action contains the work structure.
Implementation revolves around:
work packages;
tasks;
deliverables;
milestones;
budgets;
risks;
reporting periods.
The coordinator manages the formal interaction with the granting authority.
Work package leaders coordinate defined parts of the project.
Individual beneficiaries remain responsible for their own tasks and obligations.
The Portal is also used during implementation for continuous reporting and periodic reporting.
Deliverables, milestones and risks are updated over the project lifecycle.
Periodic reports support the payment process according to the schedule and conditions in the Grant Agreement.
Results, IP and Security
Defence R&D creates additional considerations around intellectual property and security.
For development actions, the EU does not automatically own the defence products, technologies or resulting IP generated by beneficiaries.
The EDF Regulation contains safeguards concerning transfers to non-associated third countries and restrictions that could undermine the security and defence interests of the Union and its Member States.
Individual projects may also involve:
classified information;
sensitive information;
security requirements;
export controls;
specific access restrictions.
These questions should be addressed early in consortium discussions.
Waiting until the final proposal stage can create major problems around ownership and information sharing.
The 2026 Programme
The 2026 EDF Work Programme allocates €1 billion to collaborative defence R&D.
It covers 31 topics.
The Commission structures the programme around:
major defence capability priorities;
forward-looking critical technologies;
EUDIS innovation actions.
Around half of the budget supports collaborative R&D on major defence capabilities.
Another part focuses on critical technologies and future capabilities.
The remaining share supports defence innovation through EUDIS, including disruptive technologies and SME-focused actions.
The 2026 programme also introduced simplification measures for certain calls following the Mini-Omnibus changes.
For companies, the important point is that EDF continues to evolve.
The Work Programme, call documents and official amendments should always be treated as the current reference.
Practical Company Action Plan
Read the Work Programme Before Choosing a Call | Map your technology against the actual capability priorities. |
Select One or Two Realistic Topics | Focus on clear fit rather than maximum application volume. |
Define Your Consortium Role | Write down: what you deliver; which work package it belongs to; what inputs you need; what evidence shows you can deliver it. |
Map Relevant Partners | Identify: coordinators; integrators; research actors; testing partners; end-users active in the capability area. |
Check Eligibility Early | Review: country; ownership; control; security requirements; call-specific eligibility conditions. |
Prepare Consortium-Ready Material | Create a short partner profile containing: capability; TRL; past projects; team; integration interfaces; production or testing capacity; proposed EDF contribution. |
Enter Discussions Early | Consortia often develop well before the deadline. Early discussions provide more room to shape a meaningful role. |
Prepare for Implementation While Writing | A proposal should describe work the team can actually deliver. Confirm resources, staff, timelines and dependencies before submission. |
The EDF becomes much easier to navigate once a company sees the full sequence:
capability priority → topic → consortium → proposal → evaluation → grant preparation → implementation → future industrial positioning.
Each stage requires a different decision.
Understanding those decisions is the foundation for participating effectively.
