Incident & Risk Workflow

This page consolidates incident reporting, risk escalation, major-event preparation and client-behavior review into one workflow.

When To Use This Workflow

Use this workflow when any of the following appears:

• Quote anomaly, stale quote, spike, wrong price or chart concern.
• Execution delay, timeout, reject cluster or partial-fill increase.
• Bridge anomaly, queue growth or abnormal trade-log signal.
• Exposure or concentration changes materially.
• Client complaints or disputed orders appear.
• Major news, rollover, holiday, market open / close or scheduled control creates risk.
• Abnormal order-flow pattern requires review.

Incident / Risk Record

Time:
Trigger:
Affected symbol / platform / account group:
Market context:
Quote / chart evidence:
Bridge / execution evidence:
Exposure / concentration:
Client-impact evidence:
Current action:
Responsible person / Shift Leader:
Actions requiring approval:
Next update:
Closure standard:

First Response Standard

1. Preserve evidence before interpretation.
2. Separate facts, assumptions and requested decisions.
3. Define scope by time, symbol, account group, order type and system layer.
4. Notify the Shift Leader when impact, trend or required action exceeds normal monitoring.
5. Do not promise compensation, adjust client outcomes or change conditions without approval.

Major Event Preparation

Before high-impact events, confirm:

• Event time, timezone and affected symbols.
• Platform, Bridge, quote-source and reporting access.
• Current Exposure, concentration and pending-order risk.
• Approved temporary plans, margin / spread settings or profile changes.
• Escalation responsible person and update cadence.
• Post-event recovery and closure standard.

For monthly or scheduled events, also confirm:

Item	Standard
Monthly event sheet	Event date, platform time, timezone, affected symbols and expiry / rollover information are updated
Announcement and verification	Announcement content is approved, and each platform display matches the approved announcement after publishing
Shift schedule reminders	Announcement, execution, recovery and post-event review reminders are added to relevant shifts
Risk Tool reminders	Pre-event, final pre-event, short post-event and recovery-review reminders are configured
Control plan	Stop level, margin, spread, profile or temporary plan has approval record
Client Terminal verification	After controls are enabled, client-visible trading conditions or display status are checked from an approved client-side view
Recovery check	Default settings are restored according to approval, with recovery time, evidence and reviewer recorded

Client Behavior Review

Client behavior review must remain neutral and evidence-based. Use language such as:

“This account group meets internal review criteria due to short holding time, repeated event-window activity and execution-context signals. Evidence has been escalated to the Shift Leader.”

Avoid unsupported language such as:

• “The client is abusive.”
• “Profitable flow is a problem.”
• “Restrict this account immediately.”

Internal Risk Status Principles

Internal risk-status information helps authorised teams identify cases that require review, continued monitoring or approved controls. It is not a personal judgement about a client and is not a tool that a Dealer may apply independently.

Specific labels, control-depth order, technical parameters, system paths and execution logic are restricted information and must not appear in public Academy material.

Operating Discipline

• Evidence must be saved before any internal risk-status recommendation: order records, holding time, event window, trading result, Exposure impact, account relationship and prior review history.
• Dealers may identify, record and escalate evidence, but must not independently change a client risk status or trading condition.
• Related-account scope must be reviewed through the approved process before any broader action is considered.
• External communication must not mention internal labels, control depth, execution parameters, inheritance logic or specific control logic.
• Handover wording should be limited to “account / linked scope is under internal review” or “approved control applied”; do not include personal names, real account numbers or unnecessary sensitive detail.

Common Special Risk Types

Type	What the Dealer should review
Linked accounts / same-person multi-account activity	Approved relationship signals, trade timing, funding pattern and order behavior
Fast Deal / fast-close risk	Holding time, fast-close profit, risk score, event window and post-trade price movement
Wash rebate / hedged-volume abuse	Whether hedging, volume generation or unusual holding patterns are used to obtain rebate
Automated risk-status trigger	Whether an automated review signal or restriction requires validation
Pre-close unhedge gap risk	Whether a same-account hedge is partially closed shortly before market close, leaving overnight gap exposure

Escalation Update Template

Subject:
Time:
Observation:
Affected scope:
Evidence:
Risk / client impact:
Current action:
Decision needed:
Responsible person / Shift Leader:
Next update:

Closure Standard

An incident or risk item should not be closed until:

• Quote, chart, Bridge and execution status are stable.
• Affected order or client-impact scope is confirmed.
• Exposure or concentration risk is understood.
• Required approvals or decisions are recorded.
• Follow-up responsible person and review date are clear.