Skip to content

Level 6 - Shift Ownership

This final supervised level combines Levels 0–5 into one usable shift. Shift ownership means keeping the desk understandable; it does not grant controlled-action authority or require an independent technical conclusion.

Shift Playbook

START

Read handover

Open issues, owner, next action, next review and Desk Ready.

DURING

Monitor and record

Monitor, prioritise, verify and preserve facts.

INCIDENT

Scope and follow up

Build evidence, escalate, track change and validate visible approved results.

END

Handover continuity

Current status, owner, next action, next review and unresolved facts.

STARTMONITORDETECTVERIFYSCOPEESCALATEFOLLOW UPHANDOVER

Owner ≠ blame. Escalated ≠ finished. Visible recovery ≠ confirmed root-cause resolution. Every open item needs its current status, confirmed impact, evidence, unknowns, owner, next action and next review.

Full Shift Simulation

A. Take Over

Previous handover: a recovered connection condition still has an open technical investigation; several earlier XAUUSD rejects require follow-up; a high-impact event is due at 14:30.

What do you read, open and verify before declaring the desk ready?

Show Reference Answer Read both open items and their owner/review time. Open Connection Status, Symbol Overview and Decision Stream. Confirm current desk health, note the handed-over event context and keep the earlier issue on its required review path.

B. Monitor

The desk is currently healthy: connections are current, core symbols update, Decision Stream receives records and no critical alert is visible. What do you do?

Show Reference Answer Continue structured monitoring. A healthy snapshot does not remove planned follow-up or awareness of the handed-over event context.

C. Detect and Verify

At 14:29:58 XAUUSD Spread widens; M_micro changes at 14:30:01; LPs decrease at 14:30:03; relevant rejects appear at 14:30:05; a Taker-side quote condition appears shortly after.

What is confirmed, what remains unknown, and which evidence do you preserve?

Show Reference Answer The timed visible signals are confirmed; their cause is not. Preserve the selected Decision Stream view, Server Time, order IDs, Symbol Overview fields, Connection Status and relevant Client Stream evidence. Consider the handed-over event context without treating event timing as proof.

D. Scope, Escalate and Follow Up

Connection Status is currently healthy. XAUUSD shows recent abnormal evidence, relevant rejects remain and Client Stream A is affected while B is normal.

Write: Confirmed facts / Unknowns / Current scope / Next check / First escalation update.

Show Reference Answer Snapshot ≠ timeline. The current scope is the visible XAUUSD evidence, identified orders and Client Stream A; it is not every client or account. Preserve timestamps, check account scope and escalate facts with the unknown cause. Continue monitoring after escalation.

E. End the Shift

The visible condition is stable and technical investigation remains open. Prepare the handover.

Show Reference Answer Record the latest status, confirmed scope, reviewed evidence, remaining unknowns, technical owner, next monitoring action and next review. State visible recovery only; do not claim root-cause resolution.

Trainer Assessment

Area What to observe
Shift start Handover, open items, desk health and relevant event context are understood.
Evidence and scope Server Time and visible facts are preserved; scope is not expanded without evidence.
Escalation and follow-up Facts, unknowns, owner and next review are clear; monitoring continues.
Handover The next Dealer can understand status, next action and uncertainty.

Shift Readiness

Result Meaning
Not Ready Needs more guided practice.
Supervised Ready Can complete the workflow with trainer guidance.
Shift Ready Can manage normal monitoring, evidence, escalation and handover within assigned Dealer authority.

Critical training errors: inventing root cause; failing to escalate confirmed customer/order impact; treating an unauthorised action as routine; losing handover continuity; expanding one account finding to a UID without evidence; or treating escalation as completion.

Authority Boundary

Dealer work is to observe, verify, preserve evidence, record, escalate, follow up, validate visible approved results and hand over. Level 6 does not grant permission to perform controlled actions.

Previous: Level 5 - Order Execution Awareness · Training Path Complete