A trading journal is a dated record of each trade decision and its execution: the setup or rule that prompted it, the planned entry, stop and size, what actually filled, the result in R and whether the plan was followed. Write the intent fields before the outcome is known, so a later review compares the plan with the record rather than with memory.
The journal is one part of the trading-plan and process library. The plan says what should happen, the journal records what did happen, and the review explains the difference. Keeping a journal does not make a strategy profitable; it makes the strategy's behaviour inspectable.
Trading journal at a glance
Scroll horizontally to read every column.
| Question | Short answer |
|---|---|
| What is it? | One row per trade decision: intent, execution, outcome and process fields |
| When do you fill it? | Intent before or at entry; execution and outcome after the broker records exist |
| Core measures | R-multiple per trade, slippage, costs, and whether each rule was followed |
| Automated trades add | Alert time and message, processing record, EA log line and broker ticket |
| Where it feeds | Weekly review, trading metrics and candidate rule changes |
What should a trading journal record?
Group the fields into four layers. Keeping them apart stops a good outcome from rewriting the story of a poor decision, and the reverse.
- Intent: date, instrument, direction, setup tag, plan or rule version, the reason in one sentence, planned entry, initial stop, target if any, planned size and the planned cash risk to the stop.
- Execution: signal or decision time, the reference price at that moment, order type, fill time, fill price, filled volume, slippage and costs such as commission, spread and swap.
- Outcome: exit time, exit price, exit reason (stop, target, time, manual), net result in account currency and the R-multiple.
- Process: did every entry, size and exit rule hold? If not, name the rule broken and why. Add a short note on circumstances, such as fatigue or a missed check, only when it helps explain a deviation.
Record the timezone of every time field. The clocks differ between systems. TradingView shows alert log times in your operating system's timezone and exports the alert log to CSV in UTC.[1] MetaTrader 5 shows position, order and deal times on the Trade and History tabs in the broker's trade-server timezone.[2] The MT5 Journal tab uses the timezone of your computer.[3]
Which extra fields does an automated trade need?
With a TradingView alert routed to MetaTrader 5, one trade passes through several separate stages. The alert condition becomes true and the alert triggers. The webhook is delivered. PineConnector processes the message. The EA sends an order request, and the broker accepts or rejects it, producing a deal and a position. Each stage can succeed while a later one fails, so journal each one.
- Alert: alert name, trigger time and the exact message sent, copied from the TradingView Alerts log.
- Processing: the matching entry in the PineConnector Signals log. A received signal is not, by itself, proof that the broker filled an order.[4]
- Terminal and broker: the EA's Experts line, then the order, deal and position tickets. MT5 links each deal to the ticket of the order that produced it.[5]
PineConnector's docs give this same log order for tracing an alert: TradingView Alerts log, then the Signals log, then MetaTrader's Experts tab and order history.[6] The docs also note that a chart marker, a simulated strategy fill and a broker trade are different events. Journal the broker's fill price, not the backtest's.
As of 25 September 2026, PineConnector Analytics reviews an MT5 account's history in Portal. It needs PineConnector MT5 EA v3.41 or later, is not available for MT4 and stops updating if the EA stops or the account disconnects.[7] Analytics shows account results. Your intent fields, rule-adherence flags and deviation notes still come from you.
How do you calculate slippage and R for each trade?
Slippage, long entry = fill price − reference price (positive = adverse)
Slippage, short entry = reference price − fill price (positive = adverse)
R-multiple = net trade result / initial risk R
This page uses the alert price, or your decision price for a manual trade, as the reference. It measures initial risk R as the cash loss from the actual fill to the initial stop at the filled volume. Van Tharp defines R as initial risk and expresses each result as a multiple of it.[8] Use the initial stop even if the stop later moved.
Illustrative example, not a recommendation. A long EURUSD alert fires at 1.10000. The order fills at 1.10010, so slippage is 0.00010, or 1 pip adverse. The initial stop is 1.09810, 20 pips below the fill. The volume is 0.50 lot, and a pip is worth 10 USD per 1.00 lot, so each pip is worth 5 USD. Initial R is 20 × 5 = 100 USD. Planned from the alert price, the stop was 19 pips away, or 95 USD, so the slippage also raised the risk. The position exits at 1.10310, 30 pips above the fill, for 150 USD before costs. After 7 USD commission, the net result is 143 USD, which is 143 / 100 = 1.43R. The 1 pip of slippage cost 5 USD.
Pip value depends on the symbol's contract size and the account currency. Read both from the MT5 symbol specification rather than assuming 10 USD.
Copy this trading journal template
Use one row per trade, or one block per trade in a notes app. A blank field shows missing evidence rather than a zero.
- Identity: trade number ___; date ___; account (demo or live) ___; instrument and broker symbol ___; direction ___.
- Setup and version: setup tag ___; plan or script version ___; one-sentence reason, written before the outcome ___.
- Plan: planned entry ___; initial stop ___; target or exit rule ___; planned volume ___; planned cash risk ___.
- Signal: alert or decision time and timezone ___; reference price ___; message sent (automated only) ___.
- Processing and request: Signals log result ___; Experts log line ___; order ticket ___.
- Fill: fill time and timezone ___; fill price ___; filled volume ___; slippage in pips ___.
- Exit: exit time ___; exit price ___; exit reason ___; deal ticket ___.
- Result: gross result ___; commission ___; swap ___; net result ___; initial R ___; R-multiple ___.
- Process: entry rule followed (yes/no) ___; size rule followed ___; exit rule followed ___; deviation and reason ___.
- Review notes: open question ___; evidence still needed ___.
What should the weekly review ask?
- How many trades followed every rule, out of all trades? Review rule breaches separately from rule-following losses.
- How many trades does each setup tag have? A handful of trades per tag supports a question, not a conclusion. See how many trades a test needs.
- What is the mean R per setup tag, and what share of gross results went to costs and slippage?
- Did every alert match one processing record and one expected broker outcome, with no duplicate?
- Was any trade taken outside the plan's instruments or session? Trade counts above the plan feed the overtrading checks.
- Which proposed change is backed by records, and which by the latest trade alone?
The reason field matters because of hindsight bias. In Fischhoff's 1975 experiments, people who were told an outcome judged it more likely in hindsight and were largely unaware of that effect.[9] A reason written after the exit is shaped by the exit. When the rows show a repeatable pattern, turn the journal into testable rules.
What can a trading journal not tell you?
- Whether an edge exists: a positive average over a short record can be chance. Historical results describe the past, not the next trade.[7]
- Anything about trades you skipped logging: a journal that records only memorable trades is a biased sample. Log every trade, including tiny and cancelled ones.
- Whether a rule is good because it was followed: adherence and outcome are separate columns. A followed rule can lose; a broken rule can win.
- Exact costs from estimates: use the broker's recorded commission and swap, not a backtest setting.
Frequently asked questions
How do you keep a trading journal?
Keep a trading journal by logging every trade as one row with four layers: intent, execution, outcome and process. Write the setup, reason, planned stop and planned risk before the outcome is known. Add the fill, exit, costs and R-multiple from broker records afterwards, then review the rows each week.
What should a trading journal template include?
A trading journal template should include identity fields, setup tag and plan version, planned entry, stop and risk, signal time and reference price, fill and exit details, costs, net result, R-multiple, and yes-or-no columns for each rule. Automated trades also need the alert message, processing record and broker tickets.
What should you track in a trading journal for automated trades?
For automated trades, track the TradingView alert name, trigger time and message, the PineConnector Signals log result, the EA's Experts log line, and the MT5 order and deal tickets. Record the timezone of each time. These fields show which stage failed when an alert and a broker position do not match.
Can PineConnector Analytics replace a trading journal?
PineConnector Analytics reviews an MT5 account's trading history in Portal, including metrics such as net profit, drawdown and win rate. It shows results, not intent. A trading journal still needs your setup tags, planned risk, rule-adherence flags and deviation notes, which the account history does not contain.
Reviewed 25 September 2026. Facts were checked against the linked sources on that date. Nothing in this article was tested on a trading account.
Related reading
- How to write a trading plan (with a template)
- How to turn a trading journal into testable rules
- R-multiple: measuring each trade against its initial risk
- Trading performance metrics library
Sources
- TradingView – What timezone is displayed in alerts?, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Help: Executing trades, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Help: Journal, accessed 25 September 2026.
- PineConnector – Frequently asked questions: Signals log, accessed 25 September 2026.
- MetaQuotes – Basic principles: orders, deals and positions, accessed 25 September 2026.
- PineConnector – Best practices: compare logs in the right order, accessed 25 September 2026.
- PineConnector – Trading analytics, accessed 25 September 2026.
- Van Tharp Institute – A short lesson on R and R-multiples, accessed 25 September 2026.
- Fischhoff (1975) – Hindsight is not equal to foresight, Journal of Experimental Psychology: Human Perception and Performance 1(3), 288–299 (author copy hosted at MIT), accessed 26 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
