What to Track in a Trading Journal

What to include in a trading journal is usually answered with a thirty-column template that gets abandoned within two weeks. A better test: a field earns its place when it answers a question you will ask at review time. If you cannot name the question, the field is busywork. Here are the fields, grouped by when each one starts paying off, plus the ones you can skip.

What to include in a trading journal from your first trade

These twelve fields are the core. Each answers a specific review question, and none needs a big sample to be useful.

Three of these fields are written before you click, and that is what separates a journal from a trade log.

The plan fields: written before you enter

The setup, the planned entry, the stop-loss, the take-profit and the dollar risk all go in before the order does. Once you are in a trade, memory starts editing the plan. Hindsight bias is well documented: after an outcome is known, people tend to remember having expected it. A plan written down beforehand can't be edited that way.

The dollar risk is the field most journals leave out, and it is the one that makes the rest comparable. It is the amount you lose if the stop is hit, which defines one unit of risk, or 1R. Say you plan a long at $50.00 with a stop at $48.00 and a target at $56.00, and you risk $200, which makes the position 100 shares. That is a planned 3R trade. If you get nervous and exit at $53.00, the trade made +1.5R. The result was positive, and the gap between 3R planned and 1.5R taken is the most useful thing the journal learned that day.

Writing the plan first also makes you settle your risk per trade and position size while you are calm, instead of mid-trade.

The execution fields: what happened

Date and time, symbol, direction, fills, size and fees are the facts of the trade, and the fields most likely to be wrong when typed by hand. A transposed digit in a fill price corrupts every metric built on it, so broker sync or a CSV import beats manual entry here.

Fees deserve their own column. A trader who takes 15 trades a day and pays $4 per round trip spends $60 a day, or about $1,260 over 21 trading days. Gross P&L hides that number completely, and a strategy that looks fine before costs can be flat after them.

The result fields: net P&L and the R-multiple

Net P&L is the result after fees, and it is the only P&L figure worth recording. The R-multiple is that result divided by the dollar risk you planned. A $400 win on a trade that risked $200 is +2R, the same quality as a $4,000 win that risked $2,000.

R matters because position sizes change. In dollars, a trade sized up out of boredom can look like your best work. R puts every trade on the same scale.

You do not log expectancy, win rate or profit factor. They are computed from net P&L and R across many trades, and why a 70% win rate can still lose money shows why they have to be read together.

The honesty fields: rules, screenshot, note

The single most useful field for discipline is a yes or no: did I follow my rules on this trade? It costs two seconds to fill in. After a month, it lets you split your results into trades where you followed the plan and trades where you broke it, and compare the expectancy of each. For most traders that comparison is the first time the cost of breaking rules shows up as a number.

Add a mistake tag from a short, fixed list when the answer is no. Four or five tags cover most of it: moved the stop, exited early, oversized, unplanned trade, chased the entry. A fixed list can be counted. Free text can't.

The screenshot records what you saw at entry and exit. The note is one line, not an essay: "chased after missing the first entry" is enough.

Fields that only matter after 50 trades

A second group of fields exists to slice your results by session, market condition or hold time. Slicing needs a sample, and early on there isn't one.

Here is the math. If you win half of 50 trades, the 95% range for your true win rate is roughly 36% to 64%, using the standard normal approximation for a proportion. Split those 50 trades across four sessions and each slice has about 12 trades, where the range widens to roughly 22% to 78%. At that size, a session that looks like your best one could easily be your worst.

These fields belong in this group:

• Session and time of day. Useful once each session has a couple of dozen trades.
• Market condition. A short tag such as trending, ranging or high volatility, so you can see which conditions suit each setup.
• Hold time. Shows whether your winners and losers behave differently once you are in.
• Maximum adverse excursion and maximum favorable excursion. How far each trade went against you and in your favor. They tell you whether your stops are too tight and whether you leave profit on the table, but only across dozens of trades on one setup.
• Planned versus actual entry price. The difference is your slippage, which matters most for fast or illiquid markets.

Fields you can skip

• A 1 to 10 mood or confidence score on every trade. Hard to score the same way twice, and the note plus the mistake tag carry most of the same information.
• Indicator readings at entry. If an indicator is part of the setup, the setup name already covers it, and the screenshot shows the rest.
• Account balance after each trade. It is derived from net P&L, and your equity curve already shows it.
• A paragraph per trade. One line per trade is enough. Save the long-form thinking for the weekly review.

How these fields turn into a review

A journal with the twelve core fields can answer the three questions that decide whether you improve. Which setups make money, ranked by expectancy in R. Whether you follow your plan, from the rules field and the mistake tags. And what trading costs you, from fees and the gap between planned and taken R.

The weekly trade review process walks through reading these fields each week, and how to keep a trading journal covers building the habit so the fields get filled in every time. Start with the twelve, keep them stable, and add the slicing fields once the sample is big enough to trust.