Execution Flight Simulator

Captain · CP02: Execution · About 25–30 minutes

Safety rule: Execution is part of risk. Never trade an unaffordable or unprotected ticket.

Your mission today

By the end you can demonstrate an error-free sequence from closed signal to protected demo fill and auditable result.

Before you start

Use one frozen Captain strategy card from CP01 and a demo terminal. Have the real symbol specification available. Every example in this lesson is imaginary.

1. Understand the execution problem

A simulator is useful because it tests what a student actually does, not what they claim they could do. It should contain invalid signals, stale quotes, wrong symbols, rejected orders and missing protection. Correctly refusing an unsafe ticket is as valuable as submitting an eligible one. Only broker-confirmed fills and stops count as evidence.

The execution exam is an operational assessment, not a P/L contest. Students must prove they can observe a completed trigger, check price and risk, submit the right order type, confirm protection, modify/cancel correctly and reconcile the actual executed result.

An assessment must test actions under uncertainty. Exact platform evidence and zero critical risk errors matter more than a lucky profitable practice ticket.

2. Worked example: loss before gain

Imagine an exam ticket proposes 0.20 lot on a fictional contract losing $2 per pip per 0.10 lot. A stop 10 pips away at 0.20 lot would create −$40 planned price loss. The exam risk cap is $15, so the candidate must be REJECTED or resized. If the broker minimum makes the risk-correct size impossible, SKIP is the only compliant answer.

Original Black Box Journey teaching illustration. Fictional executable prices and contract units.

3. Follow a repeatable sequence

1. Confirm the simulated account and exact symbol.
2. Identify a valid completed signal and quote timestamp.
3. Calculate stop cash loss from actual contract units.
4. Submit only a compliant demo order and verify protection.
5. Reconcile acceptance, fills, modifications and final history.

Carry out these steps before looking at the outcome. If an answer is missing, return WAIT or SKIP according to the written rule instead of guessing a fill.

4. Know when the plan breaks

A screenshot of an intended stop is not proof of a protected position. A student's confidence, trade outcome or number of green candles cannot compensate for an oversized or unprotected order. Critical risk failures require a fresh drill, not a lucky-win exception.

Unsafe alternative to reject: A trainee says 'I meant to use a stop' after opening an unprotected position. Intent is not evidence. A critical risk breach is remediated with a new test rather than erased by a subsequent winner.

5. Produce the practical record

The original flight exercise is: Deliver twenty broker-verified demo actions and a zero-critical-error checklist independently signed by the instructor.

Complete it under unseen conditions. Label requested price, actual fill, protective order status, costs, timestamp and any no-trade response. Two independent readers must reach the same decision with the same evidence.

6. Fly an execution scenario without rewinding the clock

Synthetic flight simulator: A completed M15 candle qualifies under your written entry rule. EURUSD Bid is 1.08500 and Ask is 1.08515. Your long's planned Bid stop is 1.08415, giving 10 pips of price risk. At a fictional $1 per pip, an assumed stop fill means −$10 before other costs. The simulated order then returns a fill at Ask 1.08535, not the earlier quote. The new stop distance is 12 pips, so the original risk calculation is no longer valid.

The correct response depends on your frozen rule: reduce volume if the broker permits and the ticket has not breached its allowed entry, or SKIP. Do not record the earlier Ask as the fill. A hypothetical later executable Bid at 1.08635 would yield +10 pips from the actual 1.08535 fill, but that later path is unknown at decision time.

Flight drill: Run three closed-bar tickets: one valid fill, one slippage breach and one missed pending order. Save the order request, quote timestamp, actual fill, spread, planned risk, revised risk and approval decision. A rejected order counts as an appropriate safety outcome.

Common mistake

Confusing a drawn chart line or submitted request with a broker-confirmed order. The remedy is to inspect actual server history and recalculate the downside at the executable price.

Plain-English glossary

• Simulator: Safe environment for practising an operating process.
• Critical error: Failure of a mandatory account or risk rule.
• Acceptance: Broker acknowledgement that a request is valid.
• Reconciliation: Matching the plan with executed server records.

Try it yourself

Deliver twenty broker-verified demo actions and a zero-critical-error checklist independently signed by the instructor. Record at least one deliberate rejection and one scenario where execution is worse than requested. Save the ticket, quote, stop-distance maths and final account record.

What you can now do

• Demonstrate an error-free sequence from closed signal to protected demo fill and auditable result.
• Explain how a worse fill changes the cash loss.
• Reconcile your planned ticket against executed server evidence.

Next lesson

CP03.1 · The Cash-Risk Approval Gate.