A simple MTF confluence checklist I use before any XAUUSD scalp

[Fairman]

Before any XAUUSD scalp I run a short multi-timeframe confluence check. If the layers do not line up, I do not take the trade. No indicator soup, no “almost aligned,” no forcing a trigger because the session is liquid.

The stack I use is fixed:

1. H1 bias — direction and context only. I mark the recent swing structure, whether price is accepting above/below a clear level, and whether the last few H1 candles show continuation or exhaustion. Bias is binary for the session idea: long-leaning, short-leaning, or no trade. If H1 is messy or mid-range with no clear acceptance, M1 noise is not a setup.
2. M15 structure — the map for where a scalp is allowed. I want a clear break-and-retest, liquidity sweep and reclaim, or a failed break of a level that already mattered on H1. M15 tells me the location. Without a location, a pretty M1 candle is just a pretty candle.
3. M1/M5 trigger — timing only after H1 and M15 agree. Entry is a specific rejection, reclaim, or continuation print at the M15 level, with a stop beyond the invalidation of that micro structure. If the trigger appears but H1/M15 disagree, I pass.

Checklist I tick mentally (and often in the journal) before clicking:

- Session permission: London/NY overlap or my defined window, not random hours.
- Spread within my max gate for gold.
- No high-impact USD release inside my blackout window unless the setup is on my rare pre-defined exception list (usually empty).
- H1 bias stated in one sentence.
- M15 level and invalidation marked.
- M1/M5 trigger matches the bias, not fighting it.
- Risk sized from stop distance, not from “how sure I feel.”

What I refuse:

- Taking M1 reversals against a clear H1 trend just because a wick looked dramatic.
- Stacking RSI, MACD, and three moving averages to justify a trade the structure already rejected.
- Entering because “gold is moving” during overlap. Movement is not confluence.
- Lowering the checklist mid-session after a win or a loss. Confluence rules are decided when I am calm.

A practical example of refusal: H1 bullish acceptance above a reclaimed level, M15 still compressing under a local high with no sweep/reclaim yet, M1 printing a sharp long wick. That is not an A+ long. It is a lower-timeframe tease. I wait for M15 to confirm location or I stand aside.

Using a single timeframe in isolation means you are making decisions with a genuinely incomplete picture. H1 without a trigger is analysis. M1 without H1/M15 is gambling with a tight stop. The checklist exists so I do not confuse activity with process.

If your XAUUSD scalps feel random, strip the chart back to this three-layer gate for a week. Count how many impulses you skipped because alignment failed. Those skipped trades are often the edge — not the ones you forced when only one timeframe was shouting.

[LondonScalper]

Clean stack. Forcing “almost aligned” on gold is expensive.

I use a similar gate before XAUUSD:

H1 — bias / nearby structure (not a prediction, a permission filter)
M15 — location (sweep, reclaim, clear level)
M1/M5 — trigger only if the two above already said yes

If H1 is messy, I don’t “find” an M1 story. Session liquidity is not confluence.

Optional add-on that’s helped: a spread/slippage gate as checkbox #0. Beautiful MTF alignment with a 40-point gold spread is not an A+ scalp.

Do you ever allow a two-layer pass (skip H1) in London open only, or is H1 always mandatory?

[PTScalper]

Clean stack. Forcing “almost aligned” on gold is expensive.

I use a similar gate before XAUUSD:

H1 — bias / nearby structure (not a prediction, a permission filter)
M15 — location (sweep, reclaim, clear level)
M1/M5 — trigger only if the two above already said yes

If H1 is messy, I don’t “find” an M1 story. Session liquidity is not confluence.

Optional add-on that’s helped: a spread/slippage gate as checkbox #0. Beautiful MTF alignment with a 40-point gold spread is not an A+ scalp.

Do you ever allow a two-layer pass (skip H1) in London open only, or is H1 always mandatory?

Regarding the H1 filter at the London open:

