> 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/interview-studies/conduct-an-interview-session/take-notes-during-an-interview-session.md).

# Take notes during an interview session

Ideas are likely to come to you during an interview session, and there’s no better way to remember them than taking notes as they arise. For that, you can make use of Dscout’s in-session note-taking functionality. Notes taken during a session are saved and accessible after the session has ended.

{% hint style="info" %}
Only session moderators and observers can view and add notes. Guests cannot view or add notes.
{% endhint %}

**To add notes during an interview session:**

{% stepper %}
{% step %}
During the session, click **Notes** in the right sidebar. The notes sidebar is displayed.
{% endstep %}

{% step %}
Type your note in the text box at the bottom of the sidebar.
{% endstep %}

{% step %}
Press **Return/Enter** or click the **Create new note** button.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1PEIXwZm9flZYFRCrnPF/47115286756628)
{% endstep %}
{% endstepper %}

Now, your note is added to the session along with a timestamp of when it was created. Any other moderators or observers in the session will be able to see notes added here. You’ll also be able to review these notes later during analysis. For more information, see [View interview session recordings](/interview-studies/view-interview-session-recordings.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/interview-studies/conduct-an-interview-session/take-notes-during-an-interview-session.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.