All-Hands Meeting Summary Template: Copy, Paste, Automate

An all-hands meeting summary template should capture five things: a short executive recap, a log of decisions, announcements with who they affect, the Q&A split into answered and deferred, and follow-ups with owners and dates. You can fill it in by hand, but it is faster to record the meeting, generate a draft from the transcript, and spend your time checking the decisions section.

This post gives you a copy-paste template, a prompt you can use with any AI tool, and a way to handle questions that leadership could not answer on the day.

Why static all-hands notes fail

Most all-hands notes fail because they are written as a transcript-shaped essay, so readers skim, miss the one change that affects them, and ask in Slack what was decided.

Three problems come up again and again:

• The note-taker writes everything. A live typist cannot tell which sentence is a decision and which is a passing remark, so the output is long and flat.
• Decisions and opinions blur together. "We are looking at moving the launch" and "the launch moves to March 14" read the same in a rushed summary. One is a discussion and the other is a commitment.
• The Q&A disappears. It is the part people care about most, and it is usually the first thing cut. The recurring themes in town hall questions often show what employees care about most, which is useful for leadership as well as for readers.

A recap that works is one a busy person can read in five minutes and then act on.

The 5-part all-hands meeting summary framework

Use five sections in a fixed order so readers learn where to look each month. The content follows what the published templates agree on: strategic updates, wins, decisions, follow-up commitments and the full Q&A, including deferred questions.

1. Executive recap (10 lines or fewer)

A 10-line executive recap is the part most people will read. Write it so someone who stops after this section still knows the direction, the numbers and what is new.

2. Decisions log

Document each decision with context, owner, affected teams and immediate next steps. Only include things that were actually decided. Anything still under discussion goes elsewhere.

3. Announcements and wins

For each announcement, say who it affects and from when. The announcement log format is built on that exact question. "New expense policy" tells a reader nothing. "New expense policy, all staff, from 1 November" tells them whether to care.

4. Q&A

Split it into answered and deferred. The next section covers this in detail.

5. Follow-ups

Every commitment made on stage becomes a line with an owner and a date. If you want a longer treatment of capturing these, see our post on action items from meetings.

Copy-paste all-hands summary template

This version works as Markdown in a wiki and pastes cleanly into an email. Replace the brackets.

Subject: [Company] all-hands recap, [Month Year]

RECAP (10 lines max)
1. [Headline result or direction, with the number]
2. [Second most important change]
...

DECISIONS
- Decision: [what was decided, in one sentence]
  Context: [why]
  Owner: [name]
  Affects: [teams or roles]
  Effective: [date]
  Next step: [action and date]

ANNOUNCEMENTS
- [What changed] | Affects: [who] | From: [date]

WINS
- [Team or person]: [specific result]

Q&A
Answered
- Q: [question]
  A: [answer, one or two sentences]
Deferred
- Q: [question]
  Owner: [who will answer]
  Answer due: [date]
  Status: Open

FOLLOW-UPS
- [Action] | Owner: [name] | Due: [date]

Full recording / transcript: [link]

For an email, aim to stay under 500 words and organised into clear categories such as performance, strategy, people news and Q&A. If the recap runs longer, put the full version on the wiki and keep the email to the recap plus a link.

If you also need formal minutes for the record, our meeting minutes template guide covers four formats. An all-hands recap is a different document from minutes, because it is written for readers, not for the file.

Structuring the Q&A: answered vs. deferred questions

Document unanswered questions in their own group, with an owner and a due date for each, and publish the answers in the same place as the recap.

Mixing the two is where confusion starts. A reader who sees a question and a half-answer assumes the matter is settled. Give every question one of three states:

Some rules that help:

1. Do not paraphrase numbers. If the CFO said "about 8 percent," write "about 8 percent," not "8 percent."
2. Group similar questions. Five people asking about remote work policy is one entry with a note that it came up repeatedly. That repeat is the signal leadership should see.
3. Close the loop. When a deferred question gets an answer, edit the original recap and post a short update in the same thread. Do not start a new document that nobody connects to the first one.
4. Keep names out unless asked. Record the question, not who asked it, unless the person wants credit.

How to automate town hall summaries from raw transcripts

Record the meeting, transcribe it, then give a summarizer a strict structure and instructions to flag anything it is unsure about. Review the output before it goes out.

The workflow

