> 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/create-markers-during-an-interview-session.md).

# Create markers during an interview session

Markers let you keep track of important moments that occur during an interview session. Whether you want to remember a key quote said by your participant or want to keep tabs on topics of conversation, markers let you create easy points of reference to come back to during analysis.

{% hint style="info" %}
Session moderators and observers can create markers. When viewing markers, you’ll be able to see who created them.
{% endhint %}

**To create a marker during an interview session:**

{% hint style="info" %}
To quickly create a marker, press **Control/Command + M** on your keyboard.
{% endhint %}

{% stepper %}
{% step %}
During the session, click **Mark time** to the right of the session timeline.
{% endstep %}

{% step %}
(Optional) Add a **marker label**. Then, click **Add label**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/MtFDNK3TAfw0Csuk7sVi/47115414025620)
{% endstep %}
{% endstepper %}

Now, you’ve created a session marker. Markers are shown as green lines above the timeline, and you can also view them by opening the **Markers** tab in the right sidebar. Here, you can view who created the marker, the marker’s label, and the marker’s timestamp:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/NCWift7uhwiVYEpcvUS4/47115396059796)

For information on viewing markers while analyzing completed sessions, 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/create-markers-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.