Free scoping read. A written assessment of your manuscript in two business days, at no cost.

Start one
Contents

Academy · Research Data, Analytics & AI · Cochrane RevMan Framework

Cochrane RevMan: The Methodological Framework Underlying Systematic Review and Meta-Analysis

RevMan is the software that Cochrane requires its review authors to use, and it enforces, rather than merely supports, the structured workflow specified in the Cochrane Handbook for proceeding from a search strategy to a pooled effect estimate.

Pubrica AcademyWritten by a systematic review methodologist Reviewed byan evidence synthesis reviewer Published10 October 2026 Last checked10 October 2026 Reading time8 minutes Sources12 peer-reviewed

Review Manager (RevMan) is Cochrane’s own software for preparing and maintaining systematic reviews, and Cochrane presents it not as one option among several but as the tool it describes as essential for authors working through its process from protocol to completed review1. RevMan functions as a framework rather than a generic statistics package because its structure mirrors the sequence of steps set out in the Cochrane Handbook for Systematic Reviews of Interventions: defining the review question and eligibility criteria, extracting data against a pre-specified plan, assessing risk of bias, and only then conducting the meta-analysis. The software thereby enforces a methodological order and prevents users from proceeding directly to pooling. This is of practical importance because conducting a preliminary pooled analysis before the preceding steps are complete is a common temptation, particularly under time pressure, and a review produced in this way is more difficult to defend, since reviewers and readers familiar with Cochrane methodology will expect evidence that scope, eligibility, extraction and bias assessment were settled before the data were combined, not reconstructed around a result already seen. For the same reason, Cochrane editorial groups typically require a registered or editor-approved protocol before a review team begins full-scale data extraction in RevMan, which adds an external checkpoint to the software’s internal sequencing rather than relying on the interface alone to enforce good practice.

Learning objectives

  • Why the structure of RevMan follows the review stages of the Cochrane Handbook rather than functioning as a standalone statistics tool
  • What a PICO framework is and why RevMan requires it before any data extraction takes place
  • How risk-of-bias assessment directly informs the interpretation of a meta-analysis, rather than merely being reported alongside it

Common misconceptions

  • “Meta-analysis software is interchangeable, since the math behind pooling effect sizes is the same everywhere.” The Cochrane Handbook describes risk-of-bias assessment, data extraction against a pre-specified plan and the choice of effect measure as integral, sequential steps that shape the interpretation of a pooled estimate, and the RevMan workflow is structured to enforce that order rather than to treat meta-analysis as a self-contained statistical calculation performed on whatever data have been extracted.

RevMan as a structured workflow rather than a standalone calculator

RevMan is designed to guide a review team through a defined sequence: defining the scope and question, pre-specifying eligibility criteria, extracting data in a structured format, assessing the risk of bias in each included study, and then conducting and displaying the meta-analysis, typically as a forest plot1. This sequence is not an arbitrary design choice; it follows the structure of the Cochrane Handbook’s chapters, which separately address determining the scope of a review and the question it will address, searching for and selecting studies, and analyzing data and undertaking meta-analyses as distinct, cumulative methodological stages234. A review team that conducts the meta-analysis only after every other step has been completed and fixed, rather than treating it as a calculation that can be performed on whatever data have been assembled, follows the same logic that the RevMan interface enforces through the order of its screens. Cochrane editorial groups reinforce this by typically requiring a registered or editor-approved protocol before a review team begins full-scale data extraction, adding an external checkpoint to the software’s internal sequencing rather than relying on the interface alone to enforce good practice. This layered approach, combining software structure with editorial approval, reflects a principle that applies well beyond Cochrane reviews: a tool can make a rigorous methodological sequence substantially easier to follow, but independent verification by someone outside the review team is still required to confirm that the sequence was in fact followed as intended. The same reasoning underlies the requirement for independent risk-of-bias assessment by at least two reviewers rather than reliance on the judgment of a single person, however well the surrounding software structures that work. A review that can demonstrate both safeguards operating together, a structured tool used correctly and an independent editorial check confirming its use, is in a materially stronger position to defend its conclusions than one relying on either safeguard alone.

Precedence of PICO and pre-specified extraction over pooling

RevMan requires authors to define the Population, Intervention, Comparator and Outcome (the PICO framework) before data extraction begins, because this specification determines which studies are eligible for inclusion and which data must be extracted from each1. The Cochrane Handbook chapter on determining the scope and question of a review treats this specification as foundational because a loosely defined question leaves every subsequent decision (which studies to include, which outcomes to extract, which comparisons to report) open to being made post hoc, in a manner that could be influenced by which results appear most favorable2. The RevMan data-extraction forms follow the same logic, being structured to capture exactly the fields that a pre-specified PICO and analysis plan identified as necessary; this also makes any outcome or comparison introduced without acknowledgement, and absent from the original plan, easier to detect when the completed review is later checked against its protocol. Fixing these specifications before the full body of eligible studies is known is one of the principal reasons why systematic reviews are expected to follow a pre-registered or pre-specified protocol rather than being written retrospectively around whatever data proved to be available.

