The Capacity-Aware Meeting-to-Execution Worksheet: Catch an Overloaded Owner Before the Work Stalls
Published
You finish a planning call. You've got decisions, owners, and deadlines. You write them down, send a summary, and feel good about it.
Then a week passes. One of the tasks hasn't moved. You follow up. The owner says, "Sorry — I was slammed last week. I didn't have time to start it."
The decision was made. The owner was named. The deadline was set. But nobody checked whether that person actually had room in their week to do the work.
This article adds one column to the standard post-meeting scheduling exercise to address that. The column is called Owner capacity this week. It takes about two minutes to fill in per task, and it surfaces overloaded owners at the moment of assignment — not days later when the deadline is already slipping.
Some practitioner discussions describe this kind of gap — where follow-through breaks down not because of unclear ownership but because of invisible scheduling pressure — as one of the more frustrating parts of running a team. You can see one such practitioner discussion about meeting follow-through for a sense of how commonly this comes up in conversation.
Why the gap happens
When you name an owner in a meeting, you're making a social assignment, not a scheduling one. You're saying "this person is responsible" — but you're not checking whether their week has room for the work.
Most post-meeting notes capture five things: the decision, the owner, the deadline, any dependencies, and the reason the task matters. That's a solid foundation. The 15-minute post-meeting scheduling exercise covers exactly those five columns.
What it doesn't capture is whether the named owner has any available time in the week the work is supposed to start. That gap is small but consequential. A task assigned to someone with zero capacity this week isn't really scheduled — it's just hoped for.
The six-column worksheet
The capacity-aware version of the worksheet adds one column to the existing five. Here's what each column does:
- Decision — What was agreed in the meeting. One sentence, specific enough that someone who wasn't in the room understands it.
- Owner — The single person responsible for making this happen. One name, not a team.
- Deadline — The date by which the work needs to be done or the next check-in needs to happen.
- Dependency — Anything that needs to happen before this task can start, or anything this task blocks downstream.
- Why — One sentence explaining why this task matters. This helps the owner understand the stakes without having to re-read the whole meeting summary.
- Owner capacity this week — A simple signal: does the owner have meaningful available time in the week this task is supposed to start? (More on how to check this below.)
The first five columns tell you what needs to happen and who's responsible. The sixth column tells you whether the plan is realistic right now.
A filled example
Here's what the worksheet looks like after a product planning meeting. The team decided to update the onboarding flow, write a technical spec for a new API endpoint, and brief a design contractor on a new feature.
| Decision | Owner | Deadline | Dependency | Why | Owner capacity this week |
|---|---|---|---|---|---|
| Revise onboarding flow to remove the two-step email confirmation | Priya | Friday, end of day | None | Drop-off at step 2 is blocking new user activation | Low — Priya has three customer calls and a sprint review this week. Move deadline to next Monday or reassign. |
| Write technical spec for the new webhook endpoint | Marcus | Next Wednesday | Priya's onboarding revision must be final first (spec references the new flow) | Engineering can't start the build without a signed-off spec | Moderate — Marcus has two days of focused time available. Deadline is achievable if Priya's revision lands Monday. |
| Brief design contractor on the dashboard feature | Sam | Thursday | None | Contractor starts billing next week; brief must arrive before then | Good — Sam has a clear Tuesday and Wednesday. No conflicts. |
The first row is the one that would have stalled. Priya was named as owner, the deadline was set for Friday, and nobody in the meeting knew she had three customer calls and a sprint review that week. The capacity column surfaces that conflict immediately, while there's still time to move the deadline or reassign the task.
How to fill in the capacity column
You don't need a formal capacity-planning system to do this. A quick look at the owner's calendar is enough to make a reasonable judgment.
Here's a simple approach using Google Calendar:
- Open the owner's calendar and look at the week the task is supposed to start.
- Note the hours already committed to meetings, reviews, and recurring obligations.
- Ask yourself: is there a realistic block of focused time — at least a few hours — where this task could actually get done?
- If yes, mark capacity as Good. If there's some room but it's tight, mark it Moderate. If the week is already packed, mark it Low.
You're not trying to be precise here. You're trying to catch the obvious cases — the owner who has back-to-back meetings all week, or who's already carrying three other tasks from the same meeting. A rough signal is far better than no signal.
If you use Tindlo, the Google Calendar integration lets you see the owner's existing calendar events alongside the new task in the same view. You don't have to switch tabs or ask the owner to share their schedule — the context is already there when you're filling in the worksheet.
What to do when capacity is Low
A Low rating doesn't mean the task is stuck. It means you need to make a decision now instead of later. You have three options:
- Move the deadline. If the task isn't truly urgent, push the start date to a week where the owner has more room. Update the worksheet and let the owner know.
- Reassign the task. If the deadline is fixed, find someone else with capacity this week. Update the owner column and make sure the original owner knows they're off the hook.
- Reduce the scope. Sometimes a task can be broken into a smaller first step that fits in a tight week, with the rest following later. This works well when something downstream is waiting on this task to move.
The goal isn't to protect the owner from work — it's to make sure the task actually starts when it's supposed to. A task assigned to someone with no capacity isn't a plan; it's a wish.
The blank template
Copy this into a shared doc, a spreadsheet, or a notes app right after your next planning meeting. Fill it in before you send the meeting summary.
| Decision | Owner | Deadline | Dependency | Why | Owner capacity this week |
|---|---|---|---|---|---|
For the capacity column, use Good, Moderate, or Low as your rating, then add a one-sentence note explaining what you saw. The note is what makes the rating useful — it tells the owner and anyone reviewing the worksheet why the rating was given.
A few things worth knowing before you start
Fill the worksheet before you send the summary. Once the summary is sent, people start acting on it. Catching a capacity problem before the summary goes out is much easier than correcting a plan that's already in motion.
One owner per task. If you're tempted to write two names in the owner column, that's a signal the task probably needs to be split into two tasks. Shared ownership tends to mean unclear ownership.
Check the week the task starts, not the week of the deadline. A task due in two weeks might need to start this week. The capacity check should match the start week, not the due date.
The capacity check is a conversation starter, not a judgment. If you mark someone's capacity as Low, the next step is a quick message — "Hey, I noticed your week looks packed. Want to push this to next Monday, or should we find someone else?" That's a two-minute conversation that can save a week of stalled work.
When to go further
The capacity column catches overloaded owners at assignment time. But if you're working on a project that's already in flight and you're seeing deadline risk across multiple tasks, the 30-minute deadline risk audit is a good next step. It looks at capacity as part of a broader review of what's at risk across the whole project.
And if your team passes work between people or groups at defined handoff points, the pre-handoff readiness check helps you verify that the receiving side has capacity before the handoff happens — so work doesn't pile up on someone who isn't ready to receive it.
Try it after your next meeting
The next time you finish a planning call, give yourself five extra minutes before you write the summary. Fill in the six-column worksheet. Check each owner's calendar for the week their task is supposed to start. Write a one-sentence capacity note.
You'll probably find that most owners are fine. But you'll also catch the one who isn't — and that's the task that would have stalled.
If you'd like a workspace where your team's tasks and Google Calendar events sit in the same view, Tindlo is worth a look. The Google Calendar integration means you can do the capacity check without switching tools — the owner's week is visible right alongside the work you're scheduling.