BearishReversalIntermediate

Dark Cloud Cover

A bullish candle is followed by a bearish candle that closes well into the prior body.

Professional chart anatomy

Dark Cloud Cover

Illustrative example
Context
Uptrend
Confirmation
Follow-through below the second candle low or nearby support.
Invalidation
Break above the pattern high.
Educational chart, not live market data. Real formations vary in symmetry, duration and volatility.

What the market is communicating

Buyers begin in control, but sellers reclaim more than half of the prior body.

Volume behaviour

Stronger with increased participation on the second candle.

Pro-trader lensDo not evaluate this formation in isolation. Compare relative strength, broader market regime, liquidity, volatility and nearby higher-timeframe levels.

Recognition checklist

  • Occurs after advance
  • First candle bullish
  • Second candle opens strong or higher
  • Second closes below midpoint of first body
  • Does not fully engulf first body

Quality improves when

Location is logical

The setup forms near a meaningful support, resistance or trend transition.

Structure is clean

Defining swing points are visible without forcing the label.

Participation confirms

Volume, volatility or relative strength supports the resolution.

Confirmation and trade planning

ConfirmationFollow-through below the second candle low or nearby support.
InvalidationBreak above the pattern high.
Target frameworkUse nearby support and risk/reward.
Best useIntraday · Swing

Aggressive versus conservative approach

AggressiveConservative
TriggerEarly boundary resolutionClose plus acceptance or retest
AdvantageBetter potential entryMore confirmation
Trade-offHigher false-break riskMay enter later or miss the move

Measured targets are planning references, not forecasts. Position size should be derived from defined account risk and the actual invalidation distance.

Failure modes and trader traps

  • Confusing it with bearish engulfing
  • Ignoring resistance context
  • Accepting a close above midpoint

Looks valid—but may not be

A pattern can satisfy the visual outline yet fail because it forms in the wrong context, lacks sufficient touch points, breaks on weak participation or immediately returns inside the structure. A failed setup is information, not an exception to ignore.