Track the smallest record that can reconstruct the trade, test it against the plan, and support the next decision. Start with execution identity, instrument and direction, timestamps, fills and size, and net result with currency and costs. Add plan, setup, risk, decision, screenshot, context, excursion, trader-reported state, and review fields only when you can use them consistently. The ranking below measures the damage caused when a field is missing—not a universal statistical effect.
How These 15 Journal Fields Are Ranked
A field has high impact when losing it prevents reconciliation, corrupts a denominator, or makes a later review unable to distinguish what happened from what was intended. A lower-ranked field can still be decisive for a specific strategy. The order therefore follows three tests:
- Can the trade be identified and reproduced?
- Can the result be calculated with the correct account, currency, and costs?
- Can the reviewer compare the execution with the plan without inventing context?
This is a decision-impact ranking, not a claim that one field predicts improvement for every trader. The minimum viable journal is the smallest set that passes those tests for your venue, instruments, and review question.
Tier 1: Five Fields That Make a Trade Auditable
These fields form the execution spine. Record them from the broker, exchange, or other authoritative venue whenever possible. FINRA advises investors to compare trade confirmations with account statements, including transaction date, price, quantity, and fees; that same reconciliation principle is useful for a trading journal even when the product or venue is outside FINRA's scope.
1. Account and source identity
Record: account, broker or venue, source trade/order ID, and import batch where available.
If missing: duplicates, cross-account mixing, and corrections cannot be resolved reliably.
2. Instrument and direction
Record: canonical symbol plus long/short or buy/sell.
If missing: the trade cannot enter an instrument, exposure, or directional comparison.
3. Entry and exit timestamps
Record: full timestamps, source timezone, and resolved workspace timezone.
If missing: session, sequence, duration, event, and overtrading analysis become ambiguous.
4. Fills, prices, and size
Record: entry/exit fills, quantity, partials, scale-ins, remaining size, and corrections.
If missing: the position path, slippage, risk, and realized result cannot be reconstructed.
5. Result, currency, and costs
Record: native P&L, currency, commission/fee, funding or swap where applicable, and conversion evidence.
If missing: gross and net results get mixed; missing costs can be mistaken for zero.
Date alone is not enough when a strategy depends on session boundaries or trade sequence. An instrument plus a positive P&L label is not enough when two accounts, partial fills, or an unresolved currency conversion are involved. Preserve the source record first; derive display labels and analytics from it later.
The journal-building guide shows how these execution facts fit into a durable schema. If an import cannot establish a required field, label the gap and keep the original source row instead of silently guessing.
Tier 2: Five Fields That Reconnect the Trade to the Plan
Execution facts show what happened. These next fields show what the trade was supposed to be. They must refer to the version that existed at decision time; a current plan should never rewrite a historical trade.
6. Setup and strategy version
Capture: stable setup ID/name, strategy, version, and effective date.
Enables: was this trade part of the same repeatable definition as the comparison set?
7. Planned stop, target, and invalidation
Capture: levels or rules known before entry, including no-trade and early-exit conditions.
Enables: did execution follow the intended risk and exit logic?
8. Plan adherence and exception
Capture: followed, partial, broke, not applicable, or unknown—plus the exact rule and evidence.
Enables: was the process compliant independently of the P&L outcome?
9. Decision reason
Capture: one falsifiable sentence naming trigger, permission, and disconfirming condition.
Enables: can a reviewer reconstruct why the trade was allowed without hindsight?
10. Screenshot or decision artifact
Capture: chart or order-state image tied to timestamp, symbol, plan version, and purpose.
Enables: what visual context was available at the decision that structured fields do not preserve?
A setup name and a trade reason are not duplicates. The setup name is a stable grouping key; the reason is the instance-specific case for taking this trade. “Breakout” can be a setup. “Accepted above the dated range after the permitted trigger; invalidate on return below the range” is a reviewable decision record.
A screenshot provides visual context only when it is anchored. A chart saved later without timestamp, symbol, timeframe, or plan version can support a story that was not available at entry. Save the decision-time artifact, then link it to the trade rather than treating an image folder as evidence by itself.
For a practical way to separate setup identity, filters, triggers, and evidence, use the setup-confluence framework.
Tier 3: Five Fields That Deepen Analysis
Add these when the execution and plan fields are reliable. They help answer narrower questions, but they cannot repair missing identity, fills, costs, or plan authority.
11. Session and market context
Use: session, event window, volatility/regime label, and whether the label was known in real time.
Guardrail: do not compare labels whose definitions changed mid-period.
12. Excursion and exit evidence
Use: maximum favorable/adverse price, MFE/MAE in R, and planned versus actual exit.
Guardrail: prefer venue-derived observations and disclose incomplete price-path coverage.
13. Trader-reported state
Use: a short self-report such as calm, rushed, uncertain, or revenge—recorded by the trader.
Guardrail: treat it as authored context, not a diagnosis or causal fact.
14. Behavior or mistake tag
Use: a controlled tag tied to a specific observable action.
Guardrail: keep tag definitions stable and retain “unknown” when evidence is absent.
15. Review lesson and next action
Use: finding, limitation, one action, effective date, recheck, and stop condition.
Guardrail: do not let a lesson overwrite the source facts or dated plan.
Emotional or mental-state notes can be useful because they preserve what the trader reported. They do not establish that the state caused the result. Compare them only when the labels, strategy, and surrounding evidence are consistent, and keep alternative explanations visible.
Excursion fields are valuable only if the underlying path is trustworthy. A manually remembered “maximum favorable move” is different from a venue-derived price observation. Store the source and update time beside derived MFE/MAE values so later analysis can distinguish evidence from recollection.
Do Not Add All 15 at Once
Progressive capture should follow missing evidence, not a calendar or a universal trade-count threshold:
Start with the execution spine
Make ranks 1–5 complete enough to reconcile one closed trade. If the venue exports them, import instead of retyping.
Add plan authority next
Introduce ranks 6–10 when setup definitions and risk rules can be versioned at decision time.
Add only decision-relevant context
Use ranks 11–15 when a named review question requires them and their definitions can stay stable.
Publish missingness
Count unknown, unmatched, ambiguous, excluded, and cost-incomplete records instead of hiding them.
A field earns its place when it changes a review decision, closes a known evidence gap, or supports a repeatable comparison. If nobody can name the question it answers, leave it out until that question exists.
Four Kinds of Data to Defer or Reject
The problem is not that indicators, news, timeframes, or notes are always useless. The problem is collecting unbounded detail without definitions or a review plan.
- Unversioned indicator snapshots. “RSI 32” is weak evidence without symbol, timeframe, calculation settings, timestamp, and a rule that used it.
- Narrative market hindsight. A post-trade explanation of why the market moved is not decision-time evidence. Store later commentary separately.
- Duplicate units without authority. Pips, ticks, dollars, and R can coexist, but one source value and conversion method must remain authoritative.
- Free-form tag explosions. Near-duplicate labels such as “FOMO,” “fear of missing,” and “chased” fracture comparisons unless normalized under controlled definitions.
Multi-timeframe notes can matter when the plan explicitly requires higher-timeframe permission and a lower-timeframe trigger. News context can matter for an event strategy or a no-trade window. Capture them because the plan uses them—not because a large journal looks sophisticated.
A Worked Example Without Invented Performance
Suppose an imported trade contains an account and source ID, instrument, direction, timestamps, fills, quantity, native-currency P&L, and recorded fees. The trader also attached the active setup version, planned stop, reason, screenshot, and an adherence review. The record may support conclusions such as:
- the execution matches the venue record;
- the trade belonged to the declared setup version;
- the actual entry occurred after the permitted trigger;
- the recorded fee is included in net performance;
- the screenshot preserves the stated visual context.
It still does not prove that the trader's reported state caused the outcome, that the setup has an edge, or that one rule change will improve future returns. Those claims require a defined comparison, adequate coverage, and later evidence. The trade-review workflow turns the record into a bounded decision without promoting a single example into a universal lesson.
What to Track by Trading Style
The execution spine stays stable. The optional fields change with the decisions and constraints of the strategy.
Scalping
Prioritize precise timestamps, fill sequence, fees, slippage evidence, and session. Small timing and cost differences can dominate the review question.
Day trading
Prioritize session boundary, setup version, decision screenshot, and active no-trade conditions. Intraday permission and sequence need a reconstructable clock.
Swing trading
Prioritize original thesis, invalidation, overnight costs, adjustments, and partial exits. The plan can drift during a longer holding period.
Prop trading
Prioritize exact program, account size, rule snapshot, daily/max-loss authority, and breach distance. Eligibility depends on the precise program and effective rules, not the firm name alone.
Crypto
Prioritize exchange, market type, fee asset, funding, position mode, and transaction/fill identity. Venue and instrument structure affect both reconciliation and net result.
For a prop account, connect the record to the exact program and verified rule state; the prop-rule tracking guide explains why firm-level labels are not enough. This educational page does not need a firm/program card because no particular provider participates in the decision.
How TSB Turns Fields Into Decisions
Trader’s Second Brain separates source evidence from interpretation. Journal stores imported or entered trade facts, source identity, account context, notes, review fields, screenshots, and evidence debt. Trading Plan supplies dated setup and risk authority. Deterministic analytics calculate performance and comparisons with explicit scope; the review layer can keep a trade as needs attention when account, currency, instrument, direction, timestamps, duplicate state, import mapping, or other required evidence is unresolved.
Coach is the high-leverage reasoning layer after that evidence exists. It can connect the selected plan, authoritative metrics, supporting trades, missing-field coverage, and a next action into a clear explanation. Its refusal to fabricate psychology, causality, missing facts, or recalculated metrics makes the conclusion more useful: the reader can see what supports it, what remains unknown, and what evidence would change it.
TSB has processed 600K+ imported trades across its import history, and its canonical registry recognizes 328 exact broker, exchange, platform, and prop-export profiles. Those figures mean imported trades and recognized source routes—not users, guaranteed compatibility, or trades analyzed by Coach.
Audit your journal evidence Import authoritative trade records Ask Coach what the evidence supports
Sources and Evidence Boundary
The execution-field rationale was checked against the current TSB export schema and Journal evidence contract on September 10, 2026. As an external primary-source cross-check, FINRA's trade-confirmation guidance names transaction date, price, quantity, and fee review, while Investor.gov's account-statement guide recommends reconciling transaction details and costs with confirmations. These sources support recordkeeping and reconciliation—not the earlier page's unsupported performance, dropout, psychology, or universal sample-size claims.
The Bottom Line
Begin with five auditable records: account/source identity, instrument/direction, timestamps, fills/size, and result/currency/costs. Add the plan-facing five so the trade can be judged against the rules that actually applied. Add the analytical five only for named questions with stable definitions. A good journal is not the one with the most columns; it is the one that preserves authority, exposes missing evidence, and gives the next review enough truth to make one defensible decision.
Disclosure: Trader’s Second Brain is our product. Journal fields, evidence-debt behavior, Trading Plan authority, Coach boundaries, and canonical public-truth values were checked against the local codebase on September 10, 2026. This guide is educational and does not provide investment advice or promise that tracking a particular field will improve returns. See our editorial methodology.
