Beyond PICO: Choosing the Right Question Framework (PEO, PICo, SPIDER, PCC, and More)

If a supervisor or reviewer has told you your PICOT question "does not fit," they are almost always right, and the fix is not to force it. PICO was built for one job: structuring quantitative questions about whether a treatment works. When your question is about lived experience, about mapping a field, about an exposure with no intervention, or about a policy, PICO distorts it. The distortion then propagates into your search and your eligibility criteria, which is how a badly matched framework turns into a protocol that gets sent back.

The good news is that the question-framework problem is solved. There is a purpose-built mnemonic for almost every review and question type, most of them codified by JBI, and choosing the right one is a short, defensible decision. This guide gives you each framework with a worked nursing example, a decision table you can actually apply, and the practical link most guides skip: how the framework you pick drives your search strategy and your eligibility criteria. When you want that decision checked before you build a whole review on it, our PICOT and question-formulation service does exactly this.

Quick Answer:

PICO fits the effectiveness and intervention questions. For other question types, use the framework built for it: PICo (JBI) or SPIDER for qualitative and experiential questions, PCC for scoping reviews, CoCoPop for prevalence, PIRD for diagnostic accuracy, PEO or PECO for exposure and etiology, SPICE or ECLIPSE for service and policy questions, PerSPEcTiF for complex interventions, BeHEMoTh for searching for theory, and CIMO for realist questions. Match the framework to your review type first, then turn its elements into search concept blocks, but do not search every element: leave out the outcome, which reduces sensitivity. Above all, your stated framework must match your actual eligibility criteria, or a reviewer will send the protocol back.

Why PICO Is a Tool, Not the Tool

PICO came from evidence-based medicine, introduced by Richardson and colleagues in 1995 as a way to structure a well-built clinical question into Population, Intervention, Comparison, and Outcome (Richardson et al., 1995). The T for Time and the S for Study design were added later, giving PICOT and PICOS. It works beautifully for the question it was designed for: Does this treatment, compared with that one, change this outcome, in this population?

The problem is that PICO presumes three things: a defined intervention, a comparator, and a measurable outcome. Many perfectly good research questions have none of those. A qualitative study of patients' experiences has no intervention and no comparator. A scoping review maps a field and does not test an outcome. An exposure study looks at a risk factor that no one assigned. When you force these into PICO, you end up either inventing elements that do not exist, which biases the review, or leaving PICO's slots empty, which signals to a reviewer that the framework was wrong. This is why the intervention-versus-everything-else distinction is the first fork, and if you are still deciding what kind of review you are running, our guide on choosing the right evidence synthesis settles that upstream.

The Frameworks, With a Worked Example for Each

Each framework below suits a specific question type. The worked examples are nursing and health questions, so you can see the shape of a well-formed question in each.

PICO / PICOT / PICOS is for effectiveness and intervention questions. Population, Intervention, Comparison, Outcome, plus Time or Study design. Example: In adult inpatients with type 2 diabetes, does nurse-led discharge education, compared with standard physician instructions, reduce 30-day readmissions within six months? This is the canonical DNP and MSN form, and building it well is its own skill, covered in our guide on writing a PICOT question.

PICo is the JBI framework for qualitative reviews: Population, Phenomenon of Interest, Context. Note the lowercase o, which distinguishes it from PICO. There is no outcome, because the phenomenon of interest replaces it. Example: What are the experiences of adolescents with type 1 diabetes managing their condition at school?

PEO is for qualitative and observational questions with an exposure rather than an intervention: Population, Exposure, Outcome, with no comparator. Example: What are the experiences of first-time mothers of breastfeeding in the first six weeks postpartum? PEO is often confused with PECO, so keep them distinct: PEO has no comparator and suits nursing and qualitative work, while PECO adds a Comparator and belongs to environmental and etiology reviews (Morgan et al., 2018). Use PECO when you are comparing an exposed group with an unexposed one on a health outcome.

PCC is the JBI framework for scoping reviews: Population, Concept, Context. There is no outcome or intervention, because a scoping review maps rather than tests. Example: What quality-of-life questionnaires are available for pediatric patients following tonsillectomy for chronic infection or sleep-disordered breathing? Scoping reviews report against PRISMA-ScR (Tricco et al., 2018), and we cover the full method in our guide on writing a scoping review. Because a scoping review is a distinct deliverable, our scoping review service is built around PCC and PRISMA-ScR.

SPIDER is for qualitative and mixed-methods questions: Sample, Phenomenon of Interest, Design, Evaluation, Research type (Cooke, Smith, & Booth, 2012). Example: What are young parents' experiences of attending antenatal education, explored through qualitative interviews and focus-group studies? One important caveat: SPIDER trades sensitivity for specificity. A comparison study found PICO retrieved all known relevant papers while SPIDER missed several, so if completeness matters, use SPIDER to structure the question but run a broader PICO-style search (Methley et al., 2014).

