Quiet before something, not quiet because of nothing
The measurement works everywhere; the trade only works where the quiet is temporary. Telling those apart is the market-selection problem in one sentence.
Key takeaway
- Liquidity is a hard requirement — the pattern reads highs and lows, and thin markets print meaningless ones
- An NR7 into a scheduled catalyst is a loaded spring; an NR7 in a market nobody trades is just a small bar
- The scan takes minutes a night, which makes a broad watchlist practical
Two kinds of quiet, only one of them tradeable
A market can be quiet because participants are waiting, or quiet because participants have left. The bars look identical. The first kind — a consolidation before earnings, a holiday-week drift in an index future, a currency pair coiling ahead of a policy decision — has an audience ready to act, and the contraction genuinely does load a spring.
The second kind has no spring at all. A neglected small cap prints narrow bars for weeks because nobody cares, every seventh one is technically an NR7, and the 'breakout' above a tiny bar's high is a handful of shares moving a thin book. The expansion never comes because there is nobody to supply it.
This is why the seed's market list is what it is: index futures, liquid stocks, FX. In those markets a lull is a decision to wait, and decisions to wait end.
The calendar tells you which quiet is which
| Market | The lull | What ends it |
|---|---|---|
| Liquid single stocks | Pre-earnings drift | The report and its guidance |
| Index futures | Holiday weeks, pre-Fed sessions | The macro print or the meeting |
| FX majors | Coiling ahead of policy decisions | The decision and the press conference |
| Anything liquid | A long consolidation after a move | The next marginal buyer or seller |
An NR7 that forms two sessions before a known event is the pattern at its best — the contraction and the catalyst explain each other. The same caution applies here as in every compression system: entering after the break is trading the expansion, while holding a position into the event itself is taking gap risk that no stop can manage.
Daily bars, and the fifteen-minute scan
Crabel's own work was intraday, and the pattern computes on any timeframe — but on a five-minute chart every lunchtime lull produces NR7s by the dozen, and almost none of them mean anything. The published version reads daily bars, where a seven-bar comparison spans a week and a half of real decisions.
- After the close, scan the watchlist for bars whose range is the narrowest of the last seven. This is one comparison per instrument and takes seconds each.
- For each hit, note the bar's high and low. Trigger and stop, respectively.
- Check the calendar. A known catalyst within a few sessions upgrades the setup; a dead calendar downgrades it.
- Place the orders or the alerts, then stop. There is nothing to watch until the market approaches the trigger.
Fifteen minutes a night is the honest budget, and the brevity is structural: the measurement is trivial, so the time goes into deciding which of the qualifying bars sit in markets where quiet actually predicts loud.
Common questions
- How often do NR7s appear?
- Often — on any single liquid instrument you will see one every couple of weeks, and a watchlist of twenty produces candidates most nights. The pattern is a weak filter on its own, which is exactly why the market-selection and catalyst context in this module does most of the sorting.
- Does this work on weekly bars?
- The arithmetic does — the narrowest week of seven marks a genuine multi-month contraction. But the holding logic changes: 'a few bars' becomes a month or more, the stop distance becomes a full week's range, and you are effectively trading a different, slower system. Test it as one rather than assuming the daily statistics carry over.
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.