← All posts

ICT Confluence: How to Score Your Setups Before Entry

May 3, 20265 min readTradeForge Team
ICTConfluenceStrategy

Every ICT trader has felt this. The chart looks "clean," the entry feels right, and you take the trade — and lose. Then a week later, a setup that felt mediocre prints a clean three-R win. That gap between feeling and outcome is exactly where ICT confluence scoring lives. When you grade setups objectively before entry, the pattern stops being mysterious. The setups that pay you stand out, and the ones that drain you become impossible to take by accident.

This guide walks through a practical ICT confluence framework you can apply in 30 seconds before any entry, plus the discipline rules that keep it honest.

What ICT Confluence Actually Means

ICT confluence is not just "more reasons to be in the trade." A scoring system stacked with junk reasons will tell you to take everything.

ICT confluence means independent, structural reasons — each one anchored in a real ICT concept — that align at your entry. The keyword is independent. Three reasons that all derive from the same structural fact count as one. Two reasons from different layers of the framework count as two.

A clean ICT confluence score asks: how many separate, non-overlapping ICT concepts are pointing at this exact entry?

The Eight-Point ICT Confluence Checklist

This is the framework. Eight items. Each is binary — yes or no. Your score is the count of yeses.

1. Higher-timeframe bias. 1H structure is making higher highs / higher lows for longs, or the inverse for shorts. If the 1H is messy, this is a no.

2. Liquidity sweep. Price has just taken out a meaningful liquidity pool — previous day high/low, session high/low, or an obvious equal-highs / equal-lows. Internal liquidity inside a range counts as a no.

3. Market structure shift. On the entry timeframe (1m or 5m), price has shifted structure since the sweep. A sweep without a shift is a no.

4. Displacement. The candles that produced the shift were strong, with bodies dominating wicks. Slow, overlapping candles are a no.

5. FVG or OB at entry. Your entry is into a clean Fair Value Gap or Order Block created by the displacement candles. "Close enough" is a no.

6. Session timing. The setup is forming inside London, NY AM, or NY PM. Lunch chop, overnight Asia drift — those are nos.

7. Discount / premium alignment. Longs are entered in a discount zone of the most recent dealing range. Shorts are entered in a premium. Mid-range entries are a no.

8. Higher-timeframe draw. There is a clearly defined target — previous day high, weekly high, an unmitigated FVG above. Something for price to actually reach for. "It looks like it could go up" is a no.

Score every setup. Don't fudge.

How to Use Your ICT Confluence Score

Three tiers, three actions:

A+ setup (7–8 of 8). Take it at full size. These are the trades you wait all day for. Honor your stop. Trust the level.

A setup (5–6 of 8). Take it at planned size, but ratchet expectations. Many of these will be one-R chops. That is fine — they are still positive expectancy.

B setup (3–4 of 8). Skip or take half size. A "B" setup that wins still wins. The problem is that the wins do not pay you enough to cover the losses. Be ruthless here.

Below 3. Not a trade. The reason something feels like a trade at score 2 is almost always that you are bored, tilted, or underexposed for the day. Walk away.

The point of an ICT confluence score is not to be right about every individual trade. It is to make sure your average trade is taken at high score. A trader who only takes 7+ scores will have a wildly different P&L from a trader who takes anything 4+, even with the same setup recognition.

The Discipline Layer

A scoring system fails the moment you start massaging the inputs. Three rules keep ICT confluence honest:

  • Score before entry, not after. Once price moves in your favor, the urge to retroactively upgrade the score is overwhelming. Lock the score in before you click.
  • Use the same eight items every time. Do not invent new confluence factors mid-session. New ideas are great — they belong in the journal, not in the live scoring.
  • Write the score in your journal. Not "looked solid." A number, 0–8, every trade. Without that, you cannot answer the question that makes the system valuable: what is my win rate at each score?

After 100 trades, you will see a curve. Win rate at score 8 will be much higher than win rate at score 4, and the magnitude of that gap is the most important number in your trading.

What Doesn't Count as ICT Confluence

This is where most scoring systems go off the rails. The following do not count as additional confluence — even though traders constantly add them:

  • Round numbers, pivots from other systems, indicator signals (RSI, MACD, etc.). These are not ICT concepts.
  • Multiple FVGs stacked at the same level. That is one zone, not two.
  • "Price respected this level last week." Past respect is not future confluence unless that level is itself an ICT structural feature.
  • Your gut. Score the chart, not the feeling.

Strip these out and your scores get more honest, your A+ pile gets smaller, and your win rate goes up. That is the trade you want to make.

Building ICT Confluence Into Your Journal

A confluence score is only useful if you can query it. The single most powerful filter you can run on your trading journal is win rate by score. If you can do that, you can answer:

  • What is my actual edge at each score level?
  • Which confluence factor most reliably appears in my winners?
  • Which factor is just noise — present in winners and losers equally?

Without a journal that captures the score, none of those questions are answerable. You are guessing.

This is exactly the kind of thinking TradeForge was built around. Every ICT confluence factor is a tag on the trade form, the playbook lets you require minimum scores per setup, and the analytics layer breaks down win rate by score, by tag, and by combination so you can see — clearly — what is paying you and what is leaking.

A scoring system isn't about being scientific for its own sake. It is the simplest way to slow down before clicking, force a structural review, and make sure your size matches the setup. Master ICT confluence as a habit, and the difference between an A+ day and a B-grade day becomes a number you can see, not a feeling you have to manage.

Try TradeForge free →

Build the journal your edge deserves

TradeForge is the trading journal built for ICT traders — log FVGs, bias, sessions, and confluence, and let the analytics show you exactly where your edge lives.

Try TradeForge free →