How to Find Your Best Setups

Compare setups with data, not memory

Every trader benefits from understanding which setups actually work for them — whether you are discovering what works, refining your edge, or validating performance over time. Your best setups stay profitable after you account for sample size, risk, and execution. Tag every trade in your trade journal, build at least 20–30 tagged trades per setup, then compare expectancy and profit factor in Analytics. Cut or reduce size on setups that lose money; scale only where the numbers and your execution both hold up.

June 9, 20267 min read
TraderWaves trade journal with setup tags and trade history

Why “best setup” is harder than it looks

A setup is a repeatable trading pattern or entry condition — not a single trade. One winner does not prove a repeatable edge. The goal is to see whether a setup performs consistently across different market conditions, assets, and time periods, and to use tagged data to validate your assumptions.

Label setups the same way every time, review them with enough sample size, and judge risk-adjusted performance — not highlight-reel P&L.

1. Define your setups before you tag

Write down each setup you trade in plain language. One sentence per setup is enough. Do this before you trade — tags and risk rules should be ready before the first entry, not defined after the fact.

Example — day trader on EUR/USD:
  • London breakout — First 15-min break of Asian range after London open.
  • Pullback to VWAP — Trend continuation entry at VWAP after impulse move.
  • Range fade — Short at range high / long at range low in established chop.
Rules for naming:
  • Keep names short and fixed — do not rename mid-month.
  • One primary setup tag per trade.
  • Separate setup tags from mistake tags (FOMO, revenge, oversized). Mistake tags explain why a good setup failed; they are not setups themselves.
Plan risk before you tag trades: For each setup, note your planned stop, target, and risk per trade. Use the calculators to work out position size, risk-reward, and expectancy targets upfront — so every tagged trade later compares against the same pre-trade plan.

Create setup and mistake tags as custom tags in the Journal. See Journal Basics for step-by-step tag creation.
TraderWaves journal filtered by setup tags
Filter trades by setup tag in the Journal before you compare results in Analytics.

2. Tag every trade — including losers

A setup comparison is only as good as your tagging discipline. Tag at trade close or during your daily review, not at end of month when details blur.

Minimum habit:
  1. Open the trade in your Journal after it closes.
  2. Add your setup tag.
  3. Add one context note if execution was off-plan (“entered early”, “moved stop”).
If you skip losers, you will overrate every setup. The goal is an honest dataset, not a highlight reel.

How many trades to tag per setup: Build at least 20–30 tagged trades per setup before a keep-or-cut decision. Under 15 trades, treat results as a directional hint only — keep trading and keep tagging. Do not judge a setup after five trades. If you trade infrequently, extend the window to 60–90 days per setup rather than forcing a call on 10 trades.
TraderWaves journal for tagging and reviewing trades
Tag each closed trade in the Journal so every setup builds an honest dataset.

3. Compare setup performance in Analytics

Once you have enough tagged trades per setup (see Step 2), open Analytics and filter by your setup tags. Build or switch to a dashboard template focused on setup comparison — see Trade Analytics for template and filter steps.

Compare risk-adjusted, not just dollars. A setup that makes $800 on a $50k account at 2% risk per trade is not automatically better than one that makes $400 at 0.5% risk. Rank setups by R-multiples or normalised risk units — not headline dollar P&L — so comparisons stay fair when stop sizes or position sizes differ.

Metrics and widgets to add:
  • Expectancy — Average R or $ per trade; your edge per execution.
  • Profit factor — Gross wins ÷ gross losses; is the setup net-positive?
  • Average win / average loss — High win rate means little if losers are 3× winners.
  • Win rate — Context only; pair with R-multiple data.
  • Drawdown and equity curve — A high-P&L setup with deep drawdowns may still breach prop-firm rules or your daily loss limits.
  • Trade count — Confirms whether the sample is meaningful.
Trader Tip: A setup with a lower win rate can still outperform one with a higher win rate if its average winners are significantly larger than its average losers.
Filter each setup individually first, then compare side by side over the same date range — a setup that performs well in trending markets may behave very differently during consolidation or around major news events.

