Financial Templates Hub

Trading Journal Template: What to Record and How to Run Weekly Reviews

Trading Journal Template: What to Record and How to Run Weekly Reviews | SG Group

Financial Templates Hub — Records & Reviews 03

Trading Journal Template: What to Record and How to Run Weekly Reviews

The point of a trading journal is not to line up wins and losses. It is to capture the information broker history leaves out — your reasons, whether you kept your rules, and what you noticed — so that the next trade changes. This article groups journal fields into ten areas, shows a column layout that separates facts from interpretation, follows one fictional trade across plan, fill, exit and review, and turns those entries into weekly and monthly improvement, with a path to free templates along the way.

  • The journal complements broker history: reasons, rules, emotions and amendment context
  • Split the fact column from the interpretation column so a win never flips your process grade
  • Record one trade at four timestamps: plan, fill, exit and review
  • Weekly finds concentration and recurrence; monthly revises the fields themselves
Reading timeAbout 13 min
UpdatedJuly 14, 2026
ForTraders with history but no structured review
TypeEducational, descriptive document design

Key takeaways

  • A trading journal is a complementary record that keeps ten areas — identifiers, plan, execution, costs, result, observations, behavior, rule adherence, learning and next action — with facts separated from interpretation.
  • Broker history answers what happened; the journal answers why you did it and what you will do next. Design it to avoid duplicate entry.
  • Following one fictional trade across plan, fill, exit and review makes the recording timing and column layout tangible.
  • The weekly review checks volume, rule breaks, unexpected costs and concentration, then sets one action; the monthly review revises the fields themselves.
  • Every figure, table and schema-planner example uses fictional educational data. The template is a drafting aid; it does not guarantee better performance or legal compliance.
Open contents
  1. The answer: what to record
  2. Why history alone is not enough
  3. Group fields into ten areas
  4. Separate fact, interpretation, action, next
  5. One trade at four timestamps
  6. Daily, weekly and monthly review loop
  7. Journal schema planner (educational)
  8. Choosing an output format
  9. Common failures and checks
  10. Using the Hub (Free to Pro)
  11. FAQ
  12. Summary and next step
  13. Related reading

The answer

The answer: a trading journal records what history leaves out

The first thing to decide with a trading journal template is not how the form looks but what to record. In short, a journal keeps ten areas — identifiers, plan, execution, costs, result, observations such as MFE and MAE, behavior, rule adherence, learning and one concrete next action — and it keeps facts separate from interpretation. Fill prices and profit or loss are recorded accurately in broker history, but why you entered, which rule you followed, what you felt along the way and what you will change next are not. The journal is a complementary record that fills that gap.

A second principle is not to turn the journal into a scorecard of wins and losses. A trade that broke a rule but happened to win looks like a success by result alone, yet it is a dangerous habit that leads to losses when repeated. Conversely, a trade executed correctly to plan that still hit its stop can pass on process. That is why you grade the process by rule adherence and execution quality rather than by outcome, and narrow the improvement to one action each time. Building the trade plan itself is covered in the trading plan template guide, so this article concentrates on what to keep after execution and how to review it.

The numbers, figures and schema-planner examples here are all fictional educational data. A trading journal template is a tool that helps you draft records; it is not investment advice, nor a guarantee that performance will improve. If you want the overall map of financial-document templates first, start with the series pillar, the financial document templates guide, which shows how each template divides responsibility.

Purpose

Why broker history alone is not enough

Many traders assume that having a trade history means their records are complete, but history and the journal cover different information. Broker history mechanically records the facts of the outcome: fill price, size, fill time and profit or loss. It says nothing about why you chose that trade, which setup you followed, whether you kept the rules you set in advance, whether you resisted a rushed entry, or what you will change next — none of the reasoning behind the decision survives.

That gap widens with time. Reviewing a trade from three months ago on history alone, you cannot recall why you entered there, so it offers nothing to improve on. The journal owns the “why” and the “what next” that history cannot answer, and only in combination with history can you reconstruct the full picture of a trade. Put simply, history is what happened and the journal is why you did it and what you will do next.

The key here is not to make the two compete. Fields you can pull straight from history, such as fill price and profit or loss, should not be re-entered by hand in the journal. Keep the journal to information that does not exist in history — that is the first trick to sustaining the habit. The next section groups that “information not in history” into ten concrete areas.

Field design

Group fields into ten areas

