
JBI guidance informs how a scoping review is planned and conducted. PRISMA-ScR tells authors what the completed review report should disclose.
Separate protocol, conduct and reporting
Three related jobs require different guidance:
| Job | Main question | Appropriate guidance |
|---|---|---|
| Protocol development | What will the team do, and why? | A scoping-review methodology and protocol guidance |
| Review conduct | How will the planned search, selection, extraction and analysis be performed? | A scoping-review methodology, with justified amendments documented |
| Final reporting | What must readers be told about what was planned, done and found? | PRISMA-ScR |
PRISMA-ScR is the reporting layer. Consulting it early can flag information the final manuscript will need, but completing it does not establish that the protocol or methods were appropriate.
The JBI Manual for Evidence Synthesis, Chapter 10 provides dedicated methodology for conducting scoping reviews. Its roadmap covers protocol development; alignment of objectives, questions and eligibility criteria; searching; selection; extraction; analysis; presentation; and summary. This guide uses that methodology for planning and conduct, then uses PRISMA-ScR to audit the manuscript.
Choose a scoping review for the right reason
A scoping review is not a systematic review with fewer quality checks. It is a form of evidence synthesis suited to objectives such as mapping how a concept is defined, describing the types and distribution of evidence, examining research methods or identifying evidence clusters and gaps.
The PRISMA-ScR extension was published in 2018 to improve reporting of completed scoping reviews. It contains 20 essential and 2 optional reporting items across title, abstract, introduction, methods, results, discussion and funding. It tells authors what information the manuscript should disclose.
Before searching, write the product the reader will receive:
This review will map [concept/evidence characteristic] among [population] across [context] to inform [specific decision or next research step].
If the real objective is to estimate treatment effects or answer a focused diagnostic question, a systematic review may be more appropriate. If the objective is merely “summarise the literature,” it is not yet specific enough for either design.
Our guide to choosing a reporting guideline explains the larger reporting landscape. In the completed report, identify the article as a scoping review in the title, as PRISMA-ScR requests.
Frame the question around the intended map
JBI suggests Population–Concept–Context (PCC) for framing scoping-review objectives, questions and eligibility:
| Element | Example questions |
|---|---|
| Population | Which people, organisations, documents or studies? |
| Concept | Which intervention, model, definition, experience or method? |
| Context | Which care setting, geography, discipline or policy environment? |
Not every question needs all three elements, but eligibility must remain operational. Define:
- Source types, including whether reviews, protocols, policies or grey literature qualify.
- Study designs and publication status.
- Date range and why it exists.
- Language limits and their practical or epistemic consequences.
- Setting, geography and population boundaries.
- Concept criteria that two reviewers can apply consistently.
A broad question does not justify vague inclusion. “Digital health in older adults” could encompass prevention, diagnosis, treatment and service delivery. State which dimensions will be mapped.
Draft the final table shells now. If you intend to map intervention purpose by care setting and evidence type, create those columns before searching. This exposes concepts that need definitions and ensures data charting serves the objective.
Develop the protocol with conduct guidance
PRISMA-ScR item 5 asks the final report to say whether a protocol exists, where it can be accessed and, if available, its registration information. That is a disclosure requirement, not instructions for creating the protocol.
JBI's dedicated section on developing a scoping-review protocol treats an a priori protocol as required when following JBI methodology. It does not require journal publication, but points to publicly listed platforms where a protocol can be placed for transparency. Journal requirements can differ. A protocol that follows this methodology typically describes:
- Rationale and objectives.
- Eligibility criteria.
- Information sources and draft search strategy.
- Record management and deduplication.
- Screening process and reviewer roles.
- Data-charting form and calibration.
- Critical appraisal plan, if any.
- Synthesis and presentation plan.
Registration and repository services have different scopes. The current JBI manual states that PROSPERO does not accept scoping reviews and points to public alternatives such as the Open Science Framework and Figshare. Verify each service's current rules before submission. Our guide to PROSPERO registration applies to eligible systematic reviews, not as a default route for scoping reviews.
Changes are sometimes necessary. Date each amendment, state what changed and why, and say whether it was made before or after the team saw relevant results. Quietly narrowing eligibility to create a cleaner story undermines credibility.
Conduct the review under the protocol
The next stages concern conduct, so use the selected methodology—not PRISMA-ScR—as the operational guide. Preserve search exports, screening decisions, extraction forms and amendment records so the final report can be checked.
PRISMA-ScR can still flag details readers will need, such as complete search syntax, the selection process and whether charting was done independently or in duplicate. It does not decide whether a database set or method is adequate.
Design a reproducible search
Use an information specialist or librarian where possible. Scoping searches may need breadth across disciplines, terminology and source types. More databases are not automatically better; choose sources that cover the concept and explain each choice.
PRISMA-ScR asks authors to describe all information sources (for example, databases with dates of coverage and contact with authors) and the date the most recent search was executed, and to present the full electronic search strategy for at least one database, including any limits, so it could be repeated. Giving the last-searched date for each source is good practice and is what PRISMA 2020 requires.
Record:
| Search component | What to preserve |
|---|---|
| Database | Platform as well as database name |
| Dates | Coverage limits and final search date |
| Strategy | Exact lines, syntax, fields and filters |
| Other sources | Websites, citation searching, registries and expert contact |
| Grey literature | Source, query, screening depth and access date |
| Deduplication | Software, version and process |
Do not report only a list of keywords. Database syntax, indexing terms and platform matter. Translate the strategy appropriately rather than copying syntax unchanged.
Search restrictions need reasons. A language restriction may omit locally published evidence and distort a geographic map. A date restriction may be justified by a policy change or emergence of a technology; state that rationale.
Consider updating the search near submission when the field moves quickly or the review process was long. Report both the original and update dates.
Select sources transparently
Define reviewer roles at title/abstract and full-text stages. Independent duplicate screening can reduce errors, but whatever process you use should be explicit. Calibrate first: have reviewers screen the same sample, discuss disagreements and revise guidance before the main set.
Create a decision manual for ambiguous terms. For example, if “rural setting” is eligible, specify whether author labels, population density, administrative classifications or site location determine it.
Record:
- Number after deduplication.
- Number screened.
- Number sought and not retrieved.
- Number assessed in full.
- Full-text exclusion reasons.
- Number included in the review.
Use mutually exclusive final exclusion reasons where possible. “Wrong topic” is usually too vague. Reasons such as wrong population, concept, context, source type or publication status connect directly to criteria.
A PRISMA flow diagram should reconcile exactly with the screening database. Counts in the abstract, Results and diagram must agree.
Extract data for the question
PRISMA-ScR uses the term “data charting”; the current JBI manual generally describes this stage as data extraction. Terminology does not change the need for a planned, piloted process. Categories may need refinement as the team learns how evidence is reported, but iteration should be documented rather than improvised to favour a pattern.
A useful charting form might include:
| Domain | Possible fields |
|---|---|
| Source | Author, year, country, publication type |
| Population | Eligibility, sample size, relevant characteristics |
| Concept | Definition, components, theoretical model |
| Context | Setting, sector, geography |
| Methods | Design, data source, follow-up |
| Map-specific fields | Outcome domains, implementation barriers, terminology |
PRISMA-ScR asks authors to report how data were charted, whether independently or in duplicate, and any process for obtaining or confirming information from investigators. The conduct methodology should determine the procedure; the manuscript should disclose who extracted, who checked and how disagreements were resolved.
Preserve the difference between “not reported,” “not applicable” and “none.” If a source does not mention participant involvement, that is not proof that none occurred. A codebook with definitions and examples improves consistency.
Decide whether critical appraisal serves the objective
The two PRISMA-ScR critical-appraisal reporting items are optional. That reporting status does not itself decide whether appraisal is methodologically appropriate; make and justify the conduct decision from the review objective and selected methodology.
Appraisal may help when the review maps evidence quality, identifies readiness for a focused systematic review or uses findings to inform decisions. It may be less central when mapping terminology or publication characteristics.
If you appraise:
- Select tools appropriate to each evidence type.
- Report reviewer process and disagreement resolution.
- Present domain judgments, not an unexplained total score where the tool does not support one.
- Explain how appraisal informed synthesis.
If you do not appraise, say so and explain the consequence: the review maps what was reported but does not establish the credibility of individual findings. Do not then count “positive” studies and infer effectiveness.
Analyse and present a map
Start Results with selection flow, then describe included-source characteristics and answer each review question. A useful presentation combines:
- Flow diagram.
- Summary table of source characteristics.
- Tables or figures crossing the dimensions named in the objective.
- Concise narrative explaining patterns, gaps and outliers.
Counts need denominators. “Most studies were recent” is less useful than “32 of 45 included sources were published from 2021 onward.” But counts of publications do not measure evidence strength, population benefit or research quality.
Choose displays to match the map:
| Mapping objective | Suitable display |
|---|---|
| Evidence by country and setting | Matrix or geographic map |
| Concepts and definitions | Definition table |
| Designs across populations | Evidence gap map |
| Research activity over time | Timeline |
| Intervention components | Component-by-context matrix |
Do not synthesise incompatible outcome directions into vote counting. If effectiveness is not the review objective, describe which outcomes and designs have been studied rather than whether studies were “positive.”
Our guide to tables and figures in medical papers can help make each display stand alone.
Discuss what the map can and cannot show
The Discussion should summarise the main mapped patterns, relate them to the objective and explain implications. A gap is not automatically a research priority. Absence of studies may reflect low importance, terminology, indexing or the review's limits. Priority also depends on burden, feasibility, equity and stakeholder needs.
Address limitations at two levels:
- Review process: database coverage, language limits, missed grey literature, single-reviewer steps, changing terminology.
- Evidence base: concentration in certain countries, sparse populations, inconsistent definitions, absent outcome domains or limited appraisal.
Do not attribute limitations of included sources to your review, or vice versa. If you did no risk-of-bias assessment, avoid credibility claims. If stakeholder consultation was not performed, do not imply that mapped gaps reflect patient priorities.
End with a specific next step: a focused systematic review where comparative evidence has accumulated, consensus work where definitions conflict, primary research in an absent population, or no new study where duplication is already dense.
Report the completed review with PRISMA-ScR
Calling a manuscript PRISMA-ScR-complete means its applicable reporting items are addressed. It does not certify methodological quality, eliminate bias or establish adherence to JBI.
Download the official checklist and enter a page or section for every item. Do not write “reported throughout.” Check:
- Title identifies a scoping review
- Structured summary reports background, objectives, eligibility, sources, charting methods, results and conclusions
- Rationale explains why scoping is appropriate
- Objectives specify key question elements
- Protocol location and amendments are reported
- Eligibility criteria and information sources are complete
- Full strategy for at least one database is reproduced
- Selection and charting roles are explicit
- Data items and synthesis methods are defined
- Appraisal choice and use are explained
- Flow counts reconcile
- Included-source characteristics are available
- Results answer each mapped question
- Limitations cover review process and evidence base
- Conclusions do not imply effectiveness from evidence counts
- Funding for the review and included sources is reported as requested
Finally, run three separate checks: does the protocol preserve the decisions made before conduct, did the team follow a defensible scoping-review methodology and disclose amendments, and does the final manuscript report the work completely under PRISMA-ScR? Keeping those claims separate prevents a completed reporting checklist from being mistaken for a complete method.
Frequently asked questions
What is the difference between a scoping review and a systematic review?
Both use explicit, reproducible methods, but their purposes often differ. A scoping review commonly maps concepts, evidence types, methods or gaps across a broad field. A systematic review commonly answers a focused question and may synthesise effects or associations. The label should follow the objective and methods, not a belief that scoping reviews are easier.
Is PRISMA-ScR mandatory for scoping reviews?
Journal requirements vary. PRISMA-ScR is a reporting extension with 20 essential and 2 optional items for completed scoping-review reports; it is not a protocol template or conduct manual. Consulting it early can prevent missing information, but protocol and conduct decisions need dedicated methodology such as JBI Chapter 10. Submit the checklist when the journal requests it.
Does a scoping review need a protocol?
An a priori protocol records the objective, eligibility, search, selection, extraction and analysis plans before results can influence decisions. It is required when claiming adherence to JBI scoping-review methodology, although journal requirements vary. PRISMA-ScR only asks the final report to state whether a protocol exists and where it can be accessed.
Must a scoping review assess risk of bias?
Not always. Critical appraisal is optional in PRISMA-ScR because some mapping objectives do not require judgments about study validity. Decide from the review question. If appraisal is done, justify the tools, report how it was performed and explain how the findings informed synthesis. If it is not done, state the consequence for interpretation.
Can a scoping review conclude that an intervention works?
Usually a map of study counts and findings cannot establish effectiveness. Heterogeneous designs and absent appraisal may make direction-of-effect summaries misleading. A scoping review can describe what evidence exists and identify where focused synthesis is warranted, but effectiveness conclusions require methods designed to assess and synthesise comparative evidence.