The quiet range and the volatility spike: two opposite ways this system breaks
This system fails in two opposite conditions, and the mitigation for one makes the other worse. Knowing which you are in is most of the skill.
Key takeaway
- In a quiet range both bands get tagged and the slope filter is the only thing standing between you and a loss every few days
- An ATR spike widens the stop and inflates risk unless the position size is recomputed — this is the expensive failure
- Widening the multiplier fixes the range problem and makes the spike problem worse; there is no setting that fixes both
Failure one: the quiet range
When volatility falls, the bands contract toward the EMA. A market oscillating in a narrow range now tags the upper band, then the lower, then the upper again — and each tag is technically a band breakout.
The slope filter is what saves you, and only partly. In a genuine range the EMA is flat, so most signals are correctly rejected. In a slowly drifting range it is not flat, and the system takes a series of small losses at the top of each oscillation.
Failure two: the volatility spike
This is the expensive one, and it is a risk failure rather than a signal failure. The rules still work; the position size is wrong.
A shock doubles ATR. The channel doubles in width. Your stop is now twice as far from entry as it was last week. If the position size was not recalculated, the trade carries twice the intended risk — and the environment that produced the ATR spike is the one most likely to deliver a large adverse move.
The mitigation is entirely mechanical: recompute size at every entry from the current stop distance, and treat a position size that rounds below one unit as the system declining the trade rather than as an inconvenience to be rounded up.
Why you cannot tune your way out
The obvious response to the range problem is to widen the multiplier so ordinary oscillation stops triggering signals. That works. It also means that when volatility spikes, the band is even further from the middle line and the stop is further still.
Narrow bands (1.5×)
- Signals early in a real move
- Fires constantly in a range
- Stop close to entry, so size is large
- Volatility spikes are survivable but frequent
Wide bands (3×)
- Ranges are quiet, as intended
- Most real trends never trigger at all
- Stop far from entry, so size is small
- Long idle periods that are hard to sit through
Both columns are marked as costs deliberately. There is no setting that is good at both, which is what it means for a system to have a genuine trade-off rather than an unfound optimum.
Three ways people break it themselves
- Dropping the slope filter because it rejected a signal that would have worked. It rejects many more that would not, and you only notice the first kind.
- Sizing once per market rather than per entry. The whole point of an ATR-based system is that the correct size changes; a fixed size discards it.
- Running it on a five-minute chart because the indicator computes there. Signal quality does not improve and costs do not shrink.
Common questions
- Is the Keltner squeeze a reliable signal on its own?
- It is a reliable signal that volatility is compressed and likely to expand. It contains no directional information at all. Traders who treat a squeeze as bullish are reading something into it that is not there — the breakout rules exist precisely to supply the direction the squeeze cannot.
- How do I handle an earnings gap in a stock I am holding?
- The honest answer is that you avoid it: the standard practice is not to hold this system's positions through scheduled binary events, because the stop is a price and not a promise. If you do hold, expect the inflated ATR to distort your sizing in that name for the following two weeks.
These are documented methods described for study. Nothing here is investment advice, a recommendation, or a claim about future returns — every system on this page has losing periods, and the pages say where.
Reading about a system is not having one.
Plutux is where you write your own rules down, test them against real data, and keep the record your memory would otherwise rewrite. Join the waitlist for early access.