Systematic Review Protocol Planning and Registration

Research infrastructure

Protocol planning establishes the method before the results are known

Every systematic review rests on a set of decisions: what question to ask, which evidence counts, how to search, screen, extract, appraise, synthesise, and report. A written protocol puts those decisions in one place where anyone can inspect them. Registration adds a dated public record on top of that, and version control shows how the plan changed while the work was underway.

The planning problem

Running the first database search feels like the moment the review actually starts. It is not. By then the team should already have settled a much larger set of choices. The question decides what evidence is eligible. The eligibility criteria shape the search. The outcomes you plan to report govern what gets extracted, and the synthesis plan decides which data you need to collect at all.

Cochrane treats protocol development as a way to make these judgements before the findings can influence them. Its guidance asks teams to pre-specify the search, the risk-of-bias assessment, the synthesis, any subgroup analyses, and the certainty assessment where those methods apply.1 Planning has a practical payoff too: it shows early on what expertise and resources the review is going to need.2

A weak start spreads through the whole project. Vague eligibility criteria turn into screening conflicts. An outcome list without definitions produces extraction that no two people do the same way. And when the synthesis plan is written after the results arrive, readers have no way to tell which decisions came first and which were made with the findings already on the table.

The first methodological checkpoint

Ask one question: could another trained team pick up the protocol, understand the question, apply the criteria, run the methods, and explain every planned analysis without calling you? If the answer is no, the missing instructions belong in the plan before formal screening starts.

Decision architecture

A protocol connects scientific decisions with project operations

PRISMA-P is a 17-item reporting checklist for systematic review protocols. It covers administrative information, rationale and objectives, eligibility criteria, information sources, the search strategy, study records, outcomes, risk of bias, data synthesis, meta-biases, and certainty assessment.3 If you want the reasoning behind each item, along with worked examples of complete reporting, the explanation and elaboration paper supplies both.4

A checklist gets you complete reporting, nothing more. The team still has to pick methods that fit the question and the field. An intervention review, a qualitative synthesis, a diagnostic accuracy review, an environmental evidence synthesis, and a policy review will not share one design. That is what field-agnostic planning means in practice: the decision logic travels across disciplines while the methods stay matched to the evidence.

Scientific scope

Question, rationale, eligible evidence, outcomes, comparisons, and intended users.

Review methods

Identification, selection, extraction, appraisal, synthesis, and certainty procedures.

Project operations

Roles, dependencies, milestones, training, conflict resolution, data management, and support.

Audit trail

Registration, versions, amendments, deviations, approvals, dates, and links to final outputs.

These four parts depend on each other. A sound scientific method stalls when nobody owns the tasks or the team has no access to specialist support. A polished schedule just moves the wrong method faster. Registration, for its part, will preserve an incomplete plan with perfect accuracy. The protocol’s job is to hold the scientific and operational layers together.

Public accountability

Registration creates a public record, not a quality certificate

Prospective registration lets readers find ongoing reviews, spot unplanned duplication, compare the published review with its earlier plan, and inspect major changes. PROSPERO was built around exactly those goals: public records that capture the core attributes of a review, plus an audit trail of major methodological changes.5 The wider case for registration rests on transparency, reproducibility, and protection against decisions driven by results.6

Pick a registry or repository that fits the review type, the subject area, and the stage of the work. Its fields will never hold the full method. The protocol stays the detailed source of truth, and where the platform allows it, the public record should point readers to that document.

Registration is not a promise that nothing will change. New information can expose an ambiguous criterion, a data source that turns out to be unavailable, or an analysis the evidence cannot support. Cochrane asks authors to document and report changes to protocol methods.2 PRISMA-P asks protocol authors to say up front how they will record important amendments.3

Transparency permits justified change

Record what changed, when, who approved it, and why. Say whether the change touched eligibility, data, analysis, or interpretation. Give readers that trail and they can judge the amendment on evidence instead of suspicion.

Where trust is lost

Undocumented drift separates the registered plan from the published review

A registration number says nothing about whether the team actually followed the registered methods. Readers need to see the plan and the finished work side by side. In a 2021 sample of 100 non-Cochrane systematic reviews with PROSPERO records, 90 differed from their record in at least one eligibility component, and the publications rarely explained why.7 That was one sample, so it should not be read as a prevalence estimate for reviews in general. What it does show is the exact problem an amendment trail exists to solve.

Some differences are sound responses to things the authors could not have known at the start. Others change which evidence enters the synthesis. Timing, rationale, approval, and disclosure are what separate the two. This is why a team should keep every protocol version instead of overwriting the original plan.

Protocol planning and registration evidence chain The decision need leads to a review question, protocol, public record, controlled execution, amendment trail, and final report. Each stage preserves a link to the preceding plan. Decisionneed Reviewquestion Protocol Publicrecord Controlledexecution Finalreport Version history and amendment trail Preserve the original plan, each change, its rationale, approval, and effect.
A trustworthy review preserves continuity. A reader should be able to move from the final report back through the amendments, the registration, the protocol, and the original decision need.
Standards in context

Reporting guidance supports the plan; it does not replace conduct guidance

Each guideline has one defined job. PRISMA-P covers the protocol. PRISMA 2020 covers the report of a completed systematic review.8 PRISMA-S adds detail for reporting literature searches.9 PRESS supports peer review of electronic search strategies.10

The conduct standard is a separate choice, and it has to match the review question. Cochrane, JBI, Campbell, CEE, or another established handbook may fit, depending on the evidence and the decision setting. Name the guidance you are using in the protocol, say where you adapted it, and do not claim compliance that the final methods cannot back up.

From principle to practice

Use the resource library as an evolving planning system