Influence of risk of bias on interpretation

A distinguishing feature of the Cochrane approach, around which the RevMan workflow is built, is that risk-of-bias assessment is not a separate quality check performed alongside the meta-analysis; it is intended to inform the interpretation of the pooled result directly. The current standard tool for this purpose, RoB 2, assesses randomized trials across defined domains (bias arising from the randomization process, deviations from intended interventions, missing outcome data, measurement of the outcome, and selection of the reported result) and produces an overall judgment that is intended to be incorporated into the strength of the review’s conclusions5. The Handbook chapter on completing summary-of-findings tables and grading the certainty of evidence makes this link explicit, describing risk of bias in the contributing studies as one of several factors, alongside inconsistency, indirectness, imprecision and publication bias, that lowers or raises the overall confidence a reader should place in a pooled estimate6. The structure of RevMan reflects this by keeping the risk-of-bias assessment attached to each included study throughout, so that it remains visible alongside the forest plot rather than being reported only in a separate table detached from the numerical result.

Selection of an effect measure before results are examined

RevMan requires a review team to specify the effect measure (a risk ratio, odds ratio, mean difference or standardized mean difference) to be used for a given outcome before the meta-analysis is conducted, and the Handbook chapter on analyzing data gives substantial attention to the practical and statistical reasons why this choice must be made in advance rather than afterwards, on the basis of which measure produces the most favorable forest plot4. The DerSimonian and Laird random-effects model, one of the two pooling models available in RevMan alongside a fixed-effect option, explicitly incorporates between-study variance into the confidence interval of the pooled estimate, and the Handbook’s guidance on when to prefer this model over a fixed-effect assumption concerns a methodological decision that can itself be pre-specified, rather than one to be made by observing which model yields the more convenient result11. A further practical complication that the RevMan interface is designed to address is the situation in which heterogeneity across included studies is sufficiently substantial that pooling may be inappropriate; the Handbook recommends exploring the sources of that heterogeneity, through subgroup analysis or meta-regression, rather than either imposing a pooled estimate regardless or abandoning quantitative synthesis altogether12.

PRISMA, transparency and the role of structure

PRISMA 2020, the broader reporting standard that most systematic reviews are now expected to follow, exists because the completeness and transparency with which a review is conducted and reported directly affect whether its conclusions can be trusted and reproduced7. The accompanying explanation and elaboration document for PRISMA 2020 explains the rationale for each reporting item, including documentation of the search strategy, the study-selection process, and the methods used for data extraction and risk-of-bias assessment in sufficient detail that another team could, in principle, replicate the steps taken8. Because the internal structure of RevMan captures most of these elements as the review is built, a review produced in RevMan following the Handbook’s intended sequence tends to generate most of the documentation required for a PRISMA-compliant report as a byproduct of the workflow, rather than as separate documentation assembled at the end9. This relationship between following the Handbook’s sequence and satisfying the PRISMA reporting checklist also explains why RevMan is effective as a training tool for authors new to systematic reviews: working through its screens in order conveys the methodological logic of the Handbook directly, without requiring a separate study of the reporting standard to understand why certain documentation is expected. A review team that instead conducts its meta-analysis in a general-purpose statistics package without following the same staged sequence can still produce a technically correct pooled estimate, but must independently reconstruct, often retrospectively, the documentation trail that the structure of RevMan would have generated during the review.

Key points

Key points

RevMan functions as a framework rather than a calculator: its sequence of screens enforces the Cochrane Handbook’s order of defining scope, pre-specifying extraction, assessing risk of bias and only then pooling results, which also generates most of the documentation that a PRISMA-compliant report requires.

Practical application

Practical application

  1. The PICO and eligibility criteria should be fixed before data extraction. Population, intervention, comparator and outcome should be defined at the protocol stage, before the full set of eligible studies is known, to prevent decisions being influenced by which results appear favorable.
  2. Risk-of-bias assessment should be treated as an input to interpretation, not as a supplementary table. The risk-of-bias domain judgments should qualify the weight that the discussion places on the pooled estimate, rather than being reported in isolation from the forest plot.
  3. The workflow should be structured around the reporting requirements of PRISMA 2020. The search strategy, selection process and extraction methods should be documented contemporaneously, since this is the documentation that a properly followed RevMan and Handbook sequence generates.

Frequently asked questions

Cochrane authors are required to use it, and Cochrane makes it freely available to them; non-Cochrane authors can use RevMan at a discounted subscription or follow the equivalent Handbook-based workflow in other software, but the underlying methodological sequence applies regardless of which tool performs the final calculation.

Defining PICO and eligibility criteria before full-text screening prevents those decisions from being influenced, consciously or otherwise, by which available studies would produce a more favorable or convenient pooled result.

No single domain or overall rating guarantees trustworthiness by itself; the Handbook treats risk of bias as one of several factors, alongside inconsistency, indirectness, imprecision and publication bias, that together determine the overall confidence placed in a body of evidence.

