Learn how to compare planned vs realized R without confusing normal losing trades with execution errors, using a rule-based benchmark and practical review workflow.
Quick Answer
Planned vs realized R should be compared against the result your documented trade-management rules would have produced—not simply against the original profit target. A trade that planned to risk 1R for a 2R target can legitimately finish at -1R if the stop is reached first.
To measure a meaningful execution gap, reconstruct the rule-based outcome on the same market path, calculate the actual net result in R, and attribute the difference to fills, discretionary decisions, costs, or rule violations. The main limitation is that the comparison is only reliable when the original plan was recorded before the outcome became known.
Key Takeaways
- Define 1R from the trade’s initial risk, including expected trading costs where practical.
- A profit target is a possible payoff, not the outcome every trade was supposed to achieve.
- Compare realized R with a rule-based reference outcome on the same price path.
- Separate strategy outcomes from execution, discretion, slippage, and fees.
- Review repeated patterns across comparable trades rather than judging one isolated result.
- Change rules only after testing the proposed change on a broader sample.
What Planned and Realized R Actually Measure
An R-multiple expresses a trade’s profit or loss relative to a defined unit of initial risk.
For a long trade with a fixed stop:
Initial risk per unit = Entry price − Initial stop price
At the position level:
1R = Initial risk per unit × Position size
If a trader buys 100 shares at $50 with an initial stop at $49, the gross initial risk is $100. Before costs, a $200 profit is +2R and a $100 loss is -1R.
Planned R can refer to two different values, and confusing them causes faulty reviews:
- Target R: the payoff available if price reaches the planned target.
- Rule-based R: the result the complete management plan would have produced, given the market path that actually occurred.
Suppose the plan has a 2R target and a 1R stop. The target R is +2R, but the rule-based outcome could be +2R, -1R, or another value if the plan includes partial exits, trailing stops, or time-based exits.
Realized R is the net result actually booked relative to the original risk:
Realized R = Net trade P&L ÷ Initial risk
Net P&L should include commissions, fees, and other known transaction costs. If the intended entry and actual fill differ, calculate realized R using a consistent policy. Most traders benefit from preserving both values:
- planned risk based on the intended entry;
- actual risk based on the executed entry and stop.
That distinction reveals whether the deviation came from the trade idea or the fill.
Why Target R Minus Realized R Is Often Misleading
A common review method calculates:
Target R − Realized R
If a trade targeted +2R but stopped at -1R, this method reports a 3R shortfall. That does not mean the trader made a 3R execution error. The stop may have been followed exactly.
Applied across an entire trade log, this calculation labels normal losses as execution failures. It can also encourage traders to hold for targets that market conditions no longer support.
A fairer execution-gap calculation is:
Execution gap = Realized R − Rule-based reference R
Under this definition:
- zero means actual execution matched the documented rules;
- a negative value means actual execution underperformed the reference;
- a positive value means discretion improved this particular outcome.
Positive gaps are not automatically evidence of skill. A trader who repeatedly violates stops may occasionally outperform the rules before eventually taking a much larger loss. Evaluate the decision process and the distribution of outcomes, not just the sign of one result.
Worked Example: Separating Strategy Outcome From Execution
Consider a long breakout trade with these pre-trade details:
- Intended entry: $100.00
- Initial stop: $99.00
- Profit target: $102.00
- Position size: 200 shares
- Initial gross risk: $200, or 1R
- Management rule: exit all shares at the stop or target; close at the end of the session if neither is reached
Price rises to $101.40, pulls back to $100.60, and later reaches $102.00.
The documented rules would have held the position and exited at the target for approximately +2R before costs. The trader instead exits at $100.70 during the pullback, realizing $140 gross, or +0.70R.
Ignoring costs for simplicity:
Execution gap = +0.70R − +2.00R = -1.30R
This is a genuine management deviation because the planned stop remained intact and the target was subsequently reached.
Now change the price path. Assume price rises to $101.40, reverses, and reaches the $99 stop without touching the target. The reference result is -1R. Exiting early at $100.70 produces +0.70R and a positive 1.70R gap.
That still does not prove early exits are superior. The decision must be evaluated across all comparable signals. Early exits may avoid some losses while sacrificing many larger winners. Only a representative sample can show the net effect.
The example also demonstrates why maximum favorable excursion alone is not a valid reference. A trade reaching +1.4R intraday does not mean +1.4R was realistically available under the stated rules.
A strategy laid out end to end in the Kvants editor.
A Planned vs Realized R Review Workflow
1. Freeze the plan before entry
Record the intended entry, initial stop, target, size, and management rules before the outcome is known. Include rules for partial exits, trailing stops, time exits, adding to the position, and invalidation.
“Manage based on price action” is not specific enough to reconstruct a reference outcome. Define the observable condition that permits action.
2. Preserve the original 1R
Do not redefine R after moving the stop or reducing the position. The original risk is the stable denominator needed to compare trades.
If the initial stop was excessively wide or arbitrary, flag that as a planning issue. Recalculating R later can conceal the problem.
3. Reconstruct the rule-based outcome
Apply the original rules to the actual sequence of prices. Bar order matters. If the stop and target appear inside the same candle, bar-level data may not reveal which was reached first.
Use more granular data when available. Otherwise, mark the outcome as ambiguous rather than selecting the favorable assumption.
4. Calculate actual net R
Include every fill, partial exit, fee, and commission associated with the position:
Actual net R = Net realized P&L ÷ Original planned risk
For scaled exits, combine all realized P&L before dividing by 1R.
5. Attribute the gap
Assign each difference to a practical category:
- entry slippage;
- exit slippage;
- early profit-taking;
- delayed stop execution;
- unplanned partial exit;
- position-size error;
- transaction costs;
- valid discretionary override;
- data ambiguity.
Avoid treating “discipline” as a catch-all. Specific labels lead to testable changes.
6. Segment comparable trades
Review execution gaps by setup, market, session, volatility regime, direction, and management rule. Mixing unrelated strategies can hide the source of a problem.
Useful summary measures include median execution gap, percentage of rule-matched trades, downside gap, and results with versus without discretionary overrides. A few extreme trades can distort an average, so inspect the distribution as well.
7. Test one proposed change
If early exits repeatedly reduce realized R, do not immediately ban them. Convert the proposed alternative into a precise rule and test it over historical data and unseen periods.
For example, compare the original target-and-stop plan with a rule that exits when price closes below a defined trailing level. Keep entry logic and sizing unchanged so the exit rule is the main variable.
Deploying a strategy to paper or live with a pre-flight gate.
Common Failure Modes
Treating every missed target as a mistake
Targets are conditional payoffs. A stopped trade is not an execution error when the stop was part of the plan.
Writing the plan after the trade
A reconstructed plan is vulnerable to hindsight. Timestamp plans or save strategy versions before trading them.
Ignoring partial exits
A trade can touch a 2R target without realizing +2R if most of the position was closed earlier. Calculate position-weighted P&L from actual fills.
Moving the denominator
Recalculating 1R after a stop adjustment makes trade comparisons inconsistent and can understate losses.
Assuming better realized R validates discretion
A discretionary override can produce a favorable result for the wrong reason. Judge whether the decision was repeatable and whether similar overrides improve the full distribution.
Combining strategy and execution changes
Changing entries, stops, targets, and sizing simultaneously makes attribution nearly impossible. Test one meaningful change at a time.
Turning the Reference Plan Into Testable Logic
A written plan becomes more useful when its conditions are explicit enough to execute consistently. Kvants Studio turns plain-English trading ideas into editable, auditable strategy logic for stocks and crypto research.
A trader can define the entry, initial stop, target, time exit, and management conditions, then inspect the generated logic before running an event-driven backtest. Parameter sweeps, walk-forward analysis, and crisis-stress validation can help evaluate whether a proposed management change is robust or merely fits a recent sample.
This does not replace the execution review. Instead, it provides a rule-based baseline against which discretionary results can be compared. The plan must still model realistic timing, costs, and fill assumptions. Guidance on research workflows is available in the Kvants documentation and Kvants blog.
Configuring a backtest in Kvants Studio.
Frequently Asked Questions
What is a good realized R-multiple?
There is no universal good realized R. It depends on win rate, trading costs, loss distribution, and the strategy’s rules. A lower average winner can still support positive expectancy if losses and hit rate are compatible, while a high average winner does not compensate for uncontrolled tail losses automatically.
Should planned R be the profit target or the expected value?
Keep them separate. Target R is the payoff if the target is reached. Expected value estimates the average outcome across many trades. For execution analysis, use the rule-based result that the documented plan would have produced on the same market path.
How should partial exits be calculated in R?
Add the realized P&L from every partial exit, subtract costs, and divide the total by the original risk. Alternatively, calculate each partial result in R and weight it by the fraction of the original position closed.
Can realized R be greater than planned R?
Yes. Positive slippage, holding beyond a target, trailing exits, or discretionary overrides can produce a larger result. Review whether the action was permitted, repeatable, and beneficial across a meaningful sample before changing the plan.
How many trades are needed to evaluate an execution gap?
There is no fixed number that guarantees a reliable conclusion. The required sample depends on trade frequency and outcome variability. Start monitoring immediately, but avoid redesigning rules from a handful of trades. Segment comparable setups and confirm findings on unseen data where possible.
Risk Note
This article is educational and is not investment advice. Trading involves risk, and losses can exceed expectations when markets gap, liquidity changes, or orders fill differently from the model. Kvants is a research tool, not an investment adviser. Backtested performance does not guarantee future results.
