The Meeting-to-Execution Gap Scorer: A Worksheet for Rating How Much Deadline Risk Each Recent Meeting Created

Published 2026-10-02 15:38 KST

You're three or four weeks into a project. Several planning calls and decision meetings have happened. Some of them produced scheduled work with clear context attached. Others ended with a nod and a "we'll follow up on that."

You suspect at least one of those meetings is quietly building deadline risk right now. But you can't tell which one without going back through every note, every calendar invite, and every task list. That takes time you don't have.

This worksheet gives you a faster path. Instead of reviewing each meeting from scratch, you score them side by side across three dimensions, add up the numbers, and get a ranked list of which gaps to close first.

The whole exercise takes about twenty minutes for five meetings.

Why meetings create deadline risk even when they go well

A meeting can be productive—good discussion, real decisions, genuine alignment—and still leave a gap in your project's execution layer. The gap isn't about meeting quality. It's about what happens in the hours and days after the meeting ends.

Some practitioner conversations describe this as a recurring frustration: a meeting feels resolved in the room, but the follow-through never quite materializes into scheduled work. This theme appears in a practitioner discussion about meeting follow-through and in a related discussion about lost project context.

Three things tend to determine whether a meeting translates into forward momentum or quietly stalls:

• Whether follow-through work got scheduled. A decision that doesn't produce a task with a date attached can drift indefinitely. The work feels done because the conversation happened, but nothing is actually moving.
• Whether context traveled with the work. Even when a task does get created, the person picking it up later may not know why it matters, what was decided, or what constraints apply. They have to reconstruct the reasoning from memory or ask someone—which costs time and introduces errors.
• Whether dependencies got named. Some follow-through work blocks other work. If that blocking relationship isn't visible, the downstream task looks fine on paper until the upstream task is late—and by then it's too late to adjust easily.

These three factors are the basis for the scoring rubric below.

The three scoring dimensions

Each meeting gets a score on three yes/no questions. Each "yes" is worth 0 points. Each "no" is worth 1 point. A higher score means more risk.

This might feel backwards at first—usually higher is better. But here you're measuring gaps, not achievements. A score of 3 means all three structural supports are missing. A score of 0 means the meeting translated cleanly into execution.

Dimension 1: Follow-through scheduled (Y/N)

Did the meeting produce at least one task or work item with a scheduled date and an assigned owner? Not a note in a doc. Not a verbal agreement. A scheduled item that will appear on someone's work plan.

• Yes = 0 points
• No = 1 point

Dimension 2: Context attached (Y/N)

Does the follow-through work carry enough context for the person doing it to understand the decision behind it? This could be a linked note, a brief, a summary comment, or a reference to the meeting record. The test: could someone pick up this task cold and know what they're doing and why?

• Yes = 0 points
• No = 1 point

Note: If follow-through wasn't scheduled at all (Dimension 1 = No), score Dimension 2 as No by default. There's nothing to attach context to.

Dimension 3: Dependency named (Y/N)

If the follow-through work blocks something else on the project, is that blocking relationship visible somewhere? A named dependency doesn't need to be formal. It just needs to exist in a place where the project lead and the downstream owner can both see it.

• Yes = 0 points
• No = 1 point

Note: If the follow-through work doesn't block anything else, score this dimension as Yes (0 points). The risk only applies when a dependency exists but isn't named.

Composite risk score

Add the three dimension scores together. The result is the meeting's composite risk score.

• 0 — Low risk. The meeting connected to execution cleanly.
• 1 — Moderate risk. One structural gap. Worth a quick check.
• 2 — High risk. Two gaps. This meeting needs attention before the next milestone.
• 3 — Critical risk. All three supports are missing. This is your first repair priority.

Filled example: Five recent meetings scored

Here's how the scorer looks when applied to a realistic set of five meetings from a mid-project week. The project is a product launch with a hard external deadline six weeks out.

What this table tells you

Two meetings scored 3: the stakeholder alignment call on Tuesday and the cross-team dependency sync on Friday. Both produced no scheduled work, no attached context, and no named dependencies. These are your first two repair priorities.

The cross-team dependency sync is especially worth flagging. A meeting called specifically to discuss dependencies that produced no named dependencies is a structural gap with compounding risk. If those dependencies exist but aren't visible, every downstream task is operating on an assumption that may already be wrong.

