ARTICLE
Meeting Notes Template: Decisions, Owners and Next Steps
Tapquence Editorial
·
5 min read
Editorial week of
A record people can use
D
Decisions
What was agreed, including conditions.
A
Actions
The next step, owner and confirmed date.
Q
Open questions
What still needs an answer.
KEY TAKEAWAY
Keep decisions, actions and open questions separate. Leave uncertain owners and dates visible rather than filling the gaps.
A meeting notes template should make the next step easy to find. The most useful record is usually the decision, the reason it matters, who will act and what is still unresolved. It does not need to be a polished account of every minute.
Copy the format below into your preferred notes app. Use it while listening, or fill it from a reviewed transcript after the meeting. The structure stays the same either way.
1. Copy this meeting notes template
Keep the header short and give decisions and actions their own space. If a section is genuinely empty, say so or remove it rather than inventing something to fill the page.
MEETING NOTES
Copy and adapt
Meeting:
Date and time:
Participants:
Purpose:
CONTEXT
What does the reader need to understand the discussion?
DECISIONS
Decision | Reason or condition | Who confirmed it
ACTION ITEMS
Action | Owner | Due date | Status
OPEN QUESTIONS
Question | Who will clarify it | Next check-in
NEXT STEP
Where the notes will be shared and when to follow up
This is a text format for your notes, not an automation recipe. If you also want a recording and transcript, the Audio Notetaker setup template serves that separate purpose.
2. See a completed example
The example below is a fictional client review. Notice that a confirmed design choice, a requested task and an unresolved launch date have different labels.
CLIENT PROJECT REVIEW
Fictional example
Purpose
Choose an onboarding direction for the prototype.
Context
The team reviewed a short and a detailed onboarding flow.
Decision
Use the short flow for the next prototype, subject to accessibility review.
Action
Maya to send revised screens by 24 September. Maya confirmed the task and date during the meeting.
Open point
The launch date is not agreed. Ellis will check the dependency with engineering.
Follow-up
Share reviewed notes with the project group and revisit the dependency at the next check-in.
The condition matters. Dropping “subject to accessibility review” would make the decision look more final than it was. Similarly, checking a dependency is not the same as confirming a launch date.
3. Write action items people can actually use
Start an action with a concrete verb and a clear object: “Send the revised onboarding screens” is easier to act on than “Design follow-up”. Add the owner and deadline only when they have been agreed.
From vague note to useful action
Vague
Useful
Check pricing
Jordan to confirm the revised service price with finance; due date not yet agreed.
Website done Friday
Team aims to finish the website on Friday, pending final copy approval.
Client approved
Client approved option B for the prototype, excluding the payment screen.
If the meeting did not name an owner, write “Owner to confirm”. If somebody suggested a date and nobody accepted it, leave it as a proposal. Making uncertainty visible helps the team resolve it; hiding it inside a tidy table does not.
4. Adapt the format to the meeting
For a team check-in, shorten the context and focus on blockers, owners and next steps. For a client review, preserve approval conditions and exclusions. For a one-on-one, agree which notes are shared and keep sensitive personal material out of a general team record.
You do not need a different system for every meeting. Add one useful section when the situation requires it, rather than adding ten fields nobody will maintain. The test is whether a reader can answer: what changed, what happens next, and what still needs a decision?
5. Fill the template from a transcript
A transcript can help you recover a detail you missed while participating. Audio Notetaker keeps a session’s recording, transcript and recap available for review on your Mac.
Read the relevant passage before moving a statement into the template. Check names and numbers against the recording, and separate ideas discussed from decisions made. A recap can be a useful starting point, but it still needs a person to check what the meeting actually established.
Keep the source and the working notes distinct
Preserve enough source material to verify an important statement. Edit the working notes for clarity without changing the meaning of a condition, commitment or unresolved question.
For the recording workflow and permissions, use the Notetaker setup guide. The template on this page works just as well with manual notes; recording is an optional input, not a requirement.
6. Review before sharing
Check that decisions include any limits or conditions.
Confirm owners and deadlines instead of inferring them.
Keep unresolved questions in the open section.
Remove irrelevant personal details.
Share with the intended readers and explain how they can flag a correction.
Use a short recap email when people need a quick update, and link to the fuller notes in an approved location. Good meeting notes leave enough context to act confidently without making everyone reread the whole conversation.
Common questions
Are meeting notes the same as formal minutes?
Not necessarily. This format is a practical working record. If your organisation requires formal minutes, follow its approval, attendance and recordkeeping process.
Should I include a transcript in the notes?
Usually a short, reviewed record is easier to use. Keep the transcript as source material where appropriate, and share it only when readers need that level of detail.
