Checklist

Options assignment and exercise checklist

Assignment and exercise events can distort your journal if they are logged inconsistently. Use this checklist to capture what happened, why it happened, and what should be reviewed later.

Why this checklist matters

Many journals record assignment events as simple position closes, which can hide the decision context. A consistent checklist helps you separate routine expiry outcomes from process issues that need follow-up.

Assignment and exercise checklist

  1. Event type recorded. Mark whether this was assignment, exercise, or a related close/roll decision.
  2. Contract and timing captured. Log strike, expiry, quantity, and event timestamp.
  3. Trigger context noted. Record whether the event followed your plan, expiry mechanics, or an unplanned situation.
  4. Resulting position documented. Confirm whether shares were delivered/received, position was closed, or risk changed.
  5. Fees and cash impact logged. Capture execution costs and assignment-related cash movement.
  6. Review tag applied. Add a clear tag such as assignment-planned, assignment-unplanned, or exercise-decision.

Suggested journal fields for event logging

FieldWhy it helpsExample
Event typeSeparates assignment and exercise outcomesAssigned short put
Event timestampSupports timeline reconstruction2026-03-01 20:05 UTC
Resulting positionClarifies post-event exposure+100 shares, option closed
Plan adherenceDistinguishes planned vs reactive actionsPlanned at expiry
Follow-up actionDocuments next workflow stepEvaluate covered call entry

How to review these events weekly

During your weekly review, filter assignment and exercise tags separately from normal exits. Then compare whether these events were planned under your risk plan or occurred outside your expected workflow.

Process tip: If an assignment was unplanned, write one concrete process adjustment so the next similar event is handled intentionally.

Pair this checklist with the trade exit checklist, broker import checklist, and performance review guide.

FAQ

Should assignment events use the same exit reason as normal closes?

Use a distinct reason code or tag for assignment/exercise events so reviews can isolate them from discretionary exits.

Do I need extra notes if assignment was expected?

A short note is still useful. It confirms the event followed your plan and preserves context for future comparisons.