Five AI prompts to turn meeting notes into tasks and follow-ups
Five practical AI prompts to capture decisions, create and update tasks, track scope changes, and prepare clear meeting follow-ups, with examples using the Vaiz AI agent.
A meeting ends with a new deadline, a request for phase two, and a promise to unblock a teammate. By the next morning, those agreements need a place in the project: a decision people can find, a task someone owns, or a question that still needs an answer.
These five AI prompts turn meeting notes into a decision record, a task list, a scope update, a one-on-one recap, and a follow-up message. The examples use the Vaiz AI agent. You can adapt the prompts to other AI tools; creating or updating tasks requires a connection to your project workspace.
The examples use illustrative meeting notes from a project status meeting, a weekly sync, a scope discussion, and a one-on-one between a manager and a developer. Sections 2 and 5 include screenshots of the Vaiz agent processing the weekly sync actions and preparing a follow-up.
Choose the prompts that match what came out of your meeting:
Meeting outcome | Prompt | Result |
|---|---|---|
Decisions were made | 1. Capture decisions | A record of decisions, reasons, and open questions |
Actions were agreed | 2. Create or update tasks | Agreed actions linked to new or existing tasks |
Project scope changed | 3. Review scope | Updated scope and recorded deferred requests |
A one-on-one produced support commitments | 4. Capture commitments | Manager and developer actions, plus topics for the next one-on-one |
Others need an update | 5. Prepare a follow-up | A draft recap with task links and any details needing verification |
Give the agent the meeting context
Open a chat with the Vaiz agent. Paste your notes or transcript alongside the prompt, or provide a link to a Vaiz document containing them. If you paste notes directly, replace [meeting notes link] in the prompt with "the notes below."
Include the meeting date, participants, and relevant task or project links. If a deadline is written as "Friday," make the intended date clear. Specify the project and board where task changes should go.
Replace bracketed placeholders with your own details. In the worked examples, also replace the sample names, dates, and project or board names with yours. Include only notes appropriate for the people who can access the destination, especially after a one-on-one.
1. Capture the decisions and why they were made
A useful meeting record explains what the team agreed, why, and what happens next. It also preserves the distinction between an agreed decision and an idea still under discussion.
Example: a project status meeting. On 18 September, the team reviews an onboarding release planned for 22 September. Legal approval for the consent text is still outstanding. The team agrees to move the launch target to 25 September. Maya will request approval by 21 September, and Andrew will update the release plan by 22 September. Adding extra onboarding analytics remains an open question.
Prompt to run in Vaiz:
Read [meeting notes link] from [meeting date] for [project link]. Create a meeting-minutes document in [destination] with the meeting date, participants, confirmed decisions, reasons, agreed next steps, and open questions.
For each decisi
on, include the reason stated in the notes and links to any referenced work. For each next step, include its owner and deadline when explicitly agreed. Mark missing details as "Not specified in the notes." Keep suggestions and unresolved questions separate from decisions.
If the notes have a source link, include it. Otherwise, include the notes in the document so readers can trace each decision. Return the new document link.
The record should make these outcomes clear:
Item | Outcome |
|---|---|
Launch target | Moved from 22 to 25 September |
Reason | Consent text still awaits legal approval |
Maya's next step | Request approval by 21 September |
Andrew's next step | Update the release plan by 22 September |
Open question | Whether to add extra onboarding analytics |
"Request approval" is the action Maya owns. The record should preserve that wording: receiving approval depends on someone else.
2. Turn agreed action items into tasks
Small follow-ups are easy to lose after a weekly sync. Add each agreed action to your work plan with an owner, a deadline, and a place to track progress.
Example: a weekly team sync. Maya agrees to send a revised pricing note by 21 September. Andrew will update the onboarding guide by 22 September; a task for that work already exists. Someone also suggests rebuilding the help center, but the team makes no commitment.
Prompt to run in Vaiz:
Process these notes from our 18 September 2026 weekly sync in Development > AI Features:
- Maya: send the revised pricing note by 21 September 2026.
- Andrew: update the onboarding guide by 22 September 2026. This task already exists.
- Rebuilding the help center was suggested but not approved.
Check existing tasks first. Create or update tasks for agreed actions only, preserving existing descriptions. Do not create a task for the help-center idea. Ask if an owner or task match is unclear.
Return a short table: Created / Updated / Draft | Task | Owner | Due date | Link
List the unapproved idea separately.
What the agent showed in this run:
Meeting item | Visible result |
|---|---|
Send revised pricing note | Task APP-6310 marked Created for Maya, due 21 September 2026 |
Update onboarding guide | Existing task APP-6265 already matched the notes: Andrew, due 22 September 2026; no changes needed |
Rebuild the help center | Listed separately as an unapproved idea; no new task created from this sync |
Andrew's row is labeled "Updated," with the clarification "no change needed - already matched." In this run, checking the existing task was enough; another edit was not needed.
3. Record what changed in the project scope
Scope decisions need a visible boundary. A request discussed during a call can otherwise start to look like a commitment for the current release. Use the scope agreed in your project charter as the starting point when reviewing new requests.
Example: a scope review. A client asks for CSV exports in a reporting feature. The team agrees to keep the current phase focused on the dashboard and place CSV exports in the phase-two backlog. No owner or delivery date is agreed for the export work. The current release target stays unchanged.
Prompt to run in Vaiz:
Compare [meeting notes link] with [current scope document link] and the relevant tasks in [project/board link]. Identify confirmed additions, removals, deferred requests, and unresolved scope questions.
If a person, task, or conflicting detail is unclear, ask before changing the affected fields.
Update [scope document] to reflect only the changes explicitly agreed in the meeting, including the stated reasons and a link to the meeting record. For an agreed deferred request, find its existing backlog task or create one in [backlog destination]. Record the agreed phase without inventing an owner or deadline.
Preserve release dates and active work unless the meeting explicitly changed them. Report what you updated and flag any conflicting information.
The expected result: the scope document keeps the dashboard in the current phase. CSV exports have a phase-two backlog item, with the owner and date left open. The release target remains unchanged.
"Phase two" gives the request a place. It does not establish a delivery date.
4. Capture support commitments after a one-on-one
A manager-developer one-on-one can produce actions for both people. The record should show what the developer will do and what the manager agreed to change or provide.
Example: a manager and developer meet on 18 September. Mark explains that support interruptions are slowing the authentication work. Andrew, the manager, agrees to arrange support coverage by 21 September. Mark agrees to draft an authentication design outline by 24 September. They will review the outline together on 25 September.
Mark also mentions an interest in developing architecture skills. They agree to explore that at their next one-on-one, without setting a training deliverable yet.
Prompt to run in Vaiz:
Read these agreed follow-up notes from the one-on-one between Andrew (manager) and Mark (developer): [notes or document link].
Prepare a recap with four parts: developer commitments, manager commitments, blockers and agreed support, and topics for the next one-on-one. Preserve who committed to each action. Do not infer performance judgments or turn development interests into deliverables.
If a person, task, or conflicting detail is unclear, ask before creating or updating the affected tasks.
For the explicitly agreed project actions, find matching tasks in [project/board link] and update them or create new ones with the agreed owners and dates. Include only the operational context needed for those tasks; do not copy the full one-on-one notes into shared tasks.
Return the recap and the task links, with missing agreements clearly marked.
The recap should distinguish these commitments:
Person | Commitment | Date |
|---|---|---|
Andrew, manager | Arrange support coverage | 21 September |
Mark, developer | Draft the authentication design outline | 24 September |
Andrew and Mark | Review the outline together | 25 September |
The next one-on-one also has a discussion topic: what architecture experience Mark wants to build. That stays a conversation topic until they agree on a specific next step.
Mark's work can be reviewed alongside Andrew's commitment to address the interruptions.
5. Prepare a follow-up people can act on
Once decisions and tasks are recorded, a short follow-up helps participants and other stakeholders find what changed. It should point them to the work and make unresolved questions easy to answer.
Example: follow-up after the weekly sync in section 2. The team needs a short update linking to Maya's pricing-note task, APP-6310, and Andrew's onboarding-guide task, APP-6265. The help-center rebuild remains an unapproved suggestion from this meeting.
Use the chat containing the meeting notes, or paste them again before the prompt. For your own meeting, replace the date and task IDs with your references.
Prompt to run in Vaiz:
Draft a team follow-up from the 18 September 2026 weekly sync above. Check APP-6310 and APP-6265 for context.
Keep it under 180 words. Include the agreed actions, owners, due dates, and direct task links. State that the help-center rebuild was not approved and no task was created. Include a next checkpoint only if one was agreed.
Flag conflicting details rather than guessing. Return a ready-to-share draft. Do not send it or change any tasks.
What the agent showed in this run:
The draft listed Maya's pricing note due 21 September and Andrew's onboarding guide due 22 September, with links to both tasks. It recorded the help-center suggestion as unapproved and stated that no next checkpoint had been agreed.
It also flagged two details for verification:
- Owner identity: the task assignee appeared as an email address, while the meeting notes named Andrew. The agent asked whether they referred to the same person.
- Related work: it found an existing task, MR-2525, titled "Help Center restructuring," and asked whether it concerned the same work as the unapproved suggestion.
Resolve those questions before sharing the follow-up. The earlier help-center task may concern different work; its existence does not mean this meeting approved the rebuild. In section 2, "no new task created" describes the action taken for these notes.
At the next meeting, open the linked tasks to check progress. If stakeholders need the overall state of delivery, use a project summary to put the meeting outcomes in context.
Make the meeting outcome easy to find
After your next major meeting, put the notes in Vaiz and start with the decision-record prompt. Use the remaining prompts wherever the conversation produced tasks, scope changes, support commitments, or updates to share.
Review the owners, dates, and unresolved questions in the result. The meeting record should explain the decisions, while the linked tasks show who is carrying them forward.
Try Vaiz and use these prompts with your next meeting record.
