29 August 2026
A recurring meeting wastes time when it's doing a job that no longer needs a room. Read its last five transcripts before you touch the agenda: if the same three lines get said every week, if decisions get raised but never dated, if half the room is there for context they could get in writing, you're not looking at a bad meeting, you're looking at three different problems wearing one calendar slot.
Most people fix a stale weekly by shortening it. Thirty minutes instead of sixty, then it creeps back. The better diagnostic is to pull the last four or five transcripts and read only what was said in the first ten minutes of each. If it's a status - 'still waiting on legal,' 'same as last week' - that's not a meeting, that's a field in a tracker that nobody updates because the meeting is where updates happen instead.
AVAY keeps every past transcript searchable, so this audit takes fifteen minutes instead of a memory exercise. Search the meeting series for a phrase like 'still waiting' or 'no update' and count how often it recurs word for word. Three repeats in a row is the signal, not a hunch.
The fix here isn't a shorter meeting, it's no status segment at all. If a line gets said the same way three weeks running, it should live as a written line in a shared doc that updates the moment it changes, not a spoken update that waits for Tuesday to be true. The people who need to know can read it before the call; the people who don't need to know stop attending.
This is the cleanest cut because it costs nothing. Nobody misses hearing 'still blocked on legal' out loud a fourth time.
A different failure looks similar from the outside but needs the opposite fix. The topic changes week to week, people argue, and it sounds productive - but nobody ever says 'we decided X' with a date and a name attached. Read back three transcripts and count decisions that were proposed versus decisions that were actually closed. If the ratio is bad, the meeting isn't too long, it's missing an ending.
This is a facilitation gap, not a scheduling one. AVAY's live notes track decisions as the call makes them, but a decision only lands if someone says the sentence that closes it - 'so we're going with the March date' - not just discusses toward one. If your transcripts are full of live options and empty of closed ones, the fix is a habit: end every topic with someone stating the call out loud before moving on, and let the notes catch it.
The third pattern is the one people notice but rarely name: eight people on the call, three of them speak. The other five are there because they might need to know what happened, not because the meeting needs them. That's not a meeting problem, it's a distribution problem, and a meeting is an expensive way to solve it.
This is where a written brief replaces attendance outright. If someone's only reason for being in the room is 'in case something relevant comes up,' send them the notes instead and see if they ever ask a follow-up question. Most of the time they don't, because the thing they needed was the outcome, not the discussion that produced it. AVAY's post-meeting summary already goes to anyone tagged on the invite, so cutting someone from the room doesn't cut them from knowing - it just removes them from the hour.
The test is what's left after you remove the status and the drift. Strip a transcript down to only the parts where a decision got made or a genuine disagreement got worked through - not discussed, worked through, meaning two people held different views and the call changed one of them. If that residue is fifteen minutes across a sixty-minute meeting, shorten it. If that residue is zero across four consecutive weeks, the meeting has outlived the reason it was created for and shortening it just delays the harder conversation.
A meeting that should be shorter still has a job. A meeting that should not exist has a name and a slot but no job left, and everyone in it already half-knows it. The tell is that nobody can say, without checking their calendar, what the meeting is for anymore.
| What the transcript shows | Root cause | Fix | |
|---|---|---|---|
| Same status line, week after week | Update has no home outside the meeting | Move it to a living doc, drop the segment | — |
| Topics discussed but rarely closed | No one states the decision out loud | Require a closing sentence per topic | — |
| Most attendees silent, week after week | Meeting used for distribution, not decisions | Replace attendance with a written brief | — |
| No decisions or disagreements across a month | Meeting has no remaining job | Cancel it, not shorten it | — |
Show them the transcript pattern, not your opinion of the meeting. If four weeks of notes show the same status line repeated or zero closed decisions, that's evidence a decision-maker can act on without it reading as a judgment on anyone's work.
Yes, but the agenda should only list what genuinely needs live discussion - open disagreements or decisions still in motion. Anything that's a status or a readout belongs in a doc sent before the call, not a line on the agenda.
Split the recurrence: keep the full group cadence at half the frequency, and run a smaller weekly with just the people actively working the open items. AVAY's meeting search makes it easy for the less-frequent group to catch up on what they missed instead of sitting through it live.
It fails the same way a meeting does if it's status dressed up as a document. A brief works when it states decisions and open questions, not a narrative of what was discussed - the same discipline that fixes the meeting fixes the brief.
A recurring meeting doesn't get better by getting shorter; it gets better when you separate the status that belongs in a doc, the decisions that need a closing sentence, and the people who only ever needed to read the outcome.
AVAY is a video meeting platform that transcribes the call itself — no bot joins, because there is nothing to join. Start one at avay.ai, read how each part works in the documentation, or see what it costs.