Research offices reviewing Horizon Europe calls for proposals in 2026 face a familiar but persistent problem: the open science obligations attached to EU grant agreements are not optional add-ons, but they are also not uniform. Some provisions in the horizon europe open access requirements are contractual conditions with financial consequences for non-compliance; others are strongly encouraged practices that reviewers reward but auditors do not enforce. Grant administrators who conflate the two categories either over-engineer compliance workflows for recommendations that carry no penalty, or — more dangerously — miss a mandatory obligation buried in boilerplate annex text.
With the horizon europe work programme 2026 calls now open across multiple clusters, institutions are fielding a fresh wave of applications, and pre-award teams need a working checklist rather than a policy summary. This article separates what is genuinely mandatory under the Model Grant Agreement from what is best-practice guidance, and sets out a practical review sequence research offices can apply to each new proposal.
Horizon Europe Open Access Requirements: What Is Actually Mandatory
The core obligation has not changed in substance since the start of the programme, though its enforcement has sharpened as later horizon europe calls 2026 reference updated annotated grant agreement language. Three elements remain non-negotiable for funded projects:
- Immediate open access to peer-reviewed publications. Beneficiaries must ensure open access to any peer-reviewed publication arising from funded work, deposited in a trusted repository at the moment of publication — there is no embargo period available under the standard grant conditions.
- A licence permitting reuse. Publications must carry a licence, typically CC-BY, that allows reuse, distribution and text/data mining, subject to proper attribution.
- Bibliographic metadata and persistent identifiers. Deposited records must include funding acknowledgement, project identifiers, and — increasingly checked at reporting stage — persistent identifiers such as DOIs, ORCID iDs for authors, and, where applicable, Research Organization Registry (ROR) identifiers for affiliated institutions.
These are contractual terms under the Model Grant Agreement. Non-compliance can trigger corrective action requests during reporting and, in persistent cases, affect payment of the final instalment.
Data Management Plans and FAIR Data: Mandatory Process, Flexible Content
The second pillar of Horizon Europe open science policy concerns research data, and this is where administrators most often misjudge the compliance boundary. Every project that generates, collects or reuses research data must produce a Data Management Plan (DMP), typically as a deliverable within the first six months and updated at least once more during the project lifecycle. Producing the DMP is mandatory. What the DMP says is not prescriptive in the same way.
The underlying principle — data should be “as open as possible, as closed as necessary” — gives beneficiaries legitimate grounds to restrict access where commercial exploitation, personal data protection, security concerns or third-party rights apply. The FAIR principles (Findable, Accessible, Interoperable, Reusable) are the design standard the DMP must address, but FAIR does not equal fully open. A dataset can be FAIR-compliant with metadata openly discoverable while the underlying data remains access-controlled.
Grant administrators should check that the DMP:
- Identifies which datasets will be shared openly, and which are justifiably restricted, with a stated rationale for each.
- Names a repository (project-specific, institutional, or a generalist option) and describes metadata standards to be applied.
- Assigns responsibility for updates, since a stale DMP submitted once and never revisited is a common audit flag.
- Addresses costs — data management and open access publication costs are eligible under Horizon Europe, and DMPs should reference the relevant budget lines.
Recommended, Not Mandatory: Where Reviewers Reward Beyond Compliance
A separate set of practices appears throughout horizon europe work programme guidance documents and evaluation criteria as encouraged behaviour rather than contractual obligation. Distinguishing these matters because over-promising in a proposal creates a self-imposed obligation that reviewers will later check against actual delivery. Common recommended-not-mandatory items include:
- Open access to monographs and other long-form outputs, where CC-BY-ND is accepted as an alternative to full CC-BY.
- Preprint deposit ahead of formal peer review, which is widely encouraged but not required for compliance.
- Open access to software and code produced during the project, generally framed as good practice aligned with FAIR principles rather than a hard deliverable.
- Citizen science and public engagement components, which strengthen an application’s societal-impact score without being conditions of the grant agreement.
Bodies such as cOAlition S and national funders including UKRI maintain parallel but not identical open access frameworks, which is why administrators supporting international consortium partners should confirm which funder’s policy is operative for each work package rather than assuming Horizon Europe terms travel automatically to co-funders.
A Practical Review Checklist
For research offices triaging applications against upcoming horizon europe calls 2026 deadlines, a sequential review works better than a single long checklist. At proposal stage, confirm the DMP outline (even a short version) addresses data types, FAIR alignment, and repository choice; confirm ORCID iDs are recorded for all named researchers; and confirm the budget includes open access publication and data management costs as eligible items. At grant agreement stage, verify the consortium agreement assigns clear DMP ownership, confirm repository selection meets trusted-repository criteria, and check that publication clauses in any co-funding or industry partnership agreement do not conflict with the immediate open access requirement. At reporting stage, audit that deposited publications carry correct funding acknowledgement and persistent identifiers, and confirm the DMP has been updated to reflect actual project data outputs rather than left in its original submitted form.
What This Means for Research Administrators
The practical risk in 2026 is not ignorance of the headline open access requirement — most institutions have internalised that peer-reviewed outputs must be openly deposited. The risk sits in the secondary layer: DMP maintenance treated as a one-off submission, persistent identifiers omitted from repository metadata, and proposal teams voluntarily committing to open code or open monographs that then become de facto obligations reviewers expect to see delivered. Building a standard pre-award checklist that flags mandatory versus recommended items separately — and assigning DMP review to the same office that tracks reporting deadlines — closes most of this gap without adding significant administrative burden.
Professional bodies including EARMA, ARMA and INORMS continue to publish guidance aimed at exactly this administrator audience, and research offices new to Horizon Europe compliance should treat their briefings as a first point of reference alongside the Commission’s own annotated grant agreement.
Looking Ahead
As the horizon europe work programme 2026 cycle progresses, expect continued tightening around persistent identifier reporting and repository certification, mirroring trends already visible in national policies such as the UKRI open access update and NIH data sharing enforcement. Institutions that build DMP review and identifier hygiene into standard pre-award workflows now will find compliance easier to demonstrate as funders move from policy statements to systematic verification.
Leave a Reply