Four positions open. Long EURUSD, long GBPUSD, short USDCHF, long gold. Each was sized at one per cent of the account, so the trader believes four per cent is at risk. In practice the first three are close to the same trade expressed three ways, and if the dollar rallies hard they lose together. The real exposure is nearer three per cent on one bet plus one per cent on another, and knowing that changes what you do with the next signal.
A risk dashboard is one screen that answers that question without arithmetic. It is not a reporting tool for later. It is a live panel you glance at before every entry, and its job is to make the account-level number impossible to ignore.
The four numbers that belong on it
Dashboards fail by including everything. A screen with twenty-five metrics gets ignored the same way a cluttered chart does. Four live numbers cover almost all of the decisions a discretionary trader makes.
- Total risk at stop. The sum, across all open positions, of what you lose if every stop fills. This is the number most traders guess at, and it should be in currency and in percentage of equity.
- Distance to the daily limit. If your rules say stop trading at three per cent down on the day, the dashboard shows how much of that is spent. Realised and unrealised together, because a floating loss becomes a realised one at the wrong moment otherwise.
- Grouped exposure. Positions collapsed into their underlying driver: dollar direction, gold, indices. Four charts can be one bet, and this is the line that says so.
- Current drawdown from peak equity. Not the day, the account. This is the number that should govern position size in the medium term.
Everything else is review material and belongs in the journal rather than on the live screen. Win rate, average hold time and expectancy are useful monthly and useless mid-session.
Grouping exposure without building a risk system
Proper correlation modelling is a quantitative exercise and overkill for a discretionary account. A workable approximation is a fixed group table you write once and revise quarterly, assigning each instrument you trade to a driver bucket with a rough weight. Dollar pairs go into a dollar bucket with a sign, gold and silver into a metals bucket, the equity indices into one bucket because they mostly move together.
The output is a per-bucket risk figure, and the rule attached to it is the useful part: no bucket above a stated share of the account. That single constraint prevents the failure mode where a trader takes six independent-looking setups that turn out to be one position. Traders wanting the real numbers behind the grouping can check a correlation matrix tool, but the fixed buckets do most of the work at a fraction of the effort.
A dashboard reports risk, it does not reduce it. Only position size, stop placement and the decision not to enter do that. Leveraged trading carries a high risk of loss regardless of how well it is monitored.
Building it from what the platform already knows
The data behind all four numbers exists in the account: open positions, stop levels, contract sizes, equity and balance. Assembling it is a matter of pulling positions and computing risk at stop per position, which is contract size multiplied by the distance from entry to stop, converted into account currency.
Three practical builds, in rising order of effort. A spreadsheet fed by a manual position list takes ten minutes to build and thirty seconds per update, which is enough for a trader who holds a handful of positions for days. A platform-side indicator or script reads the terminal's own position list and prints the numbers in a corner of the chart, updating live. A separate application reading the account through an API gives the most room but needs maintenance, and maintenance is where private tools die.
Start with the spreadsheet. If it gets used daily for a month, promote it. Building the API version first is the most common way to end up with no dashboard at all.
Where the daily limit line goes
The distance-to-limit figure only works if the limit is set before the session, not adjusted during it. Traders using a hard daily loss cap should have the dashboard change appearance at a threshold, for instance at 70 per cent of the limit spent, rather than only at the limit itself. The warning matters more than the alarm, because by the time the cap is hit the decision has already been made for you.
This mirrors how firms run the same control on the other side of the account. Prop firms enforce daily and overall loss limits in their own risk layer, and the trader who monitors those numbers themselves is never surprised by a breach. The mechanics of the firm-side version are covered in drawdown rules, and understanding how drawdown is measured matters because balance-based and equity-based measurement give different answers at the same moment.
Alerts, and the fatigue trap
A dashboard that pushes a notification for every change stops being read within a week. Two alerts are enough: one at the warning threshold on the daily limit, one when grouped exposure exceeds the bucket cap. Both are actionable, both are rare, and both arrive at a moment where you can still do something. The general principle is covered in alert fatigue management, and it applies to risk tooling more than anywhere else, because the alert you learn to dismiss is the one that mattered.
Platforms differ in how much of this they expose. A terminal that streams position and equity data live, such as the one behind eTrader, makes the panel a display problem rather than a data problem. On platforms where the position feed is harder to reach, the spreadsheet route stays perfectly adequate, and a manually updated dashboard that gets looked at beats an automated one that does not exist.
"If the only place your total risk is written down is your head, you will discover it is wrong on the worst possible day."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- Four live numbers cover most decisions: total risk at stop, distance to the daily limit, grouped exposure and drawdown from peak equity.
- Assign instruments to fixed driver buckets and cap each bucket, which catches the case where several setups are really one position.
- Build the spreadsheet version first and only automate it once you have used it daily for a month.
- Two alerts, a daily-limit warning and a bucket-cap breach, keep the dashboard readable; more than that trains you to ignore it.
Frequently Asked Questions
What is a sensible cap for one exposure bucket?
That is a personal risk decision rather than a standard, and it depends on account size, strategy and how long positions are held. The value of the cap is that it exists and is written down before the session, not the exact number.
Should unrealised profit and loss count towards the daily limit?
Most traders who use a limit seriously include unrealised, because a floating loss can be realised by a stop at any moment. Excluding it means the limit only binds after the damage is booked.
Do I need a dashboard if I only hold one position at a time?
Less urgently, but the drawdown from peak equity line still earns its place. Single-position traders mostly get hurt by size drift after a losing run rather than by correlated exposure.
About the Author
Alex Onta is an Executive Director at SINGUARD. He built eTrader, the terminal, the mobile apps, eTrader Broker, Copytrading, Business and Community, along with the worldwide clustered-server infrastructure it all runs on, with his brother Roman Onta helping on the design, and he leads that division today. Together with Roman he builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals, and the two of them carry worldwide compliance, payment processing and international business structuring side by side. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.