How to Log Market Conditions With Each Trade

The same setup does not pay the same in every market

You take a breakout. It works. You take the same breakout two weeks later, same rules, same size, and it fails at the open and stops you out. Nothing about your execution changed. What changed was the market around the trade: the trend flipped, volatility expanded, the session was quieter. That is exactly why you log market conditions in a trading journal alongside the entry itself.

Most journals record the trade and ignore the weather it happened in. So when you review, every trade looks like it lived in the same environment. It did not. A momentum setup that prints in a trending, high-volatility tape can bleed money in a flat, quiet one, and if your journal cannot tell those two days apart, your win rate is an average of two different strategies pretending to be one.

The fix is a small, disciplined context layer: a handful of fields you record before you enter, describing the conditions the trade is walking into. Do it consistently and your history stops being one undifferentiated pile and starts being sortable by regime. You can pull every trade you took in a trending market and compare it against everything you took in chop.

Here is the short version:

• Log market conditions at entry, never after you see the result.
• Capture three axes that actually move outcomes: trend, volatility, and session/context.
• Use a small controlled vocabulary per axis, one spelling each, so the field stays queryable.
• Keep the reading objective: anchor labels to indicators or index levels, not to a gut feeling.
• Slice by regime only after you have enough trades in each bucket to trust the number.

Why regime beats "the market was choppy"

There is real evidence that market behavior clusters into regimes rather than drifting randomly. Benoit Mandelbrot noticed in 1963 that "large changes tend to be followed by large changes, of either sign, and small changes tend to be followed by small changes." Robert Engle formalized that observation into the ARCH model in 1982, work that won him a share of the 2003 Nobel Memorial Prize in Economic Sciences "for methods of analyzing economic time series with time-varying volatility" (The Nobel Prize, 2003). The practical takeaway for a trader is blunt: volatility is not constant, it clusters. A calm market and a violent one are genuinely different environments, and treating them as one market with more noise loses the distinction that matters.

That matters because your edge is usually conditional. A trend-following setup wants a trending tape. A fade or mean-reversion setup often wants elevated volatility and a range. When you average all of those together in one win-rate figure, you get a number that describes no real trading condition. The point of logging market conditions is to un-average that number and see which environment your setup actually pays in.

If you have already read what to log in a trading journal, think of market conditions as the context columns sitting alongside your entry, exit, and size. They are not decoration. They are the axis you will eventually slice performance along.

The three axes worth logging

You could tag a hundred things about the market. Do not. A context layer that takes ninety seconds to fill in gets skipped, and a field you skip half the time is worse than no field, because the gaps quietly bias every summary you run. Pick three axes that genuinely change how setups behave, and give each a tiny controlled list.

Trend: is there a direction to lean on

Trend is the first question a setup cares about. Is price going somewhere, or is it stuck in a box. Keep the vocabulary to three or four values:

• up (higher highs and higher lows on your reference timeframe)
• down (lower highs and lower lows)
• range (bounded, no clean directional structure)

To keep this objective rather than a mood, anchor it to a repeatable reading. A moving-average stack (price above a rising 20 and 50 EMA, say) is one simple anchor. Another is the Average Directional Index, or ADX, which J. Welles Wilder introduced in his 1978 book New Concepts in Technical Trading Systems specifically to measure trend strength independent of direction. A common convention treats readings above roughly 25 as a trend worth respecting and readings below 20 as directionless. The exact threshold matters less than picking one and applying it the same way every time.

Volatility: how much room is price using

Volatility decides how far things travel and how violently they reverse. Two clean anchors:

• Average True Range (ATR), also from Wilder's 1978 work, measures how much an instrument moves per bar. Compare a short-window ATR to a longer-window ATR: when the short one is meaningfully larger, volatility is expanding.
• The VIX, for equity traders, measures the market's expectation of 30-day volatility of the S&P 500 from index option prices (Cboe, VIX methodology). It is a fast, public read on how nervous the broad market is.

For context on how wide that dial actually swings: the VIX set its all-time closing record of 82.69 on March 16, 2020 during the COVID crash, after peaking at a close of 80.86 on November 20, 2008 during the financial crisis, versus long stretches in the low teens in calm years (VIX, Wikipedia summarizing Cboe data). A setup tested only in a teens-VIX market has told you nothing about how it behaves at 40. Log it as a small band: low, normal, high.

Session and context: the stuff a chart alone will not show

The third axis is everything structural that a price reading misses. Keep it to what changes behavior on your instrument:

• Session or time: pre-market, open, mid-day lull, close. Liquidity and follow-through differ across them.
• Scheduled events: was there a Fed decision, CPI print, or an earnings report on your symbol that session. Central bank and inflation releases routinely reprice risk.
• Breadth or leadership, if you trade stocks: was the broad tape confirming or fighting your trade.

You do not need all three every time. One field, "event / no event," already separates the days your journal should probably analyze separately.

Log it at entry, or do not log it at all

This is the one rule that makes or breaks the whole exercise. Record the market-condition tags before you know the outcome, ideally as part of your pre-trade checklist.

The reason is a bias you will not feel yourself committing. If you label the regime after the trade closes, your memory of "the market was choppy" is contaminated by whether you won or lost. Winners get remembered as clean trends; losers get remembered as chop. Tag after the fact and you will quietly draw a correlation that is really just you rationalizing results. The data will look like a discovery and be an illusion.

Logged at entry, the tag is a fact about the world that existed independent of your result. That is the only version worth analyzing. If your workflow makes this hard, shrink the fields until it is a five-second job: three dropdowns and a checkbox. Conditions belong with the rest of the facts you know before you commit, alongside everything else in what to log in a trading journal, firmly on the pre-trade side of the entry.