SPICE is for service evaluation and qualitative questions: Setting, Perspective, Intervention or Interest, Comparison, Evaluation (Booth, 2006). It splits PICO's population into setting and perspective and replaces outcome with the broader evaluation. Example: For teenagers in a community clinic, from the smokers' perspective, do Quit Kits versus no support increase successful quit attempts?

ECLIPSE is for health policy, management, and service questions: Expectation, Client group, Location, Impact, Professionals, Service (Wildridge & Bell, 2002). Use it where there is no discrete clinical intervention. Example: What is the impact of a nurse-led discharge-coordination service for older inpatients in an acute hospital, from the perspective of ward nurses and managers, on reducing delayed discharges?

PerSPEcTiF is for complex interventions and context-heavy qualitative synthesis (Booth et al., 2019). It captures perspective, setting, phenomenon, environment, optional comparison, timing, and findings, and is cited in the Cochrane Handbook for complex-intervention reviews.

BeHEMoTh is for searching for theory: Behavior of interest, Health context, Exclusions, Models or Theories (Booth & Carroll, 2015). Use it in realist synthesis or best-fit framework synthesis when you need to locate theories, not just empirical studies.

CIMO is for realist and management questions: Context, Intervention, Mechanisms, Outcomes. It foregrounds the mechanism, the "what works, for whom, in what circumstances, and why" that PICO cannot represent.

Two more JBI mnemonics complete the set: CoCoPop (Condition, Context, Population) for prevalence and incidence reviews, and PIRD (Population, Index test, Reference test, Diagnosis of interest) for diagnostic test accuracy.

Table 1: The Question Frameworks and Their Elements

The Decision: Matching Review Type to Framework

The single most useful move is to diagnose your review type first, then read the framework for it. Do not start from PICO and try to adapt. Start from the question.

Table 2: Which Framework for Which Review

This mapping is corroborated across JBI, Cochrane, and the major university library guides, which converge on the same review-type-to-mnemonic assignments. The JBI Manual is explicit that each review type has its own mnemonic, which is why a scoping review uses PCC and not PICO. Getting this right at the question stage is what keeps the rest of the review coherent, and it feeds directly into the protocol, where the framework becomes your eligibility criteria, and our protocol and registration service will set you up correctly.

How the Framework Drives Your Search and Eligibility Criteria

This is the practical link most guides omit, and it is where a good framework choice pays off. Each element of your framework becomes a search concept block: synonyms within a block joined with OR, blocks joined with AND, using both subject headings and free text.

But you should not search every element. The established guidance and the empirical evidence are to keep the concept count low and generally not to search for the outcome. Outcomes are described inconsistently across studies and are often unknown in advance, so searching for them risks excluding relevant papers. A study of Cochrane reviews found that including outcomes in the search was associated with potentially exaggerated results, and the guidance is to leave outcomes out unless the search is multi-stranded (Frandsen et al., 2022). This applies doubly to scoping searches, where PCC has no outcome, and to qualitative searches, where the phenomenon of interest replaces it. Turning framework elements into a sensitive, well-structured search is precisely what our search strategy service handles.

The framework also becomes your eligibility criteria directly; its elements are your inclusion and exclusion rules, and it appears in the objectives section of a PROSPERO registration or a JBI protocol. One note: PROSPERO does not register scoping reviews, so a PCC-framed scoping review goes on the Open Science Framework instead.

The DNP Problem: Forcing PICOT Onto the Wrong Question

PICOT is taught as near-universal in DNP and MSN programs, and it drives the literature search in CINAHL and MEDLINE. But it is frequently misapplied, and the evidence is striking. A national evaluation of DNP projects found that of the projects that identified a PICOT question, only a small fraction actually followed the method; every one was an intervention question, and the average project contained multiple formatting errors, missing comparisons, directional outcomes, and using the question as the project's purpose statement (Milner et al., 2024). The authors warn that these gaps lead to biased searches and jumping to non-evidence-based solutions.

The core DNP error is forcing a PICOT onto a project that is not an intervention comparison. A quality improvement project runs on an aim statement and the Model for Improvement with PDSA cycles, not a comparative PICOT, and misclassifying one as the other is a common reason committees send projects back. If you are unsure which category your project falls into, our guide on QI versus research versus EBP draws the line, and a mismatched question is one of the practice-gap problems that sink DNP proposals. For qualitative DNP work, use PICo or SPIDER, not a forced PICOT. Our DNP project support matches the framework to the project type before the proposal goes to the committee.

