Your Daily Risk Dashboard: 9 Metrics Brokers Should Watch (Before the Spreadsheet Breaks)

Spreadsheets can run a brokerage—until they can’t. The moment you add multiple LPs, multiple platforms, more symbols, more accounts, and more people touching the same “source of truth,” the daily risk routine turns into manual reconciliation and late reactions.

A modern Risk Backoffice (RiskBO) should give you a repeatable daily checklist with real-time data, auditability, and alerts. Below is a practical set of daily metrics brokers should track (and why spreadsheets fail as soon as you scale).

1) Net & gross exposure by symbol, currency, and book

Your first daily job is simple: know what you’re holding and where the risk sits. Track exposure at multiple levels so you can spot concentration early.

At minimum, review:

• Gross exposure (sum of longs + shorts) per symbol and asset class
• Net exposure (longs minus shorts) per symbol
• Exposure by currency (especially if you run multi-currency wallets)
• Exposure by book (A-book vs B-book vs internal netting)
• Exposure by platform (MT4/MT5/cTrader/etc.) and by server

Why spreadsheets fail: exposure changes every second. By the time an ops analyst exports positions, filters pivots, and shares a file, you’re already looking at stale risk—often without a consistent definition of “net,” “gross,” or “book.”

2) Realized/unrealized P&L and “why” breakdowns

Daily P&L isn’t just a number; it’s a diagnosis tool. A healthy RiskBO view separates “good wins” (spread capture, clean B-book performance) from “bad wins/losses” (LP slippage, misrouting, toxic flow, or pricing issues).

Track daily:

• Realized P&L (closed trades) by symbol, account group, and book
• Unrealized P&L (open risk) and how it shifts with market moves
• P&L by source: spread/markup, swaps, commissions, execution costs
• Exception P&L: manual adjustments, cancellations, off-market fills

Why spreadsheets fail: you can total P&L in Excel, but you can’t reliably attribute it across platforms, LP fills, routing rules, and execution venues without a consistent data pipeline and identifiers.

3) A-book/B-book routing health (and drift)

Routing is not “set and forget.” Daily checks should confirm that your execution policy is actually being applied and that routing hasn’t drifted due to new groups, symbols, or plugins.

A daily routing health check should include:

• A/B split by volume, trades, and notional
• Routing by group (e.g., VIP, standard, IB traffic, prop evaluation)
• Routing by symbol (gold and crypto often behave differently)
• Rule exceptions: accounts/symbols routed differently than intended
• Latency & reject rates by route (A-book path vs internalization)

Why spreadsheets fail: routing decisions are event-driven and rule-based. Spreadsheets tend to capture a snapshot, not the rule chain (what happened, when, and why), which makes post-incident review slow and subjective.

4) Hedging status: coverage, timing, and residual risk

Even if you hedge only a portion of flow, you need daily clarity on whether hedges were placed, when they were placed, and what residual risk remains.

Daily hedging checks:

• Hedge coverage ratio (how much net exposure is covered)
• Hedge timing (immediate vs delayed; average time-to-hedge)
• Residual net exposure after hedging by symbol
• Hedge P&L vs client P&L (are you bleeding on execution?)
• Failed/partial hedges and the reason (limits, rejects, connectivity)

Why spreadsheets fail: hedging is a workflow. If a hedge fails, you need alerts and a trail (request → response → fill → reconciliation). Excel typically records the end state—if it’s recorded at all.

5) Flow toxicity signals (who is hurting you—and how)

“Toxic flow” isn’t a buzzword; it’s a daily operational reality for brokers that internalize risk or run hybrid models. You want early warning that certain accounts, groups, or strategies are consistently extracting value through latency, arbitrage, or news spikes.

Practical toxicity signals to track daily:

• Win rate + average hold time (short hold + high win can be a red flag)
• Slippage asymmetry (client positive slippage vs broker negative)
• Execution-to-quote latency patterns (especially around volatility)
• Trade clustering around news and rollovers
• Symbol-specific anomalies (e.g., XAUUSD, NAS indices, major crypto)

Why spreadsheets fail: toxicity analysis depends on high-frequency timestamps, quote/fill comparisons, and consistent execution metadata. Manual exports usually lose precision and context.

6) Pricing & execution quality: spreads, slippage, rejects

Daily risk isn’t only market exposure—it’s also execution risk. If your spreads widen unexpectedly, or slippage/rejects spike on a specific LP, your P&L and client experience can deteriorate fast.

A daily execution-quality checklist:

• Effective spread (what clients actually paid) vs configured markup
• Slippage distribution (not just average—look at tails)
• Requotes/rejects by symbol and LP/bridge route
• Off-market fills and price outliers
• Top 10 worst execution symbols by cost and incident count

Why spreadsheets fail: execution quality is multi-dimensional. You need drill-down by LP, route, symbol, and time window—plus automated anomaly detection—without waiting for an analyst to rebuild pivot tables.

7) Liquidity provider performance and concentration risk

Brokers often discover LP issues after client complaints or after a bad P&L day. A RiskBO should make LP health visible daily so you can re-route before damage accumulates.

Track per LP (and per bridge route):

• Fill ratio and partial fill frequency
• Response times and timeouts
• Spread competitiveness by symbol/time (especially during peaks)
• Last-look behavior indicators (where applicable)
• Concentration: % of total A-book volume handled by one LP

Why spreadsheets fail: LP performance changes intraday and during volatility. A daily spreadsheet can’t reliably capture time-based degradation, and it rarely ties symptoms (rejects) to business impact (execution cost, churn risk).

8) Operational exceptions: adjustments, limits, and access

Daily risk control includes operational hygiene—because many “risk events” start as manual actions: balance corrections, leverage changes, group moves, or emergency symbol settings.

Daily exception monitoring should cover:

• Manual balance/credit adjustments (who, when, why)
• Leverage changes and margin overrides
• Group changes (routing group, swap profile, commission profile)
• Trading condition changes (symbol settings, freeze levels, markups)
• Admin access logs and permission changes

Regulatory expectations vary by jurisdiction, but audit trails and controlled access are common themes—check local regulations and align with your compliance advisors.

Why spreadsheets fail: they’re not an access-control system. Even with version history, Excel doesn’t give you robust role-based permissions, tamper-evident logs, or consistent approval workflows.

9) A daily “risk close” process: alerts, sign-off, and evidence

The most underrated scaling problem is process consistency. A RiskBO isn’t just dashboards—it’s a daily close routine that produces evidence you can defend internally (and, where relevant, externally).

A scalable daily risk close should include:

• Threshold-based alerts (exposure, slippage, rejects, P&L swings)
• Commentary fields (what happened today, actions taken)
• Task assignment (who investigates which anomaly)
• Sign-off by risk/ops lead
• Exportable audit pack (daily snapshot + exceptions + actions)

Why spreadsheets fail: they don’t enforce workflows. When volume grows, the “daily file” becomes a shared artifact with unclear ownership—and institutional memory disappears when a key analyst leaves.

The Bottom Line

A broker Risk Backoffice should track daily exposure, P&L drivers, routing integrity, hedge coverage, toxicity, execution quality, LP health, and operational exceptions—then wrap it all in a repeatable close process.

Spreadsheets are fine for early-stage checks, but they break under real-time requirements, multi-system data, and auditability needs.

If you want a daily RiskBO workflow that scales with your brokerage (without manual reconciliation), talk to Brokeret at /get-started.