Skip to main content

    Meeting Summary: How to Do It Right (and Automate It with AI)

    A good meeting summary turns 60 minutes of conversation into 5 minutes of useful reading. This guide shows you how to structure it, a practical example and how to automate it entirely with AI.

    What is a meeting summary

    A meeting summary is an operational synthesis of what was discussed, decided and assigned during a meeting. Its goal is to let absentees — or anyone returning days later — understand what they need to know and what to do, without re-listening.

    How to structure it

    • Executive summary: 3–5 paragraphs, what happened and why it matters
    • Decisions made, with rationale for each
    • Action items, with owner and deadline
    • Open issues to revisit

    How to automate it

    Upload the recording to TANYRA: the platform identifies speakers, transcribes the audio and produces a structured summary in minutes, exportable to PDF.

    Generate your summary automatically

    Structured meeting summary with decisions and action items

    Meeting summary: the practical guide

    What is a meeting summary

    A meeting summary is an operational synthesis of what was discussed, decided and assigned during a work meeting. It lets absentees catch up in a few minutes, and attendees remember what was agreed.

    Unlike minutes, which have a more formal structure (header, agenda, votes, signature), a summary is typically freer and focused on what to do next.

    What a good summary should contain

    • Executive summary. 3–5 paragraphs answering "what happened and why it matters".
    • Decisions made. Clear list, with the rationale of each decision.
    • Action items. What to do, who owns it, by when.
    • Open questions. Unresolved items to revisit at the next meeting.
    • References. Cited documents, links, external people mentioned.

    How to summarise a meeting in 5 steps

    1. Identify the meeting goals

    Before summarising, ask: why did we meet? The summary should answer this in the opening lines.

    2. Extract the main themes

    Group the discussion into 3–5 key themes. Ignore tangents and passages not relevant to the outcome.

    3. Separate discussion from decisions

    Cleanly separate what was discussed from what was decided. A summary mainly serves those who were not present.

    4. List the action items

    For each action: what to do, who is responsible, by when. Without these three, an action stays on paper.

    5. Share within 24 hours

    A good summary loses value over time. Sending it within 24 hours is the rule that makes the difference.

    Meeting summary example

    A short example for an operational hour-long meeting. Replace names and content with your own.

    Marketing weekly meeting — 14/05/2026
    Summary: the team reviewed Q1 campaign results (on target) and defined the Q2 editorial plan. Approved a 15% paid budget increase for May to test a new channel.
    Decisions:
    • Q2 budget reallocation: 60% LinkedIn, 40% Google Ads.
    • 12 Q2 pillar contents approved.
    • +15% May paid budget.
    Action items:
    • L. Bianchi → Q2 editorial calendar (by 21/05).
    • F. Verdi → new paid channel setup (by 18/05).
    • M. Rossi → confirm budget with CFO (by 16/05).
    Open questions: define KPIs for the new paid channel before end of May.

    Generate the summary automatically with AI

    A good manual summary takes 20–40 minutes after every meeting. For a team running 3–5 meetings a week, that's hours of work that almost always doesn't get done.

    TANYRA automates this entirely:

    • Upload the recording: Audio or video, even from phone or exported from Zoom/Meet/Teams.
    • Speaker identification: Automatic diarization: who said what.
    • Decisions and action items: Structured and attributed, ready to share.
    • Export to PDF: Send to the team via email or link in one click.
    • In a few minutes: No more 30 minutes of manual work after every meeting.

    How long should it be

    The practical rule: one page per hour of meeting. A 60-minute meeting summarises well in 250–400 words; a half-day strategic meeting in 600–1,000 structured words.

    Frequently asked questions

    What is the difference between a summary and meeting minutes?

    Minutes are a more formal, structured document (header, agenda, discussion, decisions, action items, closing). A summary is a freer, more operational synthesis focused on what to know and what to do. In ordinary corporate contexts the two terms are often used interchangeably.

    How long should a meeting summary be?

    A good rule is 1 page per 60 minutes of meeting. An hour-long meeting summarises in 250–400 words, organised into executive summary, decisions and action items.

    How do you summarise a long meeting?

    For half-day-or-longer meetings, structure the summary into thematic sections, one per macro-topic. The page-per-hour rule still holds: better to condense than leave everything in.

    Can a meeting summary be generated automatically?

    Yes. AI tools like TANYRA let you upload an audio or video recording and receive a structured summary with synthesis, decisions and action items in minutes.

    What should a good meeting summary contain?

    Three essential blocks: a 3–5 paragraph executive summary, the decisions made (with rationale), the action items (with owner and deadline). Everything else is optional.

    Can AI really tell who said what?

    Yes. Speaker diarization separates speech by voice and — when instructed — associates each voice with a name, producing a summary with correct attributions.

    Automatic summaries for every meeting

    Upload the recording and receive a structured summary in minutes. Try it free.

    Generate your first summary