Level 4 — Ticket Investigation

Classic teaches the Incident method. This level answers one practical question: when a Ticket or complaint arrives, how do you build a reproducible evidence chain in Edge?

Fix Ticket→Confirm Order result→Verify Decision prices→Execution when needed→Ticks / Alarm when needed→Define Scope→Evidence Summary

Lock Ticket, Account, Symbol and Time Window first. Preserve the original timezone and align to Server Time.

• Order: existence, type, volume, price and final Status.
• Decision: Request, Filled and Client fill prices, Final, Cost and Status.
• Execution: only for split, external, counterparty or timeout questions; Junior records IDs/status/reason and escalates.
• Ticks: only when quote context is required, using the exact symbol/taker and a narrow window.
• Alarm / System: only when evidence suggests wider impact in the same period.

Start at Single Order. Expand to Account, Multiple Accounts, Symbol Window or System Wide only with a written evidence basis.

Need more detail? See Order, Execution and Decision, the Investigation Result template and the Investigation Map, then complete the illustrated Client Complaint Ticket Investigation.