Why iron condors need their own journal structure
Condors are easy to flatten into one premium number and one final result, but that loses the core reason the trade exists. You need to know the short strikes, long strikes, wing width, expected range, event risk, and what made the position attractive at entry. Without that context, a later review cannot tell whether the structure matched the setup or whether it was just the easiest defined-risk trade available.
The better approach is to keep the condor together as one position while still preserving leg-level execution detail. That makes the spread trading journal guide, the implied volatility checklist, and the performance review process much more useful because the range thesis and management path remain visible.
Core iron condor journal fields
| Field group | What to capture | Why it matters |
|---|---|---|
| Structure | Short call strike, long call strike, short put strike, long put strike, expiry, wing width | Keeps each condor comparable instead of reducing the trade to one credit figure. |
| Entry context | Underlying price, expected range, volatility note, catalyst or earnings note, liquidity note | Shows why a range-based trade was chosen for this setup. |
| Risk plan | Net credit, max risk, size, planned profit-taking level, max loss or adjustment trigger | Preserves the written plan before price pressure changes the decision quality. |
| Management state | Threatened side, tested strike, roll or close decision, time-left note, reason for each change | Separates setup quality from the choices made after the condor was challenged. |
| Range thesis | What price action would confirm the condor, what would break it, and when you would stop defending it | Prevents vague reviews where every condor looks acceptable after the fact. |
| Review summary | Outcome versus plan, process score, one lesson, and one rule to keep or change | Turns the trade into a repeatable review input instead of a one-off premium collection note. |
How to log an iron condor as one position
- Write the range thesis before entry. Use the trade plan template and risk plan checklist to define the expected range, the key break levels, and what would force an early exit.
- Record the full structure, not just the net credit. The journal should show both short strikes, both long strikes, and wing width so you can compare condors with similar shape later.
- Keep one shared condor tag. A tag such as
iron-condorplus a ticker or cycle ID makes later adjustments easier to connect during weekly review. - Log each state change when one side is threatened. If you narrow risk, roll one side, or close the trade early, use the trade adjustment checklist or roll decision checklist to record what changed and why.
- Close with one structure-level lesson. The final note should say whether the condor fit the volatility environment, whether the management plan stayed disciplined, and what you would repeat or avoid next time.
Weekly review questions for condors
- Did the condor match the expected range and volatility environment at entry?
- Was the tested side identified early, or did the first real note arrive only after the trade became stressful?
- Did the adjustment improve the position, or only postpone taking the original loss or smaller win?
- Were earnings, macro events, or other catalysts written down before the trade was opened or defended?
- What one rule should change before the next range-bound setup?
These questions work best with the tags and notes guide, the trade review scorecard, and the weekly review checklist so condors stay comparable across similar environments.
Common iron condor journaling mistakes
- Logging only the net credit and expiry while skipping the exact wing structure.
- Reviewing each threatened side separately and losing the original range thesis.
- Adjusting the condor without recording how the range, risk, or expected outcome changed.
- Ignoring volatility or event context even though condors are highly sensitive to both.
Related guides
Use this guide with the spread trading journal guide, the implied volatility checklist, the trade management checklist, the roll decision checklist, and the performance review guide.
FAQ
What fields matter most in an iron condor journal?
Track the short strikes, long strikes, wing width, net credit, expiry, planned exit trigger, volatility context, and one short note about why the condor fit the setup.
Should each side of the iron condor be reviewed separately?
Execution details can stay leg-specific, but the review should keep the condor together as one range-based risk decision so adjustments and outcomes are judged in the original structure.
How should condor adjustments be recorded?
Record what side changed, why the adjustment happened, how the risk or range changed, and what condition would make the new structure wrong so later review reflects the real management path.