> 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/what-are-diary-studies-in-dscout/activities-and-entries-in-a-diary-study.md).

# Activities and entries in a diary study

Studies, activities, and entries are the structural elements of a diary study. Getting these three clear makes guidance when building much easier to follow.

* A **study** is the whole piece of research you're asking participants to complete. Most projects consist of one study.
* An **activity** is a distinct task within that study, with its own instructions, question set, and timeframe. A diary study usually has several.
* An **entry** is what a participant sends you each time they answer all of an activity's questions. Some activities ask for one entry; others ask for the same questions to be answered repeatedly, which is where the diary-style rhythm comes from.

{% hint style="info" %}
**Note:** You may still see activities referred to as *parts* in some places. They're the same thing.
{% endhint %}

### What goes into an entry

In each entry, participants answer the combination of open- and closed-ended questions you've written for that activity, and submit whatever media those questions ask for.

Two limits shape how much you can ask for in a single activity:

* **Media:** An activity can include up to **5 photo questions** and **3 video or screen recording questions**. Video and screen recording share that limit of three—so three screen recording questions leave no room for a video question. Both limits are counted along any one path through your skip logic, so if different participants see different questions, what matters is the most any single person could be asked.
* **Questions:** Above **15 questions** in one activity, Dscout warns you at launch and suggests splitting the work into multiple activities. You can dismiss the warning and launch anyway, but it's usually a sign the activity is doing too much.

Participants don't have to finish an entry in one sitting. If they leave partway through, their progress is saved as a draft they can come back to—which also means you can design an activity that deliberately asks them to go away and do something before continuing.

### Activities that ask for a single entry

If you have a specific set of questions you want answered once—more like a survey or an interview guide—set the activity's entry requirement to one. In the example below, participants have been asked to submit a single entry answering a set of five questions.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/GZ5DjRoisZFqYBHProED/360048832232)

### Activities that ask for multiple entries

You can also design an activity so participants answer one set of questions several times, submitting a new entry each time. This is the pattern that makes a diary study a diary study: the same questions, asked repeatedly, capturing a different moment each time.

In the example below, participants have been asked for a minimum of three entries to capture different snacking moments. They answer the same four questions each time.

Q1 \[VIDEO PROMPT]\
**Take a 30 second video of the snack you're eating right now! (Please make sure you're in a well-lit and quiet space so we can see & hear you clearly!)**

Q2 \[OPEN END]\
**What is this snack you just showed us?**

Q3 \[SINGLE SELECT]\
**Which of the following best describes why you chose this snack on this occasion?**

* Healthiness
* Cost
* Taste
* Convenience
* Other (tap to type)

Q4 \[SINGLE SELECT]\
**Where are you right now?**

* Home
* Someone else's home
* Work/school
* On the go/in transit
* In another public space
* Other (tap to type)

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/xgLEEVcuvJWF70qZ381E/14564034635156)

### Entries keep coming until you close the study

The number of entries you set is a **minimum**, not a cap. Participants can submit more if they want to, and they can keep adding entries to any activity they've already finished.

{% hint style="info" %}
**Note:** There's no way to close an individual activity. Due dates set expectations, but they don't stop submissions: an activity stays open to new entries until you [close the study](/study-basics/edit-close-or-relaunch-studies/close-a-study.md) or [close that participant](/recruit-participants/working-with-participants/close-or-re-open-a-participant.md). For more information, see [Activity due dates and reminders](/diary-studies/create-a-diary-study/activity-due-dates-and-reminders.md).
{% 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/diary-studies/what-are-diary-studies-in-dscout/activities-and-entries-in-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.
