A mitigation block is one of the more subtle ICT concepts because it is defined by what price fails to do, not by what it does. It forms when price pushes toward a prior swing point, cannot quite reach it, and reverses — leaving behind the last candle before the failed attempt as a zone where trapped positions get "mitigated" on the next visit. This guide covers what a mitigation block is, how it differs from an order block and a breaker block, a step-by-step process for identifying one, and how to journal mitigation block trades so you have real data instead of a hunch.
What Is a Mitigation Block?
A mitigation block forms when price attempts to break a prior high or low, fails to actually reach and run that level, and reverses direction instead. The last up-close or down-close candle before that failed push becomes the mitigation block. The name comes from what happens there on the next test: traders who entered on the failed breakout attempt are still underwater or flat, and when price returns to that zone, it is often "mitigating" their position — letting them exit near breakeven — before continuing in the original direction.
This is different from an order block, which marks the last candle before a level was actually taken out with a genuine structure break. A mitigation block exists precisely because the level was not reached. It is the footprint of an incomplete move, not a completed one.
Mitigation Block vs. Order Block vs. Breaker Block
| Mitigation Block | Order Block | Breaker Block | |
|---|---|---|---|
| How it forms | Price fails to reach a prior high/low and reverses | Last candle before a level is decisively broken | An order block that failed and flipped polarity |
| What it implies | A weak push that ran out of momentum early | Genuine institutional commitment through the level | A trapped position now acting as support/resistance |
| Relative strength | Generally the weakest of the three on its own | Stronger — confirmed by an actual break | Strong, but requires the original failure first |
| Typical trader mistake | Treating every failed push as a mitigation block | Marking a block before the break is confirmed | Confusing it with a fresh, untested order block |
How to Identify a Mitigation Block Step by Step
- 1Mark the prior significant swing high or low that price is approaching.
- 2Watch the push toward that level — does price actually sweep through it, or does it stall and turn before getting there?
- 3If price reverses without reaching the prior high/low, locate the last candle in the direction of that failed push.
- 4Mark that candle's range as the mitigation block.
- 5Wait for price to return to that zone on a later leg and watch for a reaction — a stall, a BOS/CHoCH, or rejection wick.
- 6Treat the mitigation block as a lower-confidence zone than a confirmed order block, and size accordingly.
Mitigation Block Entry Checklist
| Step | Question | Pass condition |
|---|---|---|
| Failed push | Did price fail to reach the prior swing high/low before reversing? | Clear stall short of the level, not a touch-and-reverse at it |
| Block location | Is the mitigation block the last candle before that failed push? | Correctly marked from the failed leg, not an arbitrary candle |
| Context | Does the higher-timeframe bias support a reaction at this zone? | Trend or structure agrees with the direction you are trading |
| Return test | Has price come back to retest the mitigation block? | First or second return, not a zone already used up repeatedly |
| Confirmation | Is there a reaction on arrival — rejection, BOS, or stall? | Visible rejection rather than price slicing straight through |
| Risk | Is the trade still at least 2R with a sensible invalidation? | Stop beyond the block, target at the next liquidity pool |
Example: A Failed Breakout Becomes a Mitigation Block
Price is rallying toward a prior high at 4,550. It pushes up to 4,542, stalls for two candles, and reverses lower without ever tagging 4,550. The last bullish candle before that stall — say the one that closed at 4,538 — becomes the mitigation block. Days later, price pulls back down and returns to the 4,538 zone. Traders who bought the failed breakout near 4,542 are still holding a small loss; as price taps 4,538 again, enough of them exit near breakeven that the zone produces a reaction, and price turns back down toward the next liquidity pool.
Common Mitigation Block Mistakes
- Labeling any pullback as a mitigation block instead of confirming the original push genuinely failed to reach the prior level.
- Treating a mitigation block with the same confidence as a confirmed order block, when it is structurally a weaker signal.
- Ignoring higher-timeframe context and trading a mitigation block against the dominant trend.
- Trading a mitigation block that has already been retested multiple times and lost its significance.
- Sizing positions the same way across mitigation blocks, order blocks, and breaker blocks without weighting for the difference in reliability.
- Never recording whether the trade was actually a mitigation block setup, making it impossible to review the concept's real performance later.
A mitigation block marks where a failed move gets cleaned up, not where a strong one begins. Treat it as a lower-confidence zone until your own data says otherwise.
How to Journal Mitigation Block Trades
Because mitigation blocks are easy to mislabel in hindsight, the most useful thing you can do is separate them from order blocks and breaker blocks in your journal tags rather than lumping every supply/demand zone together. Record the specific type of block so you can measure whether mitigation blocks are actually worth trading for you, or whether you only take them confidently in hindsight.
| Field | Example | What it reveals |
|---|---|---|
| Block type | Mitigation block (failed push to 4,550) | Whether this specific block type is being tracked separately |
| Failed level | 4,550 high, price reached 4,542 | Whether your failed-push identification is accurate |
| Retest count | 1st return to the zone | Whether block reliability decays with repeated tests, as expected |
| Confirmation on return | Rejection wick + CHoCH on the 15m | Whether you are waiting for real confirmation or entering blind |
| Result in R | +1.8R | Expectancy of mitigation blocks specifically vs. order/breaker blocks |
After 30+ tagged mitigation block trades, compare their win rate and expectancy against your order block and breaker block trades. If mitigation blocks consistently underperform, that is a signal to size them smaller or skip them entirely — not a reason to stop marking them, since the only way to know is to keep the data separate.
A level that failed once can still matter later — but it earns a smaller position size until your journal proves otherwise.
TradeEdge lets you tag trades by block type — mitigation, order block, or breaker — then automatically compares win rate, expectancy, and R-multiple across each, so you know exactly which zones are actually worth your risk.