Forward testing is often treated as a simple profit check. That is too narrow. A strategy may not fail immediately in profit terms, but it can start behaving differently from the tested model. The earlier that deviation is measured, the better the decision process becomes.
Forward testing should compare behavior, not only final profit. Frequency, cost profile, trade distribution and drawdown path can reveal degradation before the headline result does.
Profit is a late signal
Net profit is important, but it may be a delayed indicator. A forward account can remain near break-even while trade frequency, spread sensitivity, average loss or session behavior already diverges from the backtest. Waiting only for a large loss can make the review reactive rather than analytical.
The better approach is to define expected behavior ranges before the forward period begins and then monitor deviation against those ranges.
Deviation can be structural
A strategy can diverge in several ways: fewer entries than expected, more blocked trades, worse execution, longer holding periods, lower payoff ratio, deeper floating drawdown or a change in BUY versus SELL contribution. Any one of these may be tolerable. Several at the same time suggest that the live environment is no longer close to the tested assumptions.
Forward review should compare at least frequency, average trade, cost per trade, drawdown path and signal blocking. Do not rely on net profit alone.
Sample size still matters
A short forward window can be useful for execution sanity, but it should not be overstated. Ten trades can reveal a technical problem, but they rarely confirm a strategy. The interpretation should match the evidence: early forward data can reject obvious issues, while longer samples are needed to support stronger conclusions.
What to compare
- Trade frequency: whether the strategy enters at the expected pace.
- Direction split: whether BUY and SELL contribution remains coherent.
- Cost profile: spread, commission, swap and slippage compared with assumptions.
- Average outcome: average win, average loss and payoff ratio.
- Drawdown path: depth, duration and recovery behavior.
- Blocking reasons: whether filters prevent entries more often than expected.
- Execution errors: rejected orders, invalid stops and connection events.
Decision states
Forward results should lead to clear states: continue observation, reduce exposure, revise assumptions or reject the candidate. The state should come from predefined criteria rather than emotional reaction to a single trade or day.
This is where dashboards and evidence scorecards are useful. They make deviations visible and force the review to stay consistent across strategies.
Conclusion
Backtest-forward deviation is not only a profitability issue. It is an evidence issue. A system that behaves differently from its tested model should not be promoted until the reason is understood. Forward testing is strongest when it measures whether the strategy is still the same strategy under real execution conditions.