The Recurring Meeting Scheduling Audit: A Worksheet for Deciding Which Standing Meetings Produce Scheduled Work

The Recurring Meeting Scheduling Audit: A Worksheet for Deciding Which Standing Meetings Produce Scheduled Work

Published

Most calendars carry a quiet weight. Buried inside them are meetings that were set up months ago, for reasons that made sense at the time, and that nobody has stopped to question since. They just keep appearing every Monday, every Tuesday, every other Thursday.

This worksheet is for the moment you decide to look at those meetings honestly. Not to cancel everything—some recurring meetings genuinely move work forward. But to ask a simple question for each one: does this meeting produce scheduled work, or does it just produce more conversation?

The audit takes about thirty minutes if you work through it methodically. You'll end with a short list of meetings to keep, a few to restructure, and probably one or two you can let go entirely.


Why "scheduled work" is the right test

A meeting can feel productive without producing anything. People share updates, nod along, raise concerns, and then return to their desks without a single new task on the calendar. The conversation was real. The work it was supposed to generate? Still waiting.

Some practitioner discussions describe this gap between what gets decided in a meeting and what actually gets done afterward—a pattern where decisions dissolve because no one captures them as concrete next steps with owners and dates. A practitioner discussion about meeting follow-through and lost project context touches on exactly this problem: https://news.ycombinator.com/item?id=30808821.

"Scheduled work" means a task or deliverable that has a person responsible for it and a time on the calendar when it will happen. If a meeting regularly produces that kind of output, it's earning its place. If it doesn't, it's worth examining.


Before you start: gather your recurring meetings

Open your calendar and make a simple list. Write down every meeting that repeats—weekly, biweekly, monthly, whatever the cadence. Include the ones you run and the ones you just attend.

For each meeting, note:

That's your starting inventory. Now you're ready to run each one through the worksheet.


The worksheet: five questions per meeting

Work through these five questions for each recurring meeting on your list. Be honest. The goal isn't to justify the meeting—it's to see it clearly.

Question 1: What was this meeting originally for?

Write down the original purpose in one sentence. Not the calendar invite title—the actual reason someone set it up. Was it to unblock a specific project? To align two teams during a busy launch? To review work in progress?

If you can't remember, or if the answer is vague ("to stay aligned"), that's worth noting. Meetings without a clear original purpose tend to drift.

Question 2: Is that original purpose still relevant?

Projects end. Teams reorganize. The problem a meeting was created to solve sometimes disappears—but the meeting stays. Ask yourself whether the original reason still applies today. If the project wrapped up six months ago and the meeting is still running, that's a signal.

If the purpose has shifted, write down what the meeting is actually for now. Sometimes a meeting evolves into something genuinely useful. Sometimes it just fills a slot.

Question 3: What work came out of the last three sessions?

This is the most important question. Think back to the last three times this meeting happened. What tasks, decisions, or deliverables came out of it? Be specific.

Try to name actual items: a document that got written, a decision that unblocked a team, a task that appeared on someone's schedule. If you can name three concrete outputs across three sessions, the meeting is probably doing something real. If you're struggling to name one, that's a meaningful data point.

It can help to check any notes or follow-up messages from those sessions. If there are no notes, that itself tells you something.

Question 4: When work does come out of this meeting, does it get scheduled?

There's a difference between a meeting that produces a verbal agreement and one that produces a task on a calendar. Verbal agreements are easy to forget. Scheduled work is harder to lose.

Ask yourself: after this meeting, do people leave with something on their schedule? Or do they leave with a vague intention to "follow up" that may or may not happen?

Some practitioner conversations describe how work discussed in meetings gets lost when it isn't captured somewhere visible and time-bound—a theme explored in this practitioner discussion about coordination and follow-through. The gap between "we talked about it" and "it's on the calendar" is where a lot of work quietly disappears.

Question 5: Could this meeting's purpose be served another way?

Some meetings exist because there's no other good way to share context or make a decision together. Others exist because nobody set up a better alternative. Ask whether a shared document, a brief async update, or a one-time check-in could do the same job without the recurring slot.

This isn't about eliminating all meetings. It's about making sure the recurring ones are doing something a lighter-weight option genuinely can't.


Scoring and deciding

After you've answered all five questions for a meeting, place it in one of three categories:

You don't need a perfect score to keep a meeting. Some recurring conversations are genuinely valuable even when they don't produce a task every time—a monthly retrospective, for example, might produce insight rather than a to-do, and that's fine if that's the explicit purpose. The key is that the purpose is clear and the meeting is serving it.


The restructure move: adding a scheduling moment

If a meeting lands in the "restructure" category, one of the simplest fixes is adding a brief closing ritual: before the meeting ends, someone asks, "What gets scheduled as a result of this conversation?"

That question forces the group to translate discussion into action. It doesn't need to be formal. It just needs to happen before people close their laptops.

The output of that moment—a task, a deadline, a person responsible—should go somewhere visible. Not buried in a chat thread or a notes document nobody opens. Somewhere the person responsible will actually see it when the time comes to do the work.


Keeping the work visible after the meeting

One reason scheduled work gets lost after meetings is that it lives in a different place than the rest of the team's work. The meeting happens on the calendar. The task gets written in a notes doc. The actual work happens somewhere else entirely. Nothing connects.

Tindlo is built around the idea that your team's work should be visible across time in one place. It separates teams, projects, and work types into parallel layers on a shared time axis—so when a meeting produces a task, that task can sit alongside everything else the team has scheduled, in context, with the files, links, and notes attached to it. Work items in Tindlo can carry a brief, comments, tags, and relevant files, so the context from the meeting doesn't have to live only in someone's memory.

If you're finding that work agreed on in meetings keeps slipping through the cracks, it might be worth looking at whether your scheduling and task tools are actually connected. You can explore how Tindlo approaches that at tindlo.com.


A printable version of the worksheet

Here's a condensed version you can copy into a doc or print out for each meeting you're auditing:


A note on doing this with your team

If you run recurring meetings that involve other people, it's worth doing this audit with them rather than for them. Share the worksheet. Ask the same questions together. People are more likely to support a change—or a cancellation—when they were part of the reasoning.

It also surfaces something useful: sometimes the people in a meeting know it isn't working but assume everyone else finds it valuable. Asking the question out loud gives everyone permission to be honest.

The goal isn't a leaner calendar for its own sake. It's a calendar where the meetings that remain are ones you can point to and say: yes, this one moves work forward.

Get started with Tindlo