Keep the vocabulary small and spelled one way

A context field is only useful if a single filter returns every trade that belongs in it. The failure mode is the same one that wrecks any tag system: high, High, hi, and elevated all meaning the same thing, spread across four spellings, so no filter catches them all. This is the whole argument of building a proper trading journal tagging system: pick a controlled list per axis, allow one spelling per value, and resist the urge to invent a new label mid-session.

Concretely, that is roughly:

• Trend: up, down, range
• Volatility: low, normal, high
• Session: pre, open, mid, close
• Event: yes, no

That is eleven values across four fields. Small enough that every bucket eventually collects enough trades to mean something, and rigid enough that the filter is trustworthy. If you find yourself wanting a fifth trend value, that is usually a sign the axis is trying to do two jobs, not that you need more labels.

Reading it back: slice, but respect sample size

Once you have a stack of trades with conditions attached, the payoff is a regime breakdown: your win rate, average win, average loss, and expectancy, computed separately for each condition bucket. This is where a setup that looked mediocre overall reveals itself as excellent in one regime and a slow bleed in another. That is a decision you can act on, either by only taking the setup in its regime or by sizing down when conditions are wrong.

Two cautions keep this honest.

First, sample size. Slicing multiplies your buckets fast. Split by trend and volatility at once and one trade now lands in one of nine cells. Four trades in a cell give you an anecdote, not a win rate. Wait until a bucket holds enough trades to survive a couple of coin flips going the wrong way before you trust its number, and treat thin cells as "not enough data yet" rather than a finding.

Second, do not confuse rare with bad. A regime you traded three times and lost in is not proven unprofitable. It is unmeasured. Keep collecting before you exile a setup from a condition.

When you sit down for your periodic review, the regime breakdown is one of the most useful views to run. If you are formalizing that habit, how to audit your trading journal walks through checking your history for exactly the gaps and inconsistencies that would corrupt a regime slice, empty condition fields being the first thing to hunt for.

Where a tool helps, and where discipline is still yours

The mechanical parts of this are easy to hand off. In TradeReveal, market-condition tags are just tag dimensions on a trade, and the Trade Explorer lets you filter and compare performance across those slices, so building the regime breakdown is a matter of selecting the bucket rather than rebuilding a spreadsheet pivot by hand. The free core covers the journaling, the tagging, and the analytics you need for this.

What no tool does for you is the discipline of logging conditions honestly, at entry, every time. A field the software provides but you fill in inconsistently produces a clean-looking chart built on a dirty dataset, which is more dangerous than no chart at all. The value is in the habit. The software just makes the habit cheap to keep.

Frequently Asked Questions

What market conditions should I record for each trade?

Start with three axes that actually change how setups behave: trend (up, down, or range), volatility (low, normal, or high), and session or event context (the time of day and whether a scheduled event like a Fed decision or earnings report was in play). Three fields cover most of the signal. Adding more usually costs you consistency without adding much insight.

Should I log market conditions before or after the trade?

Before, without exception. Record the tags at entry, as part of your pre-trade checklist. If you label the regime after you know whether the trade won, your memory of "the market" gets colored by the result, and you end up measuring your own rationalization instead of the market. Logged at entry, the tag is an objective fact you can trust when you analyze it later.

How do I keep the "trend" or "volatility" label objective instead of a gut call?

Anchor each label to a repeatable reading. For trend, use a moving-average stack or an ADX threshold (a common convention treats ADX above about 25 as a real trend). For volatility, compare a short-window ATR to a longer one, or read a volatility index like the VIX and bucket it into bands. The exact number matters less than applying the same rule every single time.

How many trades do I need before the regime breakdown means anything?

Enough per bucket, not enough in total. Slicing by two axes at once splits your history into many small cells, and a cell with a handful of trades is an anecdote, not a win rate. Treat thin buckets as "not measured yet" and keep collecting. A losing bucket with four trades in it has not proven the setup fails there, only that you have not sampled it.

Is the VIX useful if I do not trade equities?

The VIX is specific to the S&P 500, so its exact level is most relevant to equity traders. The underlying idea, that volatility clusters and shifts between calm and violent regimes, applies to every market. For non-equity instruments, use an ATR-based volatility read on the instrument you actually trade rather than the VIX itself.

Final Thoughts

A trade does not happen in a vacuum. It happens in a trend, at a volatility level, in a session, with or without an event pushing the tape. Record those conditions at entry, keep the vocabulary small and consistent, and your journal gains an axis it did not have before. Your win rate stops being a blur of different environments and becomes a set of honest, regime-specific numbers you can actually trade on. The work is a few dropdowns before each entry. The reward is finally knowing which market your edge lives in.

Sources

• The Nobel Prize, "The Sveriges Riksbank Prize in Economic Sciences 2003" (Robert Engle, ARCH, time-varying volatility): nobelprize.org
• Cboe, "Cboe Volatility Index (VIX)" methodology overview: cboe.com
• "VIX" (all-time record close of 82.69 on 2020-03-16; prior peak close of 80.86 on 2008-11-20), Wikipedia summarizing Cboe data: en.wikipedia.org/wiki/VIX
• J. Welles Wilder, New Concepts in Technical Trading Systems (1978), original source of ADX and ATR: publisher/reference listing
• Nielsen Norman Group, "Taxonomy 101" (faceted vs. hierarchical classification, on keeping controlled vocabularies): nngroup.com

Start your free TradeReveal account today

Happy Trading,

The TradeReveal Team