> 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/best-practices/best-practices-by-review-type/systematic-literature-reviews.md).
# Systematic Literature Reviews
Learn about the best practices for conducting systematic literature reviews.
Here the best practices in conducting a systematic literature review are covered.
For step-by-step instructions in **Nested Knowledge**, see the [Systematic Literature Review](/guides/guidance-by-review-type/systematic-literature-review.md) guide. The guidance below applies regardless of the software you use to run your review.
### Frame A Focused Research Question
State your question in a structured format (for example, PICO) before you search. A well-framed question determines your search strategy, your eligibility criteria, and ultimately whether your review answers what it set out to answer.
### Design A Defensible Search Strategy
Search multiple databases, document your exact search strings, and record the date of each search. A reproducible strategy is what allows another reviewer to run your search and get the same result—the standard an SLR is held to.
### Screen With Consistency
Use two independent reviewers and a third to adjudicate disagreements. Predefine your inclusion and exclusion criteria before screening starts, and record a reason for every exclusion at the full-text stage—this is what your PRISMA flow diagram will report.
### Choose An Appraisal Tool That Fits Your Study Designs
Match your critical appraisal tool to the study designs you've included (for example, a tool built for randomized trials won't fit an observational study). Apply it consistently across all included studies, and report the tool and its results, not just a summary judgment.
### Report Against A Recognized Standard
Report your SLR against the PRISMA checklist, and register your protocol (for example, with PROSPERO) before you begin screening where your target journal or use case expects it.
### Next Steps
---
# 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/best-practices/best-practices-by-review-type/systematic-literature-reviews.md?ask=&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.