Journal fields collapse quickly if you list them as they come to mind. Splitting them into the following ten areas avoids both gaps and duplication. You do not need to fill every area from the start; begin with the four required areas in bold and add the rest once the habit sticks.

  1. Identifiers: date, time, instrument, direction (long/short), setup name, journal ID. These are the starting point for sorting and searching.
  2. Plan: intended entry, stop, target, size, rationale. Fill this before execution.
  3. Execution: actual fill price, fill time, slippage. The gap against the plan shows up here.
  4. Costs: spread, commission, swap and the like. Send detailed realized-cost analysis to the trading cost calculator guide and keep the journal to whether costs occurred and a rough figure.
  5. Result: exit price, exit time, realized profit or loss, pips (or points). Reconcile it against history.
  6. Observations: MFE (maximum favorable excursion), MAE (maximum adverse excursion), holding time. These let you test the exit and stop after the fact.
  7. Behavior: state at entry, while waiting and at exit. Provide preset state labels, not only free text.
  8. Rule adherence: whether you kept the rules set in advance (yes / partial / no). Always look for one rule you did not keep.
  9. Learning: what this one trade tells you, in one or two sentences.
  10. Next action: one behavior to change on the next trade. Make it testable, not abstract.

Whether the size fit your risk tolerance stays in the journal as a check in the rule-adherence area; the calculation itself goes to the lot size calculator guide, and documenting risk caps goes to the risk management plan template. Not loading every calculation into the journal is the crux of a field design you can sustain.

Handling personal data: do not record names, addresses, dates of birth, account numbers, identity-document numbers or login credentials in the journal. Keep only trade facts such as instrument and date, and separate any personally identifying information to the minimum necessary.

Column layout

Separate fact, interpretation, action and next step

Listing the ten areas is not enough: “fact” and “impression” end up in the same field, and later you cannot tell what actually happened. So split the record into four layers. The figure below shows the structure built from the bottom up — fact, then interpretation and observation, then action (rule adherence), then next step.

Structure diagram splitting the journal into four layers: fact, interpretation and observation, action and rule adherence, and next step The bottom layer is fact, above it interpretation and observation, above that action and rule adherence, and the top layer is next step. Lower layers are more objective and fixed; higher layers carry more subjectivity and judgment. No numbers are shown. The four record layers: lower is objective fact, higher is judgment and action 1 · Fact Fill price, time, profit/loss, pips (objective data you can reconcile; no interpretation mixed in) 2 · Interpretation & observation MFE/MAE, emotion state labels, your read on “why it moved” (a separate column from fact) 3 · Action & rule adherence Whether you kept the preset rules (yes/partial/no). Identify one rule you did not keep 4 · Next step — decide just one behavior to change on the next trade objective to subjective/judgment
ConceptRecord-layers figure. The core is separating fact (layer 1) from interpretation (layer 2) into different columns. Keep rule adherence and the next step independent of the fact column so the outcome (win or loss) never flips your grade of layers 3 and 4.

This layering has two practical effects. First, it creates the discipline of never rewriting the fact column after the event. If you repaint the facts after a stop-out with “what I really thought was…”, the record loses its value. Second, placing emotion in an independent column lets you treat it as analytical material — “is the same mental state repeatedly leading to losses?” — rather than an excuse for the outcome. The idea of labeling fact, counterparty statement, author observation, inference and opinion is shared with client-facing documents; the document-quality section of the pillar guide sets it out in detail.

One consistent case

Record one fictional trade at four timestamps

To make the recording timing tangible, we follow one fictional educational trade across four timestamps: plan, fill, exit and review. The tables, figures and schema-planner examples that follow all use the same trade’s values. Every instrument name and number is an illustrative example for teaching, not a real product or performance record.

This is a fictional educational example. It is not a real client, provider, product or contract, nor legal advice or a filing-ready finished document. The instrument “USDJPY (illustrative)” is an illustrative label used to show the record format.
Table 1: recording fictional trade “T-0142” at four timestamps (illustrative example, not a real trade)
TimestampFacts recordedInterpretation / observationAction / next step
1 · Plan
06-12 09:10
USDJPY (illus.) / long
Entry 156.20 / Stop 155.80
Target 157.00 / 0.30 lot
Higher timeframe in an uptrend; expecting a pullback into support. Intended risk-reward 2.0. Rule check: no entry within 30 minutes of a news release. Wait until conditions are met.
2 · Fill
06-12 09:32
Fill 156.24 (+4 pips slippage)
Spread 0.3 pips assumed
Filled 4 pips worse than intended. Record the slippage as a fact. Consider a limit entry rather than chasing at market (candidate note).
3 · Exit
06-12 14:05
Exit 156.72 / +48 pips
Realized P&L ≈ +14,400 JPY
MFE +64 pips (up to just short of target) / MAE −12 pips. Reversed 4 pips short of target. Manual take-profit on the pullback high. The take-profit condition was not written down.
4 · Review
06-12 same day
Final: +48 pips / held 4h 33m News-avoidance rule kept (yes). Take-profit rule undefined (partial). A win, but a gap in execution. Next action: define one rule, “take half profit 10 pips before target,” and test it next time.

