> 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.md).

# Journal

The Journal logs every trade across every account, so you can review what happened and refine your strategy.

The Journal is where review turns into refinement. Every trade from every account lands here with its R result. You filter, annotate and group trades until the pattern behind your results is clear.

{% hint style="info" %}
**Early access.** The Journal fills with trades once trading opens on Bybit demo, for invited traders.
{% endhint %}

## Trades log automatically

You do not type trades in. Every fill the engine records appears in the trade log with its account, strategy and R result.

## Filter down to what matters

Filters stack, so each one narrows the last.

| Name           | What it means                                |
| -------------- | -------------------------------------------- |
| **Account**    | One account or several.                      |
| **Date range** | Any window, from a day to a season.          |
| **Strategy**   | Trades from one strategy or source.          |
| **Tag**        | Trades you tagged yourself.                  |
| **Playbook**   | Trades that belong to one of your setups.    |
| **R band**     | Trades by result, such as losses beyond -1R. |

## Stats for any selection

Open the stats drawer to see expectancy, total R and other R-based numbers for exactly the trades you filtered.

## Every trade has a detail view

Open a trade to see its full record and add notes, tags, a mood and a playbook.

## 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>Tags, notes and playbooks</strong></td><td>Annotate trades so patterns show up.</td><td><a href="/platform/journal/tags-and-playbooks.md">Tags, notes and playbooks</a></td></tr><tr><td><strong>Dashboard</strong></td><td>The whole book at a glance.</td><td><a href="/platform/dashboard.md">Dashboard</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.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.