> For the complete documentation index, see [llms.txt](https://docs.senseloaf.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senseloaf.ai/hiring-pipeline/notes.md).

# Notes

Capture context and collaborate directly within your hiring workflow

Notes let you and your team capture updates, share context, and communicate decisions without leaving the platform. Whether you're flagging a delay, aligning on a candidate before an interview, or handing off to a colleague, Notes keeps all of that context attached to the candidate where it belongs.

This is especially useful in multi-recruiter setups where decisions and updates need to be visible to everyone involved in the hire.

### What Notes does

* Lets you add notes to any candidate at any stage
* Accessible from both the candidate listing and the detailed report card
* Keeps context attached to the candidate — visible to your entire team
* Supports collaboration without switching to a separate tool

### 1. How to open Notes

Notes are accessible in two places so you can add context quickly whether you're in the list view or reviewing a candidate in detail.

**From the candidate listing**

<figure><img src="https://1117388020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGO7J9uIHFkn8y0ZeBqYC%2Fuploads%2F2KRmk1EsYVZYIVVsCxIb%2FScreenshot%202026-07-10%20at%2016.59.50.png?alt=media&amp;token=6ed9053a-b3e0-4b4c-93c2-ff5bcd3e3f07" alt=""><figcaption><p>Add Notes from the candidate listing</p></figcaption></figure>

A notes icon sits at the end of each candidate row alongside other primary actions. Clicking it opens the notes panel directly, you don't need to leave the listing page to add or review notes.

**From the detailed report card**

<figure><img src="https://1117388020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGO7J9uIHFkn8y0ZeBqYC%2Fuploads%2Fzl0GgJOMFLkavVDZYtTE%2FScreenshot%202026-07-10%20at%2017.01.23.png?alt=media&amp;token=d7df2c4a-ade2-4a49-9972-f79e5b5d2022" alt=""><figcaption><p>Add Notes from report card</p></figcaption></figure>

On the detailed report card, Notes appears directly below the candidate details. You can add a note right there without navigating away. To view previously added notes, click the icon next to **Add Note** to open the notes history.

### 2. When to use Notes

Notes are most useful in situations where context needs to be captured and shared before a decision is made. A few common scenarios:

**a. Candidate delay update**

A candidate has flagged they'll submit an assignment late. Add a note so your team is aware before the deadline passes.

**b. Pre-interview alignment**

You've confirmed prerequisite details with a candidate before their interview. Log it so the next person in the workflow knows the candidate is ready to proceed.

**c. Internal handoff**

You're passing a candidate to a colleague who will handle the next stage. Leave a note with relevant context so nothing is lost in the handoff.

<figure><img src="https://1117388020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGO7J9uIHFkn8y0ZeBqYC%2Fuploads%2Fsk6DzRwzGetBzKYJPUOY%2FScreenshot%202026-07-10%20at%2017.09.28.png?alt=media&amp;token=94933dab-dc90-4ab1-bc72-0d2bf4d6b68b" alt=""><figcaption><p>Notes Panel</p></figcaption></figure>


---

# 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://docs.senseloaf.ai/hiring-pipeline/notes.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.
