> 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/review-workflow/study-inspector.md).

# Study Inspector

Learn how to filter, view, edit, appraise, explore, and download studies in your nest.

**Study Inspector** is your workspace for finding, reviewing, and updating studies across a nest. It brings together each study's record, full text, comments, and decisions from [Screening](/review-workflow/screening.md), [Tagging](/review-workflow/tagging.md), [Meta-Analytical Extraction](/review-workflow/meta-analytical-extraction.md), and [Critical Appraisal](/review-workflow/critical-appraisal.md).

Use it to find a record, correct a decision, update many records, export data, or explore a subset. You can screen, tag, extract, or appraise studies here at any workflow stage.

Filter first, then act. Your filtered list determines the studies you view, update, export, or explore.

### Navigate to Study Inspector

From the Nest menu, select **Study Inspector**.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FcozzvgFccuDfRNOZbmcB%2Fstudy%20inspector%20no%20filters.png?alt=media&amp;token=c478736d-0a48-441d-8ad4-113c07930678" alt="Nest menu with Study Inspector selected."><figcaption><p>Select <strong>Study Inspector</strong> from the Nest menu.</p></figcaption></figure>

### Find Your Way Around

| Page                                                                                             | What it's for                                                               | Start here if                                                                                    |
| ------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| [Filter Studies](/review-workflow/study-inspector/filter-studies.md)                             | Narrow the study list by bibliographic, workflow, and/or search details.    | You need a specific study or a shared trait.                                                     |
| [View and Edit Studies](/review-workflow/study-inspector/view-and-edit-studies.md)               | Read, screen, tag, extract, appraise, edit, or comment on one study.        | You're working study by study.                                                                   |
| [Customize Columns](/review-workflow/study-inspector/customize-columns.md)                       | Choose the fields shown and included in spreadsheet exports.                | You need fields beyond title, author, year, or screening status at a quick glance or for export. |
| [Bulk Actions](/review-workflow/study-inspector/bulk-actions.md)                                 | Update screening decisions, tags, module status, upload documents, in bulk. | You need the same change across many studies.                                                    |
| [Download from Inspector](/review-workflow/study-inspector/download-from-inspector.md)           | Export studies, decisions, tags, data, appraisal answers, or comments.      | You need data per module outside the nest.                                                       |
| [Explore from Study Inspector](/review-workflow/study-inspector/explore-from-study-inspector.md) | Analyze PICO terms, topics, and keywords in a filtered set.                 | You need an overview of a group of studies.                                                      |

A typical workflow is to filter, then review, update, export, or explore the results.

### 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-split">:split:</i><br><strong>Screening</strong></td><td>Review records against your eligibility criteria.</td><td><a href="/review-workflow/screening.md">Screening</a></td></tr><tr><td><i class="fa-file-zipper">:file-zipper:</i><br><strong>Tagging</strong></td><td>Capture structured data from your included studies.</td><td><a href="/review-workflow/tagging.md">Tagging</a></td></tr><tr><td><i class="fa-chart-scatter">:chart-scatter:</i><br><strong>Meta-Analytical Extraction</strong></td><td>Extract outcome data for quantitative analysis.</td><td><a href="/review-workflow/meta-analytical-extraction.md">Meta-Analytical Extraction</a></td></tr><tr><td><i class="fa-user-group">:user-group:</i><br><strong>Critical Appraisal</strong></td><td>Assess included studies against your appraisal system.</td><td><a href="/review-workflow/critical-appraisal.md">Critical Appraisal</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/review-workflow/study-inspector.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.