Range trading is one of the most repeatable setups in forex — but only if you can measure whether your version of it actually works. Most traders lose their edge in ranging markets because they never separate range trades from trend trades in their journal. This guide shows intermediate traders how to log, tag, and review range-bound positions so the data tells you exactly where you profit and where you leak.
Step 1: Define and Tag Your Range Parameters
A range trade only goes into analysis if it was identified as a range trade before entry. Log the range boundaries as specific price levels — not zones, specific prices. Record:
- Range high (resistance): exact price, e.g., 1.08450
- Range low (support): exact price, e.g., 1.08120
- Range width: 33 pips in this example
- Range age: how many touches each boundary had before your entry (minimum 2 touches per side for a valid range)
Add a tag like setup:range or setup:range-support / setup:range-resistance to distinguish which boundary you faded. This tag is the foundation for all batch analysis later. Without consistent tagging, filtering is impossible and your review will be garbage.
Step 2: Record Entry Confluence and Trigger
Log every piece of confluence that triggered the entry. The goal is to eventually filter range trades by confluence type and see which combinations produce the highest win rate. Capture:
- Trigger: what caused you to enter (e.g., bearish engulfing at resistance, RSI divergence, pin bar rejection)
- Confluence factors: session timing, trend context on higher timeframe, volume, proximity to round number
- Entry price and distance from the boundary in pips (entering 8 pips off resistance is different from entering exactly at it)
A useful format: entry at 1.08410 (4 pips below resistance), H1 bearish engulfing, RSI 68, Asian session consolidation. Over 30+ trades, you will see which confluence combinations actually improve your boundary-to-boundary hit rate.
Step 3: Track MFE and MAE Against Range Width
This is the metric most range traders ignore and it is the most revealing. After closing the trade, log:
- MFE (Maximum Favorable Excursion): the furthest price moved in your favor before close
- MAE (Maximum Adverse Excursion): the furthest price moved against you before close
- MFE as % of range width: MFE pips divided by total range width. On a 33-pip range, an MFE of 28 pips = 85% capture rate.
Target a median MFE capture rate above 70% of range width. If your MFE capture is consistently below 50%, you are either exiting too early or entering too far from the boundary. MAE consistently above 10 pips on a 33-pip range indicates your entry timing is off — see how to analyze entry timing for a framework to fix this.
Step 4: Log Exit Type and Boundary Reaction
Log exactly how the trade ended and what price did afterward:
- Exit type: target hit, partial exit, trailing stop, manual close, stop loss
- Exit price and pips captured
- Post-exit price action (log this when you review the chart the next day): did price reach the opposite boundary after your exit? Did it break out?
This post-exit tracking reveals whether your exits are premature. If price reached your original target on 70% of trades where you exited early, you have a clear exit problem — not an entry problem. Pair this with how to analyze exit timing to quantify the cost of early exits in R terms.
Also log whether the range broke out on this trade. Tagging range:held vs range:broke on closed trades lets you later calculate how often your ranges remain intact — useful context for filtering out low-quality range setups.
Step 5: Review Range Trade Batch Statistics Monthly
Once you have 30 or more tagged range trades, run a monthly review focused exclusively on this setup type. Key statistics to calculate:
| Metric | Target Benchmark |
|---|---|
| Win rate (boundary-to-boundary) | Above 55% |
| Average R per trade | Above 0.8R |
| Boundary hit rate (price reached target) | Above 60% |
| Average MFE capture (% of range width) | Above 70% |
| Breakout rate (range failed) | Under 25% |
Compare these across sessions. Asian session ranges on EUR/JPY often hold better than London open ranges on GBP/USD. This kind of session-pair breakdown — only possible with clean tags — can shift your filter criteria and meaningfully improve results. Also compare by range width: trades on ranges under 20 pips often underperform due to spread eating too much of the move.
Pro Tips
- Log the time of day the range formed. Ranges that develop during the Asian session and are traded during early London have the highest boundary-hit rates on EUR pairs.
- Record the higher-timeframe trend. Fading the boundary that aligns with the higher-timeframe trend direction fails more often — tag this as a counter-trend range trade and track it separately.
- Note spread at entry. On a 20-pip range, a 2-pip spread consumes 10% of your move before the trade starts. Filter out range trades where spread exceeds 5% of range width.
- Track how many pips from the boundary you actually entered. Entries more than 8 pips off the boundary on a 30-pip range effectively reduce your target and inflate your risk.
- Use how to calculate R multiple to express every range trade in R terms from the start — this normalizes comparisons across different lot sizes and pairs.
Common Mistakes to Avoid
-
Logging range trades without tagging them separately. Mixing range trades with trend trades in your statistics hides your true edge in each setup. Always tag the setup type before entry, not after.
-
Using the wrong stop placement for range trades. Placing a stop inside the range instead of outside the boundary invalidates the setup logic. Correct approach: stop 10-15 pips beyond the boundary, sized to your standard risk per trade.
-
Only tracking winning trades to “confirm” the strategy. Cherry-picking which range trades you log corrupts your statistics. Log every trade you take that was identified as a range trade before entry, regardless of outcome.
-
Ignoring range quality. Not all ranges are equal. A range with 2 touches per side over 48 hours is higher quality than a 3-hour micro-consolidation. Add a quality field (1-3) and track win rate by range quality separately.
-
Reviewing after too few trades. Drawing conclusions from 10-12 range trades produces noise, not signal. Wait for at least 30 trades before adjusting your entry criteria based on batch statistics. See how to identify best setups for a sample-size framework.
How PipJournal Helps
PipJournal’s custom tag system lets you create structured tags for setup type, boundary direction, confluence, and session — then filter your trade history to isolate every range trade in seconds. The analytics dashboard calculates win rate, average R, and P&L breakdowns across any filtered subset, so your monthly range-trade review is a matter of filtering by tag rather than manually sorting a spreadsheet. The MFE/MAE fields are built into every trade log, meaning your capture-rate analysis is always one click away. For traders who journal range trades consistently, PipJournal surfaces patterns across sessions and pairs that would take hours to find manually.
People Also Ask
What data should I capture for every range trade?
At minimum log the range high, range low, range width in pips, your entry price, stop, target, and whether the opposite boundary was reached. Add session, pair, and confluence tags for meaningful batch analysis.
How do I measure my edge in range trading?
Calculate your boundary hit rate (how often price reaches your target boundary after entry), average R per trade, and average MFE-to-range-width ratio. A true edge shows a boundary hit rate above 55% with R above 1.0.
Should I use a fixed R:R for range trades?
Range trades typically target the full range width, so your R:R is set by where you place your stop relative to the entry. Many traders place stops 10-15 pips outside the boundary, giving natural R:R of 2:1 to 3:1 on a 60-pip range.
How many range trades do I need before reviewing performance?
You need at least 30 tagged range trades before batch statistics are meaningful. Below that, sample size distorts win rate and expectancy calculations significantly.
How is journaling range trades different from journaling breakout trades?
Range trades require tracking boundary accuracy and MFE relative to range width. Breakout trades focus on momentum follow-through. The tags, metrics, and review questions are different enough to warrant separate logging templates.
