14 August 2026
Meeting notes get ignored for three organisational reasons that have nothing to do with how well they're written: they arrive after the decision has already moved on informally, they sit in a place nobody has a habit of opening, and they're addressed to everyone, which obligates no one specifically. Fix the writing and none of that changes. Fix the delay, the location, or the addressing, and the same notes start getting read.
A meeting ends at 3pm. Notes go out the next morning, or two days later once someone finds time to clean them up. By then the question the meeting was supposed to settle has already been re-argued in a Slack thread, re-decided in a hallway conversation, or quietly dropped because someone shipped the thing they thought was agreed. The notes arrive as a historical document about a decision that has already drifted, so reading them feels optional rather than necessary — the moment where they'd have changed anyone's behaviour has passed.
This is different from notes being wrong. Notes can be accurate and still be useless if they land after the window where accuracy mattered. The fix isn't better summarising; it's shrinking the gap between the meeting ending and the notes existing to something closer to zero.
Send a note to a group and you get the same effect as shouting a question into a crowded room: everyone assumes someone else will respond, so no one does. This is the ordinary diffusion of responsibility that shows up any time an obligation is distributed across a group rather than pinned to a person. A decisions doc emailed to twelve people gets a first skim from most of them and a second read from none, because 'the team' isn't accountable for anything — only individuals are.
The tell is in the language of the notes themselves. If an action item reads 'someone should follow up on pricing' rather than 'Priya follows up on pricing by Thursday,' it was written to be true rather than to be acted on. Notes addressed to a role or a group are description. Notes addressed to a name are an assignment.
Even a note that's timely and specifically addressed still gets ignored if it lives somewhere people don't have a reason to open. A shared drive folder, a wiki page three clicks deep, a doc linked once in a calendar invite — these are all places people visit on purpose, which means they only get opened by people who already remember the note exists. That's a small and shrinking group by day three.
Notes survive when they show up inside the tool a person already opens for other reasons — their task list, their inbox, the channel where their team actually works. The document doesn't need to be exciting. It needs to be in the path of something the reader was going to do anyway.
Attach a specific person to a specific line and three things change at once. The note stops being informational and becomes an assignment — it now has a subject who can succeed or fail at it. Failure becomes visible and attributable, which is the actual mechanism behind follow-through: not that people are more conscientious when named, but that an unnamed failure has no one to notice it. And the note gets a natural distribution path, because it can be routed to that person's own inbox or task list instead of a shared document they have to remember to check.
This is a small structural change with a large effect, and it's cheap to make. It doesn't require new tooling — a habit of writing 'who' next to every decision and action item, during the meeting rather than after it, does most of the work. The tooling matters for getting that ownership out of the doc and into the place the owner actually looks.
AVAY's AI participant writes and updates decisions and action items live, during the call, which removes the delay problem — there's no gap between the meeting ending and the notes existing, because they existed the whole time. When a decision or action item is entered with a named owner, AVAY can push it out through connectors a team has attached to their own systems, so it lands in that person's task tracker or channel rather than sitting in a call summary nobody opens.
It doesn't solve the addressing problem on its own. If a decision is logged without a name attached to it, AVAY will record it accurately and it will still be ignored for the same organisational reasons as a written-up note — the AI can carry the note to the right place, but a team still has to decide, out loud, in the meeting, whose name goes on it. And the connector routing only works where a connector has actually been set up; without one, the notes are accurate and fast but back to living in a place someone has to remember to open.
| Typical read pattern | Typical follow-through | |
|---|---|---|
| Sent to the whole team | Everyone skims once, no one rereads it | Responsibility diffuses; no single person closes it |
| Posted in a shared channel | Read by whoever happens to open the channel that day | Someone sometimes picks it up, but inconsistently |
| Assigned to a named owner in their own tool | Read because it's addressed by name, in a place they already check | Closes or visibly stalls — failure has a face attached |
Mostly, yes, but only if the ownership is decided in the meeting, not added later by whoever writes up the notes. An owner assigned after the fact by a note-taker is often wrong or contested, and that argument itself becomes a reason the note gets shelved.
That's useful information, not a scheduling problem to route around. An item nobody will claim in the room usually isn't actually a priority, or it belongs to someone who wasn't in the meeting — in which case the right action is to name that gap explicitly rather than write a note that will quietly die.
Both, for different reasons. A channel gives the team visibility into what was decided and lets anyone challenge it; direct routing to the owner is what actually produces follow-through. A note that only goes to a channel gets read; a note that only goes to an individual has no witnesses if it's wrong.
It solves the timing problem — notes exist immediately instead of arriving a day later — and it can solve the location problem if it's connected to the tools people already use. It does not solve the addressing problem, because that requires someone in the meeting to actually say a name out loud.
Notes get ignored because of when they arrive, where they live, and who they're addressed to — not because of how they're written; put a name on every decision and action item while the meeting is still happening, and route it to that person's own tools rather than a shared doc.
Meetings that take their own notes, in the browser: avay.ai.