> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/platform/journal/tags-and-playbooks.md).

# Tags, notes and playbooks

Notes, tags, moods and playbooks turn a trade log into a record you can learn from.

A trade log shows what happened. Annotations show why. This page covers the four ways to annotate a trade in the Journal.

## The four annotations

| Name         | What it means                                                                              |
| ------------ | ------------------------------------------------------------------------------------------ |
| **Notes**    | Free text about the trade: the setup, what you saw, what you would change.                 |
| **Tags**     | Short labels you choose, such as "news" or "late entry". Filter by them later.             |
| **Mood**     | How you felt when you took the trade: calm, focused, fomo, revenge, tired or other.        |
| **Playbook** | The named setup the trade belongs to, such as a London sweep or an opening-range breakout. |

## Annotate a trade

{% stepper %}
{% step %}

### Open the trade

Click any trade in the Journal to open its detail view.
{% endstep %}

{% step %}

### Add your annotations

Write a note, add tags, pick a mood and choose a playbook.
{% endstep %}

{% step %}

### Save

The annotations are stored with the trade and appear in every filter.
{% endstep %}
{% endstepper %}

## Playbooks group trades by setup

Create a playbook for each setup you trade. Filter the Journal by playbook and open the stats drawer to see each setup's expectancy in R. The setups that earn their place get more accounts. The ones that do not get cut.

{% hint style="info" %}
Mood is worth logging even when it feels unnecessary. Filtering by "fomo" or "revenge" usually shows exactly where the negative R comes from.
{% endhint %}

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Strategies</strong></td><td>Turn a proven playbook into code.</td><td><a href="/platform/strategies.md">Strategies</a></td></tr><tr><td><strong>R and expectancy</strong></td><td>Read the stats drawer correctly.</td><td><a href="/concepts-and-reference/r-and-expectancy.md">R and expectancy</a></td></tr></tbody></table>


---

# 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.tradesurge.co/platform/journal/tags-and-playbooks.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.