An all hands meeting minutes template has a harder job than most meeting notes, because the audience is not in the room agreeing with each other, it is the whole company, split across people who were half listening, people on leave that day, and a new hire who joined the week after. A good all hands recap has to stand alone for every one of them. This guide gives you a template to copy, a filled-in example from an Indian company's quarterly all hands, and the two parts most teams get wrong: the Q&A section and sharing the recap with people who were not there.
Why all hands minutes are not the same as team meeting minutes
A team stand-up or a project review assumes everyone in the room shares context. An all hands assumes almost nothing. Someone in support may not know what the engineering roadmap slide meant, someone who joined last month has never heard the founder's usual references, and a person who stepped out for five minutes missed the one number leadership actually wanted remembered. Minutes written for this audience need to spell things out a little more than an internal team would ever need, without turning into a transcript nobody reads.
The other difference is tone. Team minutes track work. All hands minutes exist to carry information down through the company accurately, so people do not end up with five different versions of what was announced by the time it reaches the last team that hears about it secondhand.
An all hands meeting minutes template you can copy
Use this structure whether the all hands ran as a call, a hybrid meeting with some people in a conference room, or an in-person town hall.
All hands, [company name], [date]
Attendance: [number present out of total headcount, and whether it was recorded for people who could not join]
Led by: [names and roles]
Announcements
- [Announcement 1, in one or two plain sentences, no jargon left unexplained]
- [Announcement 2]
Updates by team or function
- [Team name]: [what changed, what shipped, what is coming, in a sentence or two each]
Numbers shared
- [Metric]: [value], compared with [previous value or target], as stated by [who shared it]
Questions and answers
- Q: [question, attributed or marked anonymous as asked] A: [answer, in full, not summarised to the point of losing the actual commitment made]
Decisions or commitments made in the room
- [Anything leadership committed to doing, with a rough timeline if one was given]
Where to find more
- [Link to the recording, the slides, or a doc with more detail on any topic covered]
A filled-in example
Here is the same template filled in for a mid-sized company's quarterly all hands.
All hands, Finlane Technologies, 14 October 2026
Attendance: 142 of 168 employees joined live, the rest can watch the recording linked below
Led by: Arjun Mehta (CEO), Divya Rao (VP Product), Sameer Khanna (VP Engineering)
Announcements
- The company crossed 50,000 paying customers this quarter, the first time since launch
- A new office floor opens in Pune from next month for the growing support team
Updates by team or function
- Product: The new billing dashboard shipped to all customers last week. Mobile app redesign is in testing, expected to ship next quarter.
- Engineering: Migrated the search service to the new infrastructure with no downtime. Next focus is reducing page load time on the reports section.
- Support: Average response time improved from six hours to two hours this quarter after the new ticket routing went live.
Numbers shared
- Monthly recurring revenue: up 18 percent quarter on quarter, as shared by Arjun
- Customer churn: down to 3 percent from 4.5 percent last quarter, as shared by Divya
Questions and answers
- Q (asked live by Kabir, Support): Will the Pune office have space for support to grow into next year? A (Arjun): Yes, the lease covers growth up to 80 seats, well beyond current headcount.
- Q (submitted anonymously): Is the mobile redesign going to change pricing? A (Divya): No, this is a visual and performance update only, pricing is not changing as part of it.
- Q (asked live by Priya, Engineering): Is the infrastructure migration finished for all services or just search? A (Sameer): Just search for now, two more services move next quarter, we will share a schedule in the engineering channel.
Decisions or commitments made in the room
- Sameer to post the full infrastructure migration schedule in the engineering channel by end of next week
- Arjun to share Pune office floor plans company-wide once finalised
Where to find more
- Full recording and slides shared in the company-wide channel the same evening
Getting the Q&A section right
The Q&A is usually the part employees actually read, and the part most recaps butcher by compressing an honest answer into a vague line like "leadership addressed concerns about the office move." That tells nobody anything and quietly erodes trust, because people who asked the question know exactly how much got left out.
- Write the answer in full, not a summary of a summary. If the answer included a number, a date or a specific commitment, keep all three in the minutes.
- Decide on attribution before the meeting, not during it. Some companies name who asked, others keep every question anonymous by default so people feel safe asking the uncomfortable ones. Pick one and say so in the minutes, rather than naming some people and not others.
- If a question did not get a straight answer, say that too. "Leadership will follow up on this in writing" is an honest line to write down. Pretending the question was fully answered when it was deflected is the fastest way to make employees stop asking real questions at the next one.
- Carry over unanswered questions. If there was no time to get through every submitted question, list the ones still pending and who owns following up, the same way you would track an action item.
Sharing the recap with people who were not there
An all hands recap only does its job if it actually reaches the roughly one in five employees who typically miss a given session, whether from leave, a client call, or a different time zone for a distributed team.
| Who | What they need |
|---|---|
| Someone who missed it entirely | The full recording or transcript, plus the written minutes as a faster alternative to watching an hour of video |
| Someone who was in the room but distracted | The numbers and decisions sections, since those are the parts people misquote later |
| A new hire joining weeks later | A running archive of past all hands minutes, not just the latest one, so they can catch up on context without asking around |
| Managers | The same recap as everyone else, sent early enough that their team's questions in the next one-on-one do not catch them off guard |
Post the minutes somewhere every employee already checks, a company-wide channel or intranet page, rather than emailing a document that gets buried. And keep an archive. Six months of all hands minutes in one place is one of the most useful things a growing company can hand a new manager on their first week.
Common mistakes that make all hands notes useless
- Writing minutes that assume context. "The migration is finally done" means nothing to someone who never heard it was delayed. Say what changed and why it matters, briefly.
- Dropping the numbers. A vague "we had a good quarter" in the minutes, when the actual meeting shared real figures, leaves nothing for anyone to refer back to later.
- Letting the recap turn into a press release. If leadership said something cautious or uncertain in the room, the minutes should reflect that, not polish it into something more confident than what was actually said.
- No owner for follow-ups. A commitment made out loud in front of the whole company needs a name attached in the minutes, the same as any other action item, or it quietly disappears.
Doing it with an AI meeting notetaker
All hands minutes are tedious to write well precisely because they need to be this complete, which is usually why they end up thin or skipped. An AI meeting notetaker like Zrec can take the typing out of it. Zrec records the all hands from the organiser's own computer, with no bot joining the call, works the same way for a hybrid session with people in a room and others online, and transcribes with each speaker named, which matters most in the Q&A section where knowing who asked and who answered is the whole point. It then writes up a structured summary with the decisions and action items called out separately, and every line links back to the exact moment in the recording it came from, so anyone who wants the full context behind a one-line answer can jump straight to it instead of taking the minutes on faith. For an all hands in Hindi or Hinglish, or a mix of both depending on who is speaking, Zrec still produces the write-up in clear English. Minutes and the recording are available in the browser afterward, which makes it straightforward to share both with the employees who could not attend live.
A checklist before you send your next all hands recap
- Does it include the real numbers that were shared, not a vague summary of them?
- Is every question in the Q&A answered in full, with unanswered ones carried forward and owned by someone?
- Would someone who missed the meeting entirely understand every line without asking a colleague to explain it?
- Is it posted somewhere everyone already checks, and archived alongside past recaps?
- Does every commitment made in the room have a name attached to it?
For the format a smaller internal meeting needs, see our guide on board meeting minutes format, and for tracking the commitments that come out of a meeting like this, our piece on action items from meetings and how to make sure they get done covers the follow-up side in detail. You can read more about how Zrec writes minutes automatically on the Zrec home page.
If an employee has to ask a colleague what actually got said in the all hands, the recap did not do its job. Write it for the person who was not in the room, not the person who was.