Most trading journals were built for stocks and futures, then bolted on an "options" mode that's really just a stock log with strike and expiration appended. That misses everything that makes options different.
The fields a real options log needs
- Strategy structure. Long call, vertical, iron condor, calendar — strategy drives every other field's interpretation.
- Strike(s) and expiration. One row per leg; link by parent trade ID.
- IV at entry (per leg and underlying IV rank). A vertical opened at IV rank 80 is a fundamentally different trade than the same vertical at IV rank 15.
- Delta at entry. Your real directional exposure, not the strikes you picked.
- Theta and vega at entry. Tells you what's actually paying you (decay) and what's risking you (vol expansion).
- Days to expiration (DTE). Bucket your trades — 0-7 DTE behaves nothing like 30-45 DTE.
- Credit received / debit paid. Not net P&L. The opening number defines max loss math.
Why R-multiple needs a tweak for options
For a defined-risk credit spread, 1R is the spread width minus credit received. For naked options, 1R is your mental stop on premium, not the theoretical max loss. Pick a convention and never mix them in one analytics view — that's how option traders get phantom edge.
The setup tags that matter
Forget "bullish/bearish" — too coarse. Real tags: IV crush play, earnings straddle, theta harvest 30-45 DTE, gamma scalp 0DTE, vega long pre-FOMC. Now your journal analytics can tell you which of those actually pay.
Review by expiration cycle, not by week
Theta works on a clock you didn't choose. Reviewing trades by calendar week mixes apples and oranges. Group closed trades by entry DTE bucket and by IV rank bucket — that's where the real expectancy lives.
The one chart that matters
P&L vs IV rank at entry. If your iron condors only print when IV rank > 50, that's not opinion — that's your edge condition. Most journals can't draw this chart. Yours should.
Stocks log price. Options log risk. The journal has to know the difference.