CASRAI Dictionary

Tag: Horizon Europe

  • cOAlition S EU-Funded Projects: What Horizon Europe Grantees Must Still Do

    Search “cOAlition S EU-funded projects” and you land on a page that is easy to misread. It does not list the projects cOAlition S funds for grantees — it lists the European Commission grants that fund cOAlition S itself. That distinction matters for research administrators trying to work out which obligations actually attach to a Horizon Europe grant, and which belong to the separate, funder-driven Plan S mandate that the European Commission helped create.

    This piece reads that page on its own terms, then answers the practical question institutions actually have: given that the European Commission’s own Horizon Europe open access mandate already exists, where — if anywhere — does cOAlition S add anything a grantee still has to act on?

    What “EU-Funded Projects” Actually Lists on cOAlition S’s Site

    cOAlition S’s “EU-funded projects” resource page catalogues five Horizon Europe and Horizon 2020 grants awarded to the European Science Foundation and partner consortia to build the infrastructure and evidence base around Plan S — it is not guidance aimed at individual grant recipients. Each entry names the funding call, the EU contribution, the duration and the coordinating institution.

    Project Funded under EU contribution Duration Coordinator
    OA-Advance HORIZON.4.2 €132,000 2024–2025 European Science Foundation (France)
    SOAR H2020-EU.5.e. €299,930 2020–2023 European Science Foundation (France)
    DIAMAS HORIZON-WIDERA-2021-ERA-01-43 €3,000,000 2022–2025 Aix-Marseille University (France)
    CRAFT-OA HORIZON-INFRA-2022-EOSC-01-02 €5,000,000 2023–2028 University of Göttingen Library (Germany)
    PALOMERA HORIZON-WIDERA-2022-ERA-01-42 €2,000,000 2023–2025 OPERAS (Belgium)

    The through-line is instructive: the European Commission is not a passive observer of Plan S. It is a funding partner for the studies (OA-Advance’s independent review of Plan S impact), tools (SOAR’s support for identifying compliant venues) and Diamond open-access infrastructure (DIAMAS, CRAFT-OA, PALOMERA) that keep the mandate operable. That funding relationship is the real answer to how cOAlition S and Horizon Europe are connected — and it is the fact most generic summaries of Plan S skip entirely.

    How cOAlition S and the Horizon Europe Mandate Overlap

    The European Commission is itself a cOAlition S member, alongside national funders including several that fund UK-based and other associated-country researchers, and the Horizon Europe open access mandate is, in substance, the Commission’s own implementation of Plan S principles inside its Model Grant Agreement. Both frameworks require:

    • Immediate open access to peer-reviewed publications, with no embargo period.
    • Deposit of the publication, or the accepted manuscript, in a trusted repository at the time of publication.
    • A Creative Commons Attribution (CC BY) licence, or equivalent, on journal articles and conference papers.
    • Author retention of sufficient rights to comply, regardless of what a publisher’s default policy allows.

    Because these baseline requirements are shared, a grantee who satisfies the Horizon Europe Model Grant Agreement’s open access clause will, in almost all cases, also satisfy Plan S. This is why cOAlition S materials describe Horizon Europe as an aligned implementation rather than a competing regime.

    Where cOAlition S Rules Still Add to the Horizon Europe Baseline

    Alignment is not identity. Three areas where the two frameworks are not simply interchangeable deserve attention from institutional research offices.

    Scope beyond the grant. Plan S is a funder mandate: it binds a researcher’s Plan-S-relevant output for as long as they hold funding from a cOAlition S member, not only the outputs tagged to a single Horizon Europe grant number. A researcher holding both a Horizon Europe grant and, say, a Wellcome or Research Council of Norway award is subject to the combined Plan S obligations of every cOAlition S funder involved — the Horizon Europe clause alone does not cover that.

    The compliance route. cOAlition S operationalises compliance through the Journal Checker Tool, which tells an author whether a specific journal, for their specific funder and affiliation, satisfies the mandate via the fully open access “Gold” route, a compliant transformative agreement, or the self-archiving Rights Retention Strategy route. The Horizon Europe Model Grant Agreement states the requirement; the Journal Checker Tool is the operational instrument grantees actually use to verify a chosen venue — and it is a cOAlition S resource, not an EC one.

    Article Processing Charges in hybrid venues. Horizon Europe funding rules do not reimburse APCs for publishing in hybrid journals — subscription titles that also sell open access on a per-article basis — only in fully open access journals or platforms, including the Commission’s own Open Research Europe platform. Plan S’s broader principle is the same, but grantees who assume “my publisher offered an open access option” is automatically fundable frequently discover the hybrid exclusion applies regardless of which mandate they cite.

    Common Questions from Grantees

    What is an EU funded project?

    An EU-funded project is a research or coordination activity receiving a grant from a European Union programme such as Horizon Europe or its predecessor, Horizon 2020. In cOAlition S’s own case, five such projects — OA-Advance, SOAR, DIAMAS, CRAFT-OA and PALOMERA — fund the coalition’s open access infrastructure and evidence base, not individual researchers’ compliance.

    Can the UK apply for EU funding?

    Yes. The UK re-associated to Horizon Europe from January 2024, meaning UK-based researchers can again apply for and hold Horizon Europe grants directly. UK recipients follow the same open access mandate as any other beneficiary, alongside any separate Plan S obligations from UK funders such as UKRI or Wellcome.

    Is cOAlition S the same body as the European Commission?

    No. cOAlition S is a voluntary alliance of national and private research funders, of which the European Commission is one member among roughly two dozen. The Commission sets Horizon Europe’s own grant conditions independently, but has aligned them closely with Plan S principles as part of that membership.

    Do Horizon Europe grantees need to follow Plan S separately from their grant agreement?

    Usually not in substance, since the Horizon Europe Model Grant Agreement already embeds Plan S’s core requirements. Grantees should still check Plan S obligations separately whenever a co-funder, prior grant, or institutional mandate outside Horizon Europe applies to the same publication.

    A Practical Compliance Checklist

    For research offices triaging a Horizon Europe-funded manuscript against both frameworks, the practical questions are the same regardless of which document a grant officer cites:

    1. Does the venue offer immediate open access with no embargo — checked directly, not assumed from the journal’s general reputation?
    2. Is a CC BY licence (or CC BY-NC / CC BY-ND for a monograph) applied to the published or accepted version?
    3. Has the author retained rights to deposit the accepted manuscript, independent of the publisher’s standard licence terms?
    4. If the venue is hybrid, has the team confirmed the APC is not eligible for reimbursement under Horizon Europe rules before committing funds?
    5. Do any other cOAlition S funders co-fund the same output, requiring a combined compliance check beyond the Horizon Europe grant alone?

    What This Means for Institutions

    The practical risk is not that Horizon Europe and Plan S conflict — it is that research offices treat “we’re Horizon Europe funded, so we’re covered” as a substitute for checking the venue, licence and co-funder picture on each output. Teams that build Journal Checker Tool and rights-retention verification into submission workflows, rather than relying on the Model Grant Agreement clause as a proxy, catch hybrid-APC and multi-funder edge cases before they become a post-award finding.

    For teams supporting research administration workflows across multiple funders, the EU-funded projects underpinning cOAlition S’s own infrastructure — particularly DIAMAS and CRAFT-OA’s work on Diamond open access publishing — are also worth tracking directly, since they signal where funder-preferred, no-fee publishing routes are likely to expand over the current Horizon Europe programming period.

    Outlook

    With DIAMAS and CRAFT-OA running through 2025 and 2028 respectively, and OA-Advance’s independent review due to feed recommendations on what comes after Plan S, the EU-funded projects on cOAlition S’s own page are best read as a forward signal rather than a static resource list. Institutions tracking them alongside their Horizon Europe grant terms — rather than treating the two frameworks as separate compliance tracks — will be better placed as Diamond open access infrastructure matures and funder mandates converge. CASRAI’s open research terminology reference provides further grounding for related definitions.

  • Horizon Europe’s Open Access Mandate for Monographs and Books: What Publishers Need to Know in 2026

    Publishers of academic monographs and edited volumes have a narrowing compliance window in 2026. Institutional guidance issued by research offices across the European Research Area has now confirmed what many university presses suspected was coming: the Horizon Europe monograph open access requirement is being applied as an immediate, no-embargo obligation, not the softer “within twelve months” allowance that long-form outputs enjoyed under Horizon 2020. For scholarly and university-press publishers still relying on embargo windows to protect print sales, the operational implications are significant.

    The shift matters because monographs and edited volumes occupy a different economic and editorial position from journal articles. Peer review cycles are longer, production costs are higher, and many presses depend on frontlist sales in the first year after publication to recoup costs. A mandate that removes the embargo option for Horizon Europe-funded books effectively forces a shift toward open-access business models — book processing charges, subvention funds, or collective funding mechanisms — well before most presses had budgeted for it.

    The Horizon Europe Monograph Open Access Mandate: What Changed

    Horizon Europe’s Model Grant Agreement has, since the programme’s launch, required beneficiaries to ensure open access to peer-reviewed scientific publications arising from funded research, with deposit in a trusted repository at the latest at the time of publication. For journal articles this has meant immediate open access with no embargo permitted — a marked tightening compared with Horizon 2020. Monographs, book chapters and other long-form outputs, however, historically sat in a grey zone: guidance permitted longer embargoes given the different production and revenue model of long-form scholarly publishing.

    Institutional research offices are now reporting that this grey zone has closed. Updated guidance interpreting the Annotated Grant Agreement treats monographs and edited volumes arising from Horizon Europe grants as subject to the same immediate open access expectation as articles, with limited scope for embargo exceptions and only where a beneficiary can demonstrate a documented conflict with legitimate commercial interests, such as a pre-existing publishing contract negotiated before the mandate took effect. In practice, this means grant-holders negotiating new book contracts from 2026 onward should assume zero embargo is the default position, not the exception.

    CC Licensing Rules for Long-Form Outputs

    The licensing dimension is equally consequential. Horizon Europe’s default licensing requirement is CC BY (or a licence with equivalent rights) for the version of record or the final peer-reviewed manuscript, with CC BY-ND permitted in specific cases where the beneficiary can justify it — for instance, to protect the integrity of a monograph’s narrative argument or illustrative content from unauthorised adaptation. For edited volumes with multiple contributing authors, this creates a coordination burden that journal publishers rarely face: every contributor’s chapter must carry a licence consistent with the funder mandate, and permissions for third-party material (images, maps, quoted text) must be cleared for reuse under an open licence rather than the more restrictive “all rights reserved” terms many presses still default to in contracts.

    Publishers should also note that Horizon Europe’s guidance treats the CC licensing requirement as attaching to the funded output itself, not to the press’s broader catalogue. This means a single edited volume may need to carry different licensing terms for different chapters if only some contributors were funded by Horizon Europe grants — a scenario production and rights teams need workflow support to manage rather than resolving case-by-case at proof stage.

    Which Horizon Europe Calls Are Affected

    The monograph mandate is not confined to a single funding stream. It applies wherever a Horizon Europe grant supports the underlying research, which means publishers should expect it across the full spread of Horizon Europe calls that fund book-length outputs — most visibly in Cluster 2 (Culture, Creativity and Inclusive Society), where monographs remain a primary dissemination format, but increasingly in interdisciplinary projects funded through Horizon Europe cluster 5 calls (Climate, Energy and Mobility) where policy-facing edited volumes and technical assessment books are common outputs. The Horizon Europe work programme 2025 carried forward the same open access conditions into 2026-funded actions, so presses handling manuscripts from projects awarded under that programme are already inside the compliance window.

    Health-focused publishers should pay particular attention. Horizon Europe health calls 2026 continue to fund large collaborative projects that frequently produce edited clinical or public-health volumes alongside journal outputs, and the European Commission’s open science requirements apply equally to both formats. University presses that have historically treated health-adjacent edited volumes as a niche, lower-volume category may find that Horizon Europe-funded health projects now represent a disproportionate share of their open-access compliance workload, simply because health clusters fund so many large consortia.

    Attribution and Contributor Roles in Edited Volumes

    Open access mandates for long-form outputs also intersect with a separate but related trend: growing demand for standardised, machine-readable contributor attribution in multi-author books. Journal publishers have widely adopted the CRediT contributor role taxonomy to disambiguate who did what across large author lists; edited volumes with dozens of chapter authors face an analogous — arguably more acute — attribution challenge. CASRAI originated the CRediT contributor role taxonomy in 2014. The standard is now stewarded by NISO as ANSI/NISO Z39.104-2022. Presses building open-access metadata workflows for Horizon Europe-funded volumes should consider whether chapter-level contributor statements, alongside ORCID identifiers for editors and authors, would strengthen compliance reporting to funders and simplify downstream indexing by DataCite and CrossRef.

    What This Means for Research Administrators

    For research offices and grant administrators, the practical consequences fall into four areas:

    • Contract review: existing book contracts negotiated before a project’s Horizon Europe award should be audited for embargo and licensing clauses that now conflict with grant conditions.
    • Budgeting for book processing charges: administrators should confirm with principal investigators whether monograph publication costs have been included in the project budget, since immediate CC BY publication is rarely free.
    • Repository deposit workflows: institutional repositories need to support long-form deposit (full manuscripts, not just abstracts) at the point of publication, which is a different technical and rights-clearance workload than article deposit.
    • Coordination with university presses: where the institution operates its own press, research offices should establish a standing liaison so that acquisitions editors flag Horizon Europe-funded projects at contract stage, not at the point of camera-ready delivery.

    Organisations such as EARMA and ARMA have both flagged long-form open access compliance as an emerging gap in research administration training, and institutions preparing for the next REF cycle in the UK should note that funder-mandated open access terms for books can diverge from REF open access requirements, creating dual-compliance obligations that need to be reconciled rather than assumed to be identical.

    Looking Ahead

    The direction of travel is unambiguous: funders are converging on the position that “open access” means immediate, machine-readable, openly licensed access regardless of output format, and the historical carve-out for monographs is narrowing across the research funding landscape, not only within Horizon Europe. Publishers that build book-processing-charge models, chapter-level rights workflows and CC BY-compliant production pipelines now will be better positioned as other funders — building on cOAlition S’s long-standing work on open access books — follow the same trajectory. For scholarly and university-press publishers, 2026 is the year monograph open access stops being a policy aspiration and becomes a contractual condition of funding.

  • Horizon Europe Open Access Requirements in 2026: A Practical Compliance Checklist for Grant Administrators

    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.

  • Writing a Data Management Plan That Satisfies NIH, NSF, and Horizon Europe

    Research administrators managing multi-funder portfolios face a recurring headache every grant cycle: no two major funders ask for a data management plan in the same way. A single investigator with an NIH R01, an NSF collaborative award, and a Horizon Europe consortium grant may need three structurally different documents that all attempt to answer the same underlying question — how will research data be generated, described, preserved, and shared? Building a reusable data management plan template that maps cleanly onto each funder’s requirements is now one of the most practical efficiency gains available to a research office.

    The stakes have risen. NIH’s 2023 Data Management and Sharing Policy is now actively enforced through award terms and conditions, UKRI’s open access policy has tightened expectations around data underlying publications, and Horizon Europe continues to treat the data management plan as a living deliverable rather than a one-off proposal attachment. Administrators who still draft a fresh plan from scratch for every submission are absorbing avoidable cost. A well-designed crosswalk — and a template built from it — turns a compliance burden into a repeatable process.

    The Funder Crosswalk: NIH, NSF, and Horizon Europe Data Management Plan Requirements Compared

    The three funders diverge on format, timing, and philosophy, even though all three now anchor their expectations in FAIR (Findable, Accessible, Interoperable, Reusable) data principles in substance if not always in name.

    • NIH: The Data Management and Sharing Plan is submitted as a distinct attachment at the time of proposal, is not subject to the page-limit rules that apply to the research strategy, and is expected to address six elements — data type, related tools and software, standards applied, oversight of data sharing, and preservation and access timelines, including where data will be deposited. NIH review does not score the plan competitively but the awarded terms make compliance a condition of funding, and lack of an approved plan can hold up an award.
    • NSF: The data management plan is a mandatory two-page supplementary document across all directorates, required since NSF’s foundational 2011 data sharing policy. NSF is comparatively brief on prescribed sections but expects coverage of the types of data produced, standards for metadata, provisions for access and sharing, and policies for reuse and redistribution. Reviewers do weigh the plan as part of the intellectual merit and broader impacts criteria, which makes NSF’s version more consequential to scoring than NIH’s.
    • Horizon Europe: The DMP is not typically required at proposal stage for most calls; instead it is a formal deliverable due within the first six months of a funded project and is explicitly framed as a “living document” to be updated at least once more during the project lifecycle, often at mid-term and final reporting. Horizon Europe’s template, aligned with its open science policy, requires explicit narrative on FAIR compliance for each dataset, plus details on cost, responsibilities, and security, including whether data will be open by default or requires a documented exception.

    The practical consequence for administrators is that the same investigator’s data description work has to be repackaged three times: NIH wants it compact and attached at submission, NSF wants it capped at two pages and reviewer-facing, and Horizon Europe wants it detailed, iterative, and post-award. A shared template only works if it separates the stable content — data types, standards, repositories, roles — from the funder-specific packaging around it.

    Where UKRI and Clinical Trial Plans Diverge Further

    Multi-funder portfolios rarely stop at the “big three.” Two further categories complicate the picture for UK-facing and clinical research offices.

    A UKRI data management plan follows UKRI’s Common Principles on Data Policy, but implementation is devolved to the individual research councils (MRC, BBSRC, ESRC, and others), each of which has its own template and level of prescriptiveness. This is a different model from Horizon Europe’s single harmonised template, and it means a UKRI-funded co-investigator on a Horizon Europe project may technically owe two structurally distinct plans for the same dataset. UKRI’s broader push on open access — extended in recent policy updates to cover monographs and underlying data alongside journal articles — has raised the profile of the DMP as a compliance artefact rather than an administrative afterthought.

    A clinical data management plan is a different instrument entirely, and administrators should not conflate the two. Where a funder DMP addresses data stewardship at the study or grant level, a clinical data management plan operationalises data collection, validation, cleaning, and quality control for a specific clinical trial, typically governed by Good Clinical Practice (GCP) principles and referenced in trial protocols. ICMJE’s data-sharing statement requirement for clinical trial registration adds a further, related but non-identical obligation: a public statement, at registration, of whether and how individual patient data will be shared after publication. A portfolio that includes clinical trials therefore needs both a funder-facing DMP and a trial-level clinical data management plan, cross-referenced but not merged.

    Building a Template Structure That Works Across Portfolios

    A functional cross-funder template separates content into modular blocks that can be recombined per submission rather than rewritten. A workable structure includes:

    • Data inventory: types, formats, and estimated volumes of data to be generated or reused, written once and reused across all funder versions.
    • Standards and metadata: discipline-specific metadata schemas and file formats, referencing recognised community standards where they exist.
    • Storage and security during the project: active storage, backup, and access-control arrangements, particularly relevant to Horizon Europe’s security section and to clinical trial data governance.
    • Preservation and repository: the named repository (disciplinary, institutional, or generalist, such as those indexed by DataCite) and expected retention period.
    • Access and reuse conditions: licensing terms, embargo periods, and any restrictions arising from participant consent, commercial sensitivity, or export control.
    • Roles and responsibilities: named individuals accountable for each stage, which Horizon Europe expects explicitly and NIH and NSF increasingly expect implicitly through institutional data stewardship policies.

    From this modular base, administrators can generate NIH’s compact attachment, NSF’s two-page version, and Horizon Europe’s fuller living document by adjusting emphasis and length rather than starting over. Tools such as DMPonline (maintained by the Digital Curation Centre) and DMPTool already offer funder-specific templates built on broadly this logic, and reviewing existing data management plan examples published through these platforms is a faster route to a working draft than starting from a blank page. The discipline is in maintaining the underlying data inventory as the single source of truth and treating each funder’s version as an export, not an independent document.

    What This Means for Research Administrators

    For research offices supporting investigators across NIH, NSF, Horizon Europe, and UKRI portfolios simultaneously, the crosswalk approach changes three things in practice. First, pre-award staff can build a standing “data profile” per investigator or dataset at the proposal-development stage, rather than waiting for each funder’s specific form to trigger the work. Second, post-award compliance monitoring becomes more tractable: Horizon Europe’s requirement for plan updates at mid-term and final reporting, and NIH’s enforcement of the terms attached at award, both depend on someone tracking which version is current and when the next revision is due. Third, offices supporting clinical research need to keep the clinical data management plan and the funder DMP as separate but cross-referenced documents, since conflating them risks under-specifying either the trial-level quality controls or the funder-level FAIR compliance narrative.

    The administrative overhead of multi-funder compliance is not going away — if anything, the direction of travel among NIH, NSF, UKRI, and Horizon Europe is toward more explicit, more frequently updated, and more publicly scrutinised data plans. Institutions that invest now in a modular, crosswalk-based template will spend less time reconciling funder idiosyncrasies later, and will be better positioned as additional funders and national mandates converge, however unevenly, on the same underlying FAIR data commitments.

  • Horizon Europe Open Science Requirements: Compliance Guidelines for Grant Recipients

    1. Introduction to the Role of Horizon Europe Open Science in Scholarly Infrastructure

    In the contemporary landscape of global science, open research practices, and institutional data governance, establishing robust standards is crucial. The integration of Horizon Europe Open Science represents a landmark advancement in addressing long-standing hurdles in scholarly communication, administrative reporting, and metadata curation. This extensive guide provides an expert-level breakdown of the operational frameworks, specifications, and systemic requirements surrounding Horizon Europe Open Science in 2026.

    As academic funders and research ministries worldwide enforce increasingly rigid compliance pathways, universities must transition from ad-hoc administrative workflows to unified, persistent-identifier-driven schemas. Implementing Horizon Europe Open Science is not merely a technical adjustment; it is a strategic necessity that secures institutional research visibility, ensures frictionless metadata reporting, and compounds the impact of scientific investments.

    2. Technical Architecture and Core Specifications

    Underpinning the deployment of Horizon Europe Open Science is a set of rigorous, machine-actionable specifications designed to operate seamlessly across diverse platforms. This environment relies heavily on the mandatory open science mandates of Horizon Europe, including immediate open access and data management plans (DMPs). By establishing clear, standardized data exchange layers, organizations can bypass the siloed architectures that have traditionally plagued research information networks.

    A key focus of these specifications is the preservation of structural metadata integrity. This is achieved by mapping data payloads to recognized open vocabularies, such as Dublin Core, Schema.org, and custom JSON-LD graphs. This ensures that every scientific output—be it a journal article, a software version, or an administrative record—carries citable provenance tags, enabling automated indexing and cross-referencing by global citation engines such as OpenAlex and Crossref.

    3. Institutional Challenges, Workflows, and Solutions

    While the administrative and scientific benefits of Horizon Europe Open Science are indisputable, the practical deployment across universities and libraries reveals significant hurdles. Major friction points include securing intellectual property, depositing in certified repositories, and reporting compliance indicators in project portals. Faculty reluctance, legacy software limitations (such as outdated CRIS databases), and the high administrative cost of manual curation represent substantial barriers to widespread compliance.

    Overcoming these implementation bottlenecks requires a systemic, top-down commitment to administrative automation. Institutions must deploy modern API middleware to coordinate data transfers between local enclaves and global public registries, eliminating manual data-entry redundancy. Furthermore, university promotion and tenure committees must update their evaluative rubrics to formally credit researchers for complying with these modern curation workflows, establishing a cultural positive-feedback loop.

    4. Technical Evaluation and Integration Matrix

    Integration Domain Primary Objective Core Interoperability Standard Friction Mitigation Strategy
    Persistent Identification Ensure permanent, citable links across registries. Unique URI / DOI Resolve Systems Implement automated metadata harvesting on ingest.
    Metadata Exchange Frictionless transfer between CRIS and repositories. JSON-LD / XML Schema Mapping Deploy standardized REST APIs with OAuth 2.0.
    Compliance Auditing Track, verify, and report on policy adherence. Standardized SQL / GraphQL Querying Generate real-time compliance scorecards for PIs.

    5. Five-Step Institutional Implementation Roadmap

    • Step 1: Institutional Alignment & Sign-off — Establish an official cross-departmental committee representing the library, IT services, and the research office to draft the institutional deployment charter for Horizon Europe Open Science.
    • Step 2: API & Schema Mapping — Audit existing repository databases and map local metadata schemas to match the international JSON-LD specifications required for Horizon Europe Open Science.
    • Step 3: Middleware Integration & SSO — Configure enterprise middleware layers to handle automated data harvesting and synchronize access using Single Sign-On (SAML/Shibboleth).
    • Step 4: Training & Support Networks — Deploy interactive workshops, dedicated helpdesks, and online documentation to educate researchers, metadata curators, and administrative staff.
    • Step 5: Automated Verification & Auditing — Launch real-time validation checks and annual data-quality audits to measure compliance rates and automatically identify and correct orphaned records.