Nobody reads meeting notes. They read decisions and they scan for their own name. Write for those two behaviors and your summary becomes the most-read document your team produces; write a chronological recap and it becomes a file nobody opens twice.
01Lead with what was decided
Open the summary with a block titled Decisions, one line per decision, written as fact: pricing moves to annual billing in September, the launch slips one week, the vendor contract is not renewed. No attribution, no journey, no we discussed. If the meeting decided nothing, say so in one line; that sentence has a way of improving the next meeting.
02Actions: owner, verb, date
The second block is Actions, and each entry has exactly three parts: who, does what, by when. Maria sends the revised proposal by Thursday. Unowned actions do not get written down, they get resolved in the room: ask who owns it before the meeting ends. The summary is where that clarity gets recorded, not where it gets invented.
03Context in one line per topic
After decisions and actions, give each topic that was discussed a single line: what it was and where it landed. The two candidates for the API redesign were compared; a decision is expected next week. This is for the person who was not there and the attendee who was multitasking. Resist quoting the discussion; a summary that relitigates the debate reopens it.
04Ship it while the meeting is warm
A summary sent the same day gets read and corrected while everyone still remembers; a summary sent three days later gets skimmed and disputed. Set a personal rule of 24 hours. If you work from a recording or transcript, summarize from the transcript's decision points, not from its timeline, and delete the transcript reference once the summary is confirmed. The summary is the record; the recording is scaffolding.
Should meeting summaries include who said what?
Rarely. Attribution invites relitigation and makes people guarded in the next meeting. Record decisions and owners, not the debate. The exception is a formal setting where positions must be on the record.
How long should a meeting summary be?
For a one-hour meeting, ten lines is usually enough: three decisions, four actions, three lines of context. If it runs a page, it is a recap, not a summary.
Can I generate the summary from a transcript automatically?
A tool gets you a solid draft fast, and this site's free summarizer works well on pasted transcripts. Keep two manual steps: verify the decisions are stated as the room understood them, and confirm each action's owner and date. Those two checks are the part your team is trusting you for.
Summarizing at volume, not one page at a time?
Summarize Pro batches PDFs, papers and reports, every key claim cited to its source page, exports to Word or Excel. The free tool is for one page; Pro is for the pile.