Example read:
  • London breakout: 34 trades, 48% win rate, +0.42R expectancy, profit factor 1.6 → keep at standard size.
  • Range fade: 28 trades, 61% win rate, −0.08R expectancy, profit factor 0.92 → cut or halve size.
  • Pullback to VWAP: 19 trades, 37% win rate, +0.65R expectancy, profit factor 1.9 → promising but needs more data.
TraderWaves analytics dashboard for comparing setup performance
Use Analytics dashboards and tag filters to compare expectancy, profit factor, and drawdown by setup.

4. Check execution quality and use AI Coach

Two setups can show similar P&L but very different execution quality. That matters when deciding which setup to scale.

On Pro, use WaveScore™ to review entry quality, exit quality, risk management, and tempo alongside your journal data. A setup with decent P&L but weak exit scores may be profitable because of luck, not skill — worth tightening before you size up.

Ask: Am I executing Setup A cleanly and Setup B sloppily? If yes, the problem may be familiarity or rules clarity, not the setup itself.

After your manual review, ask Wave AI Coach (Pro) questions grounded in your tagged data:
  • “Which setup has the best expectancy over the last 90 days?”
  • “Do I perform worse on range fades after a losing day?”
  • “Which setup has the widest gap between win rate and average R?”
AI filtering can also isolate trades by setup plus mistake tags — e.g. all London breakout trades tagged FOMO — so you separate setup edge from behavioural leaks. AI supports your review; it does not replace the tagging habit in Step 2.
TraderWaves AI Coach reviewing tagged trading data
Use AI Coach to investigate setup performance and execution patterns in your journal.

5. Decide — cut, keep, or refine

After reviewing your Analytics data and execution quality, run each setup through this checklist before you promote or cut it:
  1. Is expectancy positive after 30+ trades?
  2. Is max drawdown during this setup’s trades acceptable?
  3. Does position sizing stay within the plan you set in Step 1?
  4. Would this setup pass your daily loss limit if you traded it every session?
Then end each setup review with a written decision:
  • Keep: Positive expectancy, 30+ trades, acceptable drawdown — standard size; trade only in conditions that match your tagged winners.
  • Reduce: Mixed metrics or small sample with warning signs — half size until 30 trades; stricter entry rules.
  • Cut: Negative expectancy over 30+ trades, or repeated rule breaks — stop trading it for 30 days; validate revisions in the backtester or paper trade before bringing it back.
  • Refine: Good concept, poor execution scores — tighten rules; journal planned vs actual for 20 trades. If the idea still looks sound on paper, use the backtester to test rule changes across more market conditions before sizing up.
Revisit this table monthly or after every 20 new tagged trades per setup.

Worked example: narrowing three setups to one focus

Trader: Part-time NAS100 futures trader, 8–12 trades/week.

After 90 days and 71 tagged trades:
  1. Opening drive — 26 trades, +0.55R expectancy, profit factor 2.1, WaveScore exit score strong → primary setup, full size.
  2. Midday reversal — 22 trades, +0.12R expectancy, profit factor 1.1, many trades tagged late entry → refine rules, half size.
  3. Afternoon breakout — 23 trades, −0.31R expectancy, profit factor 0.78, largest losers clustered here → cut for 30 days.
Outcome: Fewer trades, higher focus, less afternoon chop. Expectancy across the account rises because capital and attention shift to the one setup with proven edge.

FAQs

How many trades do I need before I know a setup works?

Aim for at least 30 tagged trades per setup before making a final keep or cut decision. Below 15 trades, treat results as preliminary and keep tagging.

Should I compare trading setups by win rate or profit?

Use expectancy and profit factor together. Win rate alone is misleading because a high win rate setup can still lose money if average losses exceed average wins.

What if I only trade one setup?

Tag sub-variations such as session, direction, or entry type instead of multiple setup names. You still need comparison dimensions to find what works best.

Can I find my best setup without tagging every trade?

Not reliably. Untagged trades skew your averages and hide which ideas actually drive your profit and loss.

Do I need TraderWaves Pro to compare setups?

No. Core journal tagging and analytics filtering are available on Essential. WaveScore and AI Coach add execution quality and pattern analysis on Pro.

What should I do with a setup that wins often but loses overall?

Cut position size immediately and review whether targets are too tight or stops too wide. Check mistake tags for early exits, moved stops, and other execution errors.

Was this article helpful?

Article feedback is not yet available.