Intellectual property
IP management in EU projects: background, foreground and access rights
6 min read · Updated 28 August 2026
Most IP disputes in EU projects trace back to two documents written in a hurry: the background list and the consortium agreement. Both are cheap to get right at the start and expensive to fix later.
Background versus foreground
- Background: what a partner brings into the project — existing software, data, patents, know-how. It stays owned by that partner.
- Foreground (results): what is generated during the project. Owned by the partner that generates it, or jointly when generated together and contributions cannot be separated.
- Sideground: results generated during the project but outside its scope. Handled by the consortium agreement, not the grant agreement.
The background list is a strategic document
Partners can define which background is made available and on what terms. Listing everything you own is not generous, it is careless; listing nothing can make your role unimplementable.
- List only the background actually needed to implement the project or exploit results.
- State explicit exclusions and any licensing conditions attached.
- Agree the list before the grant agreement is signed, not during month twelve.
Access rights, in practice
- For implementation: partners get royalty-free access to background and results they need to do their tasks.
- For exploitation: access is available on fair and reasonable conditions, which usually means negotiated terms rather than free.
- Affiliated entities may have access rights; decide whether to extend or restrict them in the consortium agreement.
- Requests and grants of access should be in writing. Verbal understandings evaporate at partner staff turnover.
Joint ownership needs a rule, not goodwill
Where results are jointly owned, agree a regime up front: whether each owner can license non-exclusively with notice and fair compensation, how costs of protection are shared, and what happens if one owner does not want to file.
Protection choices
- Patent: appropriate for technical inventions with commercial routes; publication before filing destroys novelty, so coordinate with dissemination.
- Trade secret: fits process know-how and data advantages, but requires actual confidentiality measures to be enforceable.
- Copyright and software licensing: decide open-source licence compatibility early — an incompatible licence chosen in month three can block exploitation in month thirty.
- Trademarks: relevant when the project produces a platform or service intended to continue after funding.
Consortium agreement clauses worth arguing about
- Decision-making thresholds and deadlock resolution.
- IP ownership and joint ownership regime.
- Access rights for affiliates and after project end.
- Confidentiality duration beyond the project.
- Exit conditions for defaulting partners and what happens to their results.
- Liability caps and dispute resolution forum.
Frequently asked questions
- Is a consortium agreement mandatory?
- For most Horizon Europe collaborative actions, yes — it must be in place before the grant agreement is signed unless the call states otherwise.
- Can we publish before filing a patent?
- Not without losing novelty in most jurisdictions. Coordinate dissemination with the protection plan, and use the notice mechanism agreed in the consortium agreement.
- Who owns results produced by a subcontractor?
- The contracting beneficiary should secure ownership or sufficient rights by contract. Subcontracts without IP clauses are a recurring source of exploitation problems.