Meeting Notes Template: Decisions, Owners, and Next Actions
Copy a practical meeting notes template, see a completed example, and turn discussion into decisions and actions with clear owners and dates.
A useful meeting notes template records the purpose, key decisions, action owners, due dates, and unresolved questions. It should let someone who missed the meeting understand what changed and what happens next. You do not need a transcript of every comment to create that record.
Copy the structure below or download the plain-text template. It opens in an ordinary text editor and can be pasted into Word, Google Docs, or your team's existing workspace without creating an account.
Table of contents
- What belongs in your meeting notes?
- What does a completed example look like?
- How do you take notes while participating?
- How should you close and share the record?
- How do notes become work that gets done?
- Frequently asked questions
What belongs in your meeting notes?
Include enough context to understand the decision and enough detail to carry out the next action. Leave out repetition, conversational detours, and personal commentary that does not help the team act.
Atlassian's meeting-notes guidance includes attendees, agenda, discussion, decisions, and action items. The template here emphasizes the last two so they do not disappear inside a long narrative.
| Field | What to capture |
|---|---|
| Meeting | Title, date, and purpose |
| People | Participants, note taker, and relevant decision maker |
| Context | Links to the agenda and documents discussed |
| Decisions | What was agreed, why, and any stated condition |
| Actions | Specific outcome, one accountable owner, due date |
| Open questions | What remains unknown and who will resolve it |
| Next review | When or where the team will check progress |
The downloadable version contains these headings and blank spaces to fill. Keep the same structure across recurring meetings so readers know where to look.
For each action, ask whether a person could finish it without reopening the entire discussion. “Website” is a topic. “Send the revised homepage draft to Priya for approval by Thursday noon” is an action.
Microsoft's meeting task-list documentation also distinguishes task names, assignees, and due dates. Those three fields are a useful minimum even when you are using paper instead of software.
What does a completed example look like?
A completed note separates decisions from tasks and keeps uncertainties visible. Here is an original fictional example for a small digital-product team; its dates and details illustrate the format rather than report a real project.
Meeting: Welcome guide release check, October 6, 2026
Purpose: Decide whether the revised guide is ready for Friday's release.
Participants: Priya, the product owner; Alex, the writer; Sam, customer support.
Note taker: Alex.
Context: Revised welcome guide, version 3; support questions from the previous release.
Decision: Release the guide on Friday only after the download link and mobile layout checks pass. Keep the existing guide available until the replacement has been verified.
Reason: The content is approved, but the team has not yet confirmed the final delivery link. Content approval does not establish that customers can obtain the file.
| Action | Owner | Due | Completion evidence |
|---|---|---|---|
| Verify the new download link | Sam | Thursday noon | Link opens the correct file |
| Check the guide on a phone | Alex | Thursday afternoon | All pages readable, no cropped text |
| Confirm the release decision | Priya | Friday morning | Approval recorded in the release note |
Open question: Does the receipt email link to the old guide? Sam will check this alongside the download link and report any mismatch.
Next review: Priya reviews the three completion records before the Friday release. Any failed delivery check moves the release back; the team does not treat silence as approval.
This example uses the decision-and-action distinction described in Atlassian's template, but adds completion evidence. That extra column makes “done” observable instead of merely reassuring.
How do you take notes while participating?
Capture short labels during the conversation, then clarify them before the meeting ends. Trying to write polished paragraphs in real time can make you miss the actual decision.
Use a simple three-label shorthand:
- Decision: An agreed choice, with a condition if necessary.
- Action: Something a named person will deliver.
- Question: An unresolved issue that needs an answer.
If someone says, “We probably need to simplify onboarding,” record it as a question or proposal until a decision is made. Do not convert a passing suggestion into a commitment on someone else's behalf.
Ask short clarification questions: “Are we deciding that now?” “Who owns the next step?” “What date should I record?” These interruptions are useful because they expose ambiguity while the relevant people are still present.
For collaborative notes, Microsoft explains that Teams attendees can edit notes and assign agenda items or tasks. Shared editing can distribute the work, but it does not eliminate the need to confirm the final decision.
If you are facilitating a difficult discussion, assign a separate note taker when possible. If that is not possible, pause briefly at each decision and summarize aloud. A clear pause is better than a beautifully formatted record of the wrong agreement.
How should you close and share the record?
Read the decisions and actions back before people leave, then share the notes where the team expects to find them. Confirm disagreements explicitly rather than assuming that no objection means everyone agrees.
Reserve a short closing check appropriate to the meeting. Two minutes may be enough for a small team; a complex meeting may need longer. This is a working suggestion, not a research-backed universal rule.
Ask:
- Did we record the actual decision, including conditions?
- Does each owner accept the task and timing?
- Which questions still block progress?
- Where will updates be posted?
Share the record with the people who need it. Remove unnecessary personal details and check access before sending links to clients or outside collaborators. Microsoft notes that external attendees cannot access or edit Teams meeting notes, so an internal note link may not serve an external participant.
When someone corrects the record, preserve a clear revision rather than leaving conflicting copies in circulation. “Decision corrected after review” is more useful than silently changing what others have already acted on.
How do notes become work that gets done?
Move your owned actions into the place where you plan work, then check capacity before promising delivery. A meeting can assign ten tasks without creating ten additional hours in your week.
For example, if Thursday already contains customer support and a deadline, a new review task needs a tradeoff. Clarify which commitment moves, whether the scope can shrink, or whether another owner is appropriate.
Use task prioritization to choose among competing actions and weekly planning to reserve realistic time. If recurring meetings create little usable output, the meeting cost calculator can help quantify the time commitment using your own assumptions.
Avoid keeping two independent action lists. Microsoft describes how meeting tasks can synchronize with Planner; if you use another system, link the task back to the note and choose one place for status updates.
Do Only 3 Things a Day adds a daily selection and review loop, a printable card, and a seven-day start. The notes establish what the team needs. The daily plan establishes what you can responsibly move today.
Frequently asked questions
Are meeting notes the same as formal minutes?
Not always. This template is for ordinary working meetings. Boards, committees, and regulated organizations may require formal minutes, approvals, or records under their own rules. Use the required format in those settings.
Should I write down every word?
Usually not for a working meeting. Capture decisions, reasons, commitments, and unresolved issues. If an exact statement matters, confirm the wording with the speaker rather than reconstructing it later.
Can I use the template in Word or Google Docs?
Yes. Copy the headings or paste the downloaded text into either application. Add your team's usual formatting and sharing settings. The structure does not depend on a particular app.
What if an action has no owner?
Record it as unresolved and ask who will own the next step. A task assigned to “everyone” often leaves responsibility unclear. Do not silently choose a person who has not agreed to take it.