What Should a Trading Journal Include? 18 Fields That Matter

Entry, exit, and P&L only answer whether a trade worked. The other fields, grouped into context, execution, result, and process, are what explain why.

What Should a Trading Journal Include? 18 Fields That Matter

Last updated:

In short. A trading journal that only records entry price, exit price, and profit or loss answers whether a trade worked, but not why. The fields that actually change behavior fall into four groups: trade context, execution and risk, result, and process. Missing any one of them leaves a gap that shows up later as a repeated mistake nobody can name.

Most traders start a journal with three or four columns and stop there, because that is what a spreadsheet naturally suggests. It takes a losing streak that looks identical to three previous losing streaks, with no record of what actually caused any of them, to notice that the journal answered "what happened" without ever answering "what was I doing wrong."

Trade context: the fields that make a trade findable later

A journal entry is only useful if it can be found and compared later. Five fields make that possible.

Date and time of entry. Not just the day, the time of day. Patterns tied to session (a strategy performing worse in the first hour after open, for example) are invisible without a timestamp.

Instrument or symbol. Simple to log, easy to skip when trading fast, and the first field needed to filter results by market.

Direction (long or short). A strategy can have a real long-side edge and no short-side edge, or the reverse. Without this field split into the results, both get averaged into one number that describes neither.

Setup or strategy tag. The single most important context field. Every trade belongs to some setup, even an ad hoc one, and tagging it is what makes it possible to later ask "how is this specific setup performing," not just "how am I performing."

Timeframe. A five-minute chart entry and a daily chart entry can share a symbol and direction while having nothing else in common. Mixing them in the same performance number hides which one is actually working.

Execution and risk: the fields that explain the outcome, not just report it

Entry price and exit price. The baseline every journal already has.

Position size. Needed to convert a dollar profit or loss into a percentage of the account, and to check whether size was actually consistent with the trading plan.

Stop-loss level. Not just whether one was set, but where. A stop moved after entry is one of the most common ways a small planned loss becomes a large unplanned one, and the only way to catch that pattern is comparing the original stop to where the trade actually closed.

Take-profit or target level. Comparing the planned target to the actual exit shows whether trades are being cut short out of impatience or run past the plan out of greed, a pattern that is close to invisible without logging the original target.

Risk amount, in dollars and as a percent of account. This is the number a daily or maximum drawdown limit is actually measured against, particularly relevant on a prop firm challenge account, where the difference between risking 1 percent and 3 percent per trade is the difference between surviving a losing streak and ending the evaluation on it.

Important. Logging the stop-loss and target as originally planned, not as they ended up, is what separates a journal from a trade history export. A trade history shows what happened. Only the planned levels, recorded before the outcome is known, show whether the plan was actually followed.

Result: the fields that make performance comparable across trades

Profit and loss, net of fees. Obvious, but frequently logged gross, which quietly inflates every result by the cost of trading.

Fees and commissions. Worth its own field specifically so it can be totaled separately and checked against how much it is actually costing to run a given strategy at a given size.

R-multiple result. The result of the trade expressed as a multiple of the amount actually risked, not the raw dollar amount, a framework developed by trading coach Van Tharp specifically to make trades of different sizes comparable on the same scale (Van Tharp Institute: Tharp Think Trading Concepts). Without this field, a strategy that occasionally sizes up large winners can look better than it is, since raw dollar totals do not adjust for how much was actually risked to get them.

Process: the fields most journals skip, and the ones that matter most

Psychologist and trading coach Brett Steenbarger has written specifically about this gap: a journal that only tracks outcomes documents the market, while a journal that also tracks process documents the trader, and it is the second kind that actually changes behavior over time (TraderFeed: Trading Psychology Techniques – Keeping a Trading Journal).

Plan followed (yes, no, or partial). The single field that turns a journal into a discipline tool instead of a results log. A losing trade where the plan was followed exactly is a different problem than a losing trade where the plan was abandoned halfway through, and averaging them together hides which one is actually happening more often.

Mistake or error tag. A short, consistent tag list, entered early, held too long, oversized, moved the stop, chased an entry, works better than a free-text note because it can be counted. Six months of "moved the stop" tags on losing trades is a pattern a paragraph of notes buried in a spreadsheet will not surface on its own.