References

  1. Cochrane. Review Manager (RevMan). Review writing software. The Cochrane Collaboration. read 10 October 2026. View on Cochrane
  2. Thomas J, Kneale D, McKenzie JE, Brennan SE, Bhaumik S. Chapter 2: Determining the scope of the review and the questions it will address. In: Higgins JPT, Thomas J, Chandler J, et al, eds. Cochrane Handbook for Systematic Reviews of Interventions version 6.4. read 10 October 2026. View on Cochrane Training
  3. Lefebvre C, Glanville J, Briscoe S, et al. Chapter 4: Searching for and selecting studies. In: Cochrane Handbook for Systematic Reviews of Interventions version 6.4. read 10 October 2026. View on Cochrane Training
  4. Deeks JJ, Higgins JPT, Altman DG. Chapter 10: Analysing data and undertaking meta-analyses. In: Cochrane Handbook for Systematic Reviews of Interventions version 6.4. read 10 October 2026. View on Cochrane Training
  5. Sterne JAC, Savović J, Page MJ, et al. RoB 2: a revised tool for assessing risk of bias in randomised trials. BMJ. 2019;366:l4898. read 10 October 2026. View on BMJ
  6. Schünemann H, Higgins JPT, Vist GE, et al. Chapter 14: Completing 'Summary of findings' tables and grading the certainty of the evidence. In: Cochrane Handbook for Systematic Reviews of Interventions version 6.4. read 10 October 2026. View on Cochrane Training
  7. Page MJ, McKenzie JE, Bossuyt PM, et al. The PRISMA 2020 statement: an updated guideline for reporting systematic reviews. BMJ. 2021;372:n71. read 10 October 2026. View on BMJ
  8. Page MJ, Moher D, Bossuyt PM, et al. PRISMA 2020 explanation and elaboration: updated guidance and exemplars for reporting systematic reviews. BMJ. 2021;372:n160. read 10 October 2026. View on BMJ
  9. Higgins JPT, Thomas J, Chandler J, et al, eds. Cochrane Handbook for Systematic Reviews of Interventions version 6.4. Cochrane; 2023. read 10 October 2026. View on Cochrane Training
  10. Moher D, Liberati A, Tetzlaff J, Altman DG, The PRISMA Group. Preferred reporting items for systematic reviews and meta-analyses: the PRISMA statement. PLOS Medicine. 2009;6(7):e1000097. read 10 October 2026. View on PLOS Medicine
  11. DerSimonian R, Laird N. Meta-analysis in clinical trials. Controlled Clinical Trials. 1986;7(3):177-188. read 10 October 2026. View on Controlled Clinical Trials
  12. Higgins JPT, Thompson SG, Deeks JJ, Altman DG. Measuring inconsistency in meta-analyses. BMJ. 2003;327(7414):557-560. read 10 October 2026. View on BMJ

Every source above is a peer-reviewed article, a publisher’s record of one, or a standard issued by the body that owns it. Each carries the date it was last read. Where a standard moves, this article is revised rather than left up with a note.

How to cite this article

Pick your referencing style and copy it. Your university or target journal may vary the punctuation — check its guide if it has one.

Pubrica Academy. (2026, October 10). Cochrane RevMan: The Methodological Framework Underlying Systematic Review and Meta-Analysis. Pubrica. https://pubrica.com/academy/concepts-definitions/cochrane-revman-framework/

This article is written to be learned from. Cite it if you are referring to what it says; if you are using the evidence behind it, cite the sources listed above instead.

RevMan-Style Systematic Review Sequence

This order should be followed whether or not RevMan itself is used, so that a review remains aligned with the Handbook and PRISMA.

[ ] Defined PICO and eligibility criteria in a pre-specified protocol
[ ] Documented the full search strategy and date of search
[ ] Recorded the study-selection process (numbers screened, excluded, included, with reasons)
[ ] Extracted data against a pre-specified extraction form
[ ] Assessed risk of bias per study using a named, appropriate tool (e.g. RoB 2)
[ ] Linked risk-of-bias judgments explicitly to the discussion of pooled results
[ ] Checked the final report against the PRISMA 2020 checklist before submission

Pubrica AcademyWritten and maintained by Pubrica’s subject matter experts. Articles are revised when the underlying standards change, and each article states the date on which it was last reviewed.

How Pubrica can help

The Pubrica evidence synthesis team conducts systematic reviews through this full Handbook-aligned sequence in RevMan, from protocol and PICO definition through risk-of-bias assessment to a PRISMA-compliant final report.

Find something else

Search the Pubrica Academy

Access is free and requires no account. Enter a topic, or open the full library to filter by category, sub-topic or resource type.

Alignment of review workflows with the Cochrane Handbook

A scoping assessment is free and takes two business days. It provides a written assessment of what the work requires and which specialist would undertake it.

Get a free quote

Regulations

Check your project against this rule

  1. 1Your work
  2. 2Your details
  3. 3Send
What do you need?

Material you send is held under signed confidentiality, with access limited to the assigned team and encrypted transfer. It is not used to train anything and is not passed to third-party tools. Ask for the agreement before you send anything you would rather cover first.