> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/screeners/copying-screeners-and-questions.md).

# Copying screeners and questions

Your company can have a template for repetitive or routine screeners so you don't have to start from scratch every time. This can be done by creating a screener with the routine questions, then duplicating the screener when using it for a certain study. If only certain questions are needed, you can import select questions.

Follow the steps below to accomplish either one.

## Duplicating a screener

Go to the **Screeners** page of the study you're working on, then follow the steps below:

{% stepper %}
{% step %}
Click the **New Screener** button. You can also click the **N** shortcut key on your keyboard.
{% endstep %}

{% step %}
From the **Create a new screener** pop-up, add an **Internal Title** and an **Internal Description** on their respective textboxes.
{% endstep %}

{% step %}
Click the drop-down field for **Copy a past screener**. Then, select the screener that you'd like to duplicate.
{% endstep %}

{% step %}
Click the **Create screener** button.
{% endstep %}
{% endstepper %}

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/ESCcwCv7ar0p5X8q2rGz/37074100407828)

## Importing questions from an existing screener

Within the **Screener Builder** sub-page of the screener you're working on, follow the steps below:

{% stepper %}
{% step %}
Click the **Add element** drop-down button.
{% endstep %}

{% step %}
Scroll down to the bottom of the drop-down. Click the **Import questions** option.
{% endstep %}

{% step %}
From the **Import questions from another screener** pop-up, click the drop-down field for **Choose a screener**. Then, select the screener containing the questions you'd like to import. If your company has a large number of existing screeners, you can type the name of the screener on the search bar to quickly find it.
{% endstep %}

{% step %}
The questions within the selected screener will appear as a list. Tick the checkbox beside the questions that you'd like to import. You can select multiple questions at a time.
{% endstep %}

{% step %}
Click the **Import questions** button.
{% endstep %}
{% endstepper %}

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/7YWHliVCdcT0mI7ze1QV/37074100409876)

{% hint style="info" %}
**Note:** Private Panels was previously managed outside of Dscout, so you may see a different logo and URL in some places. If you have any questions, contact <support@dscout.com>.
{% endhint %}


---

# 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://help.dscout.com/private-panels/screeners/copying-screeners-and-questions.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.