What goes on a founder's weekly planning template?
A founder weekly planner needs seven specific fields, in the same order every week, because the fields are how you force yourself to make the decisions a week needs before it starts. Most templates online include three or four of these and skip the rest, which is why they collapse by week three. The seven that actually hold a week together are: a three-priority anchor, an owner per priority, a "what will exist by Friday" definition of done, a reactive-work budget in hours, a carryover review of last week, the weekly numbers being tracked, and the one thing that, if it shifted this week, would change everything. The list below walks through each one with the prompts I use to fill them out, the trap most founders fall into, and what each field is actually for.
If you want the strategic framing first, the paired essay How to Plan Your Week as a Service Business Owner (The Founder Weekly Planner That Actually Works) sets up why this specific shape matters and how it sits inside a wider operating rhythm. The list here is the practical version, field by field.
1. The three-priority anchor
Three priorities, never more, never tiered. The trap is wanting to write five because everything feels important, but five priorities means none of them are. The prompt I use is "what are the three things that, if they happened this week, would make this a successful week regardless of what else did or didn't get done". Notice the framing isn't "what's on my plate", it's "what would make this week count". If a priority doesn't pass that test, it's a task, not a priority, and it goes elsewhere.
2. The owner per priority
Even if the owner is just you, even if you're a solo founder with no team, you write your name next to each priority. The reason this matters more than people think is that an unassigned priority is a wish. Once your name is on it, you've made a small private commitment, and that commitment catches you on Wednesday afternoon when you're tempted to deprioritise it for something easier. If you do have a team, this is also where delegation gets clean, because the owner is named on the planner, not assumed.
3. The "what will exist by Friday" definition of done
For each priority, you write what will physically exist at the end of the week if the priority worked. Not "make progress on offer redesign", that's a vague intent. "Revised three-tier offer document drafted, shared with two trusted clients for feedback by Friday" is a definition of done. You'll know it's right if you could read it on Monday and on Friday and have no doubt whether the thing happened. This field alone catches more drift than any other, because vague intent is the single biggest reason weeks blur together.
Subscribe to the Founder Essays for the next ones in your inbox each Tuesday.
4. The reactive-work budget in hours
How many hours this week are you willing to spend on email, Slack, ad-hoc client requests, and tickets that didn't exist on Monday morning? Most founders won't answer this until they have to. The truth is that reactive work eats every other budget if you don't budget it. A reasonable starting point in the messy middle is 10 to 15 hours a week. If you need 25 to keep the business alive, that's data, and it's pointing at a delegation gap, which I wrote about in You're Not Stuck, You're the Bottleneck: How to Scale a Service Business Without Working More.
5. The carryover review
Five minutes at the start of the planning session, looking at last week's planner. What got done, what didn't, what slipped to this week, and crucially, what's slipped for three weeks running. The same priority slipping three weeks in a row is signal, not noise. It usually means the priority is wrong, the definition of done was unclear, or there's a real blocker you haven't named. Most planners skip this field, and that's why the same things slip month after month without anyone noticing the pattern.
6. The weekly numbers
One or two quantitative numbers you're tracking this week. Not all your business numbers, just the leading indicators tied to the three priorities. If the priority is offer redesign, the number might be "client conversations had". If it's pipeline, the number might be "qualified calls booked". The number is there to tell you whether the priority is actually moving, not just whether you're busy. If you can't think of a number that maps to the priority, the priority is probably too vague to act on.
7. The one thing that'd change everything
A single line at the bottom: if this thing actually shifted this week, what would change about the next quarter? Most weeks you won't get to this. It doesn't matter. The act of writing it forces you to keep the bigger lever in view, and every few weeks you'll catch a window to actually move it. Without this field, the bigger lever quietly disappears under the weight of operating work, and the year drifts.
The pattern across all seven fields is the same. They aren't a to-do list, they're a thinking surface. The planner makes you decide before the week starts, instead of reacting once it does. That's the entire shift. If you've tried weekly templates that didn't survive past three weeks, the missing piece is almost always one of fields 3, 4, or 7, the three most founders skip.
Access Inner North OS to get the founder weekly planner, set up in your member area and mirrored as a Notion template if you prefer working there, the operating rhythm it sits inside, and the seven other modules that make up the full system.
%20(1).png)
%20(1200%20x%20800%20px)%20(3).png)

.png)
.png)