Skip to content

Lesson 4.5 - Client Risk Status & Control Depth

Learning Objectives

By the end of this lesson, a Dealer should be able to:

  • understand that client risk status is internal risk-management information;
  • distinguish between account-level and linked-identity-level controls;
  • perform initial verification, evidence collection, escalation, and handover after identifying unusual client activity;
  • confirm the execution result completed by authorised personnel and validate that it matches the approved scope;
  • understand that internal labels, control logic, and parameters must not be disclosed to clients, sales, or unauthorised personnel.

1. What Is Client Risk Status?

Client risk status is internal control information used to identify, record, and manage trading-related risk.

It is not a public classification of a client and does not represent a final judgement about a client. It helps authorised personnel apply consistent and auditable handling when unusual trading, linked-account risk, execution risk, or pending-review matters are identified.

Internal system markers may indicate different levels of risk-control depth. The specific labels, colours, parameters, execution methods, and adjustment criteria are restricted information.

Confidentiality Requirement

A Dealer must not explain, imply, or disclose internal risk markers, control depth, execution logic, system parameters, or handling reasons to clients, sales teams, introducing parties, partners, or any unauthorised person.

2. Scope of Risk Controls

Risk-control measures may be applied at either of the following scopes.

Account-Level Control

Account-level control applies to a specific trading account.

It may be used for a single-account review, temporary observation, or an approved case-specific action.

Linked-Identity-Level Control

Linked-identity-level control applies to a confirmed group of related accounts.

Once such a control is active, future accounts opened under the same linked identity may inherit the existing internal control status. Dealers must not independently determine or expand a linked scope. Suspected related accounts should be documented and escalated through the approved process.

3. Dealer Responsibilities and Boundaries

A Dealer is responsible for supporting the risk-control workflow, not for independently setting risk strategy.

A Dealer Should

  1. identify unusual trading, unusual order flow, linked-account indicators, or other risk signals;
  2. verify orders, positions, timing, instruments, trading behaviour, linkage information, and available system records;
  3. preserve required evidence and record the facts in handover or incident documentation;
  4. submit an escalation through the approved process;
  5. after receiving an approved instruction, confirm the execution result completed by authorised personnel and validate whether the internal risk-control status has taken effect within the authorised scope;
  6. continue to monitor pending-review matters and complete the required handover;
  7. escalate immediately if a status is not applied correctly, if its scope is inconsistent, or if a new related account appears not to be covered.

A Dealer Must Not

  • independently set, increase, decrease, or remove a client risk-control status based on personal judgement;
  • explain internal labels, system markers, or execution logic to clients;
  • use an internal risk marker as a reason in client, sales, or introducer communication;
  • expand a control scope without evidence, approval, and an appropriate record;
  • copy restricted risk-control information into uncontrolled group chats, messages, or public training material.

4. Standard Handling Workflow

Step 1: Identify

Start an initial review when any of the following is observed:

  • unusual short-holding activity, unusual order flow, or conduct that may take advantage of execution conditions;
  • multiple accounts showing highly similar timing, direction, instruments, volumes, or trading patterns;
  • suspected linked accounts displaying hedging, pairing, or control-avoidance behaviour;
  • a controlled account showing a new related account, unusual funding activity, or new risk signals;
  • a review requested by a Shift Leader, Manager, Risk function, or system alert.

Step 2: Verify and Preserve Evidence

Depending on the case, review:

  • orders, positions, execution time, holding time, and instruments;
  • order flow, price behaviour, market events, and system logs;
  • related accounts, linked-identity information, and existing internal status;
  • whether the current control has taken effect and whether any scope may be missing.

Organise the facts, timeline, report references, screenshots, and system records into reviewable evidence.

Step 3: Escalate

An escalation should include:

  • affected accounts or linked scope;
  • observed behaviour or risk signal;
  • verified facts and evidence location;
  • current risk status, where applicable;
  • recommended handling direction;
  • any immediate risk requiring attention.

Step 4: Confirm Authorised Execution Result

After receiving a clear approved instruction:

  • confirm the authorised scope, approved action and responsible operator;
  • verify that the execution result completed by authorised personnel matches the approved instruction;
  • validate that the approved control status has taken effect in the intended account or linked scope;
  • do not infer or extend the instruction independently;
  • stop and escalate immediately if the result differs from the approved instruction.

Step 5: Handover and Review

A handover must state:

  • current status;
  • actions already completed;
  • evidence location;
  • pending-review items;
  • responsible owner or next handler;
  • next review time or trigger.

5. Practical Scenario

Scenario

A Dealer identifies an account repeatedly opening and closing positions within short periods during several high-volatility windows. Further review shows that its timing and directional patterns closely resemble several other accounts.

Correct Handling

  1. Extract relevant orders, timelines, and trading records.
  2. Check whether any prior risk status or linked-identity indicator exists.
  3. Do not explain internal judgement to the client, sales team, or unauthorised personnel.
  4. Submit the facts, evidence, and recommended review to the Shift Leader / Manager.
  5. After receiving instruction, confirm the authorised personnel's execution result and validate that the approved risk-control status is active within the authorised scope.
  6. Record the pending review and follow-up focus in the handover.

Common Mistakes

  • expanding a control scope before completing evidence review;
  • explaining internal handling reasons directly to sales;
  • acting only on the observed account without submitting a related-account review;
  • sending internal risk-status screenshots to an uncontrolled group;
  • recording only “handled” without evidence, timestamps, or pending actions.

Key Principle

Client risk status supports consistent, prudent, and auditable internal handling. It is not a tool for personal judgement or client communication.

Key Takeaways

  • Controls may be applied at account level or linked-identity level.
  • Linked-identity-level controls may affect future related accounts.
  • A Dealer’s core role is to identify, preserve evidence, escalate, confirm approved results, and complete handover.
  • Actual system controls must be executed only by authorised personnel under the approved process.
  • Internal markers, control depth, parameters, and execution logic are restricted information.
  • Any adjustment, removal, or expansion of a control scope requires approval and records.

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