The resources below turn protocol principles into working documents, decision aids, logs, and project controls. This hub will grow as methods, platforms, and learner needs change. Every addition stays inside one boundary: work done before or during protocol registration, plus the controlled management of the plan that follows.

The methodological guides in the matching weblog category explain the reasoning; these resources support the application. Read together, they connect what the team decides with what it records and does.

Protocol development toolkit

Working templates for planning a systematic review, meta-analysis, or evidence synthesis

Each resource in this library turns one planning decision into a working document, from setting up the project and sequencing the workflow to registering the protocol and managing amendments after registration. New templates are added as methods, registries, and reporting standards evolve, so the collection covers the full planning phase of any evidence synthesis.

1. Protocol Planning & Registration Frameworks: Templates & Guides

Protocol

Lay the groundwork for a rigorous review before the first search runs. Organize the project workspace, map the timeline and milestones, draft the protocol, select a registration route, and keep a controlled record of every version and amendment from initial idea to final report.

Systematic review starter kit

Set up a reproducible review workspace, folder structure, file-naming system, project checklist, and data-management foundation before the search begins.

Systematic review timeline and milestone planner

Sequence protocol development, searching, screening, extraction, appraisal, synthesis, and reporting with clear responsibilities, dependencies, milestones, and progress checks.

Protocol amendment and deviation log

Record what changed after protocol approval or registration, when it changed, why it changed, who approved it, and how the change affects analysis and reporting.

The planning standard

From a research intention to a defensible public plan

A protocol earns its value through use. The team consults it during screening, extraction, appraisal, and synthesis. New decisions return to the protocol, the amendment record, and the project log. The completed review then reports where the work followed the plan and where it changed.

This approach gives the review two forms of continuity. Scientific continuity keeps the question, eligibility criteria, outcomes, and synthesis aligned. Operational continuity connects each task with an owner, dependency, approval, and record. A break in either chain can produce untraceable decisions.

Readiness gates
1Question approvedThe scope and intended use are stable.
2Methods specifiedThe team can execute each planned stage.
3Roles assignedExpertise, ownership, and conflict resolution are clear.
4Records controlledVersions, data, decisions, and approvals have a home.
5Plan publicThe appropriate registration or repository route is complete.

These gates do not promise that the review will face no surprises. They give the team a stable basis for responding to them. A justified amendment can then preserve trust because the original decision and the reason for change remain visible.

A growing infrastructure

The hub can expand without changing its methodological purpose

Future resources may address team agreements, stakeholder involvement, protocol completeness, registry selection, project risk, version control, amendment governance, or other planning needs. They belong here when they help a team define, register, operate, or preserve the review plan.

Resources that teach searching and study identification belong in the next lifecycle hub. Screening, extraction, appraisal, and synthesis have their own homes. This separation keeps the Academy navigable as the library grows and gives every resource a clear parent.

The durable rule

Decide before observing the answer, preserve the first plan, and explain each later change. Registration makes that sequence visible. Careful conduct makes it credible.

Get the Resource Infrastructure Free Forever

Get Free Lifetime Access
References

  1. Lasserson TJ, Thomas J, Higgins JPT. Chapter 1: Starting a review. In: Higgins JPT, Thomas J, Chandler J, et al, editors. Cochrane Handbook for Systematic Reviews of Interventions. Version 6.5. Cochrane; 2024. Current online chapter
  2. Cochrane. Chapter II: Planning a Cochrane Review. In: Higgins JPT, Thomas J, Chandler J, et al, editors. Cochrane Handbook for Systematic Reviews of Interventions. Version 6.5. Cochrane; 2024. Current online chapter
  3. Moher D, Shamseer L, Clarke M, et al. Preferred reporting items for systematic review and meta-analysis protocols (PRISMA-P) 2015 statement. Syst Rev. 2015;4:1. doi:10.1186/2046-4053-4-1
  4. Shamseer L, Moher D, Clarke M, et al. Preferred reporting items for systematic review and meta-analysis protocols (PRISMA-P) 2015: elaboration and explanation. BMJ. 2015;349:g7647. doi:10.1136/bmj.g7647
  5. Booth A, Clarke M, Dooley G, et al. The nuts and bolts of PROSPERO: an international prospective register of systematic reviews. Syst Rev. 2012;1:2. doi:10.1186/2046-4053-1-2
  6. Stewart L, Moher D, Shekelle P. Why prospective registration of systematic reviews makes sense. Syst Rev. 2012;1:7. doi:10.1186/2046-4053-1-7
  7. Hu K, Zhao L, Zhou Q, et al. Inconsistencies in study eligibility criteria are common between non-Cochrane systematic reviews and their protocols registered in PROSPERO. Res Synth Methods. 2021;12(3):394-405. doi:10.1002/jrsm.1476
  8. Page MJ, McKenzie JE, Bossuyt PM, et al. The PRISMA 2020 statement: an updated guideline for reporting systematic reviews. BMJ. 2021;372:n71. doi:10.1136/bmj.n71
  9. Rethlefsen ML, Kirtley S, Waffenschmidt S, et al. PRISMA-S: an extension to the PRISMA Statement for reporting literature searches in systematic reviews. Syst Rev. 2021;10:39. doi:10.1186/s13643-020-01542-z
  10. McGowan J, Sampson M, Salzwedel DM, Cogo E, Foerster V, Lefebvre C. PRESS peer review of electronic search strategies: 2015 guideline statement. J Clin Epidemiol. 2016;75:40-46. doi:10.1016/j.jclinepi.2016.01.021
Scope note: This hub treats protocol planning and registration as field-agnostic infrastructure. Review teams must select conduct guidance, reporting standards, and a registration or repository route that fit their question, evidence type, discipline, and jurisdiction.