CASRAI Dictionary

Category: Guides & Explainers

Practical how-to guides, templates, checklists, and career pathways for research administrators, authors, and institutional teams.

  • Horizon Europe Missions: Five Areas Explained

    Horizon Europe missions are five large-scale, cross-cutting research and innovation portfolios — cancer, climate adaptation, healthy oceans, climate-neutral cities, and soil health — each carrying a measurable, time-bound target for 2030. Rather than funding a single discipline, each mission pulls projects from across Horizon Europe’s thematic clusters and blends them with national, regional and private co-investment to hit one public goal.

    A Horizon Europe mission is a portfolio of research, innovation and policy actions, governed by a dedicated Mission Board, that is funded through Pillar II and structured around a single measurable societal target rather than a single scientific field.

    What are Horizon Europe missions and where do they sit in the programme?

    EU Missions were introduced as a genuine novelty of the 2021–2027 framework programme — commonly nicknamed FP9 — and did not exist in this form under Horizon 2020. Under Regulation (EU) 2021/695, missions are programmed within Pillar II, “Global Challenges and European Industrial Competitiveness”, but they may also draw on actions from other parts of Horizon Europe and from complementary Union funding streams.

    Each mission is steered by a Mission Board of around 15 independent experts who propose the targets, milestones and implementation timeline. This is the single most useful distinction for institutional staff: a cluster is a thematic grouping of Pillar II funding (there are six), while a mission is a target-driven portfolio that cuts across clusters and pulls in complementary funding to reach one outcome.

    What are the five Horizon Europe mission areas?

    Horizon Europe funds exactly five missions, each with its own board, implementation plan and public-facing platform. All five share a 2030 target horizon and were designed with input from citizens, researchers and policymakers before being written into the first Horizon Europe work programmes.

    Mission Core 2030 target Notable early funding signal
    Cancer Improve the lives of more than 3 million people through prevention, cure and quality of life, aligned with Europe’s Beating Cancer Plan €378.2 million allocated to Cancer Mission calls in 2021–2023
    Adaptation to Climate Change Support at least 150 European regions and communities in becoming climate-resilient Delivered via the Climate-ADAPT knowledge platform and national ERA hubs
    Restore our Ocean and Waters Protect and restore the health of marine and freshwater ecosystems Linked to a carbon-neutral, circular blue economy target
    Climate-Neutral and Smart Cities 100 EU cities (plus 12 in associated countries) climate-neutral by 2030, as replication hubs for all EU cities by 2050 Delivered through the NetZeroCities platform
    A Soil Deal for Europe Establish 100 living labs and lighthouses driving healthy-soil transition Delivered through the Mission Soil Platform

    Every mission publishes its own implementation plan, which sets out sub-targets, expected impact pathways and the indicators projects must report against — these plans, not the headline goal alone, are the document research offices should read before drafting a proposal.

    How do mission work programmes turn targets into calls?

    Mission targets do not become funding opportunities automatically. Each mission’s implementation plan feeds into the biennial Horizon Europe Work Programme, where the target is broken down into “destinations” and, beneath those, individual “topics” — the actual calls for proposals published on the EU Funding & Tenders Portal.

    • Implementation plan sets the mission-level target, milestones and expected impact.
    • The biennial work programme translates that plan into a “destination” — a themed cluster of calls for the two-year period.
    • Each destination is broken into “topics”, which specify the challenge, expected outcomes, scope and indicative budget per project.
    • Consortia submit proposals against a specific topic; awarded grant agreements are then tagged to the parent mission in CORDIS.

    This destinations-and-topics structure is why the same mission can appear inside more than one cluster’s work programme chapter in a given call round — the Cancer Mission, for example, draws topics from the Health cluster while the Cities Mission draws from Climate, Energy and Mobility, alongside dedicated mission-only calls.

    What should research offices track for mission-linked reporting?

    Mission-linked grants carry reporting obligations beyond the standard Horizon Europe periodic and final report. Research offices should build mission tracking into their grants-management workflow at award stage, not at reporting deadline.

    • Mission tag verification. Confirm the grant agreement’s work programme “destination” code maps to the correct mission in CORDIS, since misclassified projects distort institutional impact reporting.
    • Impact-pathway indicators. Each mission defines its own indicator set — soil-health metrics via the Mission Soil Platform, city-level KPIs via NetZeroCities, cancer-outcome metrics tied to the Beating Cancer Plan — and beneficiaries must report against these alongside standard deliverables.
    • Co-funding disclosure. Because missions blend Horizon Europe funding with national, regional or private contributions, offices must track and disclose non-EU co-investment tied to the same mission target.
    • Platform registration. Living-lab and lighthouse projects under the Soil and Cities missions typically require registration on the relevant EU platform in addition to standard grant reporting.

    Institutions that treat mission reporting as identical to standard Horizon Europe reporting under-report their own impact contribution, since mission indicators are not captured by the generic project reporting template.

    Answer-first questions on Horizon Europe missions

    What are the five EU missions?

    The five EU Missions under Horizon Europe are Cancer, Adaptation to Climate Change, Restore our Ocean and Waters, Climate-Neutral and Smart Cities, and A Soil Deal for Europe. Each targets a measurable 2030 outcome and is governed by its own Mission Board, which sets the implementation plan feeding the biennial work programme.

    Which pillar of Horizon Europe are missions programmed under?

    Missions are programmed within Pillar II, “Global Challenges and European Industrial Competitiveness”, per Regulation (EU) 2021/695. They may also draw on complementary actions from other parts of Horizon Europe and other Union funding programmes, which is why mission calls surface across multiple clusters rather than in one standalone budget line.

    Can UK-based researchers apply to Horizon Europe mission calls?

    The UK re-associated to Horizon Europe in 2024, restoring eligibility for UK-based applicants to apply to Horizon Europe calls, including mission-linked topics, on the same terms as EU member state participants, subject to the specific eligibility conditions published in each call topic.

    How often is the Horizon Europe missions work programme updated?

    Horizon Europe work programmes — including mission-specific destinations — are adopted on a biennial cycle, meaning mission targets are re-translated into fresh calls roughly every two years, with interim amendments possible when the European Commission adjusts budget or scope.

    Implications for institutional strategy

    For research offices, the practical distinction that matters is not “mission versus cluster” in the abstract but which reporting obligations attach to which grant. A project funded through a mission destination inherits both the standard Horizon Europe reporting template and a mission-specific indicator set — treating the two as interchangeable is the most common institutional compliance gap identified in mission-linked awards.

    As the current 2021–2027 programme runs toward its close and the Commission finalises the successor framework programme covering 2028–2034 — proposed at a substantially larger headline budget — the five mission areas described here remain the reference structure for any institution still reporting against live Horizon Europe mission grants, regardless of how the next programme is eventually shaped.

  • What Is REF 2029? A Plain-English Explainer for New Research Staff

    REF 2029 is the UK’s next Research Excellence Framework exercise — the national, peer-review-based assessment that determines how roughly £2 billion a year in public research funding is allocated to UK universities. Submissions are due in autumn 2028, with results published in December 2029.

    The Research Excellence Framework (REF) is the system the four UK higher education funding bodies use to assess the quality of research produced by UK universities and other higher education providers, and to inform block-grant research funding decisions accordingly.

    What Is REF 2029?

    REF 2029 is the fourth full cycle of the Research Excellence Framework, following REF 2014, REF 2021, and their predecessor, the Research Assessment Exercise. It was originally scheduled as “REF 2028” but was renamed and extended following a December 2023 policy decision, moving the results date back to December 2029.

    Research England manages the exercise on behalf of all four UK higher education funding bodies: Research England (covering England), the Scottish Funding Council, Medr — Wales’ Commission for Tertiary Education and Research — and the Department for the Economy, Northern Ireland. Their shared aim, carried over from previous cycles, is to secure a world-class, dynamic and responsive research base across UK higher education.

    Who Does REF 2029 Apply To?

    REF 2029 applies to every UK higher education provider that receives public research funding and chooses to make a submission. Submissions are organised by discipline into Units of Assessment (UoAs), each reviewed by an expert sub-panel sitting under one of four main panels covering the sciences, engineering, social sciences, and arts and humanities.

    The biggest structural change for first-time submitters: REF 2029 decouples research outputs from named individual staff. Under REF 2021, institutions submitted a set number of outputs per named staff member. Under REF 2029, an institution’s total research volume is calculated automatically from Higher Education Statistics Agency (HESA) staff data — specifically, staff recorded as having significant responsibility for research — with outputs required in proportion to that calculated volume rather than tied to individually listed academics.

    What Does REF 2029 Assess?

    REF 2029 assesses research quality through three weighted elements. Each Unit of Assessment receives a profile combining scores across all three, expressed on the same five-point scale used since REF 2014 (4* world-leading down to unclassified).

    Assessment element What it covers Weighting
    Contribution to Knowledge and Understanding (CKU) Peer review of submitted research outputs (publications, datasets, practice-based outputs) and a unit-level disciplinary statement 55%
    Engagement and Impact (E&I) Impact case studies describing effects on the economy, society, culture, public policy, health or quality of life beyond academia 25%
    Strategy, People and Research Environment (SPRE) Institution- and unit-level statements on research culture, people strategies, and research infrastructure 20%

    SPRE — renamed from the originally proposed “People, Culture and Environment” (PCE) element — is scored 60% at institutional level and 40% at unit level, meaning an institution’s overall research infrastructure carries more weight than any single department’s environment.

    How Does REF 2029 Differ From REF 2021?

    REF 2029 keeps the same three-part structure as REF 2021 but rebalances the weightings and changes how submissions are built. The table below compares the two exercises directly.

    Feature REF 2021 REF 2029
    Outputs element weighting Outputs: 60% CKU: 55%
    Impact element weighting Impact: 25% Engagement and Impact: 25%
    Environment element weighting Environment: 15% Strategy, People and Research Environment: 20%
    Staff submission model Named individual staff, fixed outputs per person Decoupled; HESA-derived research volume, no fixed per-person minimum
    Output portability Output counted for both institutions if a researcher moved Tied to the employing institution by default, with a five-year portability concession for long-form outputs

    An important, under-reported fact for anyone new to REF: the REF 2029 criteria-setting process was formally paused in autumn 2025 after sector concern about the original PCE proposals, and the current weightings above were only confirmed in winter 2025 once the pause was lifted. Guidance published before that point should be treated as superseded.

    What Is the REF 2029 Timetable?

    The REF 2029 project timetable, maintained by Research England and last updated 10 December 2025, sets out the milestones below. Institutions preparing their first submission should track this schedule directly, since dates for the census and output periods are refined as guidance is finalised.

    Milestone Timing
    REF renamed from “REF 2028” to “REF 2029”; extension confirmed Winter 2023
    Full expert panel membership announced Summer/Autumn 2025
    REF 2029 criteria-setting paused Autumn 2025
    Weightings confirmed; SPRE and Engagement and Impact guidance published Winter 2025
    Final guidance on submissions and panel criteria published Autumn 2026
    Survey of submission intentions Spring–Summer 2027
    Submission window opens Autumn 2027
    Submission deadline; assessment phase begins Autumn 2028
    Results published December 2029

    Common Questions About REF 2029

    Is it REF 2028 or REF 2029?

    It is REF 2029. The exercise was originally planned as “REF 2028” but Research England announced an extension in December 2023 following consultation, renaming it REF 2029 and moving the results date to December 2029, with submissions due in autumn 2028.

    What Are the Changes in REF 2029?

    The three headline changes are: decoupling of outputs from named individual staff in favour of a HESA-derived research volume measure; a rebalanced weighting toward outputs (CKU 55%) and research environment (SPRE 20%); and a five-year portability concession for long-form outputs when researchers move institution.

    What Is the REF 2029 Definition of Impact?

    REF’s definition of impact, carried forward into REF 2029’s Engagement and Impact element, is an effect on, change to, or benefit for the economy, society, culture, public policy, services, health, the environment, or quality of life, occurring beyond academia. It is evidenced through impact case studies at Unit of Assessment level.

    What Period Does REF 2029 Cover?

    REF 2029’s submission deadline falls in autumn 2028, with the assessment phase running through 2029 and results published in December 2029. Exact census and output-period start/end dates are confirmed in the REF 2029 guidance’s Section 1 Overview, published on the official REF 2029 site.

    What This Means for First-Time Submitters

    If you are a new research-administration staff member or an early-career researcher encountering REF for the first time, three practical points follow from the above:

    • You will not be individually “submitted” or excluded by name in the way REF 2021 worked — your institution’s HESA-derived staff data determines its overall output requirement, so your contribution matters at unit level rather than through a fixed personal output quota.
    • Impact case studies and disciplinary statements still require accurate, evidenced attribution of who contributed what to a piece of research — this is where standardised contributorship records become operationally useful for REF preparation.
    • Because REF 2029’s criteria were paused and then revised in 2025, always check the publication date on any guidance document against the official REF 2029 timetable before relying on it.

    Where to Find Primary REF 2029 Guidance

    The authoritative source for REF 2029 rules, panel criteria and open-access policy is the official REF 2029 site, maintained by Research England on behalf of the four funding bodies; institution-specific planning pages from individual universities (Reading, Leeds, Oxford, St Andrews and others) are useful secondary summaries but should always be checked against the primary guidance sections. UKRI’s Research England pages provide the policy and funding context that sits above the REF itself.

    For institutions building out their REF submission workflows, clear, standardised contributor attribution is increasingly relevant to both the Engagement and Impact and Contribution to Knowledge and Understanding elements — an area where CRediT-based contributor role taxonomies and broader research administration practice intersect with REF preparation. As REF 2029’s remaining guidance and panel criteria are finalised through 2026 and 2027, first-time submitters should expect further refinement rather than wholesale change to the framework described here.

  • REF 2029 Output Eligibility: OA Exceptions

    REF 2029 output eligibility does not require every journal article or conference paper to be immediately open access. The policy allows four exception categories — deposit, access, technical, and a catch-all “other” route covering staff circumstances, third-party rights and technical infeasibility — each keeping an otherwise non-compliant output eligible, provided the exception is identified, evidenced and stays within a unit’s five per cent non-compliance tolerance.

    The REF 2029 open access policy is the UK funding bodies’ requirement that in-scope journal articles and conference proceedings, published between 1 January 2021 and 31 December 2028, be deposited, discoverable and freely accessible to be eligible for the Research Excellence Framework 2029, subject to defined exceptions.

    Durham University’s Library Research Support service publishes a working exceptions log — updated as recently as 1 July 2026 — that maps each permitted exception to the evidence a research office should hold, offering a practical template for institutions building their own REF 2029 compliance file.

    Contents

    What counts as an REF 2029 output eligibility exception?

    An REF 2029 output eligibility exception is a recognised circumstance under which an in-scope journal article or conference contribution is exempt from some or all open access criteria while remaining eligible for submission. The REF 2029 open access policy, last updated 13 June 2025, groups these into deposit, access and technical exceptions plus a further “other” exception for circumstances beyond an institution’s control.

    Applying an exception correctly means the output is treated as no-detriment and does not count against a unit’s compliance tolerance. Misapplying one, or failing to evidence it, risks the output being reclassified as unclassified during audit.

    Two separate exception frameworks apply depending on when the output was first published:

    • Outputs published 1 January 2021 to 31 December 2025 follow the carried-forward REF 2021 exception categories, with one additional exception added for REF 2029.
    • Outputs published from 1 January 2026 follow a revised, consolidated exceptions framework of four categories, alongside tighter embargo maxima (six months for Main Panels A and B, twelve months for Main Panels C and D, down from twelve and twenty-four months respectively).

    Individual staff circumstances: who qualifies for an exception?

    Staff-circumstance exceptions cover authors whose personal, employment or contractual situation made compliance genuinely impossible. Under the “other” exception, this includes extenuating personal circumstances such as extended leave, industrial action, institutional closure days, and software problems not already covered by the technical category.

    A related technical exception applies where an output has a substantive connection to the submitting institution but was published after the author’s employment ended, and compliance could not be determined. A further exception, introduced for REF 2029, exempts outputs authored entirely by staff ineligible for the volume measure, since they had no expectation of needing compliance.

    One risk is flagged explicitly: institutions relying heavily on the “other” category are more likely to attract a higher audit risk score, though deposit, access or technical exceptions do not themselves raise risk. A researcher on long-term sick leave whose manuscript could not be deposited within the three-month window would typically be recorded under “other”, with leave dates and repository correspondence kept as evidence — the record Durham’s log recommends holding before, not after, submission.

    Third-party rights and technical infeasibility: the other routes

    Third-party rights exceptions apply where an output reproduces content — images, data extracts, previously published material — for which open licences could not be obtained at reasonable cost or within the required timescale. Here, deposit and discovery requirements still apply; only access and/or licensing conditions are waived.

    Technical infeasibility exceptions cover cases where the failure sits with infrastructure rather than the author: a repository’s short-term technical failure (excluding systemic issues), or an external service provider failure, such as a subject repository that did not lift an embargo on schedule or ceased operating altogether.

    Exception category What it exempts Typical qualifying scenario
    Deposit All open access criteria (deposit, discovery, access, licensing) Unlawful to deposit; publisher disallows repository deposit; delay securing final peer-reviewed text
    Access Access, embargo and/or licensing only — deposit and discovery still required Embargo exceeds policy maxima; third-party content licensing unavailable
    Technical All open access criteria Repository or external service provider failure; employment ended before publication
    Other All open access criteria Personal circumstances, industrial action, closure days, unlisted software issues

    Durham’s exceptions log as a working model

    Durham University’s Library Research Support service maintains a dedicated REF 2029 Open Access Exceptions guide, structured as four tabs: deposit, access, and technical/other exceptions for outputs published to 31 December 2025, plus a consolidated four-category framework for outputs from 1 January 2026. Each tab pairs the qualifying scenarios with how the exception is expected to be evidenced during any future audit.

    Two features make it a useful model: it separates outputs by publication date, since qualifying criteria and embargo maxima genuinely differ either side of 1 January 2026; and it is candid about what remains unresolved. As of its 1 July 2026 update, Durham states that “the internal process for applying exceptions is yet to be confirmed,” directing queries to its repository administration team meanwhile — a reminder that internal workflows keep evolving well after the REF policy text has stabilised.

    Documenting exceptions for audit: what research offices must keep

    REF 2029 audit will broadly mirror the risk-based approach used for REF 2021, per the funding bodies’ guidance, while final procedures remain under development. In REF 2021, ten institutions’ submissions were selected for second-stage audit on a risk basis, producing four data adjustments; three were separately selected for substantive sampling; one had to adjust its submission by a single output. For REF 2029, evidence may be required at individual-output level, including written justification for any use of the “other” category.

    A minimum evidence file for each exception should include:

    1. The exception category claimed and the REF 2029 guidance paragraph it falls under.
    2. Dates of acceptance, publication and deposit, plus any embargo end date.
    3. Correspondence documenting the barrier — a publisher refusal, or confirmation of a service outage.
    4. A short narrative justification, particularly for “most appropriate publication” or “other” claims.
    5. Confirmation the output falls within the unit’s five per cent, or one-output, tolerance.

    Institutions should also monitor exception mix over time: a submission weighted heavily toward “other”, rather than deposit, access or technical exceptions, is more likely to draw a higher audit risk score, even where every claim is legitimate.

    Answer-first Q&A

    What is the publication period for REF 2029?

    The output types in scope of the REF 2029 open access policy are journal articles and conference contributions with an International Standard Serial Number, first published between 1 January 2021 and 31 December 2028. Outputs published from 1 January 2026 follow revised deposit, embargo and licensing requirements, while earlier outputs follow REF 2021-derived rules carried forward for REF 2029.

    What publications are eligible for REF 2029?

    Eligible outputs include journal articles and conference proceedings with an ISSN, plus long-form outputs such as monographs, book chapters and scholarly editions, which carry no open access requirement. Datasets, code, protocols and artistic creations are also welcomed, though they sit outside the open access policy’s scope entirely.

    What does the REF output rating measure?

    REF output quality is measured against three fundamental dimensions: originality, the development of new concepts or techniques; significance, the capacity to influence scholarly thought, policy or practice; and rigour, the intellectual coherence and robustness of the methodology. Open access exceptions affect eligibility, not the quality score itself, which panels assess independently.

    What this means for research offices ahead of REF 2029

    For research administration teams, exception management is now a compliance workstream in its own right, not an afterthought bolted onto repository deposit. With a five per cent (or one-output) tolerance per unit of assessment, a handful of poorly evidenced exceptions can tip a submission over the threshold and trigger removal of otherwise strong outputs. Institutions should build an exceptions log now, using Durham’s date-segmented structure as a template: separate outputs to 31 December 2025 from those from 1 January 2026, record the exception paragraph relied upon, and retain evidence when the exception first arises, not retrospectively. Given that REF 2021 audits produced adjustments even at confident institutions, a living exceptions file — not a retrospective justification exercise — separates a smooth submission from a last-minute scramble.

  • REF 2029 Open Access Policy: Deposit & Embargo Rules Explained

    The REF 2029 open access policy requires journal articles and conference proceedings with an ISSN, published from 1 January 2026 to 31 December 2028, to be deposited within three months of publication, made available after an embargo of no more than six months (Main Panels A and B) or twelve months (Main Panels C and D), and shared under a licence that is at minimum CC BY-NC-ND, with CC BY strongly preferred. Monographs and other long-form outputs remain outside its scope.

    The REF 2029 open access policy is the funding bodies’ mandatory framework, set out by the four UK higher education funding bodies for the Research Excellence Framework, governing how eligible journal articles and conference outputs must be deposited, embargoed and licensed to count toward a university’s REF 2029 submission.

    What does the REF 2029 open access policy cover?

    The policy applies only to journal articles and conference contributions carrying an International Standard Serial Number (ISSN), published between 1 January 2021 and 31 December 2028. Outputs published before 1 January 2026 remain subject to the legacy REF 2021 requirements, while everything published from 1 January 2026 onward must meet the revised, tighter rules.

    Two publication windows therefore run in parallel for REF 2029 purposes:

    • 1 January 2021 – 31 December 2025: REF 2021-era requirements apply (deposit within three months of acceptance; 12/24-month embargo caps).
    • 1 January 2026 – 31 December 2028: revised REF 2029 requirements apply (deposit within three months of publication; 6/12-month embargo caps; open-licence preference).

    Datasets, code, protocols, artistic outputs and preprints without an ISSN fall outside the policy entirely, though the funding bodies encourage — but do not require — making them open where practical.

    What is the deposit window for REF 2029 outputs?

    For outputs published from 1 January 2026, the author’s accepted manuscript (AAM) — or, where the publication agreement permits, the version of record — must be deposited in an institutional repository, a shared repository service, a subject repository, or a compliant preprint server within three months of the date of publication, not the date of acceptance as under REF 2021.

    This is a meaningful procedural shift: under the REF 2029 guidance hub’s Section 5 policy, the trigger date moves later in the workflow, which library teams need to build into repository-ingest reminders rather than acceptance-stage checklists alone. Institutions that already deposit on acceptance can keep doing so “at no detriment” — the three-month-post-publication rule is a floor, not a ceiling.

    What are the REF 2029 embargo caps by panel?

    For outputs published from 1 January 2026, permitted embargo periods are halved relative to REF 2021: Main Panels A and B (medicine, health, life sciences, physical sciences, engineering, mathematics) fall to a maximum six-month embargo, and Main Panels C and D (social sciences, arts and humanities) fall to a maximum twelve-month embargo. Interdisciplinary outputs spanning A/B and C/D boundaries may use the longer of the two applicable caps.

    Requirement Outputs published 2021–2025 (REF 2021 rules) Outputs published 2026–2028 (REF 2029 rules)
    Deposit trigger Within 3 months of acceptance Within 3 months of publication
    Embargo cap, Panels A & B 12 months 6 months
    Embargo cap, Panels C & D 24 months 12 months
    Licence floor CC BY-NC-ND or equivalent CC BY-NC-ND or equivalent (CC BY preferred)
    Non-compliance tolerance 5% of in-scope outputs, or 1 output, whichever is higher Same 5%/1-output tolerance carried forward

    Outputs still under a compliant embargo at the REF submission deadline are treated as policy-compliant, provided the embargo length itself sits within the applicable cap.

    What licence does REF 2029 require?

    The funding bodies do not mandate a single licence but state a strong preference for CC BY “or other licence formats meeting this standard of openness.” CC BY-NC, CC BY-ND and CC BY-NC-ND remain acceptable for outputs published between 1 January 2026 and 31 December 2028, provided the AAM deposit route otherwise meets deposit, discovery and access requirements.

    That flexibility is time-limited. Under the same guidance, from 1 January 2029, all future in-scope outputs must fully meet the open-licensing standard (effectively CC BY or equivalent), regardless of whether the output is published gold/diamond or shared via green deposit — subject only to the standard policy exceptions. Research offices planning publication strategy now should treat 2026–2028 as a transition window, not a permanent settlement.

    Why are monographs excluded from REF 2029 open access rules?

    REF 2029 carries no open access requirement for long-form outputs — monographs, book chapters and scholarly editions — because the funding bodies judged the monograph publishing ecosystem (specialist university presses, third-party image rights, translation licensing) not yet ready for a mandatory equivalent to the journal-article regime. The REF 2029 Open Access Policy and Consultation summary, published 11 December 2024, confirms that any long-form open access mandate is deferred to the assessment cycle after REF 2029, with implementation “no earlier than 1 January 2029.” Datasets, code and artistic research outputs are similarly welcomed but not mandated.

    Frequently asked questions

    What outputs are eligible for REF 2029 open access requirements?

    Only journal articles and conference contributions with an ISSN, published between 1 January 2021 and 31 December 2028, are in scope. Preprints without an ISSN, monographs, book chapters, datasets, code and artistic outputs fall outside the policy, though open sharing of the latter is encouraged rather than mandatory.

    What are the key changes for REF 2029 open access policy?

    The three headline changes from REF 2021 are a later deposit trigger (publication, not acceptance), shorter embargo caps (6/12 months instead of 12/24), and a stated preference for CC BY licensing during 2026–2028, tightening to a full open-licence requirement from 2029 onward.

    What is an open access policy in the REF context?

    An open access policy in this context is a funder-mandated condition of eligibility: outputs must be deposited, discoverable and free to read and download for anyone with internet access before they can count in a unit’s REF submission, independent of any journal paywall.

    How can institutions check whether an output meets REF open access requirements?

    Institutions cross-reference the deposit date, publication date, embargo length and licence recorded in their repository or current research information system (CRIS) against the applicable policy window, then apply the REF 2029 audit’s risk-based sampling approach — modelled on REF 2021, where ten institutions faced second-stage audit and four required data adjustments.

    What this means for research administrators

    Repository workflows built around REF 2021’s acceptance-date trigger need re-sequencing for the publication-date trigger from 1 January 2026, and embargo-tracking systems must be updated to the new 6/12-month caps to avoid outputs drifting into the 5%-tolerance band unintentionally. Because the REF 2021 audit found four institutions required data adjustments out of ten sampled at the second stage, and one required an output removed after substantive sampling, administrators should expect comparable scrutiny under REF 2029’s “broadly mirrored” risk-based audit approach, as set out in the REF 2029 guidance hub.

    The policy aligns deliberately with UKRI’s Open Access Policy for journal articles and conference proceedings, in force since 1 April 2022, and with the wider push for openness associated with cOAlition S — meaning institutions already compliant with UKRI grant conditions have much of the REF 2029 groundwork in place. For research administrators tracking related contributor and provenance standards, see CASRAI’s research administration resources and the open research dictionary for definitions of terms such as author accepted manuscript and green/gold open access.

    Outlook: the run-up to 2029

    Guidance for REF 2029 is not yet fully finalised: the guidance hub itself notes that modules “will be formally finalised in 2026” and may see small revisions before then, with the last substantive change to Section 5 recorded on 13 June 2025. Institutions should treat the current 6/12-month embargo caps and CC BY-NC-ND licence floor as the operative rules for 2026–2028 outputs while watching for the 2029 tightening to full open-licensing standards and the separate monograph mandate expected for the cycle beyond REF 2029.

  • Do I Have an ORCID iD? How to Merge Duplicates

    Do I have an ORCID iD? Search your name in the ORCID public registry or try the password-reset page with every professional and personal email address you have used. If a record was already created for you — often automatically, through a university, funder, or journal submission system — you already have one, and sometimes two. A duplicate must be merged or deactivated; it should never be left active alongside your main record.

    An ORCID iD is a free, persistent 16-digit identifier — formatted as four blocks of four characters and validated with an ISO 7064 (MOD 11-2) check digit — that uniquely distinguishes a researcher from every other person with the same or a similar name. Because the identifier is designed to be permanent, ORCID does not delete duplicate records outright; it deprecates them, and this article covers exactly how that consolidation process works, distinct from closing an account you no longer want at all.

    How do I check if I already have an ORCID iD?

    ORCID gives three reliable ways to confirm whether a record already exists in your name. Each targets a different reason people lose track of an iD: forgotten registration, a changed email address, or an institution having created one on your behalf.

    • Search the public registry. Type your name into the ORCID search bar. If no plausible match appears, you have not yet registered.
    • Recover by email. Enter every current and former professional or personal email address into the ORCID password-reset page. If a matching account exists, ORCID emails you the 16-digit iD.
    • Attempt to register. ORCID’s own guidance confirms that the sign-up form will flag a likely pre-existing profile with your name before letting you create a new one, according to ORCID’s help article “I am not sure if I already have an ORCID ID.”

    If none of these methods surfaces a record, you do not yet have an ORCID iD and can register directly. If more than one method turns up a plausible match, treat that as the trigger to work through the duplicate-resolution process below rather than creating a third record.

    Why do researchers end up with duplicate ORCID iDs?

    Duplicate ORCID records are a routine, well-documented problem, not a rare edge case. They typically arise because ORCID registration is embedded in several independent systems that do not always check for an existing iD first.

    • Registering separately through a university onboarding portal, a funder’s grant-application system, and a journal’s manuscript-submission form, each of which can silently spin up a new iD if the researcher does not sign in with an existing one.
    • Using a different email address at each career stage — student, postdoc, staff — without linking them to a single account.
    • Name variants (middle names, hyphenation, transliteration) that make it harder to recognise an existing record during sign-up.

    None of these causes are dangerous alone — the risk is that citations, grants, and peer-review credit end up scattered across two identifiers instead of one.

    Should you merge or deactivate a duplicate record?

    These are two different actions with different outcomes, and ORCID’s support documentation is explicit that they are not interchangeable. Merging a duplicate is the correct fix; deactivating an account is for closing ORCID access altogether.

    ORCID’s own account-closure guidance states plainly: “Accidentally registered multiple ORCID iDs? Do not deactivate your account — use the duplicate record removal process to merge the accounts instead,” per ORCID’s support article “Deactivating an ORCID account.”

    Scenario Correct action What happens to the data Reversible?
    You accidentally created a second record and can log into both Remove a duplicate record (self-service merge) Duplicate’s data is deleted; only its email address transfers to the record you keep No — once removed, the duplicate cannot be reinstated
    You want to close your ORCID account entirely and stop using ORCID Deactivate your ORCID account All personal information is deleted; the iD itself is retained (masked) so it can never be reassigned Yes — a deactivated account can be reactivated at any time
    You have lost access to the duplicate record and cannot sign in to either recover or remove it Contact ORCID support directly with both iDs ORCID staff verify ownership and action the merge or deprecation on your behalf No, once ORCID staff complete the merge

    How to remove a duplicate ORCID iD, step by step

    The self-service duplicate-removal process takes only a few minutes if you can sign in to both records. ORCID’s help article “I have more than one ORCID iD” sets out the following steps:

    1. Sign in to the ORCID record you want to keep as your primary iD, and go to Account Settings.
    2. Scroll to “Account actions” and select Remove a duplicate record.
    3. Enter the sign-in details (email address or iD, plus password) for the record you want to remove.
    4. Confirm the removal. The duplicate iD is then deprecated, not deleted outright — it becomes a redirect pointing to your primary record, both in the ORCID interface and via the ORCID API.

    If you cannot remember the duplicate’s login details, use the password-reset page first, or contact ORCID support. Only the duplicate’s email address carries over automatically — works, affiliations, and peer-review records on the deprecated iD are not copied across, so check it for anything worth re-adding manually before you remove it.

    What happens to your record after a merge?

    Because ORCID iDs are built to be permanent, a deprecated iD does not simply vanish. It continues to resolve — for example, a deprecated iD such as 0000-0001-6151-2200 displays as deprecated and points visitors to the surviving record, exactly as documented in ORCID’s own duplicate-removal guidance. This matters for anyone tracking citation trails: a paper or grant that cites the old iD will still lead back to the correct, consolidated profile.

    ORCID also relies on the wider community, not only account holders, to flag duplicates it has not caught. Where a publisher, funder, or institution reports a suspected duplicate, ORCID follows its published dispute procedures to investigate and, where warranted, action a merge itself. That support-mediated route is the one to use when access — not awareness — is the blocker.

    This distinction matters for institutions too. Many funders, including UK Research and Innovation (UKRI), require an ORCID iD to submit a grant application, and journals following ICMJE recommendations increasingly request one from corresponding authors. A researcher with an unresolved duplicate risks having grant history or publication credit split across two identifiers precisely when a funder or publisher checks it.

    Common questions about duplicate ORCID iDs

    How do I check if I have an ORCID iD?

    Search your name on ORCID’s public registry, or enter your current and former email addresses on the password-reset page — a matching account will trigger a recovery email containing your 16-digit iD. Attempting to register also flags an existing profile before a new one is created.

    What if I don’t have an ORCID iD?

    If no search or recovery method returns a match, you can register directly on the ORCID registration page in under a minute, free of charge. Registering early avoids the more common problem: multiple systems each creating a separate iD later because none could find an existing one.

    Is ORCID iD compulsory?

    ORCID iDs are not universally mandatory, but they are increasingly required in practice. Many funders and publishers now require an ORCID iD for corresponding authors or grant applicants, so in those specific workflows it is effectively compulsory even where no single global rule enforces it.

    Should I put my ORCID on my CV?

    Yes — listing your ORCID iD on a CV, grant application, or publication profile helps funders, publishers, and collaborators disambiguate you from researchers with similar names. It also gives reviewers a single, authoritative link to your full, consolidated research and authorship record.

    Duplicate ORCID records will keep recurring as long as registration is distributed across universities, funders, and journals rather than centralised at first sign-up. Checking for an existing iD before registering, and merging — rather than abandoning — any duplicate you discover, keeps your research history intact across research administration systems and authorship records, correctly attributed for the rest of your career.

  • How Do I Find an Author’s ORCID iD? Editor Guide

    To find an author’s ORCID iD as an editor, first check the manuscript submission record for an authenticated iD, then search the public ORCID registry by name, email, or affiliation, and cross-check any match against the author’s known publication list before adding it to your records. An ORCID iD is a 16-digit, ISO 27729-compatible persistent identifier that uniquely distinguishes one researcher from every other researcher with a similar name.

    For editorial staff, finding the right ORCID iD matters more than finding an ORCID iD. A mismatched or unverified iD attached to a published article is difficult to correct after indexing in Crossref and abstracting databases. This guide sets out a practical verification workflow for editors and publishers checking author identity during submission and peer review.

    What is an ORCID iD and why does it matter for editorial verification?

    An ORCID iD is a free, persistent digital identifier issued by ORCID, Inc. that links a researcher to their outputs — manuscripts, grants, datasets, and peer reviews — independently of name spelling, institutional affiliation, or career moves. ORCID launched the registry in October 2012 specifically to solve the name-disambiguation problem in scholarly publishing: common surnames, transliteration variants, and married-name changes routinely misattribute work between researchers.

    For editorial teams, an ORCID iD is not just a courtesy field on a submission form. It is the identifier that Crossref, DataCite, and most manuscript-tracking systems use to link a person to their DOI-bearing outputs — which is why getting the right iD is an editorial integrity issue, not an administrative one.

    How do you search the ORCID registry for an author by name, email, or DOI?

    The most reliable route is never a manual search: it is an authenticated OAuth connection, where the author logs into ORCID from your submission system and grants permission to share their iD. Most major platforms (ScholarOne, Editorial Manager, OJS) support this ORCID Connect integration and remove transcription error entirely, since the author supplies their own verified iD.

    When authentication is not available — for a co-author who has not logged in — search the public registry directly:

    • By name: Enter the full given name and family name at orcid.org, adding a middle name or variant if the surname is common.
    • By affiliation: Combine the name with a current or former institution — the record’s “employment” section is searchable metadata.
    • By email: If the author has set an email as findable, a direct search returns an exact match; many keep this private by default, so no result does not mean no iD.
    • By existing publication (DOI): Check the article’s Crossref metadata record — publishers increasingly embed contributor ORCID iDs against each DOI, letting you confirm identity via prior work.
    Verification method Reliability Best used when Limitation
    Authenticated OAuth (ORCID Connect) Highest Submission system supports iD sign-in Requires author to actively authenticate
    Registry name search Medium Author has not authenticated but has a distinctive name Common names return multiple candidates
    Registry search by affiliation Medium-high Name is common; institution is known Affiliation data may be self-asserted, not verified
    Crossref/publisher metadata by DOI High Author has a prior published, DOI-bearing work Only works if a previous publisher embedded the iD
    Google Scholar / institutional profile Low-medium Cross-checking a candidate match, not sourcing one Never a primary source — profiles are unverified and editable

    What if the author has no ORCID iD, or you find multiple candidate matches?

    If a registry search returns no result, do not assume the author lacks an iD — their record may be set to private. The correct next step is to ask the author to register (this takes under a minute) or authenticate via your submission system, rather than proceeding without one.

    If a search returns several candidates with a similar name, treat every one as unconfirmed. Compare each candidate’s listed employment, works, and subject area against what you already know from the cover letter, affiliation line, and reference list. Where doubt remains, contact the author and ask them to supply and authenticate their own iD — never select the “closest-looking” record on a common surname alone.

    • Never publish an ORCID iD you have not independently confirmed belongs to the submitting author.
    • Treat self-reported iDs typed into a form with the same scepticism as an unverified email address — request authentication where the workflow allows it.
    • Log which verification method was used (authenticated, registry-matched, or author-supplied) for your own audit trail.

    How do you verify that an ORCID iD is genuine and correctly formatted?

    Every valid ORCID iD follows a strict, checkable format: sixteen digits in four groups of four (for example, 0000-0002-1825-0097), where the final character is a checksum digit calculated using the ISO/IEC 7064:2003 MOD 11-2 algorithm. A mistyped or fabricated iD can often be caught immediately — if the checksum fails against the preceding fifteen digits, the iD is malformed and should be queried before use.

    ORCID also distinguishes self-asserted data (anything a researcher typed in themselves) from source-verified data (affiliations, works, and funding pushed directly from a trusted employer, funder, or publisher via the ORCID API), marked with a visual trust indicator. When disambiguating a candidate match, weight source-verified entries far more heavily than self-asserted ones, since the latter can be entered by anyone with account access.

    How should ORCID verification fit into submission and peer-review workflows?

    The Committee on Publication Ethics (COPE) treats accurate author identification as a core plank of publication integrity, since misattributed authorship undermines both credit and accountability. Building ORCID verification into the submission stage — rather than retrofitting it at proof stage — is the most efficient intervention point, because it is the only stage where the author is present to authenticate their own iD.

    Funder policy adds independent pressure: UKRI has required ORCID iDs on many grant and fellowship applications since 2017, and cOAlition S signatory funders increasingly expect grant-linked outputs to carry a verified iD through to publication. A journal verifying ORCID iDs at submission is therefore also supporting the author’s compliance obligations to their funder.

    Many submission systems now collect ORCID iDs at the same step as CRediT contributor role declarations, since both serve the same purpose: attributing specific contributions to a specific, disambiguated person. Combining the two into a single identity-and-contribution step is the practical shape a defensible author identity verification policy takes.

    Answer-first Q&A: common author-ORCID questions

    Can I find someone’s ORCID iD?

    Yes. Anyone can search the public ORCID registry by name, and the record’s basic details — the iD itself, plus any information the researcher has marked public — are visible without an account. If the person has not registered, or has restricted their profile to private, a name search may return no usable result even though they exist in the registry.

    Is an ORCID iD public?

    The iD number itself is always public once created, by design, so it can function as a reliable identifier across publishers, funders, and institutions. However, the surrounding record — works, employment, education, funding — is controlled by the researcher through granular, per-item visibility settings, so a public iD does not guarantee a fully populated public profile.

    How do I check whether an author already has an ORCID iD?

    Search the author’s full name at orcid.org and scan for a record whose listed employment or works match what you already know about them. Because duplicate registrations are common with frequent name-changers or common surnames, treat a single unconfirmed hit as a lead, not a confirmation, and verify against the author’s own submission or a source-verified affiliation before relying on it.

    What this means for editorial teams going forward

    As more publishers embed ORCID iDs into DOI metadata via Crossref, the “search by DOI” route above will only get more reliable — every properly tagged prior publication becomes a verification point for the next. Editorial teams that build authentication-first collection into submission systems now, rather than relying on manual registry searches, will spend less time on post-publication correction requests as ORCID coverage across the literature grows.

  • How to Link ORCID to Publications: 2 Methods

    Linking a publication to ORCID means associating your 16-digit ORCID iD with a specific work record — either automatically through a Crossref or DataCite metadata feed authorised when you submit a manuscript, or manually by entering a DOI, PubMed ID, or BibTeX file into the Works section of your ORCID record. Auto-updated works carry a materially stronger trust signal than self-asserted entries, because the claim originates from a third-party registration agency rather than the researcher.

    ORCID is a non-proprietary, persistent digital identifier that distinguishes individual researchers from one another and links them to their publications, datasets, funding, and institutional affiliations. Understanding how to link ORCID to publications correctly — and which method to use for which purpose — determines whether that record reads as verified evidence or as an unaudited self-report.

    What Linking a Publication to ORCID Actually Means

    An ORCID “Work” is any research output — a journal article, dataset, preprint, conference paper, or software release — attached to a researcher’s ORCID record. Each record can hold up to 10,000 works, a ceiling ORCID imposes to protect Registry performance, according to ORCID’s own support documentation.

    Every work carries a source: the entity that added it. That source field is the whole point. A work added by the researcher themselves is labelled with the researcher’s own name as source. A work added via an authorised integration — a publisher, Crossref, DataCite, or a research information system — is labelled with that organisation’s name as source. This single metadata field is what separates a verified claim from a self-report.

    How Auto-Update Works via Crossref and DataCite

    Auto-update is a “push” mechanism, not something a researcher does manually after the fact. It runs on trust relationships a researcher grants once and that then apply to every future publication. Publishers who register content with Crossref (for journal articles) or DataCite (for datasets and other outputs) can include an author’s ORCID iD in the deposited metadata.

    • Set-up: the researcher supplies their ORCID iD during manuscript or dataset submission and authorises the publisher as a “trusted organisation” on their ORCID record.
    • Trigger: when the work is registered and its DOI is minted, Crossref or DataCite passes the metadata, including the ORCID iD, back to the ORCID Registry.
    • Result: the work appears on the researcher’s ORCID record automatically, with the publisher or registration agency listed as the source — no manual entry required, then or ever again.

    ORCID’s own guidance favours this route: “Allowing trusted organizations to add information to your record ensures the data connected with your ORCID iD is authoritative and trustworthy,” per ORCID Support’s “Add works to your ORCID record” article. Auto-updated entries are visually flagged in the ORCID interface with a distinct icon next to the work.

    How Manual Import Works via DOI, PubMed ID, and BibTeX

    Manual import is a “pull” process the researcher initiates, typically to backfill a body of existing work that predates any auto-update authorisation. ORCID Support lists four routes, in addition to auto-update, from the Works section’s +Add menu:

    1. Import from other services — searching connected databases such as Web of Science, Scopus, or Crossref Metadata Search and bulk-importing matched records.
    2. Add work with a DOI — pasting a Digital Object Identifier, which pulls the full citation from the DOI registration agency.
    3. Add work with a PubMed ID — the same principle, using PMID for biomedical literature indexed in PubMed.
    4. Import a BibTeX file — exporting a library from Google Scholar, EndNote, or Mendeley to a .bib file and uploading it directly.
    5. Add work manually — typing citation details by hand for works with no identifier at all.

    Each route is initiated by the researcher and populates the record once, rather than on an ongoing basis. Identifier-based and BibTeX import draw on structured external metadata, so they are more reliable than fully manual entry, but the source field still reads as the researcher, not a registration agency, unless the import tool explicitly attributes the deposit.

    Auto-Update vs Manual Import: Which Carries More Trust?

    Both routes populate the same Works section, but they are not equivalent as provenance signals. The distinction that matters to institutions, funders, and research-integrity reviewers is who is asserting the claim, not how the citation data was formatted.

    Factor Auto-Update (Crossref/DataCite) Manual Import (DOI/BibTeX/Manual)
    Who initiates it Publisher, at registration/DOI-minting time Researcher, whenever they choose
    Recorded source Publisher or registration agency The researcher themselves
    Coverage Future works only, from authorisation onward Past and present works, added retrospectively
    Ongoing effort None after initial authorisation Repeated per work or per batch
    Trust signal Third-party verified Self-asserted

    An auto-updated work is corroborated by an external registration agency’s records — the kind of independently verifiable evidence that research assessment exercises and grant compliance checks look for. A manually entered work, even one anchored to a real DOI, still relies on the researcher’s own account linking “this person” to “this ORCID iD.” Institutions running authorship audits should treat the two categories differently, not as interchangeable Works-tab entries.

    The practical recommendation, and the one ORCID itself gives, is to use both: manual import to backfill the existing publication history, and auto-update authorisation with every future submission so new works never need re-entering.

    Frequently Asked Questions

    Can I use my ORCID iD for publications?

    Yes. An ORCID iD can be attached to any publication at submission, and most scholarly publishers now capture it as standard metadata. Once attached, that iD becomes the persistent link between the researcher and the work, regardless of name changes, institutional moves, or common-name ambiguity.

    How do I add an ORCID iD to a manuscript?

    Most journal submission systems prompt for an ORCID iD during author registration, then authenticate it via ORCID’s own sign-in flow. Once authorised, the publisher can include that iD in the metadata deposited with Crossref or DataCite when the article or dataset is registered and assigned a DOI.

    How do I link ORCID to a publisher such as Elsevier?

    Publisher platforms, including Elsevier’s Editorial Manager, typically show a “Use my ORCID” or “Connect ORCID” button during login or registration. Clicking it opens an ORCID authentication window; after signing in and authorising access, the publisher can read and, where permitted, write publication data to the record.

    What This Means for Institutions, Publishers, and Funders

    For research administrators, the auto-update versus manual-import distinction is not a technical footnote — it is a compliance and evidence question. UKRI’s Funding Service requires named investigators to supply an ORCID iD as part of grant applications, and institutions increasingly rely on ORCID’s Works data to populate REF-style outputs lists and funder reports. Data drawn from auto-updated, publisher-sourced Works entries is defensible evidence in that context; data drawn from unaudited manual entries is not, without further checking.

    This “who asserts the claim” logic underpins contributor-level attribution more broadly. CASRAI originated the CRediT contributor role taxonomy in 2014, and the standard is now stewarded by NISO as ANSI/NISO Z39.104-2022. CRediT statements and ORCID auto-updates share one design principle: attribution is more trustworthy when a party other than the researcher is on record as having made the claim. Institutions building publication-verification workflows, for CRediT contributor statements or ORCID Works alike, should apply the same provenance test.

    Publishers that deposit ORCID iDs with Crossref or DataCite at DOI registration are, in effect, running the infrastructure that makes auto-update possible at scale. Where that deposit step is skipped, researchers are pushed back onto manual import by default, regardless of preference.

    Conclusion: Building a Verifiable Publication Record

    Getting works onto an ORCID record is straightforward mechanically: import from a connected database, enter a DOI or PMID, upload a BibTeX file, or authorise auto-update at submission. The strategic choice is which of these to rely on for which purpose. Manual import is the right tool for backfilling a career’s worth of existing publications in one pass. Auto-update via Crossref and DataCite is the right tool for every submission from today onward, because it produces a record institutions, funders, and integrity reviewers can treat as third-party verified rather than self-reported. As research assessment increasingly leans on machine-readable provenance rather than researcher-supplied CVs, that distinction is likely to matter more, not less.

  • ORCID Sandbox: A Developer’s Guide to Testing

    The ORCID sandbox is a free, fully functional copy of the ORCID Registry — at sandbox.orcid.org — that lets developers register test accounts, request API credentials, and run real Public and Member API calls against dummy data before touching production. No ORCID membership is required to test the Member API in the sandbox, and nothing you do there can affect a real researcher’s ORCID record.

    ORCID is a non-profit registry that assigns researchers a free, persistent 16-digit identifier (an ORCID iD) and connects it to their affiliations, works, and funding through a public API and a membership-tier Member API. Building an integration means testing the OAuth handshake and both API tiers in the sandbox before requesting production credentials.

    What is the ORCID sandbox and how does it differ from production?

    The sandbox is a mirror of the production ORCID Registry running on isolated test infrastructure. It behaves the same way as the live registry, with a handful of deliberate exceptions built in for safety.

    • Sandbox accounts only send verification and notification emails to @mailinator.com addresses, so registration mail never leaks to real inboxes.
    • Sandbox data is not backed up and can be wiped without notice — never store anything you need to keep there.
    • Anyone can request sandbox Member API credentials, even without an ORCID membership; production Member API access requires a paid membership tier.
    • Base URLs differ from production, which is the detail most tutorials skip:
    Component Sandbox Production
    Registry / sign-in sandbox.orcid.org orcid.org
    Public API base (v3.0) pub.sandbox.orcid.org/v3.0 pub.orcid.org/v3.0
    Member API base (v3.0) api.sandbox.orcid.org/v3.0 api.orcid.org/v3.0
    OAuth authorize endpoint sandbox.orcid.org/oauth/authorize orcid.org/oauth/authorize
    OAuth token endpoint sandbox.orcid.org/oauth/token orcid.org/oauth/token

    Under ORCID’s published integration guide, every client credential, redirect URI, and access token issued in the sandbox is scoped to sandbox hostnames only — a sandbox client ID will not authenticate against production, and vice versa. This is the single most common cause of “invalid client” errors when developers copy sandbox code straight into a production deployment.

    Public API vs Member API: which scope does your integration need?

    ORCID publishes two distinct APIs, and choosing the wrong one wastes weeks of sandbox testing. The Public API is free for non-commercial use and gives read-only access to publicly visible record data — no ORCID membership required. The Member API requires production membership (though not in the sandbox) and adds write access plus read access to “trusted” limited-access data that a researcher has authorised your organisation to see.

    Capability Public API Member API
    Read public record data Yes Yes
    Read trusted/limited-access data No Yes, with researcher permission
    Write or update a record No Yes, with researcher permission
    Membership required in production No Yes
    Membership required in sandbox No No — open to anyone testing
    Typical use case “Sign in with ORCID”, search, display Populate affiliations, works, funding on a record

    Research information systems, manuscript submission platforms, and repository software (for example, systems built on OJS) most often need Member API scopes because they write affiliation or works data back to a researcher’s record. Discovery tools and simple “sign in with ORCID” buttons typically only need the Public API.

    How do you register a sandbox client and complete the OAuth handshake?

    Every ORCID integration authenticates through OAuth 2.0, and the sandbox forces you to exercise the full handshake before production ever sees a request. The sequence is the same for Public and Member API integrations, only the scopes and base URLs change.

    1. Create a sandbox account. Register at sandbox.orcid.org/register using a made-up @mailinator.com address so you can retrieve the verification email from the public Mailinator inbox.
    2. Register a client application. From the account’s Developer Tools section (or via ORCID’s sandbox Member API request form), obtain a client ID and client secret plus a registered redirect URI.
    3. Send the user to the authorize endpoint. Redirect to the sandbox authorize URL with response_type=code, your client_id, the requested scope, and your redirect_uri.
    4. Capture the authorization code. After the researcher grants permission, ORCID redirects back to your registered URI with a short-lived authorization code.
    5. Exchange the code for a token. POST the code, client ID, and client secret to the sandbox token endpoint to receive an access token bound to that researcher’s ORCID iD.
    6. Call the API. Use the access token as a Bearer credential against the sandbox Public or Member API base URL to read or write record data.

    Because sandbox credentials only work against sandbox hostnames, this whole sequence must be repeated — with new, separately issued production client credentials — once testing is complete. ORCID’s own guidance recommends reviewing its integration checklist, and for Member API integrations, demonstrating the working sandbox flow to the ORCID team, before requesting production access.

    What goes wrong when moving from sandbox to production?

    Most production failures trace back to configuration, not code. Watch for these before cutover:

    • Hard-coded sandbox hostnames. Any string reference to sandbox.orcid.org, pub.sandbox.orcid.org, or api.sandbox.orcid.org left in production config will silently fail authentication.
    • Redirect URI mismatch. The redirect URI used in the OAuth request must exactly match the one registered against that specific client ID — sandbox or production, they are registered separately.
    • Wrong API tier requested. Applying for Member API production access without an active ORCID membership will be rejected; Public API access has no such requirement.
    • Assuming sandbox reliability. ORCID explicitly states the sandbox carries no uptime or data-retention guarantee, so integration tests should not depend on long-lived sandbox test records.

    Institutions building or commissioning a research administration system that writes to ORCID records — a current research information system (CRIS), grants platform, or repository — should budget sandbox testing time separately from production onboarding, since ORCID’s own review step for Member API access is a manual, asynchronous process.

    Sandbox and API questions, answered

    Does ORCID have an API?

    Yes. ORCID offers a Public API for reading publicly visible record data and connecting systems without ORCID membership, and a Member API for member organisations to read trusted data and write affiliations, works, or funding to a record with the researcher’s permission.

    Is ORCID API free?

    The Public API is free for non-commercial use by individuals and organisations under ORCID’s Public API terms of service. The Member API, in production, requires a paid ORCID membership tier — though sandbox Member API testing credentials are free and open to anyone, member or not.

    What is ORCID public API vs member API?

    The Public API allows anyone to read public-access information on ORCID records via machine-to-machine calls. The Member API is restricted to member organisations and additionally supports reading limited-access “trusted” data and writing or updating a researcher’s record with authorisation.

    The ORCID sandbox exists precisely because both API tiers, and the OAuth handshake connecting them, need to be exercised end-to-end — with real credentials and real error responses — before a single production request is made. Treat it as a mandatory rehearsal step, not an optional convenience: budget time for the manual Member API review, hard-code nothing that points at a sandbox hostname, and re-issue every credential fresh for production.