If you skip the H1, you are essentially trading a completely different system. When you drop down to a two-layer pass (M15 → M1/M5) during the London open, you are no longer trading structural alignment; you are trading pure session momentum and liquidity sweeps.

Is it viable? Yes, but it usually requires its own isolated rule set. London open volume is notorious for hunting Asian session stops before establishing the true daily direction. Because of this, if the H1 is messy or contradicting, that M15 "clear level" is highly susceptible to becoming a trap.

If you do bypass the H1 permission filter during London, it is generally safer to restrict your M1/M5 triggers exclusively to fading the initial sweeps of the Asian range, rather than playing continuations. If you are looking for trend continuation, keeping the H1 mandatory is the best way to avoid getting chewed up in the early-session chop.

[PTScalper]

Btw: If you are automating or semi-automating this, it requires its own isolated rule set. Here is a clean way to structure this logic in cTrader using C# to ensure the H1 bypass is strictly contained:

Code: Select all

[Parameter("Max Gold Spread (Pips)", DefaultValue = 4.0)]
public double MaxSpread { get; set; }

[Parameter("Allow London H1 Bypass", DefaultValue = false)]
public bool SkipH1InLondon { get; set; }

private bool IsTradePermitted()
{
    // Checkbox #0: Hard Spread Gate
    if (Symbol.Spread > MaxSpread) 
        return false;

    // Define London Open Window (e.g., 08:00 - 10:00 UTC)
    bool isLondonOpen = Server.Time.Hour >= 8 && Server.Time.Hour < 10;

    // H1 Permission Filter (Insert structural logic, e.g., EMA/PA alignment)
    var h1Bars = MarketData.GetBars(TimeFrame.Hour);
    bool isH1Aligned = EvaluateH1Structure(h1Bars); 

    // Session logic: Allow two-layer pass strictly during London Open
    if (SkipH1InLondon && isLondonOpen)
    {
        return true; 
    }

    // Default state: H1 is always mandatory
    return isH1Aligned;
}

[LondonScalper]

If you skip the H1, you are essentially trading a completely different system.... London open volume is notorious for hunting Asian session stops

That’s the honest framing. Two-layer (M15 → M1/M5) at the London open isn’t “MTF with a shortcut”; it’s a momentum/sweep playbook wearing confluence clothes.

Viable? Yes — with its own rules, size, and stop philosophy. I don’t mix it with the three-layer checklist and pretend it’s the same expectancy.

When H1 is messy, that clean M15 level is often bait for the Asian stop-run. On gold especially I’ll either wait for H1 permission or deliberately switch to a labelled “session sweep” mode at half size — never the full A+ stack with a missing filter.

[PTScalper]

If you skip the H1, you are essentially trading a completely different system.... London open volume is notorious for hunting Asian session stops

That’s the honest framing. Two-layer (M15 → M1/M5) at the London open isn’t “MTF with a shortcut”; it’s a momentum/sweep playbook wearing confluence clothes.

Viable? Yes — with its own rules, size, and stop philosophy. I don’t mix it with the three-layer checklist and pretend it’s the same expectancy.

When H1 is messy, that clean M15 level is often bait for the Asian stop-run. On gold especially I’ll either wait for H1 permission or deliberately switch to a labelled “session sweep” mode at half size — never the full A+ stack with a missing filter.

Calling out that clean M15 level as bait is at right place, especially on metals. When H1 is compressed or directionless, that pristine M15 level isn't support or resistance—it’s engineered liquidity designed specifically to feed the stop-run against the overnight Asian range.

Walling that off into a distinctly labeled "session sweep" regime with halved risk is the only disciplined way to handle it. The fastest way to ruin a strategy's expectancy is taking a compromised checklist, rationalizing it as "confluence," and sizing it like an A+ ticket. If the HTF filter isn't there to grant permission, the trade simply doesn't belong in the primary ledger.

When you switch down into that "session sweep" mode at the open, do you insist on an immediate structural rejection on the M1/tick tape to get involved, or do you fade the sweep extreme with a predetermined limit and a tight, fixed invalidation?