Your Dealing Desk’s Morning Dashboard: 12 Risk Widgets That Catch Trouble Early

Bad days in a dealing desk rarely start with a single “big” mistake. They start with small misses—an exposure pocket that grows quietly, a bridge that degrades, a toxic cluster that slips past routing rules, or a margin event that arrives faster than your team can react.

A RiskBO “control tower” is a single-screen operating view that lets your risk and dealing teams see the same truth in real time: exposure, routing, P&L drivers, and execution health. Below are 12 practical widgets you can assemble into a control tower that’s designed to prevent incidents—not just explain them after the fact.

1) Net Exposure Heatmap (by symbol, group, and book)

Start with the widget that answers the only question that matters at 9:05 AM: “Where are we actually exposed?” A net exposure heatmap should let you slice quickly by:

• Symbol / asset class (e.g., XAUUSD, NAS100, BTCUSD)
• Client group (retail, VIP, IB-driven cohorts, prop evaluation vs funded)
• Book (A-book, B-book, hybrid buckets)

Operationally, your goal is speed: one glance to spot concentrations and one click to drill into the accounts and positions driving them. If you run multiple servers (e.g., MT5 + cTrader), keep the view normalized so “exposure” means the same thing across platforms.

2) Gross Exposure + Concentration Alerts (top 10 pockets)

Net exposure can look “fine” while gross exposure quietly becomes fragile—especially around correlated symbols (indices, metals, crypto) where moves gap and spreads widen.

A gross exposure widget should show:

• Top 10 concentration pockets (symbol + group + book)
• Exposure vs internal limits (soft/hard thresholds)
• Correlation flags (e.g., NAS100 + US500 + US30 behaving as one risk)

Practical tip: define limits in notional and in stress terms (e.g., “what’s the P&L impact of a 1% move?”). Then align the widget thresholds to your hedging policy and liquidity depth.

3) Real-Time Broker P&L (split by spread, swaps, commissions, slippage)

A dealing desk control tower shouldn’t show only a single P&L number. It should show why you’re up or down.

Build a P&L widget that breaks down:

• Spread revenue vs commission revenue
• Swap/financing impact (especially around rollover)
• B-book trading P&L (mark-to-market and realized)
• Execution costs (negative slippage, rejects, LP fees)

This helps prevent the classic “we’re profitable but something feels off” scenario—where execution quality is deteriorating and hidden costs are rising.

4) A-Book/B-Book Routing Monitor (rules, overrides, and drift)

Routing is where policy meets reality. Your control tower should show whether your A/B logic is behaving as intended right now.

Key elements for this widget:

• Routing distribution by symbol and group (A%, B%, hybrid%)
• Rule triggers (what conditions caused routing decisions)
• Manual overrides and who applied them
• Routing drift (today vs 7-day baseline)

If you see routing drift without a clear market reason (news day, volatility regime change), treat it as an incident precursor. Many “bad days” start with subtle routing misconfiguration.

5) Hedge Coverage & Hedge Latency (are you actually neutral?)

A hedging automation setup is only as good as its coverage and timing. A hedge widget should answer two questions:

1. Coverage: “What % of intended exposure is hedged?”
2. Latency: “How long between client fill and hedge fill?”

Include:

• Hedge ratio by symbol (target vs actual)
• Open hedge backlog (orders pending / failed)
• Median / p95 hedge latency

When volatility spikes, latency becomes P&L. If p95 latency jumps, you want it visible immediately—before the desk starts “feeling” it in unexplained drawdowns.

6) Flow Toxicity Radar (clusters, tags, and trend)

“Toxic flow” is rarely one account. It’s usually a pattern: a cluster of accounts sharing timing, strategy footprint, or execution behavior that consistently extracts value.

A toxicity widget should show:

• Top toxic clusters (not just top accounts)
• Toxicity score trend (hourly/daily)
• Common attributes: IB source, country, instrument set, EA fingerprints (where available), session timing

Use this widget to drive routing actions (A-book, widen risk controls, or apply execution protections) that are consistent with your client terms and local regulations. If you’re unsure what’s permissible, check local regulations and consult compliance.

7) Slippage & Requote Dashboard (by LP, bridge, symbol, session)

Execution quality issues often masquerade as “market conditions.” Your control tower should separate market-wide volatility from your specific execution stack.

Track:

• Positive vs negative slippage distribution
• Reject/requote rates
• Fill ratios and partial fills (where applicable)
• By LP / bridge route / session (Asia, London, NY)

If one LP route suddenly produces worse outcomes, you want to catch it early and re-route before clients, IBs, and support tickets catch it for you.

8) Spread & Markup Integrity (what clients see vs what you intended)

This widget is about preventing accidental reputational damage. It should flag when displayed spreads or markups deviate from your configuration.

Include:

• Configured vs actual spread/markup (by symbol/group)
• Outlier detection (sudden widening or compression)
• Rollover window behavior (expected vs observed)

Operational example: if your intended markup is stable but actual spreads widen only for a specific group, you may have a misapplied group setting, a bridge rule conflict, or a symbol feed issue.

9) Margin & Stop-Out Risk Monitor (accounts at risk, not just totals)

Margin incidents are “fast failures.” By the time support hears about them, it’s too late.

A margin widget should show:

• Accounts approaching margin call/stop-out (top 20)
• Exposure drivers (which symbols are causing the risk)
• Group-level stress (prop evaluation cohorts are often correlated)

This is also where regulatory considerations matter: how margin call/stop-out is defined and communicated can be jurisdiction- and policy-dependent. Ensure your settings and disclosures match your client agreements, and check local regulations.

10) News & Volatility Regime Panel (what changed in the market)

A control tower needs context. Add a small widget that explains why your other widgets are moving.

Keep it simple:

• Volatility regime indicator (e.g., ATR/realized vol vs baseline)
• Scheduled event reminders (major macro releases)
• Symbol-specific “high risk” flags (indices, gold, crypto during spikes)

The goal isn’t to become a news terminal—it’s to prevent misdiagnosing genuine market volatility as a platform or LP failure.

11) Platform/Bridge Health (latency, disconnects, queue depth)

Risk teams often discover infrastructure issues through P&L. That’s backwards.

Your health widget should track:

• Bridge connectivity status and disconnect frequency
• Order processing latency (median/p95)
• Queue depth / backlog (if applicable)
• Price feed freshness (stale ticks detection)

If you operate in low-latency environments (e.g., LD4), small degradations matter. This widget is your early warning system before execution quality and client experience deteriorate.

12) Incident Console (alerts, playbooks, and audit trail)

Finally, give your control tower an “action layer.” A widget that only shows problems creates noise; a widget that routes actions reduces risk.

Include:

• Alert stream (exposure limits, toxicity spikes, hedge failures)
• One-click playbooks (e.g., tighten routing rules, switch LP route, pause trading on a symbol)
• Audit trail (who did what, when, and why)

From a governance standpoint, an audit trail is not optional. It supports internal controls, post-incident reviews, and (where relevant) regulatory expectations around supervision and change management.

The Bottom Line

A dealing desk “control tower” isn’t about more charts—it’s about fewer surprises. If you can see exposure pockets, routing drift, toxic clusters, hedge latency, and execution health on one screen, you prevent most bad days before they start.

RiskBO can be structured into a practical 12-widget dashboard that aligns risk, dealing, and ops around the same real-time signals.

If you’re planning your control tower layout or want help mapping widgets to your A/B and hedging policy, start here: /get-started.