The Google Calendar Meeting-to-Execution Gap Audit: A Worksheet for Finding Which Meetings Produced Scheduled Follow-Through Work
Published
You've had a busy two weeks. Plenty of planning calls, syncs, and decision meetings. But when you look at your Google Calendar right now, you can't tell which of those meetings actually led to scheduled work—and which ones just ended, with everyone logging off and nothing landing on anyone's calendar.
That gap between a meeting and the work it was supposed to produce is easy to miss in the moment. It tends to show up later, when a deadline arrives and the work that was "decided" in a meeting three weeks ago never actually got scheduled by anyone.
This audit helps you find that pattern before it becomes a problem. You'll look back at one week of past meetings, score each one, and end up with a clear picture of where your execution gaps are hiding.
Some practitioner discussions describe this kind of gap as a recurring frustration—decisions that felt settled in a meeting but never made it onto anyone's schedule. You can find one such discussion in a practitioner conversation about lost project context.
What this audit is—and what it isn't
This is a retrospective exercise. You're not evaluating meetings as they happen. You're looking at a week that's already finished and asking: for each meeting, did a follow-up event or task get scheduled within 48 hours?
It's different from the 15-Minute Post-Meeting Scheduling Exercise, which you fill out immediately after a single meeting. And it's different from the Google Calendar Scheduling Audit, which asks whether your calendar events connect to live project work going forward.
This audit asks a narrower question: looking back at last week, which meetings left a visible trace of scheduled follow-through, and which ones left nothing?
Why Google Calendar is the right place to look
Google Calendar is where most planning meetings live. It holds the title, the attendees, the time, and often a description or agenda. What it doesn't hold—at least not automatically—is any record of what was decided, who owns the next step, or whether that next step was ever scheduled.
That absence is exactly what you're auditing. If a meeting produced a real decision, there should be some visible trace in the calendar within 48 hours: a follow-up event, a task block, a working session. If there's nothing, that's a gap.
The 48-hour window isn't a magic number. It's a practical threshold. If a decision from a Monday meeting hasn't produced any scheduled work by Wednesday, the momentum from that meeting has likely faded. People have moved on to other things. The decision is still "in the air," but it's not on anyone's calendar.
How to run the audit
Pick a single week from your recent past—ideally the last full work week you can remember clearly. You'll look at every meeting that was intended to produce a decision or an action. Skip purely informational briefings where no one was expected to do anything afterward.
Open Google Calendar and set the view to that week. For each qualifying meeting, you'll fill in five columns.
The five-column worksheet
Here's what each column captures:
- Meeting Title — The name of the event as it appears in Google Calendar.
- Decision or Action Stated — What was the meeting supposed to produce? Check the event description, any notes in the invite, or your own memory. If you can't name a specific decision or action, write "unclear."
- Follow-Up Event Scheduled Within 48h (Y/N) — Look at the 48 hours after the meeting ended. Was any new event created that connects to the work this meeting was about? A working session, a review call, a task block—anything that shows the decision moved forward.
- Owner Named in Calendar (Y/N) — Is there a specific person named as responsible for the next step, either in the original event description or in a follow-up event? A meeting with five attendees but no named owner is a gap risk even if a follow-up was scheduled.
- Gap Score (0–2) — Calculated from the two Y/N columns. See the scoring guide below.
The gap score explained
Each meeting gets a score between 0 and 2. Lower is better.
- Score 0: A follow-up event was scheduled within 48 hours AND an owner was named. The decision has a visible path forward.
- Score 1: One of the two conditions is met. Either a follow-up was scheduled but no owner is named, or an owner is named but no follow-up event appears on the calendar.
- Score 2: Neither condition is met. No follow-up event, no named owner. The meeting produced a decision that has no visible scheduled home and no one clearly responsible for it.
A score of 2 doesn't mean the work definitely fell through. It means there's no evidence in the calendar that it didn't. That's the gap.
A filled example worksheet
Here's what a completed worksheet might look like for a sample week. The meeting titles and details below are illustrative—they're meant to show you how to fill in the columns, not to represent any real team.
| Meeting Title | Decision or Action Stated | Follow-Up Event Within 48h (Y/N) | Owner Named in Calendar (Y/N) | Gap Score (0–2) |
|---|---|---|---|---|
| Q3 Roadmap Planning | Finalize feature priority list | Y | Y | 0 |
| Design Review – Onboarding Flow | Approve revised wireframes | N | N | 2 |
| Sprint Kickoff | Assign tickets and set sprint goal | Y | N | 1 |
| Stakeholder Sync – Launch Timeline | Unclear | N | N | 2 |
| API Integration Check-In | Decide on error-handling approach | N | Y | 1 |
In this example, two meetings scored a 2. That's two decisions sitting in the calendar with no visible follow-through and no named owner. If either of those decisions was on a path to a deadline, the deadline is now at risk—not because anyone made a bad decision in the meeting, but because the decision never got scheduled.
What a high gap score tells you about deadline risk
A single score-2 meeting in a week isn't necessarily alarming. Meetings sometimes produce decisions that get handled through other channels—a Slack message, a quick hallway conversation, an email thread. The calendar won't often show everything.
But when you see a pattern—two, three, or four score-2 meetings in a single week—that's a signal worth taking seriously. It suggests that your planning meetings are regularly producing decisions that don't have a scheduled home. Over time, that kind of pattern can surface as missed deadlines, repeated conversations about things that were "already decided," and a general sense that planning meetings aren't moving anything forward.
If your audit reveals a high gap score pattern, the next step is a direct conversation about which of those open decisions are on a path to a deadline. The Deadline Risk Conversation Guide gives you a structured way to have that conversation with a stakeholder without it feeling like an accusation.
The blank worksheet template
Copy this into a document, spreadsheet, or wherever you keep working notes. Fill in one row per qualifying meeting from your chosen week.
| Meeting Title | Decision or Action Stated | Follow-Up Event Within 48h (Y/N) | Owner Named in Calendar (Y/N) | Gap Score (0–2) |
|---|---|---|---|---|
Add rows as needed. Most weeks will have between four and ten qualifying meetings. If you have more than that, try limiting the audit to meetings that involved a decision with a deadline attached.
A few things to watch for as you fill it in
Meetings with no stated decision. If you can't name what the meeting was supposed to produce, write "unclear" in the second column and score it a 2. A meeting with no stated decision can't have a follow-up, because no one knows what they're following up on.
Follow-up events that don't connect. Sometimes a follow-up event gets scheduled, but it's a generic recurring sync rather than something specific to the decision made. Use your judgment. If the follow-up event title and description don't connect to the decision, treat it as N.
Owner named in the original invite vs. a follow-up. Either counts. If the original event description says "Sarah will finalize the spec by Friday," that's a named owner. If a follow-up event was created and Sarah is the only attendee, that also counts.
Decisions made verbally but not recorded anywhere in the calendar. This is common. If the decision happened in the meeting but nothing in the calendar description, follow-up event, or invite reflects it, score the owner column as N. The calendar is the only evidence you're working with here.
What to do after the audit
Once you've scored your week, add up the gap scores. A total of 0–2 across all meetings suggests your decisions are generally finding their way onto the schedule. A total of 5 or higher suggests a pattern worth addressing—not by adding more meetings, but by changing what happens in the 48 hours after a meeting ends.
The forward-looking version of this exercise is the 15-Minute Post-Meeting Scheduling Exercise. It gives you a structure to fill out immediately after a single meeting, so you're building the follow-through habit in real time rather than auditing the gap after the fact.
The audit you just ran tells you where the gaps have been. The post-meeting exercise helps you stop creating new ones.
Where Tindlo fits into this
Google Calendar is good at showing you when meetings happened and who attended. What it doesn't do on its own is hold the connection between a meeting and the work that meeting was supposed to produce.
Tindlo connects to your Google Calendar and gives you a shared operational view where meetings and work items sit on the same time axis. When a planning meeting produces a decision, you can create a work item in Tindlo that carries the context—the brief, the owner, the files, the links—and schedule it alongside the rest of your team's work. The calendar shows the meeting. Tindlo holds what came next.
If your audit turned up a pattern of score-2 meetings, that's a concrete signal of where a scheduling layer would help. Try Tindlo free and see how it looks when your meetings and your follow-through work share the same view.