Options Trade Tracking: Journaling for Premium Sellers and Buyers

A stock or futures trade has two events that matter — entry and exit — and one number that drives outcome (price). An options trade has more of everything:

• Multi-leg structures. A single iron condor is FOUR fills (sell call, buy call, sell put, buy put). Most journals show that as four separate trades. Useful analytics requires aggregating them into one position.
• IV environment matters as much as direction. The same SPY 450 call bought at IV rank 20 vs. IV rank 80 is essentially a different trade. Without logging IV at entry, you can't separate "I picked the right direction" from "I overpaid for premium."
• Time decay. A trade held 3 days vs. 30 days has different theta exposure. The framework you used to enter (defined-risk vs. undefined-risk, theta-positive vs. theta-negative) should be tagged so you can review what worked.
• Defined vs. undefined risk changes the R-multiple math. A long call has a clear max loss (premium paid). A naked short put doesn't — most traders cap defined R at 2× credit received and exit there.
• Assignment risk on short options is a separate dimension entirely — was your short put assigned over weekend earnings? That's a journal-worthy event independent of the P&L.

The core trade data (symbol, entry/exit times, prices, P&L) is the easy part — your broker exports it. The fields that actually surface options edge are the ones you ADD on top:

Strategy / structure tag

Long call, long put, short call, short put, vertical (debit/credit), iron condor, iron butterfly, calendar, diagonal, straddle, strangle, ratio spread, custom multi-leg. Without this tag, you can't compute per-strategy expectancy. The single most useful field for options journaling.

IV rank / IV percentile at entry

IV rank tells you how high current IV is relative to the past year. Above 50 favors premium-selling strategies (credit spreads, iron condors); below 30 favors premium-buying (long options, debit spreads). Logging IV rank lets you build a per-strategy expectancy table by IV bucket — most traders discover their iron condors only work above IVR 40, and their long calls only work below IVR 25.

Days to expiration (DTE) at entry and exit

Theta exposure and gamma risk both scale with DTE. A short put opened at 45 DTE behaves differently from one opened at 7 DTE. Track both DTE at open and DTE at close — and the difference between them tells you how long the trade actually held vs. your plan.

Delta at entry

Delta tells you the directional risk per leg and approximate probability of expiring ITM. For premium sellers, "30 delta short put" is a strategy; "5 delta short put" is a different strategy. Tagging delta at entry lets you analyze your win rate by delta bucket.

Defined max loss (the risk denominator for R)

For defined-risk trades, this is straightforward — the spread width minus credit, or the long premium paid. For undefined-risk trades, you need to commit to a stop loss in dollars (commonly 2× credit received for short premium). Without this, R-multiple is uncomputable for the trade.

Underlying setup / thesis

Why this trade? "Earnings IV crush play," "post-Fed mean reversion," "long-term directional bet on TSLA," "high-IV premium dump." The setup tag is what lets you cluster trades by reason later — useful enough that it's worth even a 5-second tap to log.

Plan: max profit and exit trigger

For credit spreads: "exit at 50% of max profit" is the standard tasty/wheel-style trade plan. For long premium: "exit at 100% of premium paid." Logging the planned exit lets you measure plan adherence — a separate axis of skill from P&L outcome.

tastytrade (formerly tastyworks)

Account → History → Export. Choose CSV. Tastytrade's CSV is well-structured — each fill is a row with symbol, expiry, strike, action, price, quantity, fees. TradersForge's tastytrade adapter automatically groups multi-leg fills opened in the same order ticket into a single position. For tastytrade-style traders running 30+ trades a week across spreads and iron condors, this aggregation is the difference between usable analytics and chaos.

thinkorswim (TOS)

Monitor → Account Statement → set date range → Export to file. TOS exports a more complex statement that includes trade history, dividend events, and money movement. TradersForge's thinkorswim adapter parses the trade history section and ignores the rest. Multi-leg strategies submitted as a single TOS combo order are recognized and grouped.

Interactive Brokers (IBKR)

Reports → Flex Queries → create a Trades query → run for date range → export CSV. IBKR's Flex Queries are powerful but unfriendly to set up first time. For options traders, request the "Open/Close Indicator" and "Order ID" fields specifically — they're what enables multi-leg grouping. TradersForge's IBKR adapter has a sample Flex Query template documented on the import page.

Schwab (TOS-integrated, post-TDA migration)

Trade History → Export. The Schwab format is similar to TOS but with some field renaming after the migration. TradersForge's Schwab adapter handles both pre- and post-migration formats; if you have older TDA exports, they import alongside newer Schwab exports.

