Options Wheel Strategy Journal Template
Last verified: 2026-07-12 PDT
The wheel strategy sounds simple until the recordkeeping gets messy. This page gives traders a process journal for cash-secured puts, assignment, covered calls, premium, concentration, and follow-up rules without treating the strategy as automatically safe or suitable.
This page is educational only. It is not personalized money guidance, tax guidance, a recommendation to use any strategy, or a recommendation to open, close, increase, reduce, or hold any position.
The simple idea
The simple idea is to journal the obligation before journaling the premium. A wheel note should show cash reserved, assignment exposure, share concentration, covered-call tradeoffs, and the rule for what happens if the stock moves sharply.
A useful review does five jobs:
- ▸Names the source record behind the number.
- ▸Separates fixed obligations from flexible capital.
- ▸Marks timing risk, deadline risk, or expiration risk.
- ▸Writes the user-defined rule before the outcome gets emotional.
- ▸Sets the next review date so the decision can be audited later.
The core checklist
Use this checklist before changing contribution rules, opening a new options cycle, raising risk, or redirecting cash:
- ▸Write the trigger for the review.
- ▸Capture the source record: statement, paystub, bill, broker record, plan document, contract, or account history.
- ▸Separate reserves, near-term obligations, long-term contributions, and discretionary research capital.
- ▸Mark source-sensitive details as needs review when they depend on taxes, broker treatment, account rules, healthcare documents, or household-specific terms.
- ▸Define the user-controlled action that happens now.
- ▸Define the condition that would pause, reduce, restart, or review the rule.
- ▸Save the note before judging the market outcome.
Example
Assume a user sells one cash-secured put with a $45 strike. The reserved cash exposure is $4,500 before fees and broker-specific details. If assigned, the next covered call note should not only list the premium collected. It should also show cost basis records, concentration as a percentage of the portfolio, assignment comfort, and the next review rule. If the position becomes 22% of the portfolio, the journal should flag concentration before a new option is opened.
The important part is not copying the numbers. The important part is making the workflow reviewable. A future review should see what was known, what was verified, what was assumed, and what still needed a source check.
A practical scoring model
Give the decision a ten-point process score:
| Review item | Question | Score |
|---|---|---|
| Source clarity | Is there a record behind the number? | 0-2 |
| Timing clarity | Is the deadline, expiration, bill date, or review date visible? | 0-2 |
| Cash clarity | Are reserves and known obligations separated from flexible capital? | 0-2 |
| Rule clarity | Was the rule written before the outcome became emotional? | 0-2 |
| Follow-up clarity | Is the next review action obvious? | 0-2 |
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 reviewing only the outcome. A clean process can still meet a bad market, an unexpected bill, or a rough timing window. A messy process can also get lucky.
The second mistake is treating estimates like verified facts. If a number depends on tax treatment, plan documents, broker rules, healthcare records, cost basis, account limits, or household obligations, label the uncertainty instead of turning it into a universal rule.
The third mistake is changing the plan while excited, annoyed, 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
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.