> 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/diary-studies/create-a-diary-study/add-questions-to-a-diary-study.md).

# Add questions to a diary study

Questions live inside activities. Participants answer the whole set each time they submit an entry, so the question set you write once is the set they'll work through repeatedly—which makes length and clarity matter more here than in a single-session study.

If you haven't built your activities yet, start with [Add activities to a diary study](/diary-studies/create-a-diary-study/add-activities-to-a-diary-study.md).

### Add a question

**To add a question to an activity:**

{% stepper %}
{% step %}
On the **Setup** page, open the **Questions** tab and select the activity.
{% endstep %}

{% step %}
Click **Add question** and choose a question type.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FCylxtUGEEhuSupHVCMTQ%2FDiary_questions.jpg?alt=media&amp;token=8923933f-3eb5-46bf-a7f1-9832ceea117f" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Write your prompt and configure the question's settings.
{% endstep %}
{% endstepper %}

The **Options** menu on each question offers **Duplicate Question**, which is the fastest way to build a set of similar prompts.

For what each type captures, see [Question types in diary studies](/diary-studies/what-are-diary-studies-in-dscout/question-types-in-diary-studies.md) and the full [Question types](/study-basics/question-types.md) reference.

### Choose an entry headline

In each activity you can designate one question as the **Headline**. That question's response then appears on the entry card and on the entry view, which is what makes one entry distinguishable from the next when you're scanning dozens of them.

**To set an entry headline:**

{% stepper %}
{% step %}
Select the question whose response should serve as the headline.
{% endstep %}

{% step %}
Toggle on **Make prompt's response the entry's headline**.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2F2do2L5mWKpTwM0JfOL6B%2FDiary_questions%20(1).jpg?alt=media&amp;token=11361333-6026-4a41-8e5b-fb6561c20389" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Tip:** Pick a short, open-ended question that varies between entries—"What are you eating?" rather than "How did that feel?" An activity with no headline set leaves you with a grid of entries that all look alike, which makes analysis slower than it needs to be.
{% endhint %}

### Recall an earlier answer

You can pipe a participant's earlier response into a later question's text, so the question reads back what they told you.

Type **@** in a prompt to pick the question you want to recall from. Two rules govern what you can recall:

* The recalled question must be **closed-ended**.
* It must be **positioned before** the question doing the recalling.

A question that already contains recall can't itself be recalled from.

For more information, see [Piping (recall) logic](/study-basics/design-a-study/piping-recall-logic.md).

### Decide whether participants can paste

By default, **pasting is disabled on open-ended questions**. This is to encourage in-the-moment, authentic responses rather than text prepared elsewhere, including AI-assisted answers.

However, if you intend to collect complex responses like URLs, you may want to enable participants to copy and paste into an open-ended question. To do that, set the **Copy & paste allowed** toggle to **ON**:

<figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FdfXYgZzYwTBwdzo4cS5M%2FDiary_questions%20(2).jpg?alt=media&amp;token=9485c5ee-aa70-495e-ae29-3ead27385d08" alt=""><figcaption></figcaption></figure>

### Randomize choices and branch

* **Randomize choices** shuffles the answer options on a multiple choice question, so their order doesn't bias responses. Rank questions have their own **Randomize rank choices** setting.
* **Skip logic** sends participants to a different question based on how they answered a closed-ended one. Skip logic works *within* an activity, not across activities. For more information, see [Skip logic in diary studies](/study-basics/design-a-study/skip-logic-in-diary-studies.md).

### How much to ask in one activity

Two limits shape the size of a question set, and both are counted along any single path through your skip logic—so what matters is the most any one participant could be asked, not your total question count.

* **Media:** up to **5 photo questions** and **3 video or screen recording questions**. Video and screen recording share the limit of three.
* **Questions:** above **15**, Dscout warns you at launch and suggests splitting the work across activities. You can dismiss the warning and launch anyway.

For more information, see [Activities and entries in a diary study](/diary-studies/what-are-diary-studies-in-dscout/activities-and-entries-in-a-diary-study.md) and [Media limits](/study-basics/design-a-study/media-limits.md).

{% hint style="success" %}
**Tip:** Remember participants answer this whole set on every entry. A question that's interesting once can be tedious by the fourth time. Focus repeated questions on what's changed for participants between moments, and save the one-off questions for a single-entry activity.
{% endhint %}

### Next steps

Once your questions are written, publish the activity and run through the study on a real device before launching. See [Add activities to a diary study](/diary-studies/create-a-diary-study/add-activities-to-a-diary-study.md) and [Test a diary study](/diary-studies/create-a-diary-study/test-a-diary-study.md).


---

# 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/diary-studies/create-a-diary-study/add-questions-to-a-diary-study.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.