Meeting minutes should record what was decided, who will do what and by when. Keep unresolved questions in a separate section. After the meeting, you should not have to guess whether a remark was an assignment, a suggestion or simply part of the discussion.
Below is an example from a short team meeting and a blank TXT template you can save and fill in. It is intended for working notes. If your organization has an approved form, transfer the information into that form.
What to include
Start with the meeting title, date and participants. List the topics if several were discussed. This makes the document easier to find when you need to check a particular decision later.
Divide the main record into three parts:
- Decisions. What the participants have agreed on.
- Actions. The result needed, its owner and its deadline.
- Open questions. What still needs an answer and who will follow up.
You do not need every spoken sentence when the goal is a practical record of outcomes. Keep the reason for a decision when it explains a limit or choice. For example: “Publish without customer testimonials because permission to use them has not yet been obtained.”
Example meeting minutes
This is a fictional example: a team is preparing a new service page. The names, dates and agreements are illustrative.
Service page launch meeting
Date: November 16, 2026, 10:00–10:25 a.m.
Participants: Anna, project lead; Ian, editor; Maria, designer; Oliver, developer.
Topic: page content and preparation for a planned November 20 launch.
Decisions
- The first version will include a service description, pricing and an enquiry form.
- Customer testimonials are postponed. Anna will obtain permission to publish them first.
- The final publication decision will follow the form test on November 19.
Actions
- Ian: send approved page copy to Maria by November 17 at 3:00 p.m. Deliver a document containing the service description, pricing and form field labels.
- Maria: send mobile and desktop designs to Oliver by November 18 at 6:00 p.m. Use Ian's approved copy.
- Oliver: build the page and test form submissions by November 19 at 4:00 p.m. Tell the team where enquiries arrive and attach the test result.
- Anna: review the finished page and confirm publication or set a new date by November 19 at 6:00 p.m.
Open question
Can customer testimonials be added? Anna will check permissions and report back by November 23. This does not block the first version.
Next check-in: November 19 in the team conversation. If the form does not work, reconsider the publication date.
The November 20 launch remains a plan, not an unconditional promise. The minutes preserve its conditions: a form test and Anna's approval. Writing only “Publish on November 20” would lose part of the agreement.
Turn discussion into a clear action
A meeting may produce the remark “We should update the page.” That is not enough for an action record. What needs changing? Who will do it? How will everyone know it is ready?
A clearer version is: “Ian will update the service description and pricing and send the copy to Maria by November 17 at 3:00 p.m.” It identifies an action, a deliverable, an owner and a deadline.
If no owner or deadline was agreed, do not invent one afterward. Write “owner not assigned” or “deadline to be agreed,” and flag the item for clarification. An explicit gap is more useful than a fictional agreement.
Distinguish suggestions from decisions. “We could try launching on Friday” does not mean “We are launching on Friday.” If the wording is ambiguous, check before the meeting ends: “Have we agreed to do this?”
Create minutes from a recording
If you have a recording, obtain a transcript of the relevant part first. Find the moments when participants make decisions, assign actions and name deadlines. The opening discussion may contain no final agreements, so you do not always need to start at the beginning.
The audio-to-text tool accepts one file of up to three minutes and 20 MB per day without registration. For a long meeting, choose a short excerpt in advance. This free web tool is not intended for an entire hour-long meeting.
Check names, numbers, dates and negatives against the audio. If it is unclear who accepted a task, flag it for confirmation. A transcript helps locate what was said, but does not itself prove that the participants agreed to a particular interpretation.
Sort the resulting points into the template's three sections. When shortening a long discussion, keep important conditions next to the decision. This text-shortening guide shows how a shorter version can accidentally change the original meaning.
Review before sharing
Check each action. Does it have a clear deliverable, one owner responsible for handing it over and an agreed deadline? Are dependencies visible? In our example, the designer needs the copy and the developer needs the designs, so those handoffs are stated explicitly.
Review the open questions too. A question at the bottom of the page without an owner or a follow-up date is easy to forget. Name the person finding the answer, or explicitly state that this still needs to be decided.
When sharing the minutes, ask participants to check their actions and deadlines. Clarify discrepancies and update the document. Before the next meeting, return to the same list and mark what was completed, what moved and why.