Discord meeting notes: template and example

What to include in your meeting notes

For a standup or planning call, start with these four sections:

1. Decisions: what was agreed and why.
2. Action items: what needs to be done, by whom, and by when, if a deadline was agreed.
3. Open questions: what remains undecided, and who will bring back the missing information.
4. Context: the meeting date, participants, and a link to the source notes or transcript, if available.

“We discussed onboarding” is a topic. “We will test a shorter onboarding flow with five users” is a decision. “Alex will send the test plan by Thursday” is an action item.

A Discord meeting notes template you can reuse

Copy this into a Discord forum post or your team’s document. Remove fields that do not apply. If nobody agreed on an owner or a deadline, write “unassigned” or “not agreed” instead of filling the gap with a guess.

The “done when” field is especially useful for vague commitments. It describes the expected result, such as “post the reproduction steps and a proposed fix.” Agree on that result with the person doing the work before adding it to the notes.

Example: release planning notes

In this fictional call, the team agrees to delay a release and assigns the follow-up work. The notes below use only details from that conversation.

If Alex had only said “I’ll look into it,” the notes should say “Investigate the onboarding issue; deadline not agreed.” A more detailed template is not a reason to invent a deadline or extra work.

Confirm the notes before ending the call

Before everyone leaves the voice channel, read back the decisions and tasks. People can correct a misunderstanding while they are still there.

• Ask each person to confirm their task and deadline.
• Check that the date means the same thing across time zones. Use a specific date where “tomorrow” could be ambiguous.
• If someone is blocked, note what they need and who can help.
• Mark unresolved decisions as “not decided” and note what the team still needs to agree on.

Keep the notes in a dedicated forum or channel and share the link in the project chat. Use the meeting title and date in the post title so people can find it later.

Using Vyach for meeting notes and tasks

Vyach joins your Discord voice channel, records consenting participants, and transcribes the audio. After you end the meeting, it posts a summary covering decisions, action items, blockers, open questions, and next steps. See the Discord transcription setup guide for the setup commands.

Community and Pro include custom summary templates. Use section names that match your team’s notes, and ask Vyach to mark missing owners or deadlines as unspecified.

On Pro, Vyach can create a separate task forum post for each action item, including owner, deadline, and priority when available. Create a tasks forum in Discord, select it with /settings channels, then enable task creation with /settings tasks. Setup does not create that forum automatically.

Check the current plan limits and the task setup guide for details.

Review outstanding tasks at the next meeting

Open the previous notes before adding new topics. Check which tasks are done, blocked, or no longer needed. If the group reverses a decision, record the new decision and why it changed.

If you need to check an earlier discussion, ask Vyach in Discord. For example: @Vyach #backend why did we postpone the release? Follow the cited meeting to check the context. Answers are limited to retained meeting data and your plan’s question allowance.