Vertical Spread Expiration Week Review

Vertical Spread Expiration Week Review is a written way to slow down a money or trading decision before facts, risk, and emotion get mixed together. The point is not to copy someone else’s allocation, option structure, contribution amount, or trade rule. The point is to make your own rule visible enough to review later.

This page is educational only. It is not personalized money guidance, tax guidance, legal guidance, or a recommendation to open, close, increase, reduce, or hold any position.

The simple idea

The simple idea is to separate verified records from reactions. For this workflow, the key inputs are spread type, long strike, short strike, expiration date, net debit or credit, current mark, bid-ask width, assignment-sensitive leg, liquidity notes, max risk, max reward, planned exit gate, and next review time. If those inputs live in different statements, broker screens, paystubs, invoices, policy notices, calendars, apps, portals, option chains, or memory, the decision becomes hard to audit. If they are written down, you can review the process instead of only judging the result.

A useful review does five jobs:

1. ▸Names the exact trigger for the review.
2. ▸Captures the source record behind every important number.
3. ▸Separates money or risk that already has a job from money or risk still available for user-directed decisions.
4. ▸Writes the rule before the outcome becomes emotional.
5. ▸Sets a follow-up date so the decision can be checked later.

The core checklist

Use this checklist before changing the plan:

1. ▸Write the trigger in one sentence.
2. ▸List the source records: statement, paystub, invoice, broker ticket, option chain snapshot, bill, quote, account screen, calendar date, or journal note.
3. ▸Mark which numbers are verified and which numbers are estimates.
4. ▸Separate fixed obligations from flexible capital or flexible risk.
5. ▸Define the user-directed action that happens now.
6. ▸Define the condition that would pause, reduce, restart, exit, or review the rule.
7. ▸Save the note before the outcome turns the decision into a story.

Example

Assume a defined-risk vertical spread is close to expiration. The position may look simple on a payoff diagram, but expiration week adds moving parts: bid-ask spreads can widen, the short leg may become assignment-sensitive, and the mark can move quickly near the strikes. The review does not tell anyone to hold or exit. It records the structure, the spread width, the breakeven area, the liquidity, and the user-defined action gates before the clock gets emotional.

The important part is not copying the numbers. The important part is preserving the reasoning. A future review should show what was known, what was verified, what was assumed, and which items still needed a source check.

A practical scoring model

Give the decision a ten-point process score:

A low score does not prove the decision was bad. It means the record is thin. Fix the record before rewriting the whole plan.

Common mistakes

The first mistake is treating estimates like verified facts. If a number depends on taxes, broker handling, employer records, account rules, option assignment, margin treatment, household bills, debt terms, policy terms, provider bills, client payments, contractor quotes, or legal documents, label it as source-sensitive and verify it from the official record or an appropriate professional.

The second mistake is reviewing only the result. Clean process can still meet rough timing, a surprise bill, a volatility shift, or a structure that behaves differently than expected. Weak process can also get lucky.

The third mistake is changing the plan while excited, annoyed, embarrassed, tired, or trying to make up for a prior decision. Review gates exist because emotional windows make weak process feel urgent.

How Bucko fits

Bucko fits this workflow as an educational research, journaling, guardrail, scenario-analysis, and review workspace. The user defines the rule. Bucko can help organize the note, preserve the source trail, tag the review reason, and make follow-up dates visible.

That framing matters. Bucko should be used to make user-directed decisions more reviewable, not as a promise engine, managed account substitute, or signal service.

Internal links to build the system

• ▸Option Spread Exit Checklist
• ▸Options Breakeven Review Checklist
• ▸Time in Force Orders Explained

Practical takeaway

A clean plan is not a plan that never changes. A clean plan is one that explains why it changed. Write the source, the constraint, the rule, the unknowns, and the next review date before the decision turns into a memory test.