Ask any experimental researcher who has tried to reproduce a published result, and you will hear a familiar complaint: the methods section did not contain enough to actually do it. Word limits, the conventions of academic writing, and the assumption that readers share unstated background knowledge all conspire to compress the methods section into a summary rather than a recipe. The real procedure — the exact reagent concentrations, the precise timings, the small adjustments that make the difference between success and failure — lives in a lab’s working notes, not in the published paper. This gap between the reported method and the actual method is one of the quiet drivers of the reproducibility problem. This article looks at how shareable, versioned protocols and structured methods reporting are closing it, drawing on the reproducibility domain of the CASRAI Dictionary.
Why a methods section is rarely enough
The problem is not usually that authors are hiding anything; it is that the published methods section is the wrong vehicle for a reproducible procedure. A narrative paragraph cannot easily convey a step-by-step sequence with branch points, critical timings, equipment settings and troubleshooting notes. It cannot be updated when the protocol is refined. And it cannot be cited independently of the paper that contains it, so a method developed once and reused across many studies has no stable identity of its own. The result is that the same procedure is re-described, slightly differently, in paper after paper, with the operative details lost each time. What is needed is a way to capture the full procedure as a first-class, shareable, improvable object.
Shareable, versioned protocols
This is the role that protocol-sharing platforms such as protocols.io have come to play. The idea is to treat a protocol as a structured document in its own right: a detailed, step-by-step description of a procedure that can be written collaboratively, refined over time, assigned a persistent identifier so it can be cited, and shared either openly or within a group. Two properties make this approach powerful. The first is granularity: a protocol can record the actual steps, in order, with the specifics a methods paragraph omits — concentrations, durations, settings, materials. The second is versioning: methods evolve, and a versioned protocol captures that evolution, so a paper can cite the exact version of a procedure that produced its results while the protocol itself continues to improve. A persistently identified, versioned protocol is something later work can point to precisely, rather than re-paraphrasing.
The benefits of treating protocols as outputs
Treating a protocol as a citable output rather than a buried paragraph brings several advantages:
- Reproducibility. Another researcher can follow the actual steps rather than reconstructing them from a summary, which removes a major source of failed replication.
- Precise citation. Because a protocol has a persistent identifier and versions, a paper can cite exactly the procedure it used, and a widely reused protocol accumulates a traceable history of use.
- Credit for methods work. Developing and optimising a robust protocol is real intellectual labour. Making it a citable object means that work can be recognised and cited in its own right.
- Cumulative improvement. A shared protocol can be refined by its authors and adapted by others openly, so the community’s collective knowledge of how to do a procedure improves rather than being repeatedly reinvented.
Structured methods reporting in the paper
Shareable protocols solve part of the problem; the other part is how methods are reported within the paper itself. Here, structured reporting formats have emerged to impose consistency where free narrative left gaps. STAR Methods — Structured, Transparent, Accessible Reporting — is one well-known example: it organises a paper’s methods into a consistent structure, including a key-resources table that lists the reagents, materials, software and other resources used, each identified as precisely as possible. The value of such a format is that it forces the reporting of details that a free-form section can quietly omit, and it makes those details findable in a predictable place. Structured reporting and shareable protocols are complementary: the structured methods section tells you what resources and steps were involved and links out to the detailed protocol that tells you exactly how.
Protocols as research outputs
The thread running through all of this is that a protocol is a research output, not merely a description of one. It can be authored, versioned, identified, cited, reused and credited — the same lifecycle as a dataset or a piece of software. Recognising protocols this way fits within the broader expansion of what counts as a scholarly output, the subject of our research outputs domain. When the methods that underpin results are themselves durable, citable objects, the research record becomes both more reproducible and more honest about where its intellectual effort actually went.
Crediting and standardising methods work
Because developing a protocol is genuine contribution, it belongs in the structured account of who did what. The CRediT taxonomy — whose full set of roles is described in our overview of the CRediT roles — captures this through the Methodology role, which recognises the design and development of the methods a study relies on, and Investigation for carrying out the procedures. For a method, a resource or a contribution to be described the same way in a protocol, a structured methods section and an institutional record, the underlying terms must be consistent. That consistency is what the CASRAI Dictionary provides: a shared vocabulary so that reproducible reporting rests on definitions that mean the same thing wherever a method is shared, cited or credited.
Leave a Reply