Copy the template
Use this outline for a project review, customer call or weekly team meeting. Keep one record per meeting. You can download the Markdown template and edit it in your preferred tool.
# Meeting: [title]
Date and time: [include timezone]
Participants: [names or roles]
Purpose: [the decision or outcome needed]
## Summary
[Two or three factual sentences.]
## Decisions
- [Decision] | Reason: [why] | Confirmed by: [owner]
## Action items
| Action | Owner | Due date | Done when |
| --- | --- | --- | --- |
| [Specific next step] | [One owner] | [Date] | [Observable result] |
## Open questions
- [Question] | To resolve: [person or next discussion]
## Next meeting
[Date or trigger; what needs to be ready.]
## Evidence and corrections
[Transcript references or clarification still needed.]Separate discussion from a decision
“We could launch on Friday” is a suggestion. “We agreed to launch on Friday if the rollback test passes” is a conditional decision. Keep the condition in the notes. Removing it changes the meaning and can create an avoidable disagreement later.
If the transcript does not establish agreement, put the item under open questions. Do not turn an AI-generated summary into evidence of approval. Check the relevant passage or ask the participants to confirm.
Write action items that can be completed
“Improve onboarding” is too broad to track. A useful action names a concrete deliverable, a single owner, a due date and the condition for completion. If the meeting did not establish an owner or date, label it “unassigned” or “to confirm”. Do not guess either one.
| Vague note | More useful record |
|---|---|
| Check the issue | Reproduce the sign-in error and attach the steps to the issue; owner and due date to confirm. |
| Talk to the customer | Ask the customer which account and browser were affected; include their answer in the support ticket. |
| Ship this week | Proposed release this week, conditional on the regression check. Final approval still open. |
Review an AI meeting report
Meetingly can generate a report after a listening session. Its sections include an overview, key points, decisions, action items, next steps, follow-up questions and topics. Use those sections as a draft for the template.
- Read the decisions first and compare each with the transcript.
- Check every name, date, quantity and deadline.
- Move uncertain or disputed points into open questions.
- Check that each action has an owner, or explicitly mark the missing owner.
- Remove sensitive material that the recipients do not need.
- Share the reviewed record through your normal team process.
A missing or inaccurate transcript limits the quality of the report. If audio dropped out, say so in the record. Do not silently fill the gap with a plausible account of the conversation.
Use the record in the next meeting
Start the next meeting with the unfinished actions and unresolved questions. Mark actions complete when their observable result exists. If a decision changes, record the new decision and its date so readers can follow the change.
Meetingly’s account dashboard lets connected users review synced meeting history. You can also keep the workflow local. Choose the storage approach that fits the meeting’s privacy requirements; see how transcription, answers and sync differ.