1. Get the audio. Record in the browser while the meeting runs, or upload the recording file afterwards.
2. Transcribe it. Check that the language setting matches what was actually spoken, especially for mixed-language sessions.
3. Summarize into the fixed structure. Use the prompt below, or a summarizer that already outputs a TL;DR, decisions, action items and open questions.
4. Verify the decisions section. Someone who attended reads each decision and each number against the transcript.
5. Publish. Email the recap, post it in Slack, and store the full version on the wiki.

A prompt you can paste

Prompt guides for all-hands recaps recommend that you explicitly ask the model to flag uncertain items rather than guess at confirmed decisions. This prompt builds that in:

You are summarizing a company all-hands meeting transcript for employees who did not attend.

Produce these sections in order:
1. Recap: 10 lines or fewer.
2. Decisions: only items that were clearly decided. For each, give context, owner, affected teams, effective date, next step.
3. Announcements: what changed, who it affects, from when.
4. Wins.
5. Q&A: group as Answered, Partly answered, Deferred. For deferred items, note who was asked to follow up.
6. Follow-ups: action, owner, due date.

Rules:
- Ignore filler, jokes and small talk.
- Copy numbers, dates, names and deadlines exactly as spoken. Do not round or convert.
- If something sounds like a decision but was phrased as a possibility, put it under "Needs confirmation", not under Decisions.
- If an owner or date was not stated, write "not stated". Do not guess.
- Keep the whole summary under 500 words.

The "Needs confirmation" bucket is the most useful line in that prompt. It gives you a short list to check with the speaker before you publish.

Check the draft

AI summaries get the shape right far more easily than the details. Verify every number, every date and every owner. Our post on chatting with a meeting transcript covers what to ask and what to double-check when you query a transcript.

Managing all-hands recaps across multilingual and distributed teams

Write one canonical recap, keep every figure identical across languages, and publish all versions in one place.

Many all-hands meetings in Southeast Asia and Nigeria are not held in one clean language. A Yangon team may switch between Burmese and English mid-sentence. A regional lead may answer a question in Thai or Vietnamese. Generic templates and many transcription tools assume one language per meeting, and the summary suffers.

A workable approach:

• Pick the language of the meeting as the source. Summarize in the language that was spoken. Translating from a summary compounds errors.
• Check the transcription first. If the transcript is wrong, the recap will be confidently wrong. Our guide to multilingual meeting transcription explains what to check when languages mix.
• Use a bilingual reviewer for the second version. If leadership needs English and the team needs Burmese (or the reverse), one person who reads both should review the decisions and Q&A sections.
• Protect the numbers. Dates, amounts and names should match character for character across versions. Put the numbers in a table if prose is risky.
• Publish versions together. One thread, one wiki page, labelled by language, so nobody works from an older or different version.

Loka Note transcribes and summarizes in Burmese, English, Thai, Vietnamese, Chinese (Simplified), Yoruba and Hausa, and it handles mixed-language speech such as Burmese-English code-switching in a single meeting. Its summaries are produced in the meeting's language, which fits the "summarize in the spoken language first" approach above.

Distribution: Slack, email and the company wiki

Use each channel for what it does well: email for the recap, Slack for the nudge and follow-up questions, and the wiki for the permanent record.

A few habits help more than any tool:

• Send the recap while the meeting is still fresh. Speed matters more than polish.
• Put the single most important change in the email subject line.
• Use the same template every time, so people learn where the Q&A and deadlines sit.
• Review the recording's retention and access before you share it widely. Our post on whether AI note takers are safe lists the questions to ask.

Where Loka Note fits

Loka Note records meetings in the browser with no bot joining the call, or takes an uploaded audio or video file. It then produces a transcript and a structured summary with a TL;DR, decisions, action items and open questions, which map closely onto the template above. Language is detected automatically and mixed-language speech is supported, so a Burmese-English all-hands does not need to be forced into one language.

You can export notes as PDF or send them by email, and "Ask Loka" lets you ask questions such as "What did we decide about the hiring plan last quarter?" across your past meetings. There are no plan tiers. Minute top-ups start at $1.99 for 60 minutes, and an Unlimited plan costs $19.99 a month. Recordings are kept for six months and can be deleted at any time. Security details are on the security page, and larger organisations can see the enterprise page.

You still need a person to verify decisions and numbers before a recap goes out. The tool gives you the draft, and the review is yours.

Try it on your next all-hands: sign up for Loka Note