Scoping Review vs Narrative Review: Choose by Your Question

A scoping review maps what studies exist within a set question and scope. A narrative review develops an argued account of chosen works. Choose by the claim you need to make: “what has been studied and how?” or “how should we understand this debate?”

JBI defines scoping reviews as planned evidence maps, not quick background searches. The original SANRA paper asks narrative authors to state their aims and search, cite sources, and reason well. Both designs need clear choices.

Before choosing, write one sentence naming the question, the literature you need to cover, and what the reader may conclude. Atlas can compare method sources you supply and cite relevant passages. Check those passages and choose the design yourself.

The difference starts with the question

A scoping question might ask: How has a concept been defined, measured, and studied across a field? The output maps work found within stated limits. The team plans where it will search, which sources count, and what it will chart.

A narrative question might ask: How do several theories explain a problem, and where do they disagree? The output is a reasoned account. The author picks works that help build and test it, tells readers how they were found, and explains why they matter. The chosen set should not imply a full map of the field.

The JBI purpose guidance lists evidence types, concepts, methods, and gaps as possible mapping targets. The SANRA authors, writing about medical reviews, assess aims, search, sources, data, and reasoning. Their scale is not a rule for every field.

When to choose each review

Start with the output. If you need to show what kinds of work exist across a field, a scoping review may fit. If you need to explain and critique ideas for an argument, a narrative review may fit. The same subject can support either design; the question changes the work.

A map needs limits readers can inspect. Name the concept, context, source types, search sites, dates, languages, and selection rules. Chart the traits that answer the question. A broad field can make this a large project; JBI warns that scoping is not always easier than a focused systematic review.

An account needs an argument readers can follow. Explain why the chosen theories, studies, or historical texts speak to the question. Describe how you found and chose them. Include disputes and works that could weaken your reading. A narrative label does not excuse a hidden or one-sided source choice.

If the real question is whether an intervention works, neither label alone solves it. The systematic review versus meta analysis guide explains the focused review process and the separate pooling choice. Ask a methods specialist which design fits before promising an effect estimate.

When the constraint is time, a rapid review may be a better comparison to examine. It makes explicit shortcuts to a focused evidence review and reports what those shortcuts may have missed. A short deadline alone does not turn a scoping map or narrative account into one.

Scoping review vs narrative review

This table is a decision aid.

Its scoping side follows JBI's definition and purpose guidance.

The narrative side draws on the SANRA authors' account of a good narrative review article. Check your discipline and journal rules too.

Table 1: The search row is a sharp boundary. A narrative reviewer can search carefully and describe it well. A scoping team commits to a systematic map under an explicit scope. JBI distinguishes an informal preliminary scan from the scoping-review method.

PRISMA-ScR is the reporting extension for completed scoping reviews. It helps readers see what the team did; it does not conduct the review or certify its quality.

SANRA was developed for narrative articles in medical literature. Do not present either as an automatic rule for every field.

Work through one review-design decision

Imagine a fictional team studying how universities use the phrase “researcher wellbeing.” It has no search results yet. Two possible questions lead to different projects:

1. Map question: “How has researcher wellbeing been defined and measured in university studies since 2015?” The team would define eligible sources, plan a systematic search, screen against stated rules, then chart definitions and measures. Its output could show variation within the searched scope. It could not infer that an unsearched field has no evidence.
2. Argument question: “How do workload and care theories explain the tension between productivity and wellbeing?” The author would select and compare theory papers and relevant studies, explain the search and choice of sources, and develop an interpretation. The output could critique where these theories clash. It could not claim to have mapped every study on researcher wellbeing.

Choose the scoping route if the team needs the map. Choose the narrative route if it needs to test and explain the theory debate.

Neither project has been performed in this example. There are no study counts, gaps, or results to report. The choice concerns what the team would do and what it could claim after the work.

Before gathering sources, the mapping team might write: “We will map definitions and measures since 2015. Our scoping review protocol will name source types, search sites, and charting fields. The map will cover only that scope.” The theory team would instead name its argument, source choices, and works that may challenge it.

The narrative synthesis guide explains a way to bring findings together, including within systematic reviews. Narrative synthesis is a technique; it is not the narrative review design discussed here.

Document the choice and its limits

Record the choice while it can still shape the work. Write the question, expected output, evidence limits, selection plan, and strongest claim the finished work might support. Note who will settle disputes. If the project changes course, keep the earlier note and explain why.

For a scoping review, JBI's protocol guidance calls for a plan set before the search and a clear account of later changes. The final report should show how the team searched and chose sources. A plan cannot ensure that every source was found, but it lets readers inspect the method.

For a narrative review, tell readers what you sought, where, and why those works anchor the account. Name the time or field limits that matter. Trace key claims to sources and address disagreement. A clear account can be useful even when it does not map an entire field.

You can compare supplied method guides and example reviews in Atlas. Put documents you have permission to use in one project. Mention the intended sources in chat and ask how each defines its question, coverage, selection, and reporting.

Open the citations and inspect nearby text. Correct unsupported rows. Then save a note with your choice and open questions. The paper synthesis guide shows how to compare sources before writing a claim.

Atlas compares the documents you select. It does not run a full search, screen records, judge quality, or certify that a design fits your project. Keep the method sources and team choice alongside the note. A citation is a place to check a claim, not a substitute for that check.

Avoid misleading labels and claims

Do not rename a quick background search a scoping review. The word “scoping” here refers to a systematic evidence-synthesis design with a defined mapping question.

JBI's warning is explicit: an informal preliminary exercise is different work. A broad topic or a small deadline does not change that boundary.

Do not describe a narrative review as inherently careless. An author can search carefully, defend selection, assess disagreement, and reason well without promising systematic coverage.

Readers need to know what the account includes, how it was assembled, and what it leaves open. The original SANRA paper makes those elements visible in its medical-review setting.

Finally, keep the method and the writing format apart. A scoping review can describe a map in prose.

A narrative review is a type of article, while narrative synthesis is a way of combining findings that can be used in other review designs.

Choose the review by its question and method, then name the actual synthesis and reporting choices. If a reviewer asks what your label permits them to infer, your decision note should answer without stretching the evidence.