Backtesting Template for Trading Strategies

A backtest becomes more useful when every test is recorded the same way. Instead of only checking a few examples that look good, a structured backtesting template helps you review a trading strategy across a larger sample of trades.

This template can be used for forex, crypto, stocks, indices, futures, commodities, and other markets. It is for educational purposes only and does not provide financial advice.

Backtesting is the process of testing a trading strategy on historical market data.

The goal is not to prove that a strategy will work forever. The goal is to understand how clearly your rules are defined and how the strategy behaves across different trades and market conditions.

Backtesting can help you:

• Test whether your trading rules are clear
• Review a strategy across many trades
• Identify weak market conditions
• Find repeated mistakes
• Compare different strategy versions
• Understand risk-to-reward behavior
• Improve entry and exit rules
• Avoid relying only on memory or emotion

Many traders remember the best-looking examples and forget the setups that failed. A backtesting template helps reduce that bias by forcing you to record the full test.

Backtesting does not guarantee future results. It is only a research and review process.

Start by writing the exact strategy rules you are testing.

If the rule is unclear, the backtest result will also be unclear.

Document:

• Strategy name
• Strategy idea
• Market condition required
• Timeframe used
• Entry rules
• Exit rules
• Stop loss rules
• Take profit rules
• Risk management rules
• No-trade rules

Avoid vague rules like:

• “enter near support”
• “buy when momentum is strong”
• “exit when price looks weak”
• “avoid bad conditions”

Instead, write rules that can be reviewed consistently.

Example:

“Enter long only when price breaks above resistance, closes above the level on the 15-minute timeframe, and retests the broken level as support.”

Clear rules make the backtest more reliable because each trade is judged against the same conditions.

Record the market or instruments used in the backtest.

Examples:

• EUR/USD
• GBP/USD
• BTC/USDT
• ETH/USDT
• NASDAQ
• S&P 500
• Gold
• Oil

Also record the market type:

• Forex
• Crypto
• Stocks
• Indices
• Futures
• Commodities

This matters because strategies can behave differently across markets.

A strategy that looks good on one forex pair may not behave the same way on crypto. A strategy that works during high liquidity may perform differently on assets with wider spreads or lower volume.

If you test multiple instruments, record the results separately when possible.

Define the exact time period used for the backtest.

Record:

• Start date
• End date
• Total test duration
• Market conditions during the period
• Whether the period was trending, ranging, volatile, or quiet
• Whether major news or events affected the period

Example:

Time period tested: January 2026 to March 2026

Market condition: mostly trending with several high-volatility sessions

The time period matters because a strategy can look strong in one market phase and weak in another.

A breakout strategy may perform well during high volatility but poorly in low-volume ranges. A support and resistance strategy may behave differently in trending markets compared to ranging markets.

Try to test across different market conditions where possible.

Record the number of trades included in the backtest.

A small sample can be misleading. A larger sample usually gives a better picture, although quality still matters.

Track:

• Total trades tested
• Winning trades
• Losing trades
• Break-even trades
• Trades skipped
• Trades removed and why

Do not remove trades only because they make the result look worse.

A backtest should include every trade that matches the rules. If you remove a trade, write down the reason clearly.

This helps avoid cherry-picking.

Entry criteria explain exactly what triggered each trade.

Record:

• Entry rule used
• Entry timeframe
• Confirmation required
• Entry price
• Candle close requirement
• Retest requirement
• Indicator condition, if used
• Market structure condition
• News or session filter, if used

Example entry criteria:

“Entry is valid only after a breakout candle closes above resistance and price retests the level without closing back below it.”

The entry criteria should be specific enough that the same backtest could be repeated later.

If the entry rules are too subjective, the test becomes harder to trust.

Exit criteria explain how trades were closed during the backtest.

Document:

• Stop loss rule
• Take profit rule
• Partial profit rule
• Trailing stop rule
• Break-even rule
• Time-based exit
• Manual exit conditions
• Invalidation rule

Example:

“Stop loss is placed below the retest low. Take profit is placed at the next major resistance zone or minimum 2R, whichever comes first.”

Exit criteria are important because changing exit rules can completely change a strategy's results.

A strategy may look profitable with one exit method and weak with another. That is why exits must be recorded clearly.

Use consistent risk per trade during the backtest.

This helps make results easier to compare.

Record:

• Risk per trade
• Position sizing method
• Stop loss distance
• Whether risk is fixed or variable
• Maximum allowed risk
• Whether fees, spreads, slippage, or commissions are included

Example:

Risk per trade: 1R

Position size: calculated from stop loss distance

Fees and spread: included in result estimate

Using R multiples can make results easier to review because each trade is compared relative to the amount risked.

For example:

• +2R means the trade gained twice the amount risked
• -1R means the trade lost the planned risk
• 0R means the trade closed around break-even

Track the basic outcome of the backtest.

Record:

• Total trades
• Wins
• Losses
• Break-even trades
• Win rate
• Loss rate
• Average win
• Average loss
• Largest win
• Largest loss

However, do not judge a strategy only by win rate.

A strategy with a lower win rate can still be useful if average winners are much larger than average losses. A strategy with a high win rate can still be weak if the losses are too large.

That is why R multiple is important.

Average R multiple shows the average result relative to the risk taken.

This can be more useful than raw profit or simple win rate because it standardizes results.

Track:

• Result of each trade in R
• Average R per trade
• Total R
• Best trade in R
• Worst trade in R
• Average win in R
• Average loss in R

Example:

Total trades: 50

Total result: +12R

Average R per trade: +0.24R

This gives a clearer picture of whether the strategy produced positive or negative results across the sample.

R multiple is especially useful if you test different markets or position sizes.

Use the notes section to record anything the numbers do not fully explain.

Examples:

• The strategy worked better during high volatility
• Most losses happened during sideways markets
• Entries were often late after large candles
• Targets were too far during low-volume sessions
• The stop loss was too tight during news events
• The strategy performed better on higher timeframe levels
• The setup was difficult to identify in real time

Notes help turn raw numbers into useful insights.

Sometimes the most important backtesting lesson is not the result, but the condition where the strategy performed better or worse.

Backtesting can be useful, but only if it is done honestly.

Avoid these common mistakes:

1. Cherry-picking trades

Do not include only the trades that look clean or profitable. If a trade matches the rules, it should be included.

2. Changing rules during the test

If you change rules halfway through, the results become mixed. Record every rule change clearly.

3. Curve fitting

Curve fitting happens when you adjust rules too much to fit one specific historical period. A strategy may look good in the test but fail in different conditions.

4. Ignoring spreads, fees, and slippage

Trading costs matter, especially for scalping, crypto, low-liquidity assets, and frequent trading strategies.

5. Testing only one favorable period

A strategy tested only during a perfect trend may fail during ranges or high-volatility conditions.

6. Using vague entry rules

If the rules are subjective, it becomes easy to justify trades after seeing the result.

7. Ignoring losing streaks

A strategy may have a positive result overall but still include difficult losing streaks. Risk rules should account for that.

8. Not recording skipped trades

Skipped trades can reveal unclear rules or execution problems.

A backtesting template should include a section for rule changes.

When you change a strategy rule, document:

• What rule changed
• Why it changed
• When it changed
• Which data supports the change
• Whether the old and new results are separated
• Whether the change needs a new backtest

Example:

“Changed entry rule to require candle close confirmation after too many false breakouts appeared in the first 30 tested trades.”

Do not silently change rules and continue the same backtest as if nothing changed.

If the rules change significantly, start a new version of the strategy and test again.

Use this backtesting template to record your strategy test:

Strategy Name:

Strategy Version:
Example: Version 1.0, Version 1.1

Strategy Idea:
What market behavior is this strategy trying to capture?

Strategy Rules:
Market condition required:
Setup rules:
Entry rules:
Exit rules:
Stop loss rules:
Take profit rules:
No-trade rules:

Market Tested:
Market type:
Specific instrument:
Liquidity/spread notes:

Time Period Tested:
Start date:
End date:
Total duration:
Market condition during test:
Trending / Ranging / Volatile / Low volatility

Timeframe:
Higher timeframe:
Setup timeframe:
Entry timeframe:

Number of Trades:
Total trades:
Wins:
Losses:
Break-even:
Skipped trades:
Removed trades and reason:

Entry Criteria:
Entry trigger:
Confirmation required:
Entry timeframe:
Session filter:
News filter:

Exit Criteria:
Stop loss rule:
Take profit rule:
Partial profit rule:
Trailing stop rule:
Break-even rule:
Manual exit rule:

Risk Per Trade:
Risk per trade:
Position sizing method:
Minimum risk-to-reward:
Fees/spread/slippage included: Yes / No

Results:
Win rate:
Loss rate:
Total R:
Average R per trade:
Average win:
Average loss:
Largest win:
Largest loss:
Longest winning streak:
Longest losing streak:

Notes:
What worked well?
What worked poorly?
Which market condition was best?
Which market condition was worst?
Were entries clear?
Were exits clear?

Common Mistakes Found:
Did I cherry-pick trades?
Were rules too vague?
Did I change rules during the test?
Did I ignore fees or slippage?
Did I test enough trades?
Did I test different market conditions?

Rule Changes:
Rule changed:
Reason for change:
Data supporting change:
Date of change:
New version needed: Yes / No

Conclusion:
Is the strategy clear enough to test further?
What should be improved?
Should this strategy be forward-tested?
What should be tracked in the trading journal?

StrategyArchive helps traders document trading strategies, backtesting notes, journal entries, and strategy updates in one place.

You can use this backtesting template to:

• Define the rules you are testing
• Record historical results consistently
• Track mistakes and weak conditions
• Save strategy versions
• Connect backtesting notes to live journal entries
• Compare strategy changes over time
• Improve your trading process with better documentation

Backtesting is most useful when it is connected to clear strategy rules and honest trade review.