> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/guides/guidance-by-review-type/targeted-literature-review.md).

# Targeted Literature Review

Learn how to set up a targeted literature review in Nested Knowledge.

A targeted or rapid literature review (TLR) answers a focused question for a time-sensitive decision. It uses a narrower scope and a lighter workflow than a systematic literature review (SLR): fewer databases, one reviewer, and extraction limited to what the question needs. Choose a TLR when a decision can't wait for a full SLR and a bounded, documented search is enough to support it.

If your findings will support an HTA submission or a publication that expects comprehensive coverage, see the [SLR guide](/guides/guidance-by-review-type/systematic-literature-review.md) instead.

For general methodology guidance independent of the software, see [targeted literature review best practices](/best-practices/best-practices-by-review-type/targeted-literature-reviews.md).

### Run A TLR In Nested Knowledge

**Inputs:** a focused question with eligibility criteria already known, scoped for a time-sensitive decision.

**Outputs:** a PRISMA-traceable flow diagram plus a descriptive table and summary supporting that decision.

| Stage                  | Recommended tools                                                                                                                                                                                                                                                                                                                                                                                                                                             | Why                                                                                                                                                                                                    |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Search                 | [**Smart Search**](/review-workflow/literature-search/ai-tools-in-search/smart-search.md) to generate a query fast; [**Automatic Search**](/review-workflow/literature-search/add-search/automatic-search.md) against a small, targeted set of databases                                                                                                                                                                                                      | Speed matters for a TLR, so Smart Search gets you to a usable query quickly. A bounded search still needs to be documented.                                                                            |
| Screening              | [**Single Screening, Standard**](/review-workflow/screening/configure-screening.md#choose-your-screening-mode) (one reviewer, one pass); [**Criteria-Based Screening (CBS)**](/review-workflow/screening/criteria-based-screening.md)                                                                                                                                                                                                                         | TLRs are less comprehensive than SLRs, so one reviewer and one pass keep the review proportional to its scope.                                                                                         |
|                        | [**Smart Config: Screening**](/review-workflow/screening/criteria-based-screening/smart-config-screening.md) to draft criteria; [**Smart Screener**](/review-workflow/screening/criteria-based-screening/smart-screener.md) to answer them                                                                                                                                                                                                                    | Smart Config drafts Yes/No eligibility criteria from your research question, and Smart Screener answers them. The AI does the first pass and you review its output, which suits shorter TLR timelines. |
| Tagging and extraction | [**Core Smart Tags**](/review-workflow/tagging/ai-tools-in-tagging/core-smart-tags.md) for a quick PICO baseline; [**Smart Config: Tagging**](/review-workflow/tagging/ai-tools-in-tagging/smart-config-tagging.md) to build a hierarchy; [**Adaptive Smart Tags**](/review-workflow/tagging/ai-tools-in-tagging/adaptive-smart-tags.md) to extract from full texts                                                                                           | Extract only the data points your question requires. Review tags before and after extraction.                                                                                                          |
| Critical appraisal     | Optional: [**Smart Critical Appraisal**](/review-workflow/critical-appraisal/smart-critical-appraisal.md)                                                                                                                                                                                                                                                                                                                                                     | Appraisal is often lighter or skipped in a TLR. If your decision depends on study quality, Smart Critical Appraisal generates recommendations for you to review.                                       |
| Synthesis              | [**Dashboards**](/review-workflow/synthesis/set-up-synthesis-outputs/dashboard-editor.md) for tables; [**Smart Insights**](/review-workflow/synthesis/set-up-synthesis-outputs/smart-insights.md) for evidence-linked summaries; [**Synthesis Chat**](/review-workflow/synthesis/navigate-synthesis-outputs/synthesis-chat.md) for written summaries; [**PRISMA**](/review-workflow/synthesis/navigate-synthesis-outputs/prisma-chart.md) flow diagram export | Most TLRs support a narrower decision or claim, which a descriptive table and summary answer directly.                                                                                                 |

For the full click-by-click workflow, including setting up your nest and building your Dashboard, see [**Conduct a Rapid Review**](/get-started/ai-documentation/conduct-a-rapid-review.md).

### Next Steps

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-list-check">:list-check:</i><br><strong>Conduct a Rapid Review</strong></td><td>Follow the step-by-step workflow in Nested Knowledge.</td><td><a href="/get-started/ai-documentation/conduct-a-rapid-review.md">Conduct A Rapid Review</a></td></tr><tr><td><i class="fa-bullseye-arrow">:bullseye-arrow:</i><br><strong>Targeted Literature Review Best Practices</strong></td><td>Apply methodology guidance alongside this workflow.</td><td><a href="/best-practices/best-practices-by-review-type/targeted-literature-reviews.md">Targeted Literature Reviews</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nested-knowledge.com/guides/guidance-by-review-type/targeted-literature-review.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.