Scoping review vs systematic review: which one do you need?

Scoping reviews and systematic reviews are both structured ways to review literature, but they answer different questions. A scoping review maps what exists. A systematic review answers a focused question using explicit methods for finding, selecting, and synthesizing evidence.

Choosing the wrong review type creates problems later. A broad question forced into a systematic review becomes unmanageable. A focused evidence question handled as a scoping review may not answer what readers need.

This guide explains how to choose between a scoping review and a systematic review.

A scoping review maps the size, range, and nature of literature on a topic. It is useful when the field is broad, emerging, fragmented, or not ready for a narrowly focused evidence synthesis.

A scoping review often asks:

• What evidence exists?
• Which concepts are used?
• Which methods appear?
• Which populations are studied?
• What source types are available?
• Where are the gaps in coverage?
• How has the field developed?

The main output is a map of the literature rather than a single answer about effectiveness or impact.

A systematic review answers a focused research question using a defined search, screening, extraction, appraisal, and synthesis process. It is designed to reduce bias and make review decisions transparent.

A systematic review often asks:

• Does an intervention work?
• What is the effect of an exposure?
• Which method performs better?
• What evidence supports a specific outcome?
• What are the risks or benefits of an approach?

The question is usually narrower than a scoping review question. The method also carries stronger reporting expectations.

For AI-related review planning, see AI in systematic reviews.

The main difference is purpose. Scoping reviews map the field. Systematic reviews answer a focused evidence question.

Use a scoping review when you need to understand:

• What has been studied.
• How a concept is defined.
• Which methods are used.
• Where evidence is concentrated.
• Which gaps may deserve future research.

Use a systematic review when you need to determine:

• What the evidence shows about a specific question.
• Which studies meet strict criteria.
• How findings compare.
• How study quality affects conclusions.

If your question starts with "what exists," scoping may fit. If it starts with "what works," systematic may fit.

Choose a scoping review when the literature is too broad or too mixed for a focused systematic review.

Scoping reviews fit when:

• The topic is emerging.
• Definitions vary.
• Methods are diverse.
• The goal is to identify evidence types.
• The review will map research activity.
• You want to clarify whether a later systematic review is possible.
• You need to include multiple source types.

Scoping reviews are especially useful early in a research area, thesis project, or grant-planning process.

For field mapping, see how to build a literature review evidence map.

Choose a systematic review when the question is narrow enough to support explicit search, selection, extraction, and synthesis.

Systematic reviews fit when:

• The population or context is clear.
• The intervention, exposure, method, or concept is defined.
• Outcomes can be compared.
• Inclusion criteria can be applied consistently.
• Source quality matters to the conclusion.
• Readers need an evidence-based answer.

If the review cannot define what counts as relevant, it may not be ready for systematic review design.

Scoping review questions are broad and map-oriented. Systematic review questions are focused and answer-oriented.

Scoping examples:

• "What methods have been used to study X?"
• "How is X defined across disciplines?"
• "What evidence exists on X in Y setting?"

Systematic examples:

• "Does X improve Y in Z population?"
• "What is the effect of X compared with Y?"
• "Which method detects X most accurately?"

If your question has too many moving parts, start with scoping. If your question can be turned into eligibility criteria, systematic review may be possible.

For frameworks, see PICO, PECO, and SPIDER frameworks for literature reviews.

Both review types need criteria, but the strictness differs. Scoping reviews may allow broader source types and methods. Systematic reviews usually need tighter eligibility rules.

Scoping criteria may focus on:

• Topic relevance.
• Concept coverage.
• Source type.
• Date range.
• Language.
• Context.

Systematic criteria may focus on:

• Population.
• Intervention or exposure.
• Comparator.
• Outcome.
• Study design.
• Quality requirements.

Loose criteria are not a weakness in scoping review if the purpose is mapping. Loose criteria are a problem in systematic review if they prevent consistent decisions.

AI can help both review types, but it should not decide the review type for you. The decision depends on the research purpose.

AI can support scoping reviews by:

• Finding candidate papers.
• Grouping topics.
• Summarizing definitions.
• Mapping methods.
• Identifying source types.

AI can support systematic reviews by:

• Suggesting search terms.
• Prioritizing screening.
• Helping inspect full texts.
• Suggesting extraction fields.
• Checking citations.

For AI boundaries, see responsible AI automation checklist for research teams.

Avoid choosing a review type because it sounds more impressive. Choose based on the question.

Common mistakes:

• Calling a broad mapping project systematic.
• Calling a focused evidence question scoping.
• Skipping protocol planning.
• Using AI search without source criteria.
• Ignoring study quality when the conclusion depends on it.
• Treating all source types the same.
• Claiming a gap without mapping the evidence.

Review type is a method decision. It shapes every later step.

Turn the advice into a repeatable workflow by defining the decision you need to make, the evidence required for that decision, and the record that will prove how the decision was made. In review planning, the problem is rarely one missing tool. The problem is usually that search, reading, checking, and writing happen in separate places without a shared rule.

Use a short operating routine:

• Name the review question or subquestion.
• Define the source set you are working from.
• Decide what counts as enough evidence for the next step.
• Apply the same criteria to every paper in that step.
• Mark uncertain cases instead of forcing a clean answer.
• Keep source locations for claims that may enter the final review.
• Review the workflow after each major search, screening, or writing session.

This routine keeps the work moving without making the review careless. It also gives supervisors, collaborators, and future you a way to understand why the source set changed.

Record the pieces that would be hard to reconstruct later. You do not need a diary of every click, but you do need enough detail to explain the path from question to source to claim.

For this topic, the most useful record usually includes scope, criteria, tool use, review type, human checks, and reporting notes. Add the date, tool or source used, reviewer status, and next action. If AI assisted the step, write down what it helped with and what a human checked.

The record should distinguish discovery from evidence. A tool may help find a paper, but the paper itself must support the claim. A summary may help triage a source, but the original source should support any statement that appears in the literature review.

Before writing, check whether the workflow has produced usable evidence or only useful notes. Notes help you think. Evidence supports a sentence.

Ask:

• Which claim will this source support?
• Is the claim narrower than the evidence?
• Have methods, sample, outcome, or concept details been checked?
• Are limitations visible?
• Are conflicting papers handled rather than ignored?
• Is the citation real, current, and relevant?
• Can another reader understand how this source entered the review?

If the answer is unclear, keep the point in notes rather than moving it into the draft. This is the small pause that prevents AI-assisted research from becoming polished but weak writing.

WisPaper can help researchers explore the literature before choosing or refining a review type. Deep Search, Scholar Agent, and Inspiration Discovery support natural-language academic search, which can help users see whether a topic is broad, narrow, mature, or fragmented.

Paper cards show source labels, summaries, authors, publication details, and preview images. This helps with early triage and source inspection. Papers can be saved or uploaded into My Library, and Library QA can answer questions based on the user's own paper set.

That workflow can support review planning, but the researcher still decides whether the project should be scoped, systematic, narrative, or another review type.

Try WisPaper