Webull, TradeStation, E*TRADE

All three offer trade history CSV exports from their respective web platforms. Adapters exist for each; the workflow is identical to the others — find the trade history export, choose date range, drop the file into TradersForge's import page.

A vertical credit spread has two legs. An iron condor has four. A jade lizard has three. Calendars, diagonals, ratio spreads — all multi-leg. The journaling question is: how do you track these so analytics make sense?

Why one-trade-per-leg is wrong

If your iron condor shows up as 4 separate trades in the journal, you can't compute condor-level metrics: total credit, max loss, P&L of the structure, expectancy by structure type. You see only leg-level numbers, which are meaningless out of context. "I had a 65% win rate on individual options" tells you nothing about whether your iron condors made money.

How TradersForge groups multi-leg fills

On import, fills sharing an order ID (or executed within a short window for brokers that don't expose order IDs) are grouped into one position. The position is tagged with the inferred structure type — vertical, condor, butterfly, etc. — based on leg count, expiries, and strike layout. You can override the auto-detection if needed.

What the consolidated trade view shows

For each multi-leg position: structure type, total credit/debit at entry, max profit potential, max loss (defined risk), per-leg breakdown, P&L over time as legs close, current Greeks (if live API is connected). This is the level at which "did this trade work?" can actually be answered.

Closing partial positions

Common scenario: you have an iron condor; one side gets tested; you close the threatened spread and let the other expire. The journal needs to handle this — partial closes attributed to the parent position, with separate P&L per closed leg, and the remaining legs still tracked through expiration. Generic CSV importers without explicit options handling get this wrong almost every time.

Once trades are imported and tagged correctly, the analytics that surface real options edge:

Per-strategy expectancy

Win rate, average win/loss, total P&L, and R-multiple expectancy broken out by strategy tag. Almost every options trader discovers that 1–2 strategies produce the bulk of their P&L and 2–3 strategies are net losers they keep doing out of habit.

IV environment edge

Plot expectancy by IV rank bucket (0-20, 20-40, 40-60, 60-80, 80-100). Premium-selling strategies should show clear positive expectancy at high IV rank and negative or breakeven at low IV rank. If yours don't, you're selling premium at the wrong times.

DTE bucket analysis

Expectancy by entry DTE bucket (0-7, 7-21, 21-45, 45+ days). For most short-premium strategies, the 21-45 DTE bucket is where the math works best (theta acceleration starts, gamma risk still manageable). Validate this empirically against your own trades.

50% / 21 DTE rule adherence

Tasty-style traders typically follow: close credit spreads at 50% of max profit; close (or roll) by 21 DTE regardless. Both rules are testable from your journal. If you have data on trades you closed at 50% vs. trades you held longer, you can see directly whether the early-close discipline produced better risk-adjusted returns for YOUR trading.

Underlying ticker concentration

Most options traders concentrate trade volume in 5-10 tickers. Per-ticker P&L and win rate often show that 1-2 tickers contribute disproportionately (positively or negatively). The "favorite ticker that secretly costs you money" is a depressingly common finding.

Plan adherence

For each trade where you logged a planned exit (target % of max profit, target stop), did you actually exit at the plan? Or hold for more, or panic-close earlier? Plan adherence is a separate skill axis — high adherence with negative expectancy means strategy selection is the problem; low adherence with positive theoretical expectancy means execution is the problem.

Logging only the "interesting" trades

A wheel trader who only logs the spectacular wheel cycle that worked, and ignores the 30 boring credit spreads they wrote that month, has biased their data toward survivorship. The boring trades ARE the strategy. Log everything.

Ignoring expired-worthless trades

A short option that expires worthless is your full credit captured — that's a winning trade. But because no closing transaction occurred, some journals don't see it as a trade. Make sure expirations are imported as closing events, or your win rate will look terrible.

Mixing assignments into the trade P&L

A short put assigned at 5DTE turns into a 100-share long stock position. The options trade is closed (assignment); the stock trade is now a separate position. Most brokers split this correctly in their CSV, but some don't — verify the assignment shows up as a P&L event on the option, not as a $0 trade with a mystery stock position appearing later.

Not logging IV rank

IV rank at entry is the single field that separates good options journaling from generic stock-style journaling. If your broker export doesn't include it (most don't), you have to add it manually at entry — or your analytics will be missing the most useful axis options trading has.

Treating profitable assignments as failures

A short put at the 30 delta on a stock you wanted to own is a successful trade if you get assigned at a price you're happy to own — that was the plan. Tag your wheel trades and cash-secured puts with the actual intent so the assignment doesn't register as a "loss" in your stats.