Templates · Personal
Weekly planning template
Review last week and plan the next
Start with this template →Sign in
Opens on reph with the template ready to start. No account needed; sign in to keep your document.
Filled example
The template filled in for a made-up company, so you can see what good looks like.
Week of 20 October: hiring plan and offsite
Week of: 20 October 2026
Last week review
- Wins: Shipped the Fernhill onboarding checklist and the support team adopted it the same day. Protecting mornings worked: four of five mornings had no meetings, which is where most of the 14 focus hours came from.
- Misses: The Q4 hiring plan outline slipped again. It keeps losing to urgent requests because I never gave it a calendar slot. Thursday afternoon was lost to back-to-back calls.
Priorities this week
- Q4 hiring plan outline to Leo by Wednesday noon (blocked out Monday and Tuesday mornings)
- Lisbon offsite: flights booked and agenda draft shared with the team
- Close the Northwind contract, or know exactly what is holding it up
Day-by-day
| Day |
Focus |
Meetings |
| Mon |
Hiring plan: roles and levels |
Standup, 1:1 Sam |
| Tue |
Hiring plan: budget and timeline |
Standup, design review |
| Wed |
Send hiring plan, offsite agenda |
Standup, Leo (plan review) |
| Thu |
Northwind contract follow-up |
Northwind sync, 1:1 Priya |
| Fri |
Inbox zero, weekly review |
Team demo |
Habits tracker
| Habit |
Mon |
Tue |
Wed |
Thu |
Fri |
| Spanish, 30 min |
yes |
yes |
|
|
|
| No Slack before 11:00 |
yes |
|
|
|
|
| Climbing or a run |
|
yes |
|
|
|
Notes
- Finance said offsite approval comes by Thursday; do not book flights before then, the fare difference is small.
- Ask Priya whether she wants to own the onboarding checklist going forward.
- If the hiring plan slips again, the problem is scope, not time: cut it to roles and budget only.
The template
Show the blank template
Weekly planning
Week of: [date]
Last week review
Honest, not performative. The point is to notice patterns, not to feel good.
Priorities this week
Ranked, not a flat list. If everything's #1, nothing is.
Day-by-day
Rough shape, not a minute-by-minute plan, just enough structure to know where the week's time is going.
| Day |
Focus |
Meetings |
| Mon |
|
|
| Tue |
|
|
| Wed |
|
|
| Thu |
|
|
| Fri |
|
|
Habits tracker
Track the handful that actually matter this season. A 20-row tracker gets abandoned by Wednesday.
| Habit |
Mon |
Tue |
Wed |
Thu |
Fri |
|
|
|
|
|
|
Notes
Anything that doesn't fit the structure above but needs to be written down somewhere.
Questions
- Friday or Monday?
- Friday for the review while it is fresh, Monday for the plan if your week changes over the weekend
- How many priorities?
- Three, ranked, the rest belong on your TODO list
- What if I missed everything?
- Write why in Misses, that pattern is what the review is for
Fill it with your agent
Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.
Find my reph doc "Weekly planning" with search_docs, then read it with read_doc. Find my TODO list and recent meeting notes with search_docs and read them, then propose a ranked Priorities list and a Day-by-day focus around the meetings I paste. Fill last week's numbers from what I tell you. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (two priorities competing for one day) with add_comment quoting that section's heading line, then call request_review with a one-line summary.
Related templates
Start with this template →Sign in