This guide gives you a reusable starting pattern. It is designed to help you see the work more clearly; it is not a substitute for judgment, source checking, or responsibility for the result.
Prepare the inputs before you ask for output.
The model only sees what you give it. Spend a few minutes naming the reader, desired result, and uncertain information. This makes a first draft easier to assess and reduces the need for decorative rewriting later.
Give the task a useful brief.
Turn the meeting record below into a decision brief. Meeting purpose: [why the meeting took place] Participants and roles: [only what is known] Confirmed decisions: [paste decisions with source labels] Open questions and disagreements: [paste unresolved items] Actions, owners, and dates: [only if explicitly stated] Relevant evidence or links: [paste labeled sources] Return: (1) decision question, (2) confirmed decisions, (3) evidence and source labels, (4) unresolved questions or disagreements, (5) stated actions with owners and dates, (6) requests for a decision owner, and (7) a short follow-up message. Keep agreement separate from discussion. If an owner, date, approval, or decision is not explicitly stated, mark it “Not confirmed.” Do not invent commitments, consensus, citations, or next steps.
Replace every bracketed field with your real context. Read the output before reuse.
Four steps that keep the result usable.
- 1
Start from the meeting record and preserve source labels rather than summarizing from memory.
- 2
Separate confirmed decisions from suggestions, questions, and disagreements.
- 3
Keep only explicitly stated owners and dates in the action section.
- 4
Ask the decision owner to verify the brief before it becomes the project record.
A brief should expose the decision boundary
Meeting conversations mix context, proposals, concerns, and conclusions. A useful decision brief makes the boundary visible: what the group actually confirmed, what it discussed without deciding, and what question still needs an accountable person.
Do not confuse a strong suggestion with agreement
A participant may recommend an option without the group accepting it. Preserve the difference between a proposal, an objection, a question, and a confirmed decision so the follow-up does not create consensus that was never recorded.
Keep actions tied to stated ownership
A clean action list is not permission to assign work. Include an owner or date only when the meeting record states it. Otherwise, make the missing confirmation visible in the brief and follow-up message.
Use the brief as a review surface
The first draft should help the meeting owner check the record, not replace that check. Invite corrections to decisions, sources, disagreements, and next requests before the brief is shared as an official account.
A worked example: a roadmap decision
A roadmap meeting produced a strong suggestion — “move the migration to Q1” — but no confirmed vote. The brief lists that as an open question with the supporting comment labeled by speaker, and keeps the confirmed items separate. The follow-up then asks the decision owner to confirm or defer the migration, instead of treating a suggestion as agreement.
Link the brief to the record
A decision brief is a view over the meeting record, not a replacement for it. Keep the source note or timestamp beside contested claims so the meeting owner can verify wording quickly. When the brief points back to the record, corrections are easier to make and the brief stays trustworthy.
Run a human check.
- Can a reader distinguish confirmed decisions from proposals and unresolved questions?
- Does every material claim retain a source label or a visible missing-evidence marker?
- Are owners and dates included only when explicitly stated?
- Does the follow-up ask for a specific confirmation instead of implying consensus?
- Has the meeting owner reviewed the brief before it becomes the project record?
Download a meeting record template.
A plain Markdown template for separating confirmed decisions, actions, open questions, and details that still need confirmation. It contains no tracking or external requests.
Questions readers usually ask.
Use these checks when turning incomplete notes into a brief that another person can verify.
What should a meeting decision brief include?
How do I turn meeting notes into action items without inventing agreement?
Can AI summarize a meeting when the notes are incomplete?
What is the difference between meeting minutes and a decision brief?
How should I review an AI-generated meeting summary?
AI is strongest here when it makes missing information, structure, and options easier to see. The moment an output becomes a claim, commitment, or decision, bring a person back into the loop.