A practical CINAHL and MEDLINE tip: when a full PICOT search returns too little, dropping the comparison and outcome and searching only population and intervention usually retrieves more. That is the same " don't search every element " principle in daily use.

Common Mistakes That Get Protocols Sent Back

The failures are predictable. Forcing PICO onto a qualitative question, when PICo or SPIDER was the right tool. Inserting a comparison element when there is no comparator, since many good questions legitimately have none. Conflating the framework with the search strategy by searching every element, especially outcomes. Writing a question so broad that it cannot be answered. Using PICOT for a scoping review instead of PCC. Omitting context in qualitative work, where context is mandatory in PICo. And the single most common reviewer flag: a mismatch between the framework you stated and the eligibility criteria you actually used. State PICo, then write eligibility criteria with an outcome and a comparator, and the incoherence is obvious.

Each of these is a decision made at the question stage, before any writing, which is why they cannot be patched later. The question framework is load-bearing.

Frequently Asked Questions

What is the difference between PICO and PICo?

Capitalization signals the difference. PICO (all capitals) is for quantitative intervention questions: Population, Intervention, Comparison, Outcome. PICo (lowercase o) is the JBI framework for qualitative reviews: Population, Phenomenon of Interest, Context. PICo has no outcome and no comparator, because in qualitative work, the phenomenon of interest takes the place of a measured outcome. Using PICO for a qualitative question is one of the most common framework errors.

Which framework should I use for a scoping review?

PCC: Population, Concept, Context. It is the JBI-recommended framework for scoping reviews and pairs with the PRISMA-ScR reporting standard. A scoping review maps a field rather than testing an effect, so it has no intervention, comparator, or outcome; the Concept captures what you are mapping. Note that PROSPERO does not register scoping reviews, so register a PCC-framed scoping review on the Open Science Framework instead.

Can I use PICOT for a qualitative study?

No. PICOT presumes an intervention, a comparator, and a measurable outcome, none of which fit a qualitative question about experience or meaning. Use PICo (Population, Interest, Context) or SPIDER (Sample, Phenomenon of Interest, Design, Evaluation, Research type) instead. Forcing a qualitative question into PICOT produces empty or invented elements and signals to a reviewer that the framework was wrong for the study.

What is the difference between PEO and PECO?

Both handle exposure questions, but PECO adds a comparator. PEO (Population, Exposure, Outcome) has no comparator and is common in nursing and qualitative or observational work. PECO (Population, Exposure, Comparator, Outcome) explicitly compares an exposed group with an unexposed one and is standard in environmental health and etiology reviews. Choose PECO when your question compares exposed and unexposed groups on a health outcome; choose PEO when there is no meaningful comparison group.

What framework should I use for a DNP quality improvement project?

Usually not a PICOT. A quality improvement project runs on an aim statement and the Model for Improvement with PDSA cycles, not a comparative intervention question. Forcing a PICOT onto a QI project is a frequent reason committees send projects back. If your DNP work is an evidence-based practice implementation, PICOT may fit; if it is QI, use the aim-and-PDSA structure; if it is qualitative, use PICo or SPIDER. Confirm which category your project is before formulating the question.

Is SPIDER better than PICO for qualitative reviews?

Not for comprehensive searching. SPIDER was designed for qualitative questions and is more specific, but a comparison study found it missed relevant studies that PICO retrieved. The practical approach is to use SPIDER to structure the question conceptually, then run a broader, more sensitive PICO-style search so you do not miss eligible studies. Where completeness is essential, favor the more sensitive search even for a qualitative review.

Do I have to search every element of my framework?

No, and you generally should not. Keeping the concept count low makes the search more sensitive, and the outcome element in particular should usually be left out, because outcomes are reported inconsistently and searching them risks excluding relevant studies. This is doubly true for scoping searches (PCC has no outcome) and qualitative searches (the phenomenon of interest replaces the outcome). Search the population and the intervention, exposure, or concept; add outcomes only in a multi-stranded search.

Choosing the Framework That Fits Your Question

The question framework is the first decision in a review, and it governs everything after it: the search, the eligibility criteria, the protocol, and whether a reviewer accepts the whole thing. Diagnose your review type first, then read the framework for it: PICO for effectiveness, PICo or SPIDER for qualitative, PCC for scoping, PEO or PECO for exposure, and the rest for their specific cases. Turn the elements into search blocks, but leave the outcome out. And make sure the framework you name matches the eligibility criteria you write. Do that, and you never again have to force a question into a shape that does not fit it.

If your question has already come back, or you want it matched to the right framework before you build the review, send us your topic and review type. A specialist will formulate it correctly and return an itemized quote within 2 to 4 business hours, no obligation.