Skip to content

Lesson 5.6 - Incident Drill

Chapter 5 trains Dealers to use the same incident logic under pressure: preserve evidence, confirm scope, keep updates moving and close with a review. The point is not to find one perfect answer immediately. The point is to create an incident record that can be tracked, reviewed and handed over.

Chapter Review

  • Quote anomaly: distinguish market movement, abnormal quote points, stale quote recovery and internal quote issues.
  • Execution delay: separate client side, Trade Server, Bridge, quote source and result-return path.
  • Quote-source issue: confirm quotes, charts, Bridge, client impact and Exposure impact.
  • Post-incident review: close the loop with timeline, evidence, scope, cause review and improvement actions.
  • Client order dispute: review Bid / Ask, order type, trigger price and execution record objectively.

Scenario Output

After CPI release, XAUUSD shows a sharp spike on the chart. Several clients complain that stop losses were triggered abnormally. At the same time, Bridge shows delayed fills on some orders, Quote Source B quote contribution drops briefly and Quote Source A / Quote Source C remain normal.

Produce an initial incident handling record.

Expected Output

Time:
Incident summary:
Affected scope:
Evidence preserved:
Quote / chart status:
Bridge / execution status:
Client order impact:
Confirmed facts:
Still under review:
Current action:
Communication targets:
Actions not to promise or perform independently:
Recovery / closure standard:
Next update:

Behavior Standard

  • The first action is evidence preservation, not compensation promises, client blame or premature root cause.
  • Quote anomalies must be compared across quote sources, platform ticks, chart screenshots, event timing and order-trigger records.
  • Client order impact should be filtered by symbol, time window, order type, fill price, trigger price and account scope.
  • Internal and external updates should contain verified facts only; compensation, order adjustment and configuration actions require authorization.
  • Before closure, the incident must have status updates, Shift Leader / follow-up, next update time and recovery standard.

Example Output

Time: 20:31 after CPI release
Incident summary: XAUUSD showed a sharp chart spike. Several clients complained about stop-loss triggers. Bridge also showed delayed fills on some orders.
Affected scope: Initially concentrated in XAUUSD around the CPI release window. Affected order scope remains under review.
Evidence preserved: Chart screenshot, tick timestamps, Bridge log, quote-source contribution, order IDs, client complaint details and event time.
Quote / chart status: Quote Source B contribution dropped briefly. Quote Source A and Quote Source C remained normal. Whether this was a single-source abnormal quote remains under review.
Bridge / execution status: Some delayed fills observed. Number, duration and recovery status require continued review.
Client order impact: Complaints relate to stop-loss triggers. Each case must be checked against Bid / Ask, order type, trigger price and execution record.
Confirmed facts: XAUUSD showed an abnormal point, Quote Source B contribution dropped, Bridge had some delayed fills and clients complained.
Still under review: Source of abnormal quote, affected order scope, market context and whether there is platform-level impact.
Current action: Preserve evidence, filter affected orders, compare quote sources and ticks, monitor Bridge and client complaints.
Communication targets: Shift Leader; technical, risk or quote lead if needed.
Actions not to promise or perform independently: No compensation promise, order adjustment, client-result change or configuration change without authorization.
Recovery / closure standard: Quotes stable, execution delay recovered, affected scope confirmed, Shift Leader / follow-up named and post-incident review arranged.
Next update: Within 10 minutes, or immediately upon scope change.

Pass Standard

The trainee should turn a complex incident into a clear initial handling record with timeline, evidence, scope, action, escalation target and closure standard.

End of Chapter 5

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