From Backtest to Live Execution: A Validation Checklist

A backtest can show how a documented Strategy behaved across a selected sample. It cannot guarantee future results or remove uncertainty from the inputs, data quality, and assumptions.

Before comparing a backtest with live results, write down the exact symbol, session, timeframe, costs, risk rule, entry logic, exit logic, and sample period. Without that reference, “live is worse” is not yet a useful diagnosis.

A weaker live result can come from the Strategy, from Execution, or from the tracking layer. Late entries, rejected orders, symbol mapping, spread, slippage, and manual deviations belong in a different review than a changed market regime.

Keep the Trade Tracker tied to the Strategy and the Account. That makes it possible to ask whether the rule failed, the order was applied differently, or the trade was not actually comparable.

First, format and inspect the source export in Backtest Lab. Second, verify that the Strategy rules and risk units are consistent. Third, record live trades with their execution context. Fourth, compare observed behaviour with the expected edge in Edge Health.

Only then choose one controlled next step: collect more data, refine one parameter, pause the Strategy, or continue under the existing risk rule. Changing several variables at once destroys the feedback loop.

The goal of validation is not to make a curve look convincing. It is to decide what the current evidence supports and what it does not support. Keep the method, sample and limitations visible when you share a result.

LeanTrading connects Backtest Lab, Trade Tracker and Edge Health around your own Strategy. It is educational software, not a signal service or a promise of performance.