Lesson 6.2 - Live Monitoring Rhythm

“Watching Everything Is Not Monitoring”

A Dealer keeps ten dashboards open but misses a rising Bridge queue because attention is spread across too many screens. Another Dealer watches fewer items but follows a structured rhythm: baseline, exceptions, trend, action.

Dealing Room monitoring is not passive observation. It is a controlled cycle.

• Build a practical live-monitoring rhythm.
• Prioritize exceptions over static dashboards.
• Separate observation from escalation.
• Record material changes with sufficient context.

Establish Baseline → Scan Key Indicators

Scan → Identify Exception

Exception → Verify Scope / Trend

Verify → Monitor / Escalate / Act

Action → Record Material Change

Record → Baseline

Area	Key Questions
Quotes	Are prices fresh, competitive and consistent?
Execution	Are latency, fills, platform-rule rejects and timeouts within expected range?
Bridge	Is queue/route/session behavior stable?
Quote sources	Are quote sources healthy and contributing?
Exposure	Is net/gross/concentration changing?
Clients	Is abnormal flow or complaint volume increasing?
Events	Is a known market/event window approaching?

Focus first on changes such as:

• Spread widening versus baseline.
• Sudden quote-source participation loss.
• New Bridge queue trend.
• Exposure acceleration.
• Repeated rejects/timeouts.
• Clustered client activity.
• Pending orders before a major event.

Middle-Shift Monitoring Focus

The middle shift carries the operating state after the opening checks and keeps it under review during active trading hours.

Middle-shift Dealers should focus on four evidence groups:

Category	Evidence to check	Do not
Trade / Bridge	Large orders, fast closures, platform-rule reject / timeout, Bridge queue, match / route changes	Conclude from sound alerts alone
Risk review	Exposure, group concentration, accounts requiring review or special-review status, event window	Treat client profit as abnormal by itself
MT administration	Group / symbol / deal / position requests, approval basis, before/after state	Change settings when approval is unclear
Daily documentation	Daily reports, Market Watch, swap adjustment and exception notes	Turn routine checks into long narratives

The bridge trade log is a core real-time order-flow surface. Each client order appears according to the fields available on the bridge interface, such as receipt, route, match, platform-rule reject, fill or closure status.

Dealers should use this view to understand order flow and exception signals, not to jump directly to conclusions. Focus on:

| Observation | What the Dealer Checks | Evidence to Record |
|---|---|---|
| Order basics | Time, symbol, side, volume, account or group scope | Order ID, screenshot, timestamp |
| Large-volume orders | Whether size exceeds the shift attention standard and clusters by symbol or group | Volume, symbol, group scope |
| Fast closure | Whether open and close happen within a very short time and repeat | Open time, close time, holding time |
| Order clustering | Whether orders cluster near news, open, close, rollover or visible quote changes | Event context and order window |
| Platform-rule reject / timeout | Whether issues cluster by symbol, account condition, time window or route | Reject / timeout message and Bridge queue |
| Match / route information | Whether visible handling differs from the normal pattern | Record visible fields without over-inference |

Sound alerts help prioritize attention. A sound may be configured for large-volume orders, very short holding time or repeated orders. The alert is not a judgment; it means the Dealer should verify order evidence, market context and actual impact.


Bridge monitoring should be paired with MT4 / MT5 client terminal review. Keeping several client terminals open helps the Dealer confirm whether charts and platform-visible prices look normal from the client side.

| Issue Type | Typical Sign | Evidence to Collect |
|---|---|---|
| Price spike / bad tick | A sudden abnormal needle on the chart that quickly returns to normal range | Chart screenshot, tick time, Bid / Ask, affected symbol |
| Off-market price | One quote visibly deviates from other sources or reasonable market range | Quote-source comparison, timestamp, spread, reference market |
| Quote-source divergence | Visible high/low differences between quote sources create abnormal spread or chart behavior | Quote-source status, quote contribution, Bridge log |
| Chart/order mismatch | Client-side chart does not appear consistent with trigger or fill behavior | Client terminal screenshot, order ID, server time, Bridge record |

When these appear, do not state that the system or client is wrong before evidence is reviewed. Save screenshots, timestamps, symbol, quote evidence, Bridge logs, affected order IDs and client-impact scope, then escalate to the responsible lead.

### “Everything Looks Green”

All dashboards show green status, but:
- One quote source contributes less than usual.
- XAUUSD spreads are wider only on large-size orders.
- Bridge queue starts rising during the same window.

A green overall health page does not replace trend analysis. The Dealer should identify this as quote-quality deterioration and escalate with evidence.

Good monitoring is rhythmic, comparative and action-oriented. It detects meaningful change before it becomes a full incident.

---

Completion Criteria

• Can explain the key risk or operational objective of this lesson
• Can identify the required systems, data, or evidence to review
• Can describe the correct escalation or handling process
• Has completed Shift Leader / follow-up review or practical confirmation