How to keep a trading journal: what to log and when
/5 min read/GlanWick
To keep a trading journal, log ten fields for every trade right after you close it: eight mechanical facts about the execution and two about the decision behind it. Once a week, sort the rows by those two decision fields and add up the results, because that's where your patterns show up.
A full row takes under 2 minutes.
What a trading journal is
A trading journal is a record of every trade you take, with two kinds of information per trade. The first is the execution: instrument, direction, prices, size and result. The second is the decision: which setup you traded and whether you kept your own rules.
You keep it to review your performance and correct your behavior. A trade log holds the execution half only, and every broker statement or CSV export is one.
A log answers "what did the account do?" A journal also answers "which of my decisions did that?"
Psychology has tested whether self-monitoring changes behavior, and we collected the studies, limits included, on why a trading journal works.
The ten fields, in two layers
The mechanical layer is eight facts you copy from the fill confirmation or pull from a CSV export. The decision layer is two choices only you can make. The right column is one filled row: a trade on a 5,000 dollar account that risks 1% per trade, so 1R is 50 dollars.
| Layer | Field | Example row |
|---|---|---|
| Mechanical | Date and entry time | Tuesday, 10:42 ET |
| Instrument | Example stock | |
| Side (long or short) | Long | |
| Entry price | 40.00 | |
| Exit price | 38.00 (stop filled) | |
| Stop, as set at entry | 38.00 | |
| Size | 24 shares | |
| Net PnL (profit or loss) after fees | -50 dollars | |
| Decision | Setup, from your list | Pullback |
| Mistake, from your list | None |
Log the stop you placed before the entry, even if you moved it later. Entry, stop, size and fees decide what you lose if the stop is hit, and that amount is your planned risk, called 1R. Net PnL divided by 1R is the trade's R-multiple. A stop edited after the fact bends every R calculated from it, and tracking R-multiples covers the method in full.
The example's size comes from the risk budget (position sizing in one step). Of the 50 dollars, 2 go to fees, which leaves 48, and a stop 2.00 below the entry allows 24 shares (48 ÷ 2.00). The stop filled, the trade lost 48 dollars plus 2 in fees, and the net result is -50 dollars, or -1R.
That's a planned loss, and the mistake field says so. The weekly review files it under the cost of trading that setup.
Setup and mistake come from lists you write before you trade. A setup is a pattern you defined in advance as a reason to enter. Keep 3 to 5 setups, and about 5 mistakes you can answer with yes or no: moved stop, no stop, size above plan, entry outside your setups, re-entry within 10 minutes of a loss. Picking from a list takes seconds. A free-text essay per trade takes minutes, and by week three the essays stop getting written.
That's how a row stays under 2 minutes: eight facts you copy, two choices you pick.
Log versus journal
Now a week of 10 trades on the same account, each planned at 50 dollars of risk. Read as a log, the week fits in one line: 4 winners, 6 losers, -212 dollars net. That's everything a broker statement can say, and it reads like a strategy that stopped working.
Read as a journal, the mistake field splits the same 10 trades in two.
| Mistake field | Trades | Winners | Net PnL |
|---|---|---|---|
| None | 7 | 3 | +48 dollars |
| Size above plan | 3 | 1 | -260 dollars |
| Total | 10 | 4 | -212 dollars |
Three oversized trades lost 260 dollars, more than the whole week's net loss. The other seven made 48 dollars together. At plan size, three stopped-out trades cost 150 dollars (3 × 50), and these three cost 260 with a winner among them.
Seven trades are far too few to judge the setup, so the review starts with what the journal can already show: the three entries where size went above plan, and what happened right before each one.
When to write it down
Right after the exit, before the next entry. Fill the row while the trade is still on your screen. The stop and the setup are the fields that drift first: after a loss, the planned stop tends to get remembered wider, and after a win, almost any entry can be made to look like a setup. A row written the next morning is written by hindsight.
Once a week, at a fixed time. Sort the week's rows by the mistake field and add up net PnL for each value, then do the same by setup. The table above is exactly that: one sort, one sum per value. Then write one rule for the next week that targets the most expensive line, phrased so you can check it before an entry.
With entry times logged, the weekly review can also test whether your results change after a certain number of trades per day, as in max trades per day from your own data.
If you'd rather not copy the mechanical layer by hand, GlanWick's journal is free and takes trades by CSV import or through a read-only broker sync, still in beta. A manual entry has a field for the planned risk, which turns the result into an R-multiple, and your setup list maps onto strategy tags, with emotion tags next to them. R-multiple distribution and expectancy in R and win rate per setup start on Starter.
Short version
Log ten fields right after every exit: date, instrument, side, entry, exit, stop, size and net PnL after fees, then setup and mistake from lists you wrote in advance. Once a week, sort by the two decision fields and add up each group. In the example week, that one sort turned a -212 dollar week into one question about position size.
Keep reading
Note: GlanWick is a financial information service and does not provide investment advice. This article is for informational and educational purposes and is not a recommendation to act. Broker connections are strictly read-only, and every order inside the software is a simulation. Trading involves substantial risk, up to total loss.

