Templates
Meeting action items template
Turn a conversation into a reviewable list of tasks without guessing owners or deadlines.
By Eavesy · 3 min read · Updated
On this page
Fill in the fields below, or download the blank Markdown and use it in your own editor.
Make it yours
Build your meeting action items
Separate accepted work from requests awaiting agreement. Use one task per line.
This website tool formats what you enter; it does not use AI or submit these fields to Eavesy. Drafts stay in this page’s memory and disappear on reload.
Clear existing fields before loading an example. Restore keeps only the most recently cleared draft and is available when fields are empty.
Markdown preview
# Meeting action items
## Meeting and source
[Not provided]
## Agreed tasks
[Not provided]
## Requests awaiting agreement
[Not provided]
## Dependencies
[Not provided]
## Review notes
[Not provided]
Use this template after a meeting when you need a portable checklist with enough source context to verify it. It keeps agreed tasks separate from ideas and requests that have not been accepted.
Write a concrete task
Start each task with the action and the deliverable. “Send the revised pricing slide” is easier to verify than “pricing.” If one sentence includes several independent actions, split them into separate rows.
Confirm ownership
A person discussing an issue has not necessarily agreed to own it. Copy an explicit assignment or leave the owner unassigned. Apply the same rule to dates: a date mentioned elsewhere in the meeting is not automatically the due date for every action.
Example row
Task: send the revised deck. Owner: Sam, if Sam explicitly accepted it. Due date: Thursday, only if that deadline was agreed. If the source merely says “ask Sam whether the deck can go out Thursday,” place it under requests awaiting agreement instead.
Keep enough evidence
Use a timestamped passage or an accessible transcript reference. If the notes will leave your Mac, replace a private local path with an attachment or a shared source the recipient can open. Check sensitive material before forwarding any recording.
Use it with Eavesy
Review the completed brief and transcript, then fill the table. Eavesy's generated action items can help you find candidate tasks, but verify the source before treating a suggestion as a commitment. This downloadable template is a manual Markdown artifact, not a new task-sync integration.
Keep the checklist in your project notes and update its status as work happens. Preserve the source reference so changes in scope or ownership remain understandable later.
Use the editor or keep your own file
The editable form on this page produces a Markdown draft from your fields. Load fictional example shows a teaching scenario; replace its facts before using the output. Copy your draft includes your edits, while the blank download above remains available if you prefer your own editor. Reloading the page clears the in-page draft, so copy or download it before leaving.
Review before you share
Read the preview as if you were the recipient. Can you open each cited source? Are expectations separate from observations? Does every assignment or deadline come from evidence? Leave missing information explicit. A well-formatted note still needs source review before it becomes an issue, commitment, or instruction to act.
Copyable template
# Meeting action items
## Source
- Meeting title:
- Date:
- Recording or transcript reference:
## Agreed tasks
| Task | Owner | Due date | Source passage or timestamp | Status |
| --- | --- | --- | --- | --- |
| [Concrete action] | [Assigned person or unassigned] | [Agreed date or not set] | [Evidence] | Open |
## Requests awaiting agreement
- [Who requested what, and what still needs confirmation?]
## Dependencies
- [What must happen first?]
## Review
- [ ] Each task was actually requested or agreed.
- [ ] Owners and dates match the source.
- [ ] Unknown fields are marked as unknown.
- [ ] Source references can be opened by the recipient.