Write for the person who needs to act
A meeting summary is not a transcript. Its job is to help participants remember what they agreed to and help anyone who missed the meeting understand what happens next. That means selecting the information people need for decisions and follow-through, rather than preserving every point in the order it was spoken.
Before writing, imagine a reader opening the summary several days later. Can they tell which decisions are settled? Can they find their own tasks without interpreting a long account of the discussion? Can they see what is still uncertain? If the answer to any of these is no, the summary needs clearer labels or more specific wording.
Start with the meeting’s purpose in one sentence. Then put the outcome near the top: the group approved a plan, chose between options, deferred a decision, or met to gather input. A meeting that ends without a decision can still have a useful summary, provided it says what is open and how the group plans to resolve it.
Separate decisions from discussion
People often leave the same meeting with different impressions because an idea sounded popular but was never formally agreed upon. Prevent this by separating confirmed decisions, proposals and open questions. Use direct language for a decision, such as “The team will use the shorter intake form.” For an unsettled idea, say “A shorter intake form was proposed; the team has not decided whether to use it.”
Brief context can explain why a decision was made, but avoid reproducing the whole debate. Record the main consideration when it will help a future reader understand the choice: for example, “The team chose the shorter form to reduce the number of fields people must complete.” If there was no shared reason, do not invent one. Likewise, do not describe silence as agreement unless the group actually used that convention.
When a decision depends on a condition, include it. “Launch the draft after the accessibility review” is different from “Launch the draft.” Small qualifications can determine whether someone acts at the right time. If a decision was reversed or replaced during the meeting, record the final outcome rather than leaving contradictory statements in the summary.
Make every action item assignable
An action item should answer three questions: What will be done? Who is responsible for moving it forward? When is an update or completed result expected? “Review the draft” is easy to overlook. “Maya will review the draft and send comments by Thursday” gives the group a task it can check. If the meeting did not establish a deadline, write “date to be confirmed” rather than choosing one on someone else’s behalf.
Name one person as the point of responsibility for each item when possible, even if several people will contribute. This does not mean that person must do all the work; it tells others who will coordinate it. If ownership is unresolved, make that gap visible: “Owner needed for the customer FAQ; Alex will identify one before the next check-in.” Avoid assigning work to someone who did not accept it without first confirming.
For larger tasks, specify the next deliverable instead of a vague ambition. “Prepare a one-page comparison of the two options” is more actionable than “Improve the process.” If a task cannot begin until another step is complete, note that dependency so the owner and readers share the same expectation.
Keep the format easy to scan
A consistent order makes a summary useful even when readers have little time: purpose and outcome, decisions, action items, open questions, and any essential context. Include the meeting date and a descriptive subject so the summary can be found later. You can keep routine meeting notes short; length should reflect the number and complexity of the outcomes, not the duration of the conversation.
Use the same terms the group uses for projects, documents and teams. If two similar names might be confused, spell out which one you mean. Plain, neutral wording also helps. “The group needs more information about cost” is clearer and less charged than a description of who was unprepared. Mention disagreement when it affects a pending choice, but focus on the substance of the unresolved issue rather than characterizing people.
Check the summary before it becomes the record
Send the summary while participants can still recognize the discussion, and invite corrections to decisions, owners and deadlines. This is especially important when a meeting moved quickly or an absent person was assigned a role. A simple request such as “Please flag anything I have recorded incorrectly” leaves room to fix misunderstandings without reopening every topic.
Before sending, do a final pass from the perspective of someone who was not in the room. Look for verbs such as “consider,” “support” and “handle” that may hide whether something was decided or assigned. Check that each action has an owner, each deadline is one the group established, and each open question has a path toward resolution. A good summary does not make a meeting seem more conclusive than it was. It makes the outcome clear enough for people to take the right next step.
