Trade Journal Examples: From Trade Log to Behavioral Review
Compare four trade journal examples for logging results, reviewing execution, tracking rule breaks, and finding the format that matches your review question.
A trade journal example is useful only when it shows what the record will help you decide later. A compact trade log can reconcile entries and exits. A setup review can test whether results differ across defined conditions. A behavioral journal can show when execution departed from the written plan. Trying to make one entry answer every question usually creates a journal that is slow to complete and difficult to review.
This guide compares four hypothetical journal entries drawn from one trade sequence. The market details and results are illustrative, not trading recommendations. Use the examples to choose fields for your own method rather than copying the setup itself.
The four trade journal examples at a glance
| Journal format | Primary question | Minimum useful fields | Main limitation |
|---|---|---|---|
| Basic trade log | What happened? | Instrument, time, side, size, entry, exit, costs, result | Does not explain the decision |
| Setup journal | Did the trade match a defined setup? | Setup name, criteria, market context, invalidation, result | Can miss live rule changes |
| Execution journal | Did execution follow the plan? | Planned action, actual action, rule status, deviation, reason recorded at the time | Requires rules to be defined first |
| Behavioral sequence journal | What tends to happen before a repeated mistake? | Prior event, trigger, intended response, action, rule status, review tag | A pattern is not proof of causation |
These formats are complementary. A trader may keep the basic facts on every trade, add setup fields when evaluating a method, and add behavioral fields only when execution drift is the review problem.
Example 1: a basic trade log
A basic log creates a factual ledger of positions and outcomes. It is the smallest useful journal when the goal is record keeping, reconciliation, or a quick session history.
| Field | Hypothetical entry |
|---|---|
| Instrument | ABC futures |
| Date and time | 25 August, 10:12–10:26 |
| Direction | Long |
| Size | 1 contract |
| Entry | 5,020 |
| Exit | 5,012 |
| Planned stop | 5,012 |
| Fees and slippage | Recorded from statement |
| Result | −1R before costs |
Here, R means the amount the trader planned to risk if the stop was reached. Expressing a result in R can make trades with different position sizes easier to compare, but it is only meaningful when the initial risk was defined consistently.
The entry answers what was traded and how it ended. It does not answer whether the setup was valid, whether the size matched the plan, or whether the trader changed a rule while the trade was open. Add fields only when those omissions prevent a useful review.
When a basic log is enough
Use this version when you need a dependable trade history and already review strategy and behavior elsewhere. It is also a sensible starting point when a more elaborate journal repeatedly goes unfinished. Completeness across a few objective fields is more useful than an ambitious template filled in only after unusual trades.
Example 2: a setup-focused journal entry
A setup journal connects the transaction to the conditions that were supposed to justify it. Its job is not to prove that a setup has an edge from one example. Its job is to preserve the classification criteria so a group of comparable trades can be reviewed later.
| Field | Hypothetical entry |
|---|---|
| Setup | Opening-range pullback |
| Required conditions | Trend aligned; pullback holds planned level; entry trigger closes above reference |
| Conditions present? | Yes / Yes / Yes |
| Market context | Opening range expanded; scheduled announcement already passed |
| Entry trigger | Defined confirmation at 5,020 |
| Invalidation | Trade at or below 5,012 |
| Planned target or management rule | Scale only at the predefined level; otherwise exit at invalidation |
| Result | −1R before costs |
| Review note | Setup criteria were present; the planned invalidation was followed |
This record separates setup classification from outcome. The trade lost, but the entry does not automatically label the decision poor. That distinction matters because evaluating a decision only by its result can create outcome bias. In Baron and Hershey’s experiments, participants rated decision quality differently after learning whether an uncertain outcome was favorable. The finding does not establish how any particular trader will judge a trade; it supports preserving what was known and planned before the result. A separate distortion can affect the record before the outcome is even known: if the invalidation condition at 5,012 is reached and the trader searches for a reason it does not really apply, confirmation bias in trading covers how to check whether that search was held to the same standard as the entry check.
What to avoid in a setup journal
Do not let the setup name carry all the information. “A+ setup” is difficult to audit unless the entry records the conditions that made it eligible. Avoid rewriting those conditions after the result. If the definition changes, date the new version and apply it prospectively so earlier trades retain their original standard.
Example 3: an execution-focused journal entry
An execution journal asks whether the trader acted within the plan that applied at the decision point. It is useful when strategy review and execution review need to remain separate.
Consider a second hypothetical entry after the first trade stopped out:
| Field | Hypothetical entry |
|---|---|
| Intended action | Re-enter ABC futures at 10:31 |
| Applicable written rule | No new entries after the 10:30 session cutoff |
| Planned session state | One full-risk loss used; entry window closed |
| Check at decision time | Intended entry recorded at 10:31 |
| Actual action | Entered long after the cutoff |
| Rule status | Deviated |
| Outcome | +0.6R before costs |
| Review note | Profitable outcome; entry occurred outside the pre-session time rule |
This example preserves two truths at once: the trade made money in the hypothetical record, and the execution departed from the written rule. Calling it profitable does not make it aligned; calling it deviated does not erase the profit.
A useful execution label should be neutral and specific. “Deviated: entry after session cutoff” is easier to aggregate than “bad discipline.” The first describes an observable mismatch. The second is a broad judgment that gives the next review little to test.
Example 4: a behavioral sequence journal entry
A behavioral sequence journal adds the event immediately before a decision and the response that was supposed to apply. This is useful for recurring patterns such as revenge trading, FOMO, emotional re-entry, risk escalation, or continuing after a session cutoff.
| Field | Hypothetical entry |
|---|---|
| Prior event | Full-risk stop at 10:26 |
| Observable trigger | Same instrument moved back toward the prior entry four minutes later |
| State noted at the time | Urgency to recover the loss; attention narrowed to the same market |
| Predefined response | Do not initiate a new trade after the session cutoff |
| Action taken | Entered after the cutoff |
| Rule status | Deviated |
| Outcome | +0.6R before costs |
| Sequence tag | Loss → urgency → entry outside planned window |
| Next-session preparation | Keep the cutoff visible; do not rewrite it based on this profit |
The sequence tag is a retrieval aid, not a diagnosis. Repeatedly observing the same sequence can justify a closer review, but it does not prove that the prior loss caused the later action. Other conditions may differ across sessions. Designing a fuller tag vocabulary — separate from this one sequence tag — is its own problem; see trading journal tags for how to structure setup, condition, and behavior tags so they stay usable across many entries.
The predefined response can be written as an if-then statement: If the clock passes the planned session cutoff, then no new position is initiated. A 2025 meta-analysis by Paschal Sheeran, Olivia Listrom, and Peter Gollwitzer examined implementation intentions across 642 independent tests and supports contingent if-then planning as a general self-regulation mechanism across the studied contexts. That evidence is relevant because this example specifies a cue and response; it does not establish that the trading rule is appropriate for a particular strategy or that implementation intentions improve trading profitability.
A blank trade journal template
Start with the review question, then remove any field that does not help answer it.
TRADE FACTS
Date and time:
Instrument and direction:
Size:
Entry, exit, and costs:
Initial planned risk:
Result in currency and R:
SETUP
Setup name:
Required conditions:
Conditions present at entry:
Invalidation:
EXECUTION
Applicable written rule:
Planned action:
Actual action:
Rule status: aligned / deviated / not applicable
Specific deviation, if any:
BEHAVIORAL CONTEXT
Prior event or observable trigger:
State noted at the time:
Predefined response:
Response followed: yes / no / not applicable
Sequence tag:
REVIEW
What was known before the outcome?
What belongs in strategy review?
What belongs in execution review?
One change to the process, if evidence supports it:You do not need every section for every trade. Keep the facts stable, then use the modules that match the current review. For example, a trader investigating missed setup criteria may emphasize the setup block; a trader investigating repeated re-entry may emphasize the execution and behavioral blocks.
How to review several journal entries
One detailed example can explain a decision. A collection of consistently labeled entries can reveal whether the same condition recurs. Review a defined period rather than searching the journal only after a painful loss.
- Choose one question. For example: “How often did I open a new position after my planned session cutoff?”
- Filter comparable entries. Use the same rule version, setup definition, and review window where possible.
- Count aligned and deviated decisions. Keep the classification separate from wins and losses.
- Compare associated outcomes carefully. Describe what occurred in the records without treating a small sample or correlation as proof.
- Inspect the sequence. Look at the prior event, trigger, intended response, and action—not just the final note.
- Change one part of the process. Clarify an ambiguous rule, make a response more visible, or reduce a field that is not being completed. Do not rewrite a sound strategy solely to repair a behavioral deviation.
This review produces more precise conclusions than “I need better discipline.” It might show that the setup rule is ambiguous, that the response was defined but not visible, or that the observed mistake is too infrequent to justify a conclusion.
Common journal entries that look detailed but are hard to use
The emotional diary with no decision standard
“Felt anxious and exited early” records a feeling and an action, but not the planned exit. Add the original invalidation or management rule and the exact action that differed. Emotion can be relevant context without becoming the sole explanation.
The screenshot with no searchable fields
A chart image can preserve market context, yet screenshots are difficult to aggregate by rule status, setup, or trigger. Keep the image if it helps visual review, but pair it with a few consistent text fields.
The score with no definition
A discipline score of 7/10 is not comparable across sessions unless each score has stable criteria. Prefer observable labels—such as “size aligned, entry aligned, exit deviated”—before combining them into any summary score.
The lesson written after the outcome
“I should have held longer” may be hindsight rather than a valid process change. Record the rule that existed at entry and what information was available then. Strategy changes belong in a separate review across comparable trades.
Where Costante fits
A spreadsheet, notebook, or traditional journal app can support every example in this guide if the trader maintains the structure. Costante is designed for a narrower behavioral-performance job: carrying a trader’s existing process through session planning, self-defined guardrails, in-session checks, low-friction logging, and structured behavioral review.
Costante does not generate strategies, determine whether a setup has an edge, connect to brokers, execute or block trades, or guarantee discipline or profitability. The trader defines the method, decides whether to act, and remains responsible for risk. If broker imports, replay, backtesting, or extensive trade analytics are the main requirement, a traditional journal platform may be a better fit.
If the central problem is repeated rule-breaking, read why retrospective journals may not be enough by themselves. If you need to define the rules before recording them, start with the worked trading plan example.
When the records concern contracts, legs, and lifecycle events rather than a simple transaction log, use the options trading journal structure. When the account itself carries stage-specific rules, as in a prop-firm evaluation or funded account, use the prop firm trading journal structure.
Frequently asked questions
What should a trade journal include?
At minimum, include the instrument, time, direction, size, entry, exit, costs, and result. Add the setup definition, applicable rule, planned versus actual action, and behavioral context only when they answer a real review question.
What is an example of a useful trading journal note?
A useful note is specific and preserves the original standard: “My plan allowed no new entries after 10:30. I entered at 10:31, so the trade was profitable but rule-deviated.” It identifies the condition, rule, action, and classification without turning the outcome into a verdict on decision quality.
Should I journal every trade?
Keep the core facts consistently enough to support the review you intend to perform. Detailed behavioral notes can be reserved for defined triggers or deviations if completing them on every trade makes the process unsustainable.
Can a trade journal prove why I made a mistake?
No. A journal can preserve reported state, observable context, and recurring sequences. Those records can support a hypothesis for review, but they do not by themselves prove psychological cause.
Costante provides educational workflow tools, not financial advice. Trading involves risk.