Weekly Team Planning Template
A week's worth of named tasks against named people, sized to who is actually free this week. Not a goal, a to-do list checked against real availability.
Four items, named, against a team that's actually got four slots free this week: not five people minus whoever's on leave.
Why most weekly plans stop being used
A weekly board usually starts strong on Monday morning and is being ignored by Wednesday afternoon. It's not that weekly planning is a bad idea. It's that most versions of it are built on assumptions that stop being true within a day or two of being written.
It's written from memory, against headcount, not availability. Five people on the team doesn't mean five people's worth of work this week: someone's on leave, someone's half-booked in interviews, someone's covering a support rotation. A plan built on headcount rather than actual free hours is wrong before the week even starts. Build the week's column against real, leave-adjusted availability instead, the way this template does, and that particular Tuesday-morning surprise mostly stops happening.
Nothing distinguishes "started" from "will actually finish this week." Without a limit on the in-progress column, everyone pulls a new task the moment the old one gets boring or stuck, and Friday arrives with eight things half-done and nothing shipped clean.
Blockers live in standup and nowhere else. Someone mentions they're stuck, everyone nods along, and by the next standup it's forgotten because it was never written down anywhere durable. It was just spoken once, into a room, and gone.
The week has no connection to anything bigger. Tasks get picked because they're quick or because someone likes them, not because they move a quarterly goal forward, so a busy week and a productive one end up looking identical from the outside.
The structure, and why each part is there
Set against who's actually free this week, leave and half-booked days subtracted first, not against the team's full headcount on the roster.
The moment something stalls it moves here with the reason attached, so it's visible to everyone without anyone needing to remember to bring it up out loud.
Everyone opens to today's items and nothing else. No digging through a shared board to find which cards belong to them this week.
Logging a day's hours takes about five seconds, right where the task is, so the week's actual effort builds itself instead of getting reconstructed on Friday afternoon.
Anything still sitting in "this week" moves into Monday's planning review by name. It doesn't just quietly roll over unexamined into the next list.
Where a task serves a quarterly commitment, the card says so, so the week's list stays connected to why it's on the board at all, not just busywork.
Everything not yet pulled into the week sits here, ordered by priority, so "what's next" is a glance at the top of a column rather than a guess.
How to use it
- 01Build the week's column from actual availability, checked against approved leave, not from the team roster. Free for up to five people, permanently.
- 02Cap "this week" near the number of people who are actually free, not above it. A team with two people out shouldn't plan a full-strength week just because the roster says five.
- 03Pull from backlog only when a slot opens, not all at once on Monday morning. That's what keeps the column honest through the rest of the week.
- 04Move a stalled task into blocked the moment it stalls, with the reason written on the card, rather than waiting for the next standup to mention it out loud.
- 05Log time as each item finishes, not reconstructed from memory at the end of the week. It takes five seconds and it's far more accurate done immediately, right after the task closes.
None of this is about tighter control. It's about the board matching what's actually true. A week's plan that assumes full headcount and no interruptions is fiction by Tuesday; one built on real availability, with a place for blockers to land, tends to still be accurate on Friday.
- A weekly board sized to headcount instead of availability is wrong by Wednesday
- Blocked items need a column with a reason on it, not a mention in standup that everyone forgets
- Weekly planning is where quarterly goals turn into named tasks for named people, this week specifically
Common questions
Yes. All templates are included on the Free plan, which covers up to five users and two projects and does not expire. Larger teams need a paid plan for the seats, not for the template. See pricing.
Quarterly planning sets the goal: five or six things the team is committing to over twelve weeks. Weekly planning is the execution layer underneath it: the specific tasks, assigned to specific people, that this week is spent on. The weekly board is where a quarterly goal actually gets built, one week at a time.
No. There are no screenshots, no keystroke logging and no activity tracking. Time logging is a single daily total entered next to the task someone just finished, and only work outcomes ever show up on the board.
Anything the assigned person can't move forward without someone or something else: a waiting approval, a missing access grant, a dependency on another task still in progress. The rule of thumb is, if the next step isn't in that person's control, it belongs in blocked, not in "this week" quietly aging.
Related pages
See it on your own work.
A workspace your whole company will actually use is 60 seconds away. No card, no risk, nothing to install.
14-day full-access trial · sample project included · no card required