Weekly planning
Weekly Planning Template: A Rolling Two-Week Plan for Goals
Use this weekly planning template to turn goals into dated Week 1 commitments and a flexible Week 2 preview without overplanning the future.
Most weekly planning templates are containers: seven day columns, a priority box, a habit tracker, and space for notes. They help organize work that is already clear. They do less when the real problem is deciding which work should move a long-term goal.
The template below starts somewhere else. It uses the goal as the source, turns Week 1 into concrete commitments, and keeps Week 2 deliberately less detailed. This is the rolling two-week planning model we designed for Aimo after finding that long AI-generated plans looked confident long after their assumptions had expired.
You can copy the template into any notes app or document.
Start with one outcome, not the backlog
Do not begin by copying every overdue task into a fresh week. Begin with the outcome you want to move.
Goal
Launch a paid beta by November 30.
Current evidence
Landing page exists. Three people joined the waitlist. Nobody has completed onboarding.
Two-week outcome
Observe five target users attempting onboarding and fix the largest verified blocker.
The current evidence line matters. It prevents the plan from being a motivational rewrite of the goal. The next two weeks should begin from the state that exists now.
Limit Week 1 to real capacity
Before choosing tasks, list fixed constraints:
Available focus blocks: Tuesday 90 min, Thursday 90 min, Saturday 2 hr
Fixed commitments: client deadline Thursday, family plans Sunday
Maximum goal commitments: 3
We use a commitment limit because an unlimited planner quietly assumes unlimited capacity. Three meaningful actions completed are more useful than twelve tasks redistributed every night.
Write Week 1 as dated commitments
Each action needs a date and a completion condition.
| Goal progress | Date | Action | Done when |
|---|---|---|---|
| Recruit testers | Tue | Send seven targeted invitations | Seven matching people receive a message |
| Observe behavior | Thu | Watch two onboarding attempts | Steps, quotes, and drop-off points are recorded |
| Choose the blocker | Sat | Rank observed failures by frequency and severity | One blocker is selected with evidence |
Do not use labels such as work on launch or improve onboarding. They describe an area of responsibility, not a finishable action.
Keep Week 2 as a preview
Week 2 should preserve direction without pretending you already know what Week 1 will teach you.
If invitation response is the main blocker:
Rewrite the invitation and test a narrower audience.
If onboarding completion is the main blocker:
Fix the highest-frequency step and run three more attempts.
If no consistent blocker appears:
Collect five more observations before building.
This conditional preview is different from a second fixed task list. It records the likely branches while leaving the decision open until evidence arrives.
That is why we call it a rolling plan. At the end of Week 1, you convert one branch into commitments and add a new preview week.
Copy this weekly planning template
GOAL
[One outcome and deadline]
CURRENT EVIDENCE
[What is already true? What was completed or missed?]
TWO-WEEK OUTCOME
[What should become observably different?]
CAPACITY
[Available blocks, fixed commitments, maximum actions]
WEEK 1 COMMITMENTS
1. [Date] — [action]
Done when: [observable condition]
2. [Date] — [action]
Done when: [observable condition]
3. [Date] — [action]
Done when: [observable condition]
WEEK 2 PREVIEW
If [evidence A], then [next direction].
If [evidence B], then [next direction].
REVIEW
Completed:
Missed:
What changed:
Decision: keep / change / reduce / extend / stop
Separate goal work from maintenance work
Email, bills, errands, and small fixes are real work. They should not be allowed to impersonate goal progress.
Keep two lists:
Goal commitments
- Tuesday: send seven beta invitations
- Thursday: observe two onboarding attempts
Maintenance
- pay hosting invoice
- reply to support email
- book dentist appointment
This is not a judgment about importance. It keeps the weekly review accurate. A full maintenance list can explain why capacity disappeared, but clearing it does not mean the beta goal moved.
Review the plan with evidence
At the end of the week, compare the plan with what happened.
| Planned | Actual | What it tells you |
|---|---|---|
| Seven invitations | Four sent | The action exceeded the available block |
| Two observations | Two completed | The action size was realistic |
| Choose one blocker | Not started | It depended on notes that were not organized |
Now the next plan can change for a reason. Reduce the invitation batch, preserve the observation format, and add a 20-minute note cleanup before ranking blockers.
If the same goal keeps losing capacity or the date no longer fits, stop editing tasks and use the goal review checklist.
How Aimo applies the template
In Aimo, a goal is structured before its tasks are drafted. The agent proposes the near-term plan, but the user confirms it. Morning and evening Discord check-ins create the completion and missed-task record. The next plan can then use those records rather than restarting from a blank prompt.
The approach also has limits. Aimo cannot know whether a goal is still worth the trade-off, and it should not silently change scope or deadlines. It can make the evidence and options visible; the decision remains with the user.
For the full system around the template, read how to build a goal execution loop.