Lesson 5 — Timeframe Choreography (D1 → H4 → H1)

Goal: Build a top-down routine so your entries on H1 line up with what D1/H4 are doing. This is where context becomes confidence.


1) The roles of each timeframe

  • D1 (Daily): Set the playing field. Mark major swing highs/lows and the “big picture” bias. Yesterday’s and last week’s extremes (PDH/PDL/PWH/PWL) live here.
  • H4 (4-Hour): Read the current sequence: impulse → correction. Is the last strong push up or down? Has the impulse base held?
  • H1 (Hourly): Timing layer. Take pattern triggers (IB mother-bar breakout, Engulfing, Pin, Marubozu) that agree with H4’s impulse and make sense inside the D1 map.

2) Set up your tools (quick)

  • PA Context HUD: turn InpUseHTFTrend = true, set InpHTF = H4. Keep InpUseLevels = true so PDH/PDL/PWH/PWL are available.
  • CapreContext_Arrows_v2: start with MinScore = 2 or 3. This ensures H1 arrows only print when the overall context is decent.

3) The 5-minute top-down routine (every session)

  1. D1 scan: Draw or mentally note the nearest key levels: PDH/PDL (previous day high/low), PWH/PWL (previous week high/low), and current D1 swing zones. Decide a soft bias (up/down/neutral).
  2. H4 read: Identify the last impulse (fast, one-color leg) and its base. Decide: are we in a correction back toward that base or leaving it? The HUD’s “Last impulse” should match your read.
  3. H1 execution: Only consider arrows that align with H4’s last impulse and make sense relative to D1 levels (e.g., not buying straight into PDH).
  4. Location check: Prefer signals that occur near a helpful level (PDL/PWL for longs; PDH/PWH for shorts) or show a false-break story at those levels.
  5. Risk plan: Stop goes beyond the pattern’s logical invalidation (MB opposite side, pin tail, or structure). Size by pips/ATR so risk is consistent.

4) Three synchronization rules

  1. Agree or pass: If D1 says “range near resistance,” H4 impulse is down, and H1 prints a long arrow into PDH — skip. Wait for alignment.
  2. Level-led triggers: A high-quality H1 signal often comes after a tap or fakeout of PDH/PDL/PWH/PWL, then a close back in line with H4’s impulse.
  3. Base is boss: If H4 loses the impulse base (clean close and acceptance through it), your prior bias is invalid — stand down until a new impulse prints.

5) Example playbooks

A) D1 range → H4 impulse up → H1 IB breakout

  1. D1 shows we’re mid-range, PDH above, PDL below.
  2. H4 prints a clean up impulse, then pulls back (correction) toward its base.
  3. On H1, take the first IB mother-bar breakout up as price leaves the correction; avoid entries that close right under PDH.

B) D1 near PDH → H4 false-break → H1 engulfing down

  1. Price pokes above PDH on D1/H4 and closes back inside (failed break).
  2. H4 shifts to a down impulse from that failure.
  3. On H1, take a bearish engulfing continuation away from PDH; SL above the engulf bar or structure.

6) Settings that keep you aligned

  • HUD: InpUseHTFTrend = true (H4), keep InpNearLevel_ATR ≈ 0.25, InpFalseBreakLookback = 3.
  • Arrows: MinScore = 2–3. If you want only the cream, raise to 3; if too sparse, drop to 1 (study mode).
  • Session filter: Optionally enable London/NY hours on the HUD so most arrows occur in liquid windows.

7) Common pitfalls

  • Bottom-up bias: Letting an H1 arrow dictate the story when H4/D1 disagree.
  • Trading into a wall: Taking H1 longs right under PDH/PWH, or shorts right above PDL/PWL, without a clear failure pattern.
  • Ignoring invalidation: Staying biased long after H4 has cleanly lost its impulse base.

8) 10-minute drill (MTF reps)

  1. Pick a pair you trade (e.g., GBPUSD). Open three tabs: D1, H4, H1.
  2. On D1, mark PDH/PDL/PWH/PWL. On H4, mark the last impulse and its base. On H1, highlight the corrections that followed.
  3. Scroll back 2–3 months and log 10 H1 signals you would take when H4 impulse and D1 location agreed. Note outcomes and whether they launched away from a level or after a false-break.

9) Quick checklist (printable)

  • D1: nearest PDH/PDL/PWH/PWL identified; soft bias set
  • H4: last impulse and base marked; still valid?
  • H1: signal aligns with H4 impulse and respects D1 levels
  • Not breaking straight into an opposing level
  • SL beyond pattern/structure; size by pips/ATR; news checked

How your tools help

  • PA Context HUD: shows HTF trend (H4), last impulse, near-level/false-break status, and contributes to the up/down score.
  • CapreContext_Arrows_v2: prints only when H1 patterns and the HUD score meet your threshold. Hover the dot to see distances to PDH/PDL/PWH/PWL.

Next up: Lesson 6 — The PFP Lens (Positioning, Flows, Price Action): a pre-trade checklist you can run in 10 seconds. Want me to format Lesson 6 now?

::contentReference[oaicite:0]{index=0}

Chat with us
Chat
×

Want personal help? Leave your details and we can contact you.

Home Terms Of Use Contact Us Affiliate Disclosure DMCA Earnings Disclaimer