Escalation and Handover

Escalation transfers confirmed facts, unknowns and next actions to the person with the required authority or expertise. It is not a conclusion and not a way to abandon ownership.

Escalate when evidence is missing or contradictory; a repeated or cross-account pattern merits review; UID/IP/Device, fund flow, restrictions or client classification is involved; STP/LP/counterparty/routing requires specialist review; impact may be wider; or any price, order, compensation, restriction or configuration change is requested.

Use this order: Issue → Identity → Confirmed facts → Scope → Unknowns → Junior Assessment → Requested action → Next update.

[Time] Investigating [issue] for [Account/Ticket/Symbol/window]. Confirmed [facts] from [MT4/MT5/Edge source and IDs]. Current scope is [scope and basis]. Unable to confirm [unknowns]. Junior Assessment: [result]. Escalated to [role] for [request]. Next review: [time]. The observed pattern is not recorded as a violation finding.

Before handover, confirm that the next dealer can reproduce the evidence, all times are aligned, contrary evidence is retained, observations are separated from conclusions, and the owner and next checkpoint are clear.