The Research Excellence Framework has always been shaped by a narrow question: whose name goes on the output. Guidance for the next cycle, REF 2029, is beginning to unsettle that assumption. The UK’s higher education funding bodies, working through Research England and the other national funding councils, have signalled that recognition should extend to staff who “enable or support” research — regardless of their job family, contract type, or professional title. For institutions preparing submissions, this is not a cosmetic adjustment. It is a structural shift in what counts as evidence, and it exposes a gap that many research offices have not yet had to close: how do you consistently record and evidence a contribution that was never captured by authorship alone?
Technicians, research software engineers, data stewards, project managers, and core-facility staff have long done work that underpins REF-returnable outputs without ever appearing as named authors. REF 2029’s broadened framing is an implicit acknowledgement that research is produced by teams, not by bylines. But acknowledging the principle is easier than operationalising it. Institutions now need a consistent, auditable way to describe who did what — and that is precisely the problem a structured contributor-roles vocabulary was built to solve.
What REF 2029 Changes for Contributor Recognition
Previous REF cycles asked institutions to attribute outputs to named individuals meeting narrow eligibility criteria, which tended to privilege senior academic staff and marginalise the contributions of technical, software, and operational personnel. The direction of travel for REF 2029 moves recognition further toward the underlying work of enabling and supporting research — echoing wider sector commitments such as the Technician Commitment and the growing professional recognition of research software engineering as a distinct career track.
This matters for research administrators because REF submissions are evidentiary exercises. Panels expect institutions to substantiate claims about environment, impact, and contribution with documentation, not assertion. If a REF submission is going to credit a research software engineer’s role in producing a dataset, or a technician’s role in developing an experimental method, the institution needs a record of that contribution that is specific, consistent across departments, and defensible under scrutiny — not a retrospective narrative assembled at submission deadline.
The Contributor-Roles Gap: Why Institutions Need a Structured Vocabulary
Most institutional systems were never designed to capture contribution at this level of granularity. Authorship order is a blunt instrument: it conflates seniority, alphabetisation conventions, and actual task ownership, and it says nothing about who wrote software, who curated data, who validated methodology, or who supervised. Free-text acknowledgement sections are inconsistent between departments and impossible to aggregate at institutional scale — which is exactly what a REF submission requires.
A structured contributor-roles taxonomy solves this by decomposing “contribution” into a fixed, comparable set of categories — conceptualisation, methodology, software, validation, formal analysis, investigation, resources, data curation, writing, visualisation, supervision, project administration, and funding acquisition, among others. Applied consistently across a REF return, this kind of vocabulary lets research offices generate exactly the kind of granular, auditable contribution record that broadened REF eligibility now implicitly demands — without inventing a bespoke internal scheme that won’t map to how publishers, funders, or other institutions record the same information.
CRediT as a Ready-Made Framework
Institutions do not need to build this vocabulary from scratch. The Contributor Roles Taxonomy, known as CRediT, already provides exactly this structure and is in active use across scholarly publishing. CASRAI originated the CRediT contributor role taxonomy in 2014. The standard is now stewarded by NISO as ANSI/NISO Z39.104-2022, and it is widely implemented by publishers as part of manuscript submission workflows, meaning a growing share of an institution’s outputs already carry structured CRediT statements at the point of publication.
For REF purposes, this is a genuine efficiency gain rather than an additional administrative burden. Where publishers have already captured CRediT roles at submission, research offices can extract that metadata rather than reconstruct contribution histories from memory or informal records months or years later. Where CRediT statements were not captured — common in software releases, datasets, or non-traditional outputs — the same taxonomy can be applied retrospectively by the research office, in consultation with the individuals involved, to produce a consistent internal record. Because CRediT is externally stewarded and widely recognised rather than a proprietary institutional scheme, it also travels well: a contribution recorded this way is legible to REF panels, publishers, funders, and other institutions alike, without requiring a translation layer.
UKRI Funding Mechanisms and the Same Evidencing Challenge
The REF is not the only place this evidencing problem shows up. UKRI’s own funding routes increasingly ask institutions and applicants to be explicit about who is doing what, and why it matters. A UKRI Future Leaders Fellowship application, for instance, must demonstrate the fellow’s individual contribution within a wider team and host environment — precisely the kind of attribution that a structured contributor vocabulary makes easier to document consistently across a research office’s portfolio of active UKRI grants. UKRI Proof of Concept funding, aimed at translating research toward application, similarly depends on institutions being able to show which named contributors carried out which parts of the underlying research — methodology, data, software, or otherwise — before commercialisation activity began. More broadly, any UKRI fellowship scheme that supports a researcher’s transition into independence relies on host institutions being able to separate the fellow’s own contribution from that of collaborators, supervisors, and support staff.
None of these funding instruments mandate CRediT specifically. But institutions that already maintain structured contributor records for publication purposes are better placed to answer these funder questions quickly and consistently, rather than reconstructing the answer for each application, report, or REF cycle in isolation.
What This Means for Research Administrators
The practical implications for research offices are immediate and largely operational rather than exotic:
- Audit current metadata capture. Determine which outputs already carry CRediT statements from publishers and which do not, particularly software, datasets, and other non-traditional research outputs likely to benefit most from REF 2029’s broadened recognition.
- Extend contribution tracking to non-traditional outputs. Software repositories, data deposits, and core-facility work rarely carry formal author lists; a lightweight internal process for recording contributor roles at the point of creation avoids reconstruction later.
- Align internal recording with ORCID. Linking structured contribution records to ORCID iDs, which are now widely mandated across funders and publishers, reduces duplicate data entry and improves the auditability of REF evidence.
- Brief technical and professional staff early. Research software engineers, technicians, and data stewards should understand that their contributions are now potentially REF-relevant, and that consistent role attribution — not informal acknowledgement — is what will support that recognition.
- Treat this as institution-wide practice, not a submission-deadline scramble. Contribution records built incrementally, output by output, are far more defensible than narratives assembled retrospectively under REF submission pressure.
A Forward-Looking Perspective
REF 2029’s broadened recognition of who contributes to research reflects a wider sector reckoning with how research is actually produced — as team science, increasingly software- and data-dependent, and reliant on professional staff whose work has historically gone uncredited. A structured contributor-roles vocabulary does not resolve every judgement call the funding bodies or REF panels will have to make about eligibility and weighting. But it gives institutions something they have lacked until now: a consistent, externally recognised way of answering the question REF 2029 is now explicitly asking — not just who wrote the paper, but who did the work.
Leave a Reply