How to Journal Supply & Demand Zone Trades

Supply and demand zone trading lives or dies on metadata precision — not just whether you took the trade, but which zone type, how many prior tests had occurred, and exactly how price behaved when it arrived. Generic journaling that logs only entry and exit price turns dozens of structurally distinct setups into a single undifferentiated sample. Journaling the right fields from the start lets you answer the question that matters: which zone setups, in your instrument, on your timeframe, actually have edge?

Essential Fields to Track

Field	Why It Matters
Zone Origin Type	Base-and-move (consolidation before impulse) and single-candle spike zones have different reliability profiles; mixing them obscures which structure is driving your results
Touch Count at Entry	Each prior visit to a zone consumes resting limit orders; fresh zones (0 touches) carry higher hold rates than revisited ones — this field is your most powerful performance filter
Zone Boundaries (High/Low)	Exact boundaries let you calculate zone width, measure entry position within the zone, and set stops relative to structure rather than candle wicks
Entry Position Within Zone	Edge entry vs. mid-zone vs. far side produces different risk profiles; tracking this reveals timing consistency across your sample
Stop Distance — Points and % of Zone Width	A stop that is 5% of zone width is structurally tight; 40% is loose — logging both values makes cross-instrument and cross-timeframe comparisons valid
Higher-Timeframe Confluence	A 15-min demand zone nested inside a daily demand zone should be tagged separately; confluence zones tend to produce sharper, faster reactions
Reaction Type at Zone	Sharp reversal candle, wick rejection, or slow grind through each signal different demand strength and correlate differently with trade outcomes
Zone Status Post-Trade	Marking zones as ‘consumed’ or ‘intact’ after each trade builds a zone reliability database; after 30+ trades you can calculate zone-type win rates
Target and R-Multiple	Comparing realized R against the structural target reveals whether supply/demand setups are delivering the theoretical edge the chart structure implies

Touch count and zone origin type are the two most critical fields. Without them, a sample of 50 trades may appear to have a 52% win rate — but segmenting by touch 0 base-and-move vs. touch 1+ spike often reveals one group running at 65% and the other at 38%. That split is where the actual trading decision lives.

Sample Journal Entry

Date: 2026-03-14 Ticker: SPY Timeframe: Daily Zone Type: Base-and-move (demand) Zone Boundaries: $510.00 – $513.00 (width: $3.00) Touch Count at Entry: 0 (fresh) HTF Confluence: Yes — sits inside weekly demand $508–$514 Entry: $511.50 (mid-zone) Stop: $509.20 (1.5 ATR below zone low of $510; $2.30 stop = $0.80 below zone low) Target: $521.00 (prior swing high) Setup R-Multiple: 4.1R Reaction Type: Sharp reversal candle, no candle close inside zone Exit: $520.75 (+$9.25, +4.0R) Zone Status After Trade: Consumed — price rallied through; level unlikely to hold on next test Emotion: Patient — waited 2 sessions for price to reach the zone Lesson: HTF confluence added conviction; stop below zone low (not candle low) survived a wick before the reversal

SPY’s typical daily ATR of $3–6 makes the $2.30 stop a 1.5 ATR placement — a concrete, repeatable risk unit. The stop distance of $2.30 against the $3.00 zone width is 77% of zone width, which is on the wider end; for tighter base-and-move zones, this ratio often drops to 30–40%.

Review Process

1. After each trade — update zone status — before closing the chart, mark the zone as ‘consumed’ or ‘intact’ in your zone log. This detail is lost after the session ends and cannot be reconstructed from price data alone.
2. Weekly — split by zone origin type — filter your trades into base-and-move and spike categories and calculate win rate for each. Do not draw conclusions until you have at least 30 trades per category; that is the minimum sample for win-rate statistics to be meaningful.
3. Weekly — compare touch 0 vs. touch 1+ performance — calculate average R-multiple and win rate for fresh zones vs. revisited zones. If touch 1+ entries show a win rate under 45%, consider restricting new entries to fresh zones only.
4. Monthly — audit stop placement consistency — calculate the average stop distance as a percentage of zone width across all trades. High variance (e.g., ranging from 8% to 55%) indicates inconsistent risk management that will distort your R-multiple statistics.
5. Monthly — correlate reaction type with outcomes — identify which reaction type (sharp reversal, wick rejection, slow grind) preceded your winning trades vs. your losing trades. Use this to add a reaction-type confirmation requirement to your entry criteria.
6. Monthly — evaluate HTF confluence impact — compare win rates for trades taken with daily/weekly confluence vs. standalone lower-timeframe zones. For most instruments, confluence zones produce 10–15 percentage points higher hold rates — verify this holds in your own data before making it a hard filter.
7. Quarterly — assess timeframe effectiveness — determine whether daily and 4-hour zones are outperforming 15-min and 1-hour zones in your primary instrument. Higher-timeframe zones attract more institutional order flow, but the evidence should come from your own sample of 30+ trades per timeframe tier.

Common Mistakes in Supply & Demand Zone Journaling

1. Not separating zone origin types — logging every trade as “demand zone” without specifying base-and-move vs. spike collapses two setups with different statistical profiles into one blended number. Over 35 trades, this can hide a 68% win rate on base-and-move setups sitting underneath a 44% win rate on spike setups.
2. Setting the stop relative to the entry candle, not the zone low — when price wicks into a zone and reverses, the entry candle low is often well inside the zone. A stop below the candle low is structurally arbitrary; a stop 1–1.5 ATR below the zone low is structurally meaningful and produces a consistent stop-to-zone-width ratio you can track and optimize.
3. Skipping touch count when entering quickly — this single field is the most actionable filter in supply/demand journaling and the easiest to omit under time pressure. Without touch count data, you cannot split fresh vs. revisit performance — the analysis that most directly informs position sizing decisions.
4. Not updating zone status after the trade — a zone left as ‘untested’ in your log that has actually been consumed will generate false signals if you ever revisit your zone database. Set a hard rule: before you close any trade, update zone status.
5. Recording reaction type based on outcome, not observation — traders sometimes label a slow grind through a zone as a “reversal” because the trade eventually worked. Reaction type must be recorded at the moment of zone touch, describing what price actually did, not what the trade result was.

How JournalPlus Handles Supply & Demand Zone Trades

JournalPlus supports custom fields at the trade level, which maps directly to the zone-specific metadata supply/demand traders need. Zone origin type, touch count, reaction type, and zone status can be added as dropdown or text fields and then used as filters in the analytics dashboard — allowing the kind of touch 0 base-and-move vs. touch 1+ spike segmentation described above without any external spreadsheet.

The tagging system supports both setup tags (e.g., sd-fresh, sd-revisit, htf-confluence) and outcome tags (zone-consumed, zone-intact), making it possible to build a running zone reliability database within the journal itself. Filtering by tag across 30+ trades produces the win-rate breakdowns that give supply/demand trading its statistical foundation.

For traders who also journal breakout trades or trend-following trades, JournalPlus allows side-by-side comparison of win rates across strategy types using the same analytics view — useful when supply/demand zones overlap with breakout entries or technical analysis setups. The weekly review workflow integrates directly with these filters, so the monthly zone-type audits described above can be completed within the platform rather than exported to a spreadsheet.