Stop Flying Blind: A Dealing Desk Daily Routine That Keeps Risk in Check

A dealing team’s worst days usually start the same way: a quiet open, a few “normal” fills, then a sudden spike where exposure, spreads, and client behavior all change at once. The fix isn’t a bigger dashboard—it’s a consistent daily RiskBO routine that turns real-time data into repeatable decisions.

Below is a practical playbook for brokers and prop firms using RiskBO-style monitoring: what to verify in the morning, what triggers should interrupt your day, and how to close out cleanly so you don’t carry avoidable risk overnight.

Morning Checks: Start the Day With a RiskBO Baseline

Your morning goal is simple: establish what “normal” looks like today before the market tells you the hard way. Do this before peak liquidity hits your book.

1) Confirm trading conditions and market state

• Session handover notes: any overnight incidents, rejected orders, liquidity provider (LP) warnings, platform restarts, or bridge changes.
• Symbols and sessions: verify trading hours, rollovers/swaps, and any scheduled market closures (especially around holidays).
• News calendar awareness: flag high-impact events that can cause spread blowouts and slippage (CPI, NFP, rate decisions). You don’t need a prediction—just a “risk window” marked on the desk.

2) Validate your RiskBO plumbing

• Price feed sanity: check for stale quotes, abnormal gaps, or off-market spikes on top symbols.
• Execution health: compare fill ratios, requotes/rejections, and latency vs. your normal range.
• Routing rules: ensure A-book/B-book logic and any symbol-specific overrides match today’s policy (no “temporary” rules left behind).

3) Snapshot your starting risk

• Net exposure by symbol and currency: identify concentrations (e.g., too much net long gold or net short JPY).
• Client group exposure: separate retail vs. IB-driven flow, and prop evaluation vs. funded accounts.
• P&L and drawdown context: start-of-day broker P&L, hedging P&L, and any open hedge legs carried from yesterday.

A good baseline means you can later say: “We deviated at 13:40 UTC because X happened,” rather than “We always run hot.”

Intraday Triggers: The RiskBO Alerts That Should Stop Everything

Intraday risk management fails when alerts are too noisy—or too vague. Your dealing team needs a short list of triggers that force a decision (hedge, reroute, widen controls, or investigate).

Here are practical RiskBO triggers most desks can operationalize:

Exposure & concentration triggers

• Net exposure breach: a hard threshold by symbol (e.g., EURUSD net > $X notional) or by correlated basket (risk-on FX, metals, indices).
• One-way flow concentration: sudden dominance of buys or sells in a single symbol across many accounts.
• Correlation drift: exposure looks diversified by symbol, but not by risk factor (e.g., multiple USD-short positions across pairs).

Execution quality triggers

• Slippage spike: average slippage jumps above a defined band for a symbol/session.
• Reject/requote rate increase: often indicates LP issues, bridge configuration drift, or toxic flow.
• Latency jump: MT server load, network issues, or bridge congestion—often shows up before clients complain.

Behavioral / toxicity triggers

• Short-hold scalping burst: holding time collapses while win rate rises—common during news spikes or feed issues.
• “Hit-and-run” patterns: fast entries around micro-moves, repeated at the same timestamps.
• Clustered profitability: a small group of accounts generating disproportionate P&L against the book.

Operational risk triggers

• Deposit/withdrawal anomalies: sudden funding spikes aligned with high-risk periods can amplify exposure quickly.
• IB-driven surges: affiliate campaigns can change your flow profile in hours.

When a trigger fires, the desk should follow a mini-runbook: (1) confirm data integrity, (2) quantify exposure, (3) choose an action, (4) document the reason.

What to Do When Triggers Hit: A-Book/B-Book, Hedging, and Controls

A trigger without a response is just a notification. The response should be pre-approved, measurable, and reversible.

Common response actions (pick the least invasive that solves the problem):

• Adjust routing rules: temporarily A-book a symbol, a client group, or a risk segment when flow quality degrades.
• Hedge the net, not the noise: hedge only the portion of exposure that breaches your threshold, and avoid “chasing” every micro swing.
• Tighten execution protections: apply symbol-specific max deviation/slippage tolerances, or adjust risk limits for known high-volatility windows.
• Segment clients: if a cluster is driving toxicity, route that segment differently rather than punishing the whole book.
• Pause and investigate feed issues: if you suspect off-market pricing, fix the root cause before you hedge a phantom move.

A practical exampleIf RiskBO shows a sudden net long XAUUSD concentration and slippage spikes during a news window:

1. Verify quotes vs. reference feed/LP stream.
2. If pricing is valid, hedge the net exposure above your limit.
3. Temporarily route the most aggressive short-hold group to A-book.
4. Log the event with timestamp, threshold breached, and actions taken.

This approach keeps you systematic: you’re reacting to measured risk, not emotion.

End-of-Day Closeout: Don’t Carry “Accidental” Overnight Risk

End-of-day isn’t about flattening everything. It’s about ensuring anything you carry is intentional, sized, and explainable.

1) Reconcile exposure and hedges

• Net exposure by symbol: confirm it’s within overnight limits.
• Hedge alignment: ensure hedge legs match the intended net (watch for partial fills or orphaned hedges).
• P&L attribution: separate client P&L, book P&L, and hedge P&L so you know what actually drove the day.

2) Review exceptions and anomalies

• Top rejected orders and why (LP rejects vs. platform settings vs. client behavior).
• Top slippage symbols and time windows.
• Accounts with unusual profitability or suspicious execution patterns.

3) Lock in tomorrow’s starting position

• Confirm any temporary routing overrides are either reverted or formally extended.
• Update risk limits if volatility regime changed (with management/compliance sign-off where needed).
• Write a short handover note: what happened, what’s still open, and what to watch tomorrow.

Regulatory and compliance note: your exact surveillance, recordkeeping, and client-treatment obligations vary by jurisdiction and business model (broker vs. prop). Keep an auditable log of material dealing decisions and consult your compliance advisors on retention and monitoring requirements.

Make It Repeatable: The Daily RiskBO Checklist Your Desk Can Adopt

Consistency beats heroics. If you want this routine to survive staff changes and growth, reduce it to a checklist and a few hard thresholds.

Daily RiskBO routine (copy/paste):

• Morning (15–25 min): feeds OK → execution health OK → routing rules verified → baseline exposure snapshot → news windows flagged.
• Intraday (event-driven): respond to threshold breaches (exposure, slippage, rejects, latency, toxicity) using pre-approved actions and log every material change.
• End-of-day (20–30 min): reconcile exposure/hedges → review exceptions → confirm overnight limits → handover note + reset temporary rules.

If your team can’t complete this in under an hour total desk time, the routine is too complex—or your tooling isn’t centralized enough.

The Bottom Line

A strong dealing team doesn’t rely on intuition alone; it relies on a daily RiskBO routine that sets a baseline, reacts to clear intraday triggers, and closes out with reconciled, intentional overnight exposure.

Build your thresholds, define your response actions, and log the decisions—so risk stays measurable as you scale.

If you want to operationalize this routine inside a modern risk backoffice, start here: /get-started