What this example shows is that even a winning trade has something to improve. The result is a +48 pip gain, but the review column reveals that the take-profit rule was undefined. Had you recorded only the result, this gap would be left in place again and would eventually cause you to give back profit on a larger reversal. Because fact (+48 pips) and interpretation (the exit worked by luck) are kept separate, you can pick up one issue hiding behind the win. The MFE/MAE concept and its use for testing exits and stops go deeper alongside the performance-metric discussion in the backtesting guide.

Review loop

The daily, weekly and monthly review loop

A journal does not end when you write it; it drives improvement only when you read it back at set intervals. Recording and review turn in the following loop: record one trade daily, check concentration and recurrence weekly, revise the fields themselves monthly, and return to the next plan — this lap is the learning cycle.

Loop diagram running from plan through fill, exit, daily record, weekly review and monthly improvement back to plan A concept diagram linking six stages left to right with arrows — plan, fill, exit, daily record, weekly review and monthly improvement — and a dashed arrow returning from monthly improvement to plan. No numbers are shown. PLAN Before entry rationale, stop, target FILL Execution price, slippage EXIT Result P&L, MFE/MAE DAILY Daily record fill in same day WEEKLY Weekly review concentration, recurrence MONTHLY Monthly revise revise the fields Feed the fields revised in the monthly step back into the next plan to complete the loop (dashed)
ConceptThe record-and-review loop. Daily is recording, weekly is concentration and recurrence, and monthly is revising the fields themselves — each has a different role.

Five checks for the weekly review

The weekly review is not the place to chase the win or loss of individual trades; it is where you look for repeating patterns. Keep it to the following five checks and decide only “one action to change next week” at the end. Deciding many things means none get done, so the action is always one.

  • Number of trades: the gap between planned and actual count (a sign of overtrading).
  • Rule breaks: which rules you did not keep, and how many times.
  • Unexpected costs: trades where unplanned slippage, commission or swap appeared.
  • Concentration: whether losses or breaks cluster by session, instrument or setup.
  • Recurrence: whether the same mistake repeats from the previous week.

Monthly: revise the fields themselves

Where the weekly review looks at the content of the records, the monthly review looks at their framework. A column that is almost never filled, or one that always takes the same value, is not working as a field. Cut the fields that go unused and keep the ones that drive decisions — doing this stocktake once a month keeps the journal from bloating and holds down the writing burden. When you change a field version, leave a one-line note of when and why so comparisons with past records do not break. When you reach the stage of designing version control and change history properly, the document version control, approval and audit-trail guide is a useful reference.

Educational mini tool

Trading journal schema planner (educational)

This is a small teaching aid that turns the ideas so far into a draft field set matched to your own trading. Choose your trading style, the time you can spend recording, and the cost, behavior and rule fields you want, and it shows a draft of required and optional fields, capture timing, weekly questions and a suitable output format. It does not grade performance, judge a winning strategy or diagnose psychology. Nothing is saved or sent; everything is processed inside the browser. Do not enter personal data such as names or account numbers.

Affects the information per trade and the recording frequency.
Changes the suggested capture timing.
Decides whether to include effort-heavy fields such as MFE/MAE as optional.
A once-a-week check for concentration and recurrence.
Cost fields to record
Behavior fields to record
Rule fields to record

Required fields

Identifiers (date, time, instrument, direction, setup, journal ID) / Plan (intended entry, stop, target, size, rationale) / Execution (fill price, fill time, slippage) / Result (exit price, exit time, realized P&L, pips) / Learning and next action (one line each)

Optional fields (based on your selection)

Cost: SpreadCost: SlippageBehavior: Emotion at entryRule adherence: Avoid news releasesRule adherence: Maximum lot capObservation: MFE/MAE (recommended given 10–15 min)

Capture timing

Every trade: record the plan before execution, the fill and result right after the close, and the learning and next action the same day.

