The meeting is over, everyone goes back to their day, and you know you should send a summary. Except you have another call in ten minutes, three urgent emails waiting, and that summary can wait until tonight. Tonight becomes tomorrow, tomorrow becomes next week, and eventually you’re trying to reconstruct a meeting you barely remember.

It’s the classic meeting notes cycle. We know we should do it, we know it’s useful, but we put it off because it takes time and it’s tedious. Re-reading your notes, structuring information, rephrasing properly, checking you haven’t forgotten anything. For a one-hour meeting, that’s easily twenty minutes of work. Multiply by five meetings a week, and you understand why most meeting notes never get sent.

The perfect summary doesn’t exist

The first thing to accept is that a summary sent is better than a perfect summary that doesn’t exist. Nobody’s going to read a meticulously written three-page document. What people want is to know what was decided, who’s doing what, and when. The rest is bonus.

A good summary answers four questions. What was decided? Who does what and by when? What needs clarification? And for those who weren’t there, what was the general context? If you answer these four questions, even in a few lines, you’ve done your job.

The method for sending in one minute

The secret is not writing the summary yourself. You recorded the meeting with Cosmonote, and the app generated a structured summary with decisions, action items, and key points. Everything’s already there, neatly organized. You just need to copy-paste and send.

Concretely, here’s how it goes. The meeting ends, you open Cosmonote, you look at the generated summary. You quickly check that nothing major is missing. You copy the block, paste it into an email or Slack message, add an intro line like “Here’s the summary from our meeting this morning,” and send. Timed, it’s under a minute.

What changes with immediate sending

When you send the summary within minutes of the meeting, several things happen. First, people are impressed. They just hung up and they already have the summary in their inbox. It projects an image of professionalism and organization that makes an impact.

Second, errors get corrected immediately. If you misunderstood something or if a decision was interpreted differently by someone else, participants can react while it’s still fresh. Three days later, nobody remembers the nuances and misunderstandings become facts.

Third, action items are clarified right away. When John sees in the summary that he needs to send the contract by Friday, he can confirm or correct immediately. There’s no fuzzy period where nobody really knows who’s responsible for what.

What if the automatic summary isn’t perfect?

It never will be 100%. AI does an excellent job capturing the essentials, but it can miss nuances or misinterpret context it doesn’t know. That’s why you keep an eye on the summary before sending.

The right approach is to consider the automatic summary as a very advanced first draft. You scan it quickly, correct what needs correcting, add an important point if necessary, and send. It’s still much faster than starting from scratch, and the result is often better than what you would have written yourself after a busy day.