PICO, PECO, and SPIDER frameworks for literature reviews

PICO, PECO, and SPIDER are frameworks for turning a broad topic into a structured literature review question. They help researchers define what to search, what to include, and what evidence matters.

The right framework depends on the review question. PICO is often used for intervention questions, PECO for exposure questions, and SPIDER for qualitative or mixed-methods questions.

This guide explains how to choose between PICO, PECO, and SPIDER and how to use them with AI-assisted literature search.

PICO stands for Population, Intervention, Comparison, and Outcome. It is commonly used for questions about whether an intervention affects an outcome.

PICO helps define:

• Population: who or what is studied.
• Intervention: what is being tested or introduced.
• Comparison: what the intervention is compared against.
• Outcome: what result is measured.

Example question:

"In graduate students, does structured AI literacy training improve citation verification compared with standard research instruction?"

PICO works best when the review asks about effects or interventions.

PECO stands for Population, Exposure, Comparison, and Outcome. It is useful when the question is about exposure rather than intervention.

PECO helps define:

• Population: who or what is studied.
• Exposure: the condition, behavior, factor, or context.
• Comparison: unexposed or differently exposed group.
• Outcome: result or association.

Example question:

"Among early-career researchers, how is exposure to AI writing tools associated with citation-checking behavior compared with researchers who do not use them?"

PECO is often useful for observational research questions.

SPIDER stands for Sample, Phenomenon of Interest, Design, Evaluation, and Research type. It is often used for qualitative and mixed-methods review questions.

SPIDER helps define:

• Sample: who or what is included.
• Phenomenon of interest: what experience, behavior, or process is studied.
• Design: study design.
• Evaluation: outcomes, perceptions, or findings.
• Research type: qualitative, quantitative, or mixed.

Example question:

"How do doctoral students experience supervisor expectations when using AI tools during literature review work?"

SPIDER is useful when meaning, experience, or process matters.

Choose the framework that matches the question type. Do not force every review into PICO.

Use PICO when:

• There is an intervention.
• An outcome is measured.
• A comparison matters.
• Effect evidence is central.

Use PECO when:

• There is an exposure.
• The study is observational.
• Association matters.
• Random assignment is not expected.

Use SPIDER when:

• Experience, perception, or process matters.
• Qualitative evidence is central.
• Study design varies.
• Concepts are not easily measured as outcomes.

The framework should clarify the question, not distort it.

Frameworks improve search by turning the question into concept blocks. Each block can become keywords, synonyms, and database search fields.

For example, PICO can produce:

• Population terms.
• Intervention terms.
• Comparison terms.
• Outcome terms.

SPIDER can produce:

• Sample terms.
• Phenomenon terms.
• Design terms.
• Evaluation terms.
• Research type terms.

This makes search easier to test and revise.

For search-string examples, see AI literature review search strings.

Frameworks improve screening because each element can become an inclusion or exclusion criterion.

Screening questions may include:

• Does the population fit?
• Is the intervention or exposure relevant?
• Is the outcome measured?
• Is the phenomenon of interest central?
• Does the study design fit?
• Is the source type allowed?

This makes screening less subjective. Reviewers can point to a framework element when making decisions.

For criteria, see inclusion and exclusion criteria for literature reviews.

AI can help generate framework options, suggest synonyms, identify missing elements, and test whether the question is searchable.

Useful prompts:

• "Convert this topic into possible PICO questions."
• "Suggest PECO elements for this exposure question."
• "Build a SPIDER framework for this qualitative review."
• "List synonyms for each framework element."
• "Identify which element makes the question too broad."

Then test the output against actual literature. A clean framework still needs evidence.

For question refinement, see how to refine a research question with AI literature search.

Avoid using a framework mechanically. Frameworks are tools for thinking, not forms to fill at any cost.

Common mistakes:

• Forcing qualitative questions into PICO.
• Adding a comparison when none is needed.
• Defining outcomes too broadly.
• Using population terms that are too vague.
• Ignoring source type.
• Creating search blocks that return no useful records.
• Treating the framework as final before testing it.

Revise the framework after test searches and supervisor feedback.

Frameworks help synthesis by defining what comparisons matter. They should not disappear after search.

Use framework elements to organize:

• Evidence tables.
• Method comparisons.
• Outcome groups.
• Theme sections.
• Full-text screening reasons.
• Gap claims.

For example, if PICO defines the outcome, the synthesis should compare how included studies measured that outcome.

For synthesis planning, see how to build a synthesis matrix for a literature review.

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 test PICO, PECO, SPIDER, or other question frameworks through natural-language academic search. Deep Search, Scholar Agent, and Inspiration Discovery can be used to search around populations, methods, outcomes, concepts, or phenomena.

Paper cards show source labels, summaries, authors, publication details, and preview images, helping researchers judge whether search results match framework elements. Papers can be saved or uploaded into My Library, and Library QA can answer questions based on the user's own paper set.

WisPaper can support search and triage around a structured question. The researcher still defines the framework and verifies whether sources fit it.

Try WisPaper