Weekly review questions

Number of trades / any rule breaks / unexpected costs / concentration by session, instrument and setup / one action to change next week

Recommended output format

Keep structured fields as a table (CSV/TXT) and rationale or review comments as prose (Markdown/HTML) for an easy layout. Swing carries more information per trade, so give the prose column more room.

This is a teaching aid that helps draft a field design; it does not guarantee better performance, win rate, legal compliance or client suitability. Before real use, standardize account currency, time zone and fee units across every record, and confirm no personal data is included. Check the current fields and output formats for formal templates in the Financial Templates Hub.

The tool above is a simplified version for roughing out fields, more basic than the templates in the actual service. Confirm the current forms, input fields and output formats in the Financial Templates Hub. If JavaScript is disabled, the output example for the default selections above (swing / every trade / 10–15 minutes, and so on) is shown as is.

Output formats

Choosing an output format: TXT, Markdown, HTML, JSON and print

Which format to keep the journal in depends on what you want to do later. The best choice differs depending on whether you want to aggregate, to read back, or to hand off to another tool. The table below is an educational general summary of what each representative format suits and does not suit. Note that the format itself does not guarantee legal compliance or long-term preservation.

Table 2: comparing journal output formats and their uses (general summary; confirm supported formats in the current service)
FormatSuited toWatch out for
TXTMinimal notes; universal, opens anywherePoor for aggregation or formatting. You must decide the field separators yourself.
CSV / spreadsheetAggregating count and concentration; sorting by session or instrumentHard to write prose rationale or review. Fix the column design first.
MarkdownProse-centered records such as rationale and review commentsAggregation needs a separate step. Standardize heading and bullet rules.
HTMLReading back with figures and tables; formatting before printMore effort to create. Needs a self-contained layout check.
JSONHanding off to other tools; structured reuseNot for direct human reading. Consistent key names are a prerequisite.
Print / PDF-ready HTMLFixing a point-in-time record for storage or sharingPDF-ready HTML is not a certified PDF/A file itself and does not automatically guarantee authenticity.

In practice, splitting roles — structured fields in CSV or a table, rationale and review in prose (Markdown/HTML) — is the layout easiest to sustain. Decide field names and order first so a later format change is easy to migrate. Translation QA, terminology consistency, RTL and format support for recording in multiple languages are covered in the multilingual financial document templates guide.

Failures and checks

Common failures and a check procedure

When a journal does not last, or lasts but does not lead to improvement, the cause is usually one of the following. Alongside them, here is a procedure to check before you share or store records.

Main reasons it does not last or does not work

  • Too many fields: setting up 20 columns from the start leaves them unfilled and abandoned. Begin with the four required areas.
  • Fact and impression mixed: price and excuses share the same field, so you cannot tell the facts apart later. Split the layers.
  • Turned into a scorecard: chasing only profit and loss, without grading rule adherence and execution quality.
  • Too many improvement actions: trying to change several at once means none happen. Narrow the next action to one.
  • Inconsistent units and times: account currency, time zone, fee units and pip/point differ, so nothing can be aggregated.
  • Scattered screenshots: uneven locations and file names mean they cannot be tied to the trade later.

Check procedure before sharing or storing

  • Are numbers, dates, currencies, time zones and instrument names standardized across every record?
  • Do file names follow a fixed date-first rule (for example, 2026-06-12_USDJPY_T0142)?
  • Are screenshots and external charts kept under the same naming rule and location?
  • Has later interpretation crept into the fact column? Are unverified items marked “unverified”?
  • Does the record contain any personal data such as names, account numbers or credentials?

This check is a self-inspection to raise the accuracy of your records; it is not a procedure that guarantees legal compliance or audit readiness. Meeting the checklist does not lead to a conclusion of “safe” or “will pass review.” The review perspective for advertising and client-facing documents is handled separately in the financial advertising review checklist guide.

Using the Hub

Using the Hub: confirm the structure on Free, run it on Pro

Here is the flow for turning the field design so far into an actual template. The basic path is: first confirm and use the free trade-log and weekly-review templates on Free to check the record fields and review shape, then compare Pro’s scope when you need repeated output, multiple save formats and output history.

  • Free: use the free templates without registration to check the record fields and the review shape. First, see whether this article’s four required areas are present.
  • Pro: consider it when you want to run repeated output in the same layout, multiple output formats and a period of local output history as part of your workflow. Supported languages, history periods and account limits can change, so confirm the latest details on the plans page.

