> 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/studies/export-survey-responses.md).

# Export survey responses

After panelists have answered your surveys or screeners, you can export the collected data and files for study purposes.

## Export screener responses

To export screener responses into a CSV file:

{% stepper %}
{% step %}
Open the study then go to its **Overview** page.
{% endstep %}

{% step %}
Select the panelists.
{% endstep %}

{% step %}
Click the **Bulk Actions** button.
{% endstep %}

{% step %}
Select **Export to CSV** from the drop-down options.
{% endstep %}

{% step %}
A pop-up will appear.

All of the data from all of the screeners will be selected for import by default. You can untick the associated checkboxes to deselect them.

If you'd like to export the panelists' data as well, scroll down the pop-up to the **Panelist Properties** section. Tick the properties that you'd like to export.
{% endstep %}

{% step %}
Once you've selected all of the information that you'd like to export, click the **Export CSV** button.

<div align="left"><img src="https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/MDntBsAojzAunX1s29ij/37060534113300" alt="" width="563"></div>
{% endstep %}
{% endstepper %}

The exported CSV file will look similar to the image below. The panel properties will become the column headers.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/rBGXdcaRFnDzUx5tTGpV/37060555236628)

## Export file submissions

All file submissions, such as documents and videos, can be exported from a study by:

{% stepper %}
{% step %}
Open the study, then click the **Bulk Actions** button.
{% endstep %}

{% step %}
From the drop-down options, select **Export**.
{% endstep %}

{% step %}
Select the submissions you'd like to export.
{% endstep %}

{% step %}
Click the **Export Bulk Files** button at the bottom left of the pop-up.

<div align="left"><img src="https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/8O4PdNmFJYu5w3dytJ0M/37060534115092" alt="" width="563"></div>
{% endstep %}

{% step %}
All files will be compressed in a .zip file. Once done, click the **Download Files (.zip)** button at the bottom left of the pop-up.

<div align="left"><img src="https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/E1Lal5JPLtBW1EYv5isT/37060555238420" alt="" width="563"></div>
{% endstep %}
{% endstepper %}

{% 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/studies/export-survey-responses.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.