Emotional state or confidence level. A simple scale logged before the trade, not after. Reconstructed after a losing trade, emotional state tends to get rewritten to match the outcome; logged in the moment, it can actually be compared against results later.

Notes or lessons learned. The one open-text field worth keeping, specifically because the other seventeen are structured enough to be searched and filtered, which is what makes a short free-text note next to them actually readable months later instead of buried in a wall of similar entries.

The 18 fields at a glance

Group Field Why it matters
Context Date and time Surfaces time-of-day and session patterns
Context Instrument/symbol Filters results by market
Context Direction (long/short) Separates long-side and short-side edge
Context Setup/strategy tag Enables per-setup performance review
Context Timeframe Prevents mixing incompatible strategies
Execution Entry price Baseline result calculation
Execution Exit price Baseline result calculation
Execution Position size Converts P&L to percent of account
Execution Stop-loss (as planned) Detects stops moved after entry
Execution Take-profit (as planned) Detects early exits or greed
Risk Risk amount ($ and %) What drawdown limits are measured against
Result P&L, net of fees Accurate trade outcome
Result Fees/commissions Isolates the cost of trading
Result R-multiple Makes trades of different sizes comparable
Process Plan followed (Y/N/partial) Separates discipline from results
Process Mistake/error tag Turns recurring errors into countable data
Process Emotional state (pre-trade) Links confidence level to actual outcomes
Process Notes/lessons learned Captures context the structured fields miss

What happens with a journal that skips the process fields

The first ten fields, context through result, are enough to calculate win rate, profit factor, and expectancy. They are not enough to explain why those numbers are moving. A trader whose expectancy declines over a month with only outcome fields logged can see that something changed and nothing about what. The same decline with plan-followed and mistake tags logged usually shows a specific, nameable cause: size creeping up past the tested plan, or a specific setup being taken outside its normal conditions, or entries drifting earlier than the tested rules called for.

Illustrative example of a trading journal entry with context, execution, and process fields grouped together

Eighteen fields, not more

More fields are not automatically better. A journal with forty fields per trade tends to get abandoned within a few weeks, because the friction of logging a trade starts to compete with actually taking the next one. Eighteen fields, grouped into the four categories above, cover context, execution, risk, result, and process without turning journaling into a second job. Each one earns its place by answering a specific question a shorter journal cannot: which setup, which session, which mistake, which emotional state, tied to which actual outcome.

Logging all eighteen by hand in a spreadsheet is possible, and for a low trade count, reasonable. It becomes error-prone once R-multiples, plan-followed rates, and mistake-tag frequency need to be calculated and cross-referenced across multiple setups or multiple accounts, which is where a structured trading journal that calculates these fields automatically removes the most common reason journals get abandoned: the gap between what should be logged and what is actually sustainable to log by hand.

This article is for educational purposes only and is not financial or investment advice. Trading with leverage carries a high risk of loss. Past performance does not guarantee future results.

Track all eighteen fields automatically, from trade context to plan-followed and R-multiple, in the BitStat trading journal, instead of rebuilding the spreadsheet every time a new pattern needs checking.

The essentials, answered

Frequently asked questions

What is the most important field in a trading journal?
Setup or strategy tag is arguably the most important context field, since it makes it possible to review how a specific setup is performing rather than only an account-wide average. Plan followed (yes/no/partial) is the field most journals skip that matters most for catching discipline problems.
Why log the stop-loss and target as originally planned?
Logging the planned stop and target, not just where the trade actually closed, is what shows whether a plan was followed. A stop moved after entry or a target abandoned early are both invisible if only the final exit price is recorded.
What is an R-multiple and why track it?
An R-multiple expresses a trade's result as a multiple of the amount actually risked, not the raw dollar amount, making trades of different sizes comparable. The framework was developed by trading coach Van Tharp specifically for this purpose.
Is 18 fields too many to log for every trade?
Manually, it can become a lot, which is why journals with too many fields per trade tend to get abandoned. Eighteen fields grouped into four categories, context, execution, result, and process, cover what matters without turning journaling into a second job, especially when a journal tool calculates the derived fields automatically.
What is the difference between outcome fields and process fields in a journal?
Outcome fields (entry, exit, P&L, R-multiple) show what happened. Process fields (plan followed, mistake tag, emotional state) show why. A journal with only outcome fields can show that performance declined without showing what specifically changed.