CASRAI Dictionary

Tag: data management plans

  • 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.

  • UKRI’s New Research Data Policy: A Plain-English Briefing for Institutional Administrators

    UKRI is expected to publish an updated research data policy in summer 2026, and institutional research offices should not wait for the final text to start preparing. Signals from UKRI’s existing Common Principles on Data Policy, its 2022 open access policy, and the broader direction of travel across funders point clearly toward a single organising idea: “maximising data value.” For research administrators, that phrase is not a slogan — it is a compliance requirement in waiting, and it will touch data management plans, persistent identifiers, and the systems that track them long before any enforcement clock starts ticking.

    The pattern is familiar. When the UKRI open access policy took effect for journal articles in 2022 and for monographs in 2024, institutions that had already invested in repository infrastructure, author identifier hygiene, and rights-retention workflows absorbed the change with minimal disruption. Those that had not scrambled. A forthcoming UKRI research data policy is likely to follow the same script, extending the funder’s open research agenda from published articles to the underlying datasets, code, and materials that support them.

    This briefing sets out, in plain English, what “maximising data value” is likely to mean operationally, and what a research data management policy readiness checklist should contain before the formal text arrives.

    What “Maximising Data Value” Means for a UKRI Research Data Policy

    UKRI’s framing of data value draws directly on the FAIR principles — Findable, Accessible, Interoperable, and Reusable — first articulated in the scientific data community and now embedded in funder expectations across the UK, the EU’s Horizon Europe programme, and beyond. In practice, “maximising value” is unlikely to mean simply “publish more data.” It means data that can be discovered through standard metadata, accessed under clear licensing terms, described in formats other researchers’ tools can parse, and reused with enough provenance information to trust it.

    For administrators, the operational translation is threefold:

    • Findable — datasets need persistent identifiers and rich, machine-readable metadata, typically registered through services such as DataCite, so they surface in discovery tools rather than sitting on an unindexed institutional server.
    • Accessible — access conditions (open, embargoed, or restricted for sensitive data) must be stated explicitly and consistently, not left to individual researcher discretion.
    • Interoperable and Reusable — data needs documented standards, controlled vocabularies where they exist, and licensing that permits reuse, mirroring the rights-retention logic already familiar from open access compliance.

    None of this is achievable researcher-by-researcher at the point of grant closeout. It requires infrastructure that exists before the data is generated — which is precisely why an anticipatory approach matters more than a reactive one.

    Data Management Plans as the Compliance Backbone

    Data management plans (DMPs) are the mechanism through which funders convert data policy principles into auditable commitments. UKRI councils already require DMPs for many grant types, but a unified data policy is likely to standardise expectations across councils that have historically varied — a source of persistent friction for multi-council and interdisciplinary awards.

    Institutions should treat the DMP not as a one-off grant-application document but as a living compliance artefact, reviewed at key milestones: award, mid-project, and closeout. This is where the overlap with research integrity policy becomes explicit. Bodies such as COPE and the UK’s own research integrity infrastructure have repeatedly linked poor data stewardship — undocumented provenance, irreproducible datasets, unclear authorship of derived outputs — to the conditions that enable disputes and, in the worst cases, retractions tracked by services such as Retraction Watch. A robust DMP process is therefore not merely an administrative box to tick; it is a frontline research integrity control.

    Administrators should also expect closer alignment between DMP compliance and the CRediT contributor role taxonomy, which clarifies who is responsible for which stage of data collection, curation, and analysis. CASRAI originated the CRediT contributor role taxonomy in 2014. The standard is now stewarded by NISO as ANSI/NISO Z39.104-2022. Institutions that already map CRediT roles into their publication workflows are well placed to extend the same logic to dataset contributorship statements.

    Persistent Identifiers: The Infrastructure Layer Nobody Notices Until It’s Missing

    Persistent identifiers (PIDs) are the connective tissue of any credible research data infrastructure, and they are the single most concrete thing an institution can fix before a policy lands. Three PIDs matter most:

    • ORCID identifiers for researchers, now widely mandated across funder and publisher workflows, ensuring datasets are correctly attributed even when authors move institutions or change names.
    • ROR (Research Organization Registry) identifiers for institutional affiliation, increasingly required alongside ORCID to disambiguate which organisation is accountable for which output.
    • DataCite DOIs for the datasets themselves, giving each dataset a citable, resolvable, permanent address independent of where it happens to be hosted.

    CrossRef DOIs for articles and DataCite DOIs for datasets should be linked bidirectionally wherever possible, so that a published paper and its underlying data form a verifiable pair. Institutions that have not yet audited their systems for consistent ORCID and ROR capture — particularly in their electronic research administration platforms, current research information systems, and repository intake forms — should treat this as the highest-priority, lowest-cost preparation step available. It requires no new policy to justify; it improves compliance readiness for every funder mandate, not just UKRI’s.

    What This Means for Research Administrators

    The institutions best positioned for a summer 2026 policy announcement will not be the ones that read it fastest — they will be the ones whose sponsored research administration infrastructure already produces compliant metadata as a by-product of normal grant management, rather than as a bolt-on exercise triggered by audit anxiety. Practical steps worth starting now include:

    • Auditing current DMP templates against FAIR principles and standardising them across faculties or research councils where practice has diverged.
    • Confirming that ORCID and ROR capture is mandatory, not optional, at the point of grant setup within the institution’s research administration system.
    • Establishing or reviewing institutional agreements with DataCite (directly or via a national or subject repository) for dataset DOI minting.
    • Mapping data stewardship responsibilities using a CRediT-style contributor framework, so accountability for data quality is documented rather than assumed.
    • Briefing research integrity offices now, so that data policy compliance is understood as an extension of existing research integrity policy rather than a parallel, competing process.

    Professional bodies including ARMA, NCURA, EARMA, and INORMS have all flagged funder data mandates as a growing training and resourcing need for research administrators; institutions that engage with these networks now will have a head start on interpreting whatever UKRI ultimately publishes.

    Looking Ahead

    A formal UKRI research data policy, when it arrives, will almost certainly be framed around the language of value, openness, and reuse rather than restriction. But the operational substance — FAIR-compliant metadata, disciplined data management plans, and consistent use of persistent identifiers — is already knowable, and already actionable. Institutions that treat the coming months as a compliance sprint rather than a waiting period will be the ones for whom “maximising data value” is simply a description of how they already work, not a new burden imposed from outside.

  • NIH’s March 2026 Grants Policy Statement: What Every Institution’s Research Office Needs to Do Now

    The National Institutes of Health has issued a March 2026 revision to the NIH Grants Policy Statement (NOT-OD-26-057), and research offices outside the United States are not exempt from its reach. Any UK or international institution holding a subaward, consortium agreement, or direct NIH grant now has a compliance clock running: the most consequential change — a new prior-approval requirement for subawards — takes effect from 1 June 2026.

    For research administrators, this is not a routine annual refresh. The revised NIH grants policy statement 2026 tightens subrecipient monitoring, reinforces the NIH Data Management and Sharing (DMS) Policy, and, less visibly but just as significantly, hardens expectations around how contributor roles are documented on funded outputs. Institutions that treat this as a US-only administrative update will find themselves scrambling when their next competing renewal or Just-in-Time submission is flagged for missing subaward documentation.

    This explainer sets out what changed, why it matters for research grant administration beyond NIH’s own borders, and the concrete steps a research office should be taking this quarter.

    What NOT-OD-26-057 Actually Changes

    The headline change in the March 2026 NIH Grants Policy Statement revision is the introduction of a prior-approval step before a recipient institution may issue certain subawards under active NIH grants. Historically, subaward issuance sat largely within a recipient’s own delegated authority once the parent award was in hand, subject to standard federal subrecipient monitoring obligations under 2 CFR 200 (the Uniform Guidance). From 1 June 2026, awardee institutions must obtain NIH sign-off before finalising subawards that meet the thresholds specified in the revised policy — a shift that mirrors the agency’s broader push, visible across recent Notices, to get earlier visibility into where federal research funds ultimately flow.

    For UK universities and research institutes that sit downstream as subrecipients on US-led NIH awards, this changes the practical timeline of collaboration. A subaward that might previously have been executed within weeks of a parent award’s Notice of Award could now be delayed pending NIH’s prior-approval review. Research offices coordinating multi-country consortia — a common pattern in genomics, infectious disease, and clinical trials networks — need to build this lag into project start dates and budget-period planning, and should flag it explicitly to principal investigators who are used to faster subaward turnaround.

    Data Management and Sharing: Convergence, Not a New Burden

    The revised Grants Policy Statement does not introduce a new data-sharing regime; instead, it folds the existing NIH Data Management and Sharing Policy more tightly into the core policy document, making DMS plan compliance an explicit, cross-referenced condition of award rather than a companion policy institutions could treat as separate. In practice, this means DMS plans are now read alongside the Grants Policy Statement’s subaward and reporting provisions as a single compliance package, which raises the stakes for institutions whose data plans have been thin or templated.

    The same logic applies to the NIH open access policy lineage — the NIH Public Access Policy that governs deposit of peer-reviewed manuscripts arising from NIH funding. The 2026 revision continues to align expectations around timely deposit, persistent identifiers, and machine-readable metadata with the broader global shift toward open science, echoed in UKRI’s own open access policy and the cOAlition S Plan S principles. Institutions with NIH-funded outputs should treat manuscript deposit compliance and DMS plan fidelity as two halves of the same reporting obligation, not separate boxes to tick.

    Contributor Roles and the Attribution Layer

    A quieter but structurally important element of the revised policy is its reinforcement of contributor-role transparency in reporting and progress reports involving multiple investigators and subrecipient teams. Where an award spans several institutions, NIH’s expectation is that reporting clearly distinguishes who did what — an expectation that maps naturally onto the contributor role taxonomy first published as CRediT.

    CASRAI originated the CRediT contributor role taxonomy in 2014. The standard is now stewarded by NISO as ANSI/NISO Z39.104-2022, and its fourteen roles — from Conceptualization and Methodology through to Writing – Original Draft and Writing – Review & Editing — give research offices a ready-made, internationally recognised vocabulary for exactly the kind of multi-institution attribution NIH’s revised reporting language is asking for. Institutions that already require CRediT statements on manuscripts arising from grant-funded work, and that track contributor roles at the ORCID-linked researcher level, will find it far easier to produce the kind of granular reporting the 2026 policy anticipates than those relying on ad hoc author-order conventions.

    This is a useful moment for research offices to check whether their internal reporting templates for multi-site NIH awards actually capture contributor roles in a structured way, or whether that information exists only informally between collaborating PIs.

    What This Means for Research Administrators

    The combined effect of the subaward prior-approval rule, the tighter DMS/open-access linkage, and the contributor-attribution expectations is a policy environment that rewards institutions with mature research administration policy 2026 infrastructure and penalises those still managing NIH compliance manually. Concretely, research offices should:

    • Map every active and pipeline NIH subaward against the new prior-approval thresholds, and rebuild subaward issuance timelines to account for the review step from 1 June 2026.
    • Audit existing DMS plans against the revised Grants Policy Statement language, not just the standalone DMS Policy text, to close any gaps in how the two are cross-referenced.
    • Confirm that manuscript deposit workflows tied to the NIH Public Access Policy are functioning ahead of any competing renewal or annual progress report.
    • Introduce or reinforce CRediT-based contributor statements in multi-institution reporting, using ORCID identifiers to anchor role attribution at the individual level.
    • Brief PIs directly — subaward delays and reporting changes affect project planning, not just the compliance office, and PIs are often the last to hear about policy notices like NOT-OD-26-057.

    Bodies such as NCURA, EARMA, and ARMA have all flagged the growing complexity of cross-border federal compliance as a priority area, and institutions should look to these networks — alongside INORMS — for shared templates and peer benchmarking rather than building compliance responses in isolation. Investment in structured research administration training on the revised Grants Policy Statement, delivered before the June deadline, will do more to prevent downstream delays than any last-minute scramble once subawards start stalling in review.

    Looking Ahead

    NIH’s March 2026 revision is best read as part of a broader convergence: funder policies, open science mandates, and structured attribution standards are increasingly expected to interlock rather than operate as parallel compliance streams. Research offices that align their subaward management, data-sharing infrastructure, and contributor-role reporting now — rather than treating each as a separate policy silo — will be far better placed not only for this revision, but for the funder policy changes that are likely to follow it as NIH, UKRI, and other major funders continue to tighten the links between funding, data stewardship, and verifiable attribution of research contributions.