The design review and the legal check-in each scored 1. They're not urgent, but they're worth a quick look before the next milestone. The design review has a task scheduled but no context attached—whoever picks it up may need to ask questions before they can start. The legal check-in has a task with context but a dependency that isn't named. If legal sign-off blocks the launch build, that relationship needs to be visible to both sides.

The sprint planning call scored 0. Leave it alone.

Ranked repair list from this example

1. Cross-team dependency sync (score: 3) — Schedule follow-through tasks, attach meeting context, and name every dependency surfaced in the call.
2. Stakeholder alignment (score: 3) — Identify what decisions were made, create tasks for any committed actions, and attach a brief summary to each.
3. Legal check-in (score: 1) — Name the dependency between legal sign-off and the launch build so it's visible to both teams.
4. Design review (score: 1) — Add a context note to the scheduled task so the assignee knows what was decided and why.
5. Sprint planning call (score: 0) — No action needed.

Blank template: Copy and fill in for your own meetings

Use this for any set of recent meetings. Five is a practical number for a single sitting, but you can extend it to cover more if you're doing a broader review.

Ranked repair list (fill in after scoring)

1. Meeting: __________ Score: __ Action: __________
2. Meeting: __________ Score: __ Action: __________
3. Meeting: __________ Score: __ Action: __________
4. Meeting: __________ Score: __ Action: __________
5. Meeting: __________ Score: __ Action: __________

A few notes on using the scorer well

Score from memory first, then verify

Your instinct about which meetings feel unresolved is often a useful starting signal. Try filling in the table from memory before you open any notes or task lists. If your gut says a meeting scored 3, it probably did. The verification step is most valuable for the 1s—those are the ones where a quick check can save you from either over-repairing or missing something small.

The scorer is a triage tool, not a full audit

This worksheet tells you which meetings to look at first. It doesn't replace a full review of task estimates, handoff readiness, or context age across the project. If you want to go deeper after scoring, the 30-minute deadline risk audit extends the analysis to those layers.

For high-scoring meetings, use the post-meeting exercise to repair them

Once you've identified your top one or two meetings by score, the 15-minute post-meeting scheduling exercise gives you a structured way to close the gap for a single meeting. It's designed for exactly this situation: a meeting that happened, produced no scheduled work, and needs to be repaired before deadline pressure builds.

Check your calendar after scoring

One thing that often surfaces after running this scorer is that some follow-through work was discussed but never made it onto anyone's calendar. The Google Calendar meeting-to-execution gap audit is a useful next step if you want to verify which calendar events actually connect to scheduled project work.

What to do with your ranked list

Once you have your scores and your repair list, the goal is straightforward: work from the top down and close the gaps before they compound.

For a score-3 meeting, the repair usually involves three things: creating at least one task with a date and owner, writing a short context note that explains the decision behind it, and checking whether that task blocks anything else on the project. That's often a fifteen-minute conversation with the right person.

For a score-1 or score-2 meeting, the repair is usually smaller—adding a note to an existing task, or making a dependency visible that everyone already knows about but hasn't written down yet.

The meetings that scored 0 don't need your attention right now. That's the point of the scorer: it tells you where to spend the next hour, not where to spend the next week.

How Tindlo connects to this

After you've scored your meetings and identified the gaps, the next practical step is making sure the repair work actually lands somewhere visible—not just in a doc or a message thread that gets buried.

Tindlo's Google Calendar integration lets you see which calendar events connect to scheduled project work. When you're repairing a high-scoring meeting, you can create work items in Tindlo with context, people, and schedule attached, then see how that work sits alongside everything else happening on the project's time axis. That shared view is what makes the repair durable: the work isn't just created, it's visible to the people who depend on it.

If you're already using Tindlo, the scorer is a natural pre-step before checking your scheduling layer. If you're not, you can try it here.

Quick summary

• Score each recent meeting across three dimensions: follow-through scheduled, context attached, dependency named.
• Each missing element adds 1 point. Higher score = more deadline risk.
• Sort by score to get your ranked repair list.
• Start with score-3 meetings. They're the ones most likely to be quietly building pressure right now.
• Use the blank template above to run this for your own project in about twenty minutes.