JOURNAL · REVIEW

How to Review Crypto Trades by Setup Instead of Win Rate Alone

Overall win rate mixes good setups with bad ones. Reviewing by setup shows which ideas actually make money.

Short answer

Tag every journal entry with a setup name defined in advance (e.g. 'range-low absorption', 'breakout retest', 'funding fade'), then review each setup's trade count, win rate, average R and net expectancy after costs. A 45% overall win rate can hide one setup at +0.4R per trade and another at −0.3R. Keep setups with positive expectancy and enough trades, refine or drop the rest, and check that process errors aren't concentrated in one setup.

A setup table

SetupTradesWin rateAvg R (net)Verdict
Range-low absorption3447%+0.38Keep
Breakout retest2854%+0.12Refine
Funding fade1937%−0.29Drop/rework
Illustrative net expectancy by setup (R)Illustrative net expectancy by setup (R): Absorption +0.38 R; Breakout retest +0.12 R; Funding fade -0.29 R.ILLUSTRATIVE NET EXPECTANCY BY SETUP (R)Absorption+0.38 RBreakout retest+0.12 RFunding fade-0.29 R
Win rate alone would rank them differently. Original ChartsPod editorial graphic.

Test How to Review Crypto Trades by Setup Instead of Win Rate Alone on a perpetual chart; no account is needed to chart.

Launch ChartsPod

Defining setups

Setup definitionSetup definition: Name and short description; Entry criteria; Invalidation criteria; Markets and timeframes; Written before tagging trades.SETUP DEFINITIONName and short descriptionEntry criteriaInvalidation criteriaMarkets and timeframesWritten before tagging trades
Tags chosen after the fact bias the review. Original ChartsPod editorial graphic.

Monthly review

Setup reviewSetup review. Steps: 1. Filter by setup — Tagged trades; 2. Compute net R — After costs; 3. Check sample — Enough trades?; 4. Check errors — Rule breaks per setup; 5. Decide — Keep, refine, drop1Filter by setupTagged trades2Compute net RAfter costs3Check sampleEnough trades?4Check errorsRule breaks persetup5DecideKeep, refine, drop
One decision per setup. Original ChartsPod editorial graphic.

Related: Journal a Losing Crypto Trade: Separate Process Errors From Variance, Trading Journal Expectancy: Include Fees, Funding and Partial Exits, A Profitable Crypto Backtest With 20 Trades: Is the Sample Useful?.

Sample size per setup

Splitting trades by setup reduces the sample per setup. Before dropping a setup, check whether its trade count is large enough to judge; a setup with 8 trades and negative expectancy may simply be unlucky. Keep tagging and review again when it reaches a meaningful count, unless it also shows frequent process errors.

Conclusion

Review trades by predefined setup with net expectancy, not by overall win rate.

See How to Review Crypto Trades by Setup Instead of Win Rate Alone on live data in the free ChartsPod terminal.

Open the ChartsPod terminal

Questions readers ask

Why review by setup?

Overall win rate mixes profitable and unprofitable ideas.

How many trades per setup before deciding?

Enough to make the estimate meaningful; dozens at least.

Should I tag trades afterwards?

Define setups first, tag at entry.

Sources and methodology

Risk arithmetic follows standard position-sizing formulas; liquidation mechanics reference Bybit's and Binance's documentation; ChartsPod's position planner and journal were checked on its public pages on 17 October 2026. All examples are illustrative.

  1. ChartsPod documentation — guides for order flow, derivatives, alerts, backtests, journal and workspaces.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.