WHY ENGLISH?
A registration record makes a review plan visible; it does not certify the plan, complete the review or guarantee the final publication followed it.
This guide helps readers use PROSPERO records to compare planned methods with completed reviews, notice amendments and write transparent evidence notes.
PROSPERO is an international prospective register of systematic reviews. A public record can reveal a review question, planned methods, team, dates, funding and changes. English matters because words such as registered, protocol, ongoing, completed and published describe different states. Collapsing them can turn administrative visibility into a false quality endorsement.
People searching for a PROSPERO registration, systematic review protocol or review status often want to know whether a review was planned in advance and whether another team is already studying the question. The record is useful evidence about declared intentions. It must be compared with full protocols, final methods and publications before making claims about what actually happened.
This is practical English for further study, research and professional evidence use. It does not promise that registration prevents bias, that every eligible review is registered or that PROSPERO peer reviews records. The current PROSPERO registration guidance, checked on 4 November 2026, explicitly says a record is not a full protocol, is not peer reviewed, is not endorsed and retains a dated audit trail of amendments.
Name the Object: A Registration Record
A PROSPERO page is a registration record containing structured information supplied by a review team.
Official guidance says the record is not a full protocol, although a protocol PDF may be uploaded. The record helps discovery and transparency; it does not contain every operational detail needed to reproduce a review.
Record-reading case: Name the Object: A Registration Record
A student finds a record with a precise question and search dates. The student writes ‘The team registered these planned methods’ rather than ‘PROSPERO approved the method.’
Registration status must not be used as a quality badge.
Audit move: Name the Object: A Registration Record
In notes, label each object separately: registration record, attached protocol, final review article and later update.
Registration Is Not Peer Review or Endorsement
PROSPERO performs structured and automated checks, but its guidance says it does not peer review or endorse content.
This distinction protects readers from an authority shortcut. A detailed record can still contain a weak question, inadequate search or inappropriate planned synthesis.
Status-language case: Registration Is Not Peer Review or Endorsement
A registered review plans one database for a broad health question. The record is transparent, but the search plan may still be insufficient. The student describes both facts.
Do not write ‘PROSPERO-certified’ or ‘PROSPERO-approved’ unless an official source establishes that exact status, which current guidance does not.
Audit move: Registration Is Not Peer Review or Endorsement
Replace status language with evidence language: registered on date, content supplied by team, methods require independent appraisal.
Read the Review Question Before the Title
Titles can be broad; eligibility fields reveal the real question.
Extract population, intervention or exposure, comparator, outcomes, context and review type. Note whether the record concerns intervention effects, diagnosis, prognosis, prevalence, methodology or another eligible category.
Question-reading case: Read the Review Question Before the Title
A title says ‘digital learning and achievement’, while eligibility fields restrict the review to randomised secondary-school mathematics studies. The narrow question controls interpretation.
A final paper may legitimately narrow or expand scope, but the change must be visible and justified.
Audit move: Read the Review Question Before the Title
Write a one-sentence structured question from the record and compare it with the final abstract.
Use Similar-Review Results as a Discovery Prompt
PROSPERO guidance says its system can identify similar registered reviews during registration.
A similar record can reveal overlapping questions, vocabulary and potential duplication. It does not prove two reviews are identical; compare eligibility, dates, outcomes and planned methods.
Similarity case: Use Similar-Review Results as a Discovery Prompt
Two reviews concern school anxiety, but one evaluates interventions and the other estimates prevalence. Similar titles hide different purposes.
Absence of a similar record does not prove novelty. Other registers, protocols and completed reviews may exist.
Audit move: Use Similar-Review Results as a Discovery Prompt
Search titles, keywords, authors, databases and recent publications before claiming a unique review.
Interpret Dates as Different Events
Registration, planned start, anticipated completion, amendment and publication dates answer different questions.
Build a timeline. Prospective registration is most informative when it precedes key review decisions, but circumstances and policies vary. A later registration should be described accurately rather than treated as invisible.
Timeline case: Interpret Dates as Different Events
A review starts in January, registers in March, updates methods in June and publishes next year. The timeline helps readers ask which decisions were truly prospective.
Do not infer misconduct from timing alone. Seek explanation and compare documents.
Audit move: Interpret Dates as Different Events
Record the date type beside every date and avoid the vague phrase ‘published on PROSPERO.’
Read Review Status as Team-Reported State
Statuses such as ongoing or completed help discovery but can become stale if teams do not update records.
The registration guide asks teams to update records and add publication details when complete. Treat status as the record’s current reported state on the date checked.
Status case: Read Review Status as Team-Reported State
A record says ongoing three years after anticipated completion. The reader searches the authors and title before concluding the review is unfinished.
No publication link does not prove no publication exists; a completed label does not prove results are publicly available.
Audit move: Read Review Status as Team-Reported State
Write ‘record listed as ongoing on 4 November 2026’ and conduct a separate publication search.
Inspect Search Plans Without Pretending They Are Search Results
A record can state planned databases, dates, restrictions and search concepts.
Use these fields to understand intended coverage. The actual review must report what was searched, when and with which strategies. Compare plan and execution rather than assuming the plan happened.
Search-plan case: Inspect Search Plans Without Pretending They Are Search Results
The record plans five databases and no language restriction; the final paper reports three databases and English-only inclusion. That difference needs an explanation in appraisal.
Database names alone do not establish search quality. Strategies, interfaces, dates and supplementary methods matter.
Audit move: Inspect Search Plans Without Pretending They Are Search Results
Create planned-versus-reported columns for sources, date limits, language and supplementary searching.
Compare Eligibility Criteria Across Versions
Eligibility criteria define which evidence can enter the review and therefore shape the conclusion.
Compare participants, interventions, comparators, outcomes, designs, settings, languages and publication status between registration, protocol and final paper.
Eligibility-change case: Compare Eligibility Criteria Across Versions
A registered review includes qualitative studies, while the final publication reports only trials. The discussion should clarify whether the question changed or the evidence was absent.
Not every wording difference is substantive. Distinguish editing from a boundary change.
Audit move: Compare Eligibility Criteria Across Versions
Quote or paraphrase both versions and state the practical effect of any change.
Use the Amendment Trail as Evidence of Transparency
PROSPERO retains prior versions and a dated audit trail when records are amended.
Read what changed, when and why. An amendment can be responsible adaptation; the concern is whether it was disclosed and whether knowledge of results could have influenced it.
Amendment case: Use the Amendment Trail as Evidence of Transparency
A team changes the primary outcome after discovering inconsistent measurement. The record dates the change and provides a rationale. The reader then checks whether screening or preliminary results were already known.
A change log does not automatically make a change unbiased, and no visible change does not prove the plan was followed.
Audit move: Use the Amendment Trail as Evidence of Transparency
Build a table with original field, new field, date, stated reason and possible impact on interpretation.
Separate Primary and Secondary Outcomes
Outcome hierarchy matters because selecting favourable results after seeing data can distort conclusions.
Read which outcomes are primary, how measured and at what time points. Compare the final review’s abstract, synthesis and Summary of Findings with the registered hierarchy.
Outcome case: Separate Primary and Secondary Outcomes
A record names reading comprehension as primary and motivation as secondary. The publication headline emphasises motivation because comprehension was uncertain. The reader keeps both outcomes and their planned roles visible.
Protocols may define several co-primary outcomes. Do not invent a hierarchy not stated by the team.
Audit move: Separate Primary and Secondary Outcomes
Mark each final outcome as registered primary, registered secondary, added, omitted or unclear.
Check Planned Risk-of-Bias and Synthesis Methods
A record may name tools and synthesis approaches, but their appropriateness requires domain judgement.
Compare planned risk-of-bias assessment, effect measures, heterogeneity handling, subgroup analysis and narrative or meta-analytic synthesis with the final report.
Synthesis case: Check Planned Risk-of-Bias and Synthesis Methods
The plan proposes meta-analysis if studies are sufficiently similar; the final review uses narrative synthesis because measures differ. That conditional change may be reasonable when explained.
Do not penalise a team for following a prespecified condition. Appraise the explanation and data.
Audit move: Check Planned Risk-of-Bias and Synthesis Methods
Write the planned decision rule and the final method side by side.
Read Funding and Conflicts Without Mind Reading
Funding and team information help readers ask governance questions, not assign motives automatically.
Record funder, sponsor role and declared conflicts from the registration and final paper. Compare whether responsibilities or affiliations changed.
Governance case: Read Funding and Conflicts Without Mind Reading
An industry-funded review states that the funder had no role in selection or analysis. The reader reports the declaration and appraises safeguards without claiming hidden influence as fact.
Absence of a declaration is not proof of no conflict, while funding is not proof of invalid results.
Audit move: Read Funding and Conflicts Without Mind Reading
Use neutral sentences: ‘The record reports __; the publication declares __; independent appraisal found __.’
Link Registrations, Protocols and Publications Reliably
The evidence chain can break when titles, authors or scope change.
Use registration number, DOI, authors, title keywords and dates to link records. Check corrections and updates. Do not assume the first similarly titled paper is the final review.
Linkage case: Link Registrations, Protocols and Publications Reliably
A final paper shortens the title and adds an author. The registration number in the methods confirms the link.
Some publications omit the identifier; some records are not updated. Identity then requires careful cross-checking.
Audit move: Link Registrations, Protocols and Publications Reliably
Create a provenance line for every review: registration URL, protocol DOI, review DOI and update or correction status.
A Worked Planned-Versus-Reported Comparison
Imagine a review of feedback interventions for secondary writing.
The PROSPERO record plans English and non-English studies, two primary outcomes, independent screening and meta-analysis if measures are comparable. The publication reports an English-only set and narrative synthesis.
End-to-end case: A Worked Planned-Versus-Reported Comparison
The reader confirms that no non-English eligible studies were found and that outcome measures were too diverse for pooling. The final report is consistent with the conditional plan, but the reasoning must come from the methods, not assumption.
If the explanation were absent, the correct label would be unclear, not automatically biased.
Audit move: A Worked Planned-Versus-Reported Comparison
Write a five-row comparison: question, search, eligibility, outcomes and synthesis; add exact citations for differences.
Use PROSPERO in School Research Without Overclaiming
Students can use registry records to learn how research questions become protocols.
Choose one review record and one final paper. Compare question, criteria, outcomes and dates. This turns abstract research methods into a reading exercise.
Student case: Use PROSPERO in School Research Without Overclaiming
A JC student notices that a broad media headline rests on a review with a narrow age range. The student revises the claim to match the registered population.
A school comparison is not a full methodological audit unless it examines all required domains.
Audit move: Use PROSPERO in School Research Without Overclaiming
Ask the student to produce a one-page planned-versus-reported note with three verified differences and one unresolved question.
Keep Non-Registered Reviews in Proper Perspective
A review without a PROSPERO record is not automatically poor, and some review types or dates may fall outside register eligibility or practice.
Appraise the published protocol, methods and reporting. Search other registries or repositories. Describe absence of a located record as a search result, not a verdict.
Absence case: Keep Non-Registered Reviews in Proper Perspective
A high-quality historical review predates common registration practice. Its methods remain appraisable even though no prospective record exists.
Do not create a binary registered-good, unregistered-bad rule.
Audit move: Keep Non-Registered Reviews in Proper Perspective
State where and when you searched, then evaluate the review with appropriate appraisal criteria.
Transfer Registration Literacy to Projects and Careers
Registration literacy teaches a broader professional habit: distinguish a declared plan from completed work.
Project charters, preregistrations, audit plans and tender specifications all record intentions. Later reports should show execution, deviations and reasons.
Workplace case: Transfer Registration Literacy to Projects and Careers
A workplace pilot promised three evaluation measures but reports one. A careful reader asks for the change record before accepting the conclusion.
Plans can adapt responsibly. The goal is not rigid obedience but transparent change control.
Audit move: Transfer Registration Literacy to Projects and Careers
Use three columns in any project: promised, performed and explained difference.
Finish With a Registry-to-Review Audit
A final evidence note should make the chain from registration to conclusion visible.
Verify record identity, dates, status, question, eligibility, search, outcomes, appraisal, synthesis, amendments, funding and publication links. Date the check because records can update.
Final audit case: Finish With a Registry-to-Review Audit
The audit catches that a review labelled completed has a newer corrected publication. The student cites the corrected record and notes the registration timeline.
No registry audit replaces reading the full review and its included evidence.
Audit move: Finish With a Registry-to-Review Audit
End with two sentences: what the registration supports and what remains unverified.
Check Whether the Record Fits the Review You Found
Shared authors and keywords do not guarantee that a registration belongs to a publication.
Compare question, dates, population, intervention, outcomes and registration number. Contact details or a protocol DOI can help when titles changed.
Linkage case: Check Whether the Record Fits the Review You Found
A team publishes two reviews in the same year; only one matches the registered outcome hierarchy.
Do not attach the wrong registration merely because it looks plausible.
Audit move: Check Whether the Record Fits the Review You Found
Record positive identifiers and remaining uncertainty.
Read the Named Guarantor and Team Roles
PROSPERO guidance requires a named guarantor and team confirmations during registration.
The guarantor role signals responsibility for the record, while listed team membership supports provenance. It does not mean each person performed every task.
Team case: Read the Named Guarantor and Team Roles
The final paper adds a statistician not listed initially. The change may be normal; the contribution statement clarifies their role.
Do not infer ghost authorship or endorsement from names alone.
Audit move: Read the Named Guarantor and Team Roles
Compare team lists and contribution statements neutrally.
Interpret Anticipated Completion Dates Cautiously
An anticipated date is a plan, not a deadline enforced by the register.
Delays may reflect search complexity, staff changes, new evidence or abandonment. Status and publication searches provide additional context.
Schedule case: Interpret Anticipated Completion Dates Cautiously
A review anticipated completion in 2024 but remains ongoing in 2026. The reader reports the stale plan and searches for updates.
Do not call the review late or failed without evidence.
Audit move: Interpret Anticipated Completion Dates Cautiously
Use planned, reported and verified date labels.
Compare Contact Details Without Exposing Them
Public records can contain professional contact information to support transparency.
Use the record’s contact route for legitimate research queries, but do not republish personal details unnecessarily. Note affiliation changes when they affect record linkage.
Contact case: Compare Contact Details Without Exposing Them
A corresponding author moves institutions; ORCID and DOI metadata help link the same person and review.
Public availability is not permission for unrelated use.
Audit move: Compare Contact Details Without Exposing Them
Reference the record URL rather than copying contact data into student notes.
Check Attached Protocols as Versioned Documents
An uploaded protocol PDF has its own version and date.
Compare it with the registration fields. Note whether later amendments appear in the record, a new protocol or only the final review.
Protocol-file case: Check Attached Protocols as Versioned Documents
The PDF predates an outcome amendment visible in the registry. The reader uses both documents and does not call the PDF current.
A protocol link can break or an attachment can lag.
Audit move: Check Attached Protocols as Versioned Documents
Record filename, version, date and relationship to the active record.
Search for Results Beyond the Publication Field
A missing publication citation in the record may reflect delayed maintenance.
Search authors, title phrases, registration number, DOI services and relevant databases. Verify that any located paper actually reports the registered review.
Publication-search case: Search for Results Beyond the Publication Field
A final review cites the registration in Methods even though the PROSPERO record lacks the article link.
Do not assume completion from a conference poster or protocol alone.
Audit move: Search for Results Beyond the Publication Field
Document queries and date checked.
Distinguish Review Updates From New Reviews
An updated systematic review may reuse a question while extending searches and methods.
Check whether the record identifies an update, prior review and new search period. Link old and new conclusions without double-counting.
Update case: Distinguish Review Updates From New Reviews
A 2026 update adds three trials and changes certainty. The student cites the update for current evidence and the earlier review for history.
A similarly titled new review may be independent rather than an update.
Audit move: Distinguish Review Updates From New Reviews
Write the relationship explicitly: updates, replicates, overlaps or independently reviews.
Use Registry Searches to Refine Vocabulary
Registration records expose structured terms used by review teams.
Collect synonyms for populations, interventions and outcomes, then verify them in subject headings and database thesauri. Registry wording can improve search sensitivity.
Vocabulary case: Use Registry Searches to Refine Vocabulary
‘Feedback literacy’ records reveal related phrases such as uptake, revision response and learner engagement.
Do not copy another team’s search terms without checking fit and dates.
Audit move: Use Registry Searches to Refine Vocabulary
Build a concept table with source and rationale for each synonym.
Notice When No Meta-Analysis Was Planned
A systematic review need not include meta-analysis.
Read whether synthesis is narrative, qualitative, meta-analytic or mixed and what conditions govern pooling. The final method should follow a defensible decision rule.
Synthesis-format case: Notice When No Meta-Analysis Was Planned
Heterogeneous classroom interventions are synthesised narratively as planned. The absence of a forest plot is not a methodological failure.
Narrative synthesis can still be selective and requires transparency.
Audit move: Notice When No Meta-Analysis Was Planned
Compare planned grouping and final synthesis structure.
Use Cautious Language for Deviations
The word deviation describes a difference, not its motive or consequence.
Classify differences as clarification, justified adaptation, unexplained change or outcome-related concern only after evidence. Quote rationale where available.
Deviation case: Use Cautious Language for Deviations
A database becomes unavailable and the team substitutes another with documented coverage. The change is real and explainable.
Accusatory language without evidence weakens appraisal.
Audit move: Use Cautious Language for Deviations
Write observed difference, stated reason and potential impact as separate clauses.
Create a One-Page Review Provenance Card
Readers benefit from a compact record of how a review moved from plan to publication.
Include registration ID, protocol, question, dates, status, amendments, final citation, correction status and key planned-versus-reported differences.
Provenance-card case: Create a One-Page Review Provenance Card
A school research team can reuse the card when updating an essay months later.
A card summarises; it does not replace full appraisal.
Audit move: Create a One-Page Review Provenance Card
Store the card beside the bibliography and date every refresh.
Read Inclusion of Grey Literature as a Planned Choice
Reports, theses, registries and other non-journal sources can reduce publication bias and expand coverage.
Check whether the record plans grey-literature searches and how eligible material will be appraised. Compare with the final search.
Grey-literature case: Read Inclusion of Grey Literature as a Planned Choice
The registration includes theses, but the final paper lists journals only. The reader looks for an explanation before judging completeness.
Grey literature is not automatically low quality or automatically unbiased.
Audit move: Read Inclusion of Grey Literature as a Planned Choice
Record source types, search routes and final treatment.
Inspect Language Restrictions and Their Rationale
Language restrictions can shape which populations and findings remain visible.
Read whether restrictions were planned, why and how non-English material would be handled. Compare the final set and report translation methods.
Language case: Inspect Language Restrictions and Their Rationale
A review plans no language restriction but later excludes non-English studies because resources changed. The deviation may affect generalisability and deserves disclosure.
Language is not a proxy for methodological quality.
Audit move: Inspect Language Restrictions and Their Rationale
Write restriction, rationale, affected records and likely consequence separately.
Check Whether Stakeholders Were Planned
Some reviews plan patient, learner, practitioner or public involvement in question and outcome selection.
Read who was involved, at which stage and with what influence. Compare the final contribution report.
Stakeholder case: Check Whether Stakeholders Were Planned
Teachers help prioritise classroom burden as an outcome, which explains its presence in the Summary of Findings.
A stakeholder name does not prove meaningful involvement.
Audit move: Check Whether Stakeholders Were Planned
Describe role, task and decision impact rather than using a ceremonial label.
Distinguish Review Completion From Evidence Currency
A completed review can become outdated when new studies appear.
Check final search date, publication date, update plans and later major studies. Registration completion status says nothing by itself about currentness.
Currency case: Distinguish Review Completion From Evidence Currency
A review published in 2025 searched only to 2022; several later trials may change the conclusion.
Newer is not automatically better; inspect relevance and quality.
Audit move: Distinguish Review Completion From Evidence Currency
Write the evidence cut-off date beside every current-use decision.
Use Neutral Questions When Contacting Review Teams
Sometimes unresolved linkage or amendment questions justify a professional query.
Identify the record, quote the field, state what you found and ask one answerable question. Avoid accusations and disclose the purpose.
Contact case: Use Neutral Questions When Contacting Review Teams
A student asks whether a changed outcome was amended before extraction because the public record is unclear.
No reply does not prove wrongdoing.
Audit move: Use Neutral Questions When Contacting Review Teams
Keep the message concise and record date and response without publishing private correspondence improperly.
Read Country and Setting Fields as Scope
Country, institution and setting fields help readers judge where evidence was intended to apply.
Compare planned settings with final included studies. A global title can rest on evidence from a narrow group of systems, climates or service models.
Setting case: Read Country and Setting Fields as Scope
A review of school counselling includes studies from three high-income urban systems. The reader avoids describing the conclusion as universally applicable.
Geographic concentration does not automatically invalidate a result; it defines a transfer question.
Audit move: Read Country and Setting Fields as Scope
Name represented settings and the important settings not evidenced.
Check Whether Data Extraction Was Prespecified
Extraction methods influence which characteristics and results enter the synthesis.
Read planned duplicate extraction, forms, piloting and author contact. Compare whether the final review reports the same safeguards.
Extraction case: Check Whether Data Extraction Was Prespecified
The record plans two independent extractors, while the publication reports one extractor with checking. The difference may affect error risk and needs explanation.
A registration may summarise extraction briefly; consult the protocol before concluding that a safeguard was absent.
Audit move: Check Whether Data Extraction Was Prespecified
Add extraction method to the planned-versus-reported table.
Frequently Asked Questions
Is a PROSPERO record a full protocol?
No. Official guidance says it is not a full protocol, although a protocol PDF can be attached.
Does PROSPERO peer review registrations?
No. Current guidance says PROSPERO does not peer review or endorse record content.
Does registration prove a review followed its plan?
No. Compare the record and protocol with the final methods, outcomes, synthesis and amendments.
What does ongoing status prove?
It reports the record’s current state as maintained by the team. Search separately for publications and note the date checked.
Are amendments automatically suspicious?
No. They may be necessary and responsible. Examine timing, reason, transparency and possible impact.
Can two similar registrations ask different questions?
Yes. Compare population, intervention or exposure, outcomes, design, setting and dates before calling them duplicates.
Is an unregistered review unusable?
No. Eligibility, era and practice vary. Appraise its protocol, methods and reporting and search other registries.
Should students cite the registration?
Cite it when discussing planned methods or status. Cite the final review and underlying evidence for substantive findings.
Why do registration and publication titles differ?
Scope, wording or authorship can change. Link records through identifiers, authors, dates and methods.
What is the safest summary sentence?
State what the team registered, when, what changed and what the final paper actually reports.
Useful Next Reading
- PROSPERO registration guidance — read the register’s current scope and cautions.
- How systematic reviews work — place registration inside the full review process.
- Write verifiable project commitments with DMPTool — compare another plan-versus-practice workflow.
- Critical reading and information literacy — evaluate authority without turning labels into verdicts.
Closing thought: PROSPERO gives a review a visible before-picture. English lets the reader compare that picture with what happened next—accurately, fairly and without turning registration into endorsement.