What Makes a Review 'Cochrane Standard'?

"Cochrane standard" gets used fairly loosely in casual conversation, sometimes just meaning "very rigorous," but the phrase actually refers to a specific, well-documented set of methodological and reporting expectations laid out in the Cochrane Handbook for Systematic Reviews of Interventions. Understanding what it specifically requires helps clarify whether that's genuinely the standard your review needs to meet.

Grounded in the Cochrane Handbook

The Cochrane Handbook is a detailed, regularly updated methodological reference covering every stage of an intervention systematic review, from formulating the question through interpreting results. Following Cochrane methodology means your protocol, conduct, and reporting align with this specific reference throughout, not just borrowing a few of its more well-known elements like PRISMA reporting.

PICO framing as the starting point

Cochrane reviews are built around intervention effectiveness questions framed explicitly in PICO terms, historically centered on randomized controlled trial evidence, though the Handbook has expanded over time to address non-randomized evidence and diagnostic test accuracy reviews as well.

RoB 2 and ROBINS-I as the required tools

Cochrane developed and maintains both RoB 2 for randomized trials and ROBINS-I for non-randomized studies, and using these specific tools, matched correctly to study design, is a defining feature of Cochrane methodology rather than an optional choice among equivalent alternatives.

Dual independent screening and extraction as standard, not optional

Cochrane Handbook guidance treats dual independent screening and data extraction, with documented conflict resolution, as expected practice throughout the review, not a nice-to-have add-on for teams with extra capacity.

GRADE for certainty of evidence

Cochrane reviews use GRADE to rate certainty of evidence by outcome, presented in a Summary of Findings table -- a structured, transparent process for communicating how much confidence readers should place in each specific finding, rather than a single blanket quality statement for the whole review.

RevMan as the conventional software

Cochrane reviews are traditionally produced using RevMan, Cochrane's own review management software, which structures the review according to Cochrane's specific formatting conventions and handles meta-analysis computation within the same environment used for the rest of the review.

The Cochrane editorial process

Reviews intended for publication in the Cochrane Database of Systematic Reviews go through Cochrane's own editorial and peer review process, which is structurally different from submitting to an independent academic journal, involving a Cochrane Review Group's editorial oversight specific to the topic area.

Following Cochrane methodology without formal Cochrane publication

A review can follow Cochrane Handbook methodology rigorously -- the same PICO framing, the same risk-of-bias tools, the same GRADE approach -- and still be submitted to an independent academic journal rather than the Cochrane Database itself. This is a completely legitimate approach, and stating explicitly in your methods section that your review "followed Cochrane Handbook methodology" while publishing elsewhere is honest and common practice, provided the underlying methodology genuinely was followed rather than loosely gestured at.

When Cochrane standard is and isn't the right fit

Cochrane methodology is well suited to intervention effectiveness questions with a primarily quantitative evidence base. It is a less natural fit for qualitative evidence synthesis, scoping reviews, or reviews with a strongly mixed-methods purpose, where JBI methodology's broader native support for these review types is generally the better-fitting choice. Choosing between them should be a deliberate decision based on your review's actual purpose and evidence base, not a default assumption that Cochrane methodology is simply the more rigorous option regardless of fit -- both frameworks are genuinely rigorous within their intended scope.

Mixing elements from both frameworks

Some reviews genuinely need to borrow specific elements from each -- Cochrane's RoB 2 for the randomized trials in a review otherwise following broader JBI conventions for a mixed-methods synthesis, for instance. This kind of deliberate, disclosed combination is different from vaguely gesturing at "rigorous methodology" without committing to either framework's specific conventions consistently, and reviewers generally respond well to a clearly justified hybrid approach as long as it's explained explicitly rather than left for the reader to piece together.

Institutional and journal expectations

Some institutions, funders, or target journals have a stated preference or requirement for one framework over the other, and checking this before committing significant time to a specific methodological approach can save real rework later. Where no explicit requirement exists, the decision genuinely should rest on which framework's native strengths best match your review's actual purpose and evidence base, rather than on which one happens to be more familiar to you personally at the outset of the project.

Learning a new framework mid-career

Researchers trained primarily in one framework sometimes hesitate to take on a review requiring the other, worried about a steep learning curve. In practice, both frameworks share enough conceptual common ground -- systematic search, structured appraisal, transparent synthesis -- that a researcher genuinely competent in one can usually learn the specific conventions of the other with focused study and, ideally, an experienced co-reviewer already familiar with the target framework's specific expectations for a first collaborative project. This kind of cross-framework collaboration also tends to produce genuinely stronger methodology than either researcher working entirely alone within their more familiar framework, simply from the added scrutiny a second, differently trained perspective brings. Institutions that regularly conduct both Cochrane and JBI methodology reviews often find that pairing researchers with complementary framework experience becomes a genuine organizational strength over time, rather than a logistical inconvenience to be minimized. Teams that build this kind of cross-framework fluency deliberately, rather than by accident, often find themselves better positioned to take on a wider and more interesting range of review projects than teams committed exclusively to just one methodology. The added flexibility this brings is a genuine professional asset over a longer career, not just a convenience for any single project. It's worth investing in deliberately rather than waiting for it to develop by accident over the course of a longer career. Reading the Cochrane Handbook and the JBI Manual side by side, even briefly, for a topic you already know well is a genuinely efficient way to start building this kind of dual fluency without committing to a full second review project just to learn the differences firsthand.