> For the complete documentation index, see [llms.txt](https://help.topstepx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.topstepx.com/components/performance-stats/journalling.md).
# Journalling
Journalling allows traders to add notes to both trading days and individual trades.
## Adding Notes to Trade Days
To add a note to your trade day, follow these steps:
1. Navigate to your Performance Stats page on the trading platform.
2. Scroll down to the Calendar
3. Click on a Calendar Day
4. Click the Add Journal button
5. Write a journal entry
6. Click Save Journal
> A Note icon will appear on the calendar day if a Trading Day note or an Individual Trade note exists on that day.
## Adding Notes to Individual Trades
To add notes to individual trades, you may do so through the Calendar or the Trades Panel within your Performance Stats page.
1. Navigate to your Performance Stats page on the trading platform.
2. Access the Trades panel by either:
1. Clicking on a Calendar Day or
2. Scrolling down to the Trades panel
3. Click the Add Journal icon
4. Write a journal entry
5. Click Save Journal
---
# 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.topstepx.com/components/performance-stats/journalling.md?ask=&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.
