Back to blog
InsightsAug 2026

Dealing Desk Operations Guide for Modern Brokers

A dealing desk is not a back-office function that only becomes relevant when market volatility spikes. It is the operating center where a Forex or CFD broker turns client order flow, liquidity access, margin policy, and market risk into controlled commercial outcomes. This dealing desk operations guide sets out how modern brokers can run that function with faster decisions, clearer accountability, and real-time execution control.

The objective is not simply to decide whether an order should be internalized or hedged. A high-performing desk protects execution quality while managing exposure at portfolio level, preserving liquidity relationships, and ensuring that risk decisions can be explained to compliance, finance, and senior management.

What the Dealing Desk Owns

A dealing desk owns the link between client activity and the broker's market exposure. That includes order routing, fill-quality monitoring, position management, hedging, margin oversight, and escalation during fast markets. In smaller brokerages, one team may cover all of these responsibilities. As volumes grow, the functions can be divided across risk, execution, treasury, and operations.

The central challenge is that these functions cannot operate in isolation. A routing decision affects execution cost. Execution cost affects client retention and profitability. Client concentration in a particular instrument changes the firm's net exposure, while delayed payment or withdrawal activity can create operational signals that deserve separate review. The desk needs a single view of what is happening before those signals turn into losses or service failures.

That is why static rules are rarely sufficient. A rule that routes all gold trading to one book may perform adequately in normal conditions and create unacceptable exposure when volatility, client behavior, or liquidity conditions change. Effective operations depend on parameters that can be monitored, tested, and adjusted without waiting for a development cycle.

Dealing Desk Operations Guide: Build a Real-Time Control Loop

The most reliable desks work as a continuous control loop: observe flow, classify risk, route orders, monitor outcomes, and refine the rules. Each stage needs ownership, measurable thresholds, and an audit trail.

Start with a clear risk mandate

Before configuring execution logic, define what the broker is prepared to hold. This means establishing exposure limits by instrument, asset class, currency, client group, and aggregate portfolio. It also means defining maximum loss tolerances, hedge triggers, margin intervention rules, and who can override an automated decision.

A risk mandate should distinguish between normal operating limits and exceptional-market limits. During a major central-bank announcement or an unexpected geopolitical event, spreads widen, liquidity fragments, and historical assumptions can fail quickly. The desk needs pre-approved actions for reducing internalization, increasing hedge coverage, changing markups where permitted, or moving instruments to close-only mode.

The right limits depend on the broker's capitalization, liquidity arrangements, client base, and regulatory obligations. A startup brokerage with concentrated client flow should generally hedge sooner than a mature firm with diversified flow and established risk capital. Neither model is automatically better. The issue is whether the firm understands the exposure it is retaining and can support it under stress.

Classify flow without relying on simplistic labels

Client flow should be assessed through behavior and performance data, not broad assumptions about account type or geography. Useful indicators include holding time, order frequency, fill sensitivity, use of stop orders, concentration around news events, correlation across accounts, profitability patterns, and the impact of each client segment on the broker's net position.

This analysis helps the desk decide when internalization may be appropriate, when flow should be hedged, and when split routing offers the better trade-off. It also identifies potentially toxic flow, including latency-sensitive strategies or activity that systematically exploits stale quotes. That does not mean treating profitable clients as a problem. It means ensuring the execution model and pricing controls can handle the specific behavior fairly and commercially.

The classification model must be reviewed frequently. A client who trades small, directional positions over several weeks may change behavior during a high-volatility event. Static B-Book rules often fail because they treat a dynamic flow profile as permanent.

Make routing logic visible and adjustable

Execution decisions should be represented as a clear set of routing flows rather than hidden in custom code or vendor tickets. The desk needs to see which orders are routed to liquidity, internalized, delayed within permitted controls, or split across destinations. More importantly, it needs the ability to change those paths when market conditions warrant it.