If you want to manage investment theses or instrument-analysis notes in a separate template, the investment thesis template guide is the entry point, and to place recorded learnings within the wider set of articles, the English financial learning articles index is the way in. Separating analysis outside the trade, such as reading the macro environment, into the macro analysis guide keeps the journal itself light. Because the range of templates and support can be updated, no fixed count is placed in the body. Confirm the latest on the service side.

FAQ

Frequently asked questions

What should a trading journal record?
It records ten areas — identifiers, plan, execution, costs, result, observations such as MFE and MAE, behavior, rule adherence, learning and one next action — while keeping facts separate from interpretation. Fill prices and profit or loss already sit in broker history and are only part of the result; the reasons for entering and whether you followed your rules live in the journal. Rather than filling every field from the start, fix four first — plan, execution, result and next action — and add behavior or MFE/MAE once the habit sticks. The grouping is shown in the record-layers figure in the body.
Why is broker trade history not enough?
It is not enough because history records outcomes such as fill price, size and profit or loss accurately, but not why you entered, which rule you followed, how you felt during the trade or what you will change next. The journal is a complementary record that fills that gap: history answers what happened, and the journal answers why you did it and what you will do next. The two do not compete, and duplicating fields you can copy from history keeps the workload down.
Should I review winning trades too?
Yes, because whether you won and whether you followed the plan and rules are separate axes. A trade that broke a rule but happened to win is dangerous: repeat it and it tends to lose, and looking only at the result hides the habit. Conversely, a trade executed correctly that still lost can pass on process. Grade the process by rule adherence and execution quality rather than by win or loss, and always look for one rule you did not keep even on winning trades.
How should emotions be recorded without overinterpreting them?
Do not rely on free text alone; use a few prepared labels plus a short note. Defining states such as “at entry: calm / slightly anxious / rushed” makes later aggregation easier and reduces writing effort. Record emotions in the interpretation and observation column rather than the fact column, and never use them as an excuse for the result. Treat behavior notes as material for spotting whether the same state repeatedly leads to losses, not as self-diagnosis.
What belongs in a weekly trading review?
Check the number of trades, whether any rules were broken, unexpected costs, concentration by session, instrument or setup, and a recurrence check. The weekly review looks for repeating patterns rather than the win or loss of individual trades. Keep it to three to five checks and decide only one action to change next week. Reviewing whether the fields themselves still fit reality belongs in the monthly review, which keeps the granularity consistent.
Should a journal include MFE and MAE?
They are not mandatory, but recording them helps improve exits and stops. MFE (maximum favorable excursion) is the largest unrealized gain reached before the close, and MAE (maximum adverse excursion) is the largest unrealized loss, so you can later test whether you took profit too early or set the stop too tight. If manual entry is a burden, start with a simple “reached target?” and “came near the stop?” choice and replace it with numbers later. Keep the MFE/MAE definition aligned with the backtesting view to avoid confusion.
Is a spreadsheet or narrative template better?
A spreadsheet suits aggregation and concentration analysis, while a narrative template suits capturing reasoning and observations. In most cases the practical answer is to split roles: structured fields such as numbers, dates and rule adherence in a table, and rationale and review comments in prose. What matters is less the format itself than a column layout that separates facts from interpretation and recording the same fields every time. Decide field names and order first so a later format change is easy to migrate.
How should I name and retain journal files?
Set a retention period that matches your own review cycle and use a fixed file-naming rule that starts with the date. A format such as “2026-06-12_USDJPY_T0142” sorts chronologically, which is easy to handle. Keep screenshots and external charts under the same naming rule and location, and standardize time zone, account currency and fee units across every record. Never put names, account numbers or credentials in the file name or the body.

Summary

Summary: the answer and your next step

What a trading journal template should really keep is not a list of wins and losses but the information broker history leaves out: why you entered, whether you kept the rules, and what you will change next. Record the ten areas from identifiers to next action with facts separated from interpretation, and grade the process by rule adherence and execution quality rather than by outcome — this design is the backbone.

In practice, five points make the journal drive improvement: (1) start with the four required areas and do not add too many fields, (2) split the fact column from the interpretation column, (3) keep one trade across plan, fill, exit and review, (4) check concentration and recurrence weekly and decide one action, and (5) revise the fields themselves monthly. After that, all that remains is to record the next trade with the same fields.

Read next

FH04: Trading Risk Management Plan Template — document per-trade loss, daily caps and stop rules — turn the rule gaps you spotted in the journal into a management plan set in advance.