How to Plan Your Week
The Weekly Planning Loop is a seven-step review that closes the prior week, scans constraints, selects one major output, allocates maintenance, protects capacity, identifies risks, and prepares Monday’s first action.
Weekly planning connects strategy to a finite calendar. It prevents every active project from demanding foreground attention at the same time.
How the Weekly Planning Loop Works
Step 1: Close completed, partial, and abandoned loops from the prior week
Close completed, partial, and abandoned loops from the prior week.
Completion evidence: Record the observable result before moving to the next step. If the step cannot be observed, rewrite it as a physical action or concrete decision.
Step 2: Scan deadlines, meetings, travel, and personal obligations
Scan deadlines, meetings, travel, and personal obligations.
Completion evidence: Record the observable result before moving to the next step. If the step cannot be observed, rewrite it as a physical action or concrete decision.
Step 3: Choose one major output that deserves foreground energy
Choose one major output that deserves foreground energy.
Completion evidence: Record the observable result before moving to the next step. If the step cannot be observed, rewrite it as a physical action or concrete decision.
Step 4: Assign maintenance floors to other responsibilities
Assign maintenance floors to other responsibilities.
Completion evidence: Record the observable result before moving to the next step. If the step cannot be observed, rewrite it as a physical action or concrete decision.
Step 5: Reserve recovery and administrative space
Reserve recovery and administrative space.
Completion evidence: Record the observable result before moving to the next step. If the step cannot be observed, rewrite it as a physical action or concrete decision.
Step 6: Identify the most likely derailment and prewrite a response
Identify the most likely derailment and prewrite a response.
Completion evidence: Record the observable result before moving to the next step. If the step cannot be observed, rewrite it as a physical action or concrete decision.
Step 7: Prepare the first action and materials for the week
Prepare the first action and materials for the week.
Completion evidence: Record the observable result before moving to the next step. If the step cannot be observed, rewrite it as a physical action or concrete decision.
Weekly Planning Board
| Area | Decision |
|---|---|
| Foreground output | The one result the week should produce |
| Fixed constraints | Calendar and deadlines |
| Maintenance floors | Minimum obligations that prevent collapse |
| Recovery space | Unassigned capacity for real disruption |
| Risk | Most likely derailment |
| Response rule | What happens if the risk occurs |
| Monday launch | First physical action |
Why This Framework Works
The framework reduces hidden decisions and turns an abstract goal into observable actions, evidence, and review. It also makes failure diagnosable: the reader can see whether the problem was task clarity, capacity, environment, timing, authority, or the absence of a recovery rule.
Use the framework as a bounded experiment. Keep the first version small enough to run under ordinary conditions, record what actually happened, and change one operating variable at a time instead of replacing the entire system.
Implementation Notes for Weekly Planning Loop
Checkpoint 1
Close completed, partial, and abandoned loops from the prior week. Before acting, write the current constraint and the smallest observable result this checkpoint should create.
Run this checkpoint in one bounded context, then record what changed. When the result is incomplete, preserve the last known state and choose the smallest valid restart instead of expanding the plan.
Checkpoint 2
Scan deadlines, meetings, travel, and personal obligations. Before acting, write the current constraint and the smallest observable result this checkpoint should create.
Run this checkpoint in one bounded context, then record what changed. When the result is incomplete, preserve the last known state and choose the smallest valid restart instead of expanding the plan.
Checkpoint 3
Choose one major output that deserves foreground energy. Before acting, write the current constraint and the smallest observable result this checkpoint should create.
Run this checkpoint in one bounded context, then record what changed. When the result is incomplete, preserve the last known state and choose the smallest valid restart instead of expanding the plan.
Checkpoint 4
Assign maintenance floors to other responsibilities. Before acting, write the current constraint and the smallest observable result this checkpoint should create.
Run this checkpoint in one bounded context, then record what changed. When the result is incomplete, preserve the last known state and choose the smallest valid restart instead of expanding the plan.
Checkpoint 5
Reserve recovery and administrative space. Before acting, write the current constraint and the smallest observable result this checkpoint should create.
Run this checkpoint in one bounded context, then record what changed. When the result is incomplete, preserve the last known state and choose the smallest valid restart instead of expanding the plan.
Checkpoint 6
Identify the most likely derailment and prewrite a response. Before acting, write the current constraint and the smallest observable result this checkpoint should create.
Run this checkpoint in one bounded context, then record what changed. When the result is incomplete, preserve the last known state and choose the smallest valid restart instead of expanding the plan.
Checkpoint 7
Prepare the first action and materials for the week. Before acting, write the current constraint and the smallest observable result this checkpoint should create.
Run this checkpoint in one bounded context, then record what changed. When the result is incomplete, preserve the last known state and choose the smallest valid restart instead of expanding the plan.
Common Failure Modes
Failure Mode 1: Selecting several foreground priorities.
Use the framework to identify the failed condition and return to the smallest action that restores evidence. Do not interpret the failure as a permanent identity judgment.
Failure Mode 2: Planning from goals without checking the calendar.
Use the framework to identify the failed condition and return to the smallest action that restores evidence. Do not interpret the failure as a permanent identity judgment.
Failure Mode 3: Using Sunday night to create an unrealistic rescue week.
Use the framework to identify the failed condition and return to the smallest action that restores evidence. Do not interpret the failure as a permanent identity judgment.
Worked Example: Founder balancing fundraising and product
The week chooses a completed investor data room as the foreground output. Product work remains at a defined maintenance floor, customer support is batched, and Friday afternoon remains open for displaced work or recovery.
What to measure: Did the framework produce a clearer decision, a completed action, a shorter recovery time, or a better handoff? Record the observable outcome rather than whether the process felt impressive.
When to Use Another Kind of Support
- The weekly plan is a resource-allocation decision, not a moral scorecard.
- Unplanned urgent events may require explicit tradeoffs.
Use the system as an execution and review layer, not as a substitute for professional judgment.
Frequently Asked Questions
What should I do first?
Use the smallest step in the framework that produces new evidence or restores motion. Do not begin by redesigning the entire system.
What if the framework fails on a difficult day?
Use the minimum valid version, record where the breakdown occurred, and change one constraint at the next review. Do not create catch-up punishment.
Does this framework guarantee an outcome?
No. It creates a clearer process and evidence loop, but results depend on context, execution, resources, and decisions outside the framework.
Related search intents
These are closely related phrasings and adjacent decisions supported by this page and its cluster.
Close variants
- How to Plan Your Week
- How to Plan Your Week guide
- How to Plan Your Week framework
- How to Plan Your Week checklist
- How to Plan Your Week for executives
- How to Plan Your Week with AI
This is one of the frameworks inside the Billionaire High Performance Coach system — a structured executive OS for using ChatGPT as your accountability and decision partner.
Editorial Method
This page was built from an approved query specification, assigned one primary intent, checked against existing query owners, and required to contain a page-specific framework and usable artifact. It is reviewed for visible-content and structured-data parity before publication.
Health-adjacent pages receive an additional non-diagnostic review. Product comparisons rely on current official product information where available and do not claim first-person testing unless such testing is documented.