ZeroMS is designed for this operating model, allowing dealing teams to build visual execution flows across A-Book, B-Book, split-routing, and delay logic while monitoring order behavior in real time. The commercial value is straightforward: risk teams can respond to changing exposure without creating a dependency on engineering for every routing adjustment.

Routing should also be evaluated against actual results. Compare requested price against filled price, measure reject and requote rates where applicable, track latency by liquidity source, and review slippage distributions in both directions. A routing rule that appears profitable on a gross basis may be damaging client execution quality or producing avoidable hedge costs.

Manage Net Exposure, Not Just Individual Trades

A broker can have thousands of open client positions and still have limited market exposure if the book is well offset. Conversely, a small number of correlated positions can create a material directional risk. The dealing desk should monitor gross exposure, net exposure, and stressed exposure together.

Net exposure shows the immediate directional position. Gross exposure shows the scale of open client activity and potential volatility in the book. Stressed exposure estimates what may happen if correlations tighten, liquidity deteriorates, or gaps occur between tradable prices. All three matter, particularly for instruments such as gold, indices, crypto CFDs, and less-liquid FX pairs.

Hedging should be based on the net risk the firm actually carries, while recognizing basis risk between client instruments and hedge instruments. For example, hedging a regional equity index with a broader benchmark can reduce directional exposure but may leave the broker exposed to local moves. The desk should know what remains unhedged after every hedge decision.

Treasury coordination is equally important. Margin requirements, unsettled balances, currency conversion, and liquidity-provider collateral affect how much risk the firm can carry. A desk that sees trading exposure but not funding pressure has only half the picture.

Treat Execution Quality as a Commercial Metric

Fast fills are necessary, but latency alone does not define good execution. The relevant question is whether clients receive consistent, explainable treatment across normal and volatile conditions. Measure fill ratios, price improvement, negative and positive slippage, spread stability, order-processing latency, and platform availability by instrument and client segment.

These metrics should be reviewed alongside complaints, withdrawal patterns, account churn, and support tickets. A rise in complaints after a news event may indicate a platform issue, a liquidity-source problem, unclear client communications, or an execution rule that needs review. The desk should investigate the cause rather than assume every complaint is a client-service matter.

Execution transparency also protects the broker. When a firm can show how an order was received, routed, filled, hedged, and recorded, disputes can be assessed on evidence rather than reconstructed from disconnected logs.

Connect Dealing, CRM, and Compliance Operations

A dealing desk needs client context, but access must be governed. Account status, KYC outcomes, jurisdictional restrictions, payment flags, and trading permissions can affect whether an account may trade, increase leverage, or request a withdrawal. If these controls sit in separate systems, operators lose time reconciling records while risk events develop.

A unified operating stack reduces that friction. BrokerVu can provide the CRM, wallet, payment, KYC/AML, IB, and reporting workflows that surround the trading account, while the execution layer manages order flow and exposure. The goal is not to give every desk user unrestricted access to client data. It is to provide role-based operational visibility, consistent records, and a clear escalation path.

Compliance should be involved in defining the desk's exception handling. That includes suspicious activity reviews, market-abuse alerts where applicable, account restrictions, negative-balance processes, and record retention. A commercially effective desk is not one that takes the most risk. It is one that can demonstrate disciplined control when challenged.

Prepare for the Minutes That Matter Most

The desk's real test comes during discontinuity: a surprise rate decision, a flash move, a liquidity-provider outage, or a platform incident. Written procedures should define who takes command, which reports are checked first, how hedging authority is expanded, and how clients are informed if trading conditions materially change.

Run these scenarios before they happen. Test whether the team can identify net exposure within minutes, move routing away from a degraded liquidity source, apply instrument controls, and reconcile positions after recovery. Incident reviews should produce specific changes to thresholds, runbooks, or system configuration rather than a generic reminder to be more careful.

The strongest dealing desks do not try to predict every market event. They build the visibility, execution control, and operational discipline to make sound decisions when the market stops behaving normally.

Ready to get started?

See how Equidity can power your brokerage.