Boot Camp Day 38: Stop Losses

Main ideas / lessons

• Stop loss = your trade’s invalidation point. If price returns to (or breaks) the level your setup depends on, then the premise behind the trade (e.g., the liquidity sweep) was not actually valid.

• Most common rule (primary method): place the stop-loss above the liquidity sweep. In the typical setup described:

  • liquidity sweep → break of structure → order block / fair value gap entry

Traders often place the stop above the swept high because:

- If the bias was correct and liquidity truly was taken, price should not realistically move back above the swept high.
- If price *does* move back above it, that suggests the liquidity sweep wasn’t valid (i.e., there wasn’t enough volume/volatility/orders to force price as expected).

• Practical adjustment: account for spread.

  • A stop placed exactly on the visible price level can get triggered due to bid/ask spread.
  • Therefore, the stop should include a small buffer beyond the technical invalidation level.

• Exceptions / alternative placement when risk:reward would be too poor.

  • If the liquidity sweep is so high that placing the stop above it makes risk:reward unacceptable, the speaker suggests using an alternate invalidation/confluence point, such as:
    • Placing the stop above the order block (or another relevant structure) within the setup region.
  • Caveat: this is imperfect—price could still rise enough to stop you out even if the broader bias remains intact.

• Correct execution example: stop placement and why it got stopped out.

  • The trade was entered after:
    • candle closure / break of structure
  • The speaker placed the stop with a spread buffer.
  • The trade was stopped out when the setup’s invalidation condition was reached (they treated a specified move as the liquidity sweep + structure break on a particular lower timeframe).

• Higher-timeframe vs lower-timeframe trade management (scaling).

  • If the clean liquidity sweep occurs on a higher timeframe, taking the full move may create an overly large stop and poor risk:reward.
  • Suggested approach:
    • Scale into a higher-timeframe plan, but execute the entry on a lower timeframe
    • Find an entry on/under the liquidity sweep for a better risk:reward.
  • Emphasis: keep risk management aligned with your comfort level.

• Risk tolerance / position sizing determines stop-loss effectiveness.

  • Set the stop where price invalidates the setup, but how much you can risk depends on your personal risk tolerance.
  • The speaker mentions de-risking during:
    • high-impact news
    • bank holiday conditions
  • Reason: markets may be choppy, low-volatility, or otherwise behave unusually.

• General wrap-up instruction

  • Focus on:
    • Finding your invalidation point
    • Using your risk tolerance to size the trade
  • Tomorrow’s topic is hinted to be set lot sizes and calculating risk/lot size.

Method / step-by-step instruction (stop-loss placement)

Step 1: Identify the setup sequence and key levels

Look for:

• Liquidity sweep
• Break of structure
• Entry trigger (e.g., order block / fair value gap)

Step 2: Default rule for stop-loss location

• Place stop loss slightly above the liquidity sweep high.
• Rationale: if price comes back above the swept high, the sweep was likely not “real,” meaning your bias/setup is invalidated.

Step 3: Apply a spread buffer

• Do not set the stop exactly on the shown price level (spread can trigger you early).
• Instead, place the stop with a small margin/buffer.

(Example referenced: the stop-loss was placed some amount relative to the exact invalidation price to create buffer spacing and prevent spread-related stop-outs.)

Step 4: Consider exceptions only if needed (risk:reward constraints)

• If the sweep-based stop would create a terrible risk:reward:
  • Find another confluence/invalidation reference inside the setup (example: place stop above an order block rather than above the sweep high).
• Note: this can increase the chance of being stopped even if the larger bias remains correct.

Step 5: For higher-timeframe scenarios, manage risk via scaling

• If the higher timeframe’s stop would be too large:
  • Scale/enter using a lower timeframe execution
  • Look for a safer entry under/near the liquidity sweep
• Keep risk management consistent.

Step 6: Always define invalidation on the timeframe relevant to execution

The speaker highlights that for a specific execution trade, they may treat:

• a liquidity sweep on one timeframe
• plus a structure break on a different lower timeframe as the true invalidation framework for that trade.

Speakers / sources featured

• Primary speaker: The instructor/trader hosting the “Boot Camp,” explaining stop-loss rules directly.
• Group source mentioned: A Discord community (referenced as viewers/participants who asked about the Zoom boot camp video and shared reactions/outcomes).
• Other named guests: None clearly identified beyond the instructor and Discord reference.