> 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/dashboard.md).
# Dashboard
The Dashboard shows every connected account in one view, measured in R.
The Dashboard is the review step of the loop. It shows every account you run on one screen, so you can see whether your strategy is holding up across the whole book. Every number is in R.
{% hint style="info" %}
**Early access.** The Dashboard fills with results once trading opens on Bybit demo, for invited traders.
{% endhint %}
## What you see
| Name | What it means |
| ------------------------- | ------------------------------------------------------------------------------ |
| **KPI strip** | Headline numbers across the selected accounts, such as total R and expectancy. |
| **Chart tabs** | Equity and performance over time, in R. |
| **Trading-days calendar** | Each day coloured by result. Open a day to see its trades. |
| **Live positions** | What is open right now, per account. |
| **Trade history** | Closed trades with their R result. |
| **Account cards** | Each account's balance, phase and progress against its Rules & Limits. |
| **Surge score** | A 0 to 100 readout of expectancy and consistency. In beta. |
## Why R, not win rate
A 70% win rate can still lose money. Expectancy in R tells you what each trade is worth on average, so it is the number TradeSurge leads with. See [R and expectancy](/concepts-and-reference/r-and-expectancy.md).
## Trading days count toward payouts
Firms usually require a minimum number of trading days before a payout. The calendar shows which days count, meaning days with at least one trade.
## Next steps
---
# 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/dashboard.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.