# Building a Backtesting Log: Template and Best Practices

> A practical backtesting log template with all the fields that matter. Use this structure in a spreadsheet or Trader Journal to build reliable strategy performance data.

**URL:** https://traderjournal.app/backtesting/backtesting-journal-template-what-to-track

---


# Building a Backtesting Log: Template and Best Practices

A backtesting log is only useful if it is consistent. These are the fields that actually matter and how to fill them without wasting time.

## The Core Fields

Every backtest entry needs these minimum fields:

| Field | Notes |
|---|---|
| Date | Historical date of the setup |
| Time | Session matters for many strategies |
| Pair | Which instrument |
| Direction | Long or Short |
| Setup tag | Brief label: "H4-OB", "M15-FVG", "BOS-retest" |
| Entry price | The price you would have entered |
| Stop loss | The price you would have placed SL |
| Take profit | TP level (first target if partial) |
| Risk in pips | Distance from entry to SL |
| R:R ratio | Distance to TP / distance to SL |
| Result | Win / Loss / BE |
| P&L in R | How many R you gained or lost |

## Context Fields (Worth Adding)

| Field | Notes |
|---|---|
| HTF bias | Bullish / Bearish / Neutral at D1 or H4 |
| Session | London / New York / Asian |
| News nearby | Y/N — high impact news that day |
| Market condition | Trending / Ranging / Volatile |
| Setup quality | 1-3 star rating (your subjective quality score) |
| Notes | One line: what made this setup stand out or fail |

## The Quality Rating Field

Adding a 1–3 star quality rating before you know the outcome is powerful. After 100 trades, compare:
- 3-star setup win rate vs 1-star win rate
- If 3-star setups win more, your intuition is meaningful and you should be more selective

## Spreadsheet vs Trader Journal

A Google Sheet works well for backtesting logs. But if you want to use the same analytics (equity curve, win rate by pair, profit factor) as your live trading data, importing backtest trades into Trader Journal under a separate "Backtest" account is more efficient.

Trader Journal accepts CSV imports, so you can build your log in a spreadsheet and import it in bulk.

## Review Schedule

Review your backtest log:
- **After every 50 trades:** Check win rate, profit factor, average R per trade
- **After every 100 trades:** Look for patterns — best pairs, sessions, market conditions
- **After completing a full backtest:** Before going live, do a final review of all statistics

## Summary

A consistent backtesting log is the difference between a trader who says "I think this works" and one who can say "this has a 1.65 profit factor over 200 trades across varied market conditions." Build the habit of logging from the first backtest trade.