Updated: 2026-02-20
In trading, Expectancy is the average expected outcome per trade, usually measured in R, based on win rate and average win/loss size. This glossary entry explains why expectancy matters, how traders use it, and how to track it with evidence instead of vibes.
Quick definition
Expectancy: the average expected outcome per trade, usually measured in R, based on win rate and average win/loss size.
Expectancy is the average expected outcome per trade, usually measured in R, based on win rate and average win/loss size. The practical version is: can you define it as a field you can log and audit later?
Most trading terms become confusing when they are used as vibes instead of variables. Your goal is a definition that helps you decide size, stop, entry timing, or whether to skip the trade.
Traders sometimes confuse Expectancy with expected value (EV) per dollar. Treat them as separate variables in your journal so your reviews stay honest.
Expectancy answers the only question that matters for a system: does this process make money over many trades? It prevents you from worshipping win rate alone.
If Expectancy never changes your decision, it is just jargon. The term earns its place when it improves your process consistency under real market pressure.
A useful mental model: plan first (risk and invalidation), execute second (order type and fills), review last (tags and metrics).
Use it to make one decision pre-trade. Example decisions: where the stop goes, whether to take partials, how to scale size, or whether conditions are too thin to trade.
Write the rule in one sentence, then run it consistently for a week. Consistency matters because it creates comparable data for review.
If the rule fails, adjust slowly. Do not rewrite the whole system after one bad session.
Track win rate, average win (R), and average loss (R) per setup tag. Recompute weekly; expectancy drifts when execution and regime change.
Use tags so you can slice results by regime and behavior state. The same term behaves differently when volatility changes or when you are fatigued.
Your review question should be binary: did this variable improve outcomes or reduce rule breaks? If not, simplify.
If win rate is 45%, avg win is 2.0R, and avg loss is 1.0R, expectancy = 0.45*2 - 0.55*1 = +0.35R per trade.
The point of an example is not to predict price. It is to show what you would log before the trade and what you would audit after the trade.
Mixing multiple strategies into one bucket, which hides which setups actually have positive expectancy.
The fastest way to improve expectancy is to remove one failure mode at a time. If you try to fix everything, you will fix nothing.
Expectancy becomes useful when it changes your behavior. The fastest test is simple: did it change your size, your stop placement, or your decision to skip a trade?
A good glossary definition is operational. It should convert into a constraint you can apply pre-trade and audit post-trade.
If you want one rule: write the rule in one sentence, then track compliance weekly.
Expectancy is the average expected outcome per trade, usually measured in R, based on win rate and average win/loss size. In practice, it matters when it changes a concrete decision like size, stop placement, or whether you skip a trade.
They are related but not identical. In your journal, track Expectancy as its own variable and treat expected value (EV) per dollar as a separate context factor so you can audit each cleanly.
Track win rate, average win (R), and average loss (R) per setup tag. Recompute weekly; expectancy drifts when execution and regime change.
Mixing multiple strategies into one bucket, which hides which setups actually have positive expectancy.
See plans and run one weekly review loop with Tiltless: edges, leaks, and enforceable next actions.
