Open the planning window
Plan owner: ___ Start date: ___ Day 30: ___ Day 60: ___ Day 90: ___ Chosen role from Chapter 6.3: ___ Next scale-review date: ___ Reliable business hours or blocks: ___ Protected life boundary: ___ The question this plan must answer by Day 90: ___
Bring forward the current state
Bring forward the final outputs you will actually use during this planning window. Leave a missing input visible as a dependency rather than rebuilding its rule here. Keep each value’s original unit, period, definition, and date.| Baseline record | Current value and period |
|---|---|
| Resource window (Chapters 1.3 and 1.4) | Reliable hours/blocks ___; knowledge boundary ___; saleable starting stock ___; acquisition budget ___ |
| Inventory thesis (Chapter 3.2) | Primary/supporting lane ___; lane cap ___; cash-conversion window ___; lane-loss limit ___ |
| Offer and cost (Chapters 2.1 and 2.2) | Current offer ceiling/assumptions ___; modeled order revenue ___; inventory cost ___; modeled selling/fulfillment cost ___; modeled contribution ___; input dates ___ |
| Pricing (Chapter 2.4) | Price floor ___; target ___; review and markdown rule ___ |
| Cash (Chapters 5.1 and 5.2) | Latest close ___; cleared cash ___; commitments/protected/deployable cash ___; pending payouts ___ |
| Inventory movement (Chapter 2.3) | Sales/contribution period ___; turns period/result ___; item-age rule/result ___ |
| Operations (Chapters 4.1 through 4.4) | Sourcing targets/acceptance boundary ___; selected venue/test result ___; intake/sale-ready queue ___; oldest sale-readiness age ___; fulfillment method/capacity/incidents ___ |
| Direction (Chapters 5.3 and 6.1 through 6.3) | Measured constraint/response ___; material risk/control/trigger ___; demand result ___; chosen role/blockers ___ |
Choose the active work
Schedule the unresolved decision that matters now and any dependency it genuinely requires. A business still testing its basic offer uses the validation owner first. A mature operation may be testing sourcing, venue, demand, or a diagnosed capacity constraint. Park work whose question, budget, or operating capacity is not yet clear. Complete one record for each active experiment or decision:Owner and question: ___ Baseline: ___ One change being tested: ___ Cash budget: ___ Time budget: ___ Capacity dependency: ___ Outcome measure: ___ Validity rule: ___ Boundary that cannot be crossed: ___ Prewritten result branches: Pause/stop if ___; repair/extend if ___; continue if ___; change ___ if ___. Review owner: ___ Review date: ___
Put the work in dependency order
The rows below are calendar slots, not prescribed phases. Add or remove rows to fit the active work.| Start–end | Action or experiment | Must be true first | Owner and finished-when signal |
|---|---|---|---|
| ___ | ___ | ___ | ___ |
| ___ | ___ | ___ | ___ |
| ___ | ___ | ___ | ___ |
| ___ | ___ | ___ | ___ |
Set the operating rhythm
| Cadence | Work and record | Boundary response |
|---|---|---|
| Inventory blocks: ___ | Receive, decide, make sale-ready/findable; record queue and sale-readiness age | Apply the existing pause/recovery rule; open a bottleneck review if the same queue persists |
| Fulfillment windows: ___ | Perform the chosen handoff; maintain incident and remedy records | Use the written response deadline and authorized remedy |
| Experiment blocks: ___ | Run only the planned change; capture outcome and validity evidence | Apply its budget, boundary, and stop rule |
| Weekly review: ___ | Update the scorecard; make one recorded decision | Assign the next action, owner, and date |
| Monthly close: ___ | Capture, reconcile, resolve differences, and lock/export the period | Hold decisions that require an unresolved record |
| Trigger review: ___ | Apply the capital policy and inspect material risk triggers | Stop adding to the triggered risk and follow its named response |
Keep a small decision scorecard
Use only measures tied to the work and branches in this plan.| Measure and owner | Current value / period | Existing boundary or target | Decision if crossed |
|---|---|---|---|
| ___ | ___ | ___ | ___ |
| ___ | ___ | ___ | ___ |
| ___ | ___ | ___ | ___ |
| ___ | ___ | ___ | ___ |
Commit the branch order
Apply these rules in order at every review:- A hard boundary breach or unresolved required record invokes pause/stop, even when the test is incomplete.
- If no hard boundary was crossed but the test was invalid or incomplete, use repair/extend.
- Only a valid test that stayed within its boundaries can reach continue or change one variable, according to the result written before launch.
Pause/stop: ___ crosses ___, a required record remains unresolved, or ___ occurs. Next action: ___; owner/date: ___. Repair/extend: The validity failure is ___. Repair: ___. New budget: ___. New review date: ___. Continue: The valid result remains within ___ and produces ___. Next action/owner/date: ___. Change one variable: The valid result shows ___. Change ___; hold ___ constant; owner/date: ___.
Record the three decisions
| Review point and date | Evidence and validity | Boundary or assumption that changed | Decision, next action, owner, and date |
|---|---|---|---|
| Day 30: ___ | ___ | ___ | ___ |
| Day 60: ___ | ___ | ___ | ___ |
| Day 90: ___ | ___ | ___ | ___ |