The minimum fields every journal entry should include
Start with fields that support review quality. If a field will not help you improve a future decision, keep it optional.
| Category | What to record | Why it matters |
|---|---|---|
| Position details | Ticker, strategy, strike, expiry, contracts, entry date | Lets you segment results by setup and instrument. |
| Execution context | Entry price, commissions/fees, order type, fill notes | Separates idea quality from execution quality. |
| Risk plan | Defined risk, max loss assumption, sizing logic, exit plan | Makes risk discipline reviewable after the trade. |
| Thesis | Why you entered, what would confirm/invalidate the trade | Prevents hindsight bias during review. |
| Outcome | Exit date, exit price, result, notes on deviations | Ties process to outcomes without hiding mistakes. |
Track decisions in a review cadence, not just one-off entries
A journal becomes more valuable when it supports recurring review. Use a weekly review to look for repeated mistakes, strong setups, and process drift.
Use the weekly review checklist alongside this page so your journal data turns into action items.
Common journaling mistakes to avoid
- Recording only P&L and omitting thesis or risk assumptions.
- Using inconsistent tag names, which makes filtering unreliable.
- Writing notes after the trade closes, which introduces hindsight bias.
- Skipping losing trades because they are uncomfortable to review.
Next guides
Once your journal fields are defined, move to how to track options trades consistently and then add structure with tags and notes.
FAQ
Do I need a long note for every trade?
No. A short, consistent note with entry thesis, risk trigger, and exit condition is usually better than a long note written inconsistently.
Should I track greeks and fundamentals for every trade?
Track the metrics that are relevant to your process. The goal is repeatable review, not maximum data collection.