Meeting workflow
Turn discussion into actions without inventing agreement.
Turn meeting notes into traceable decisions, realistic action lists and useful follow-up with ChatGPT or Claude.
Updated
Separate a proposal from a decision
A meeting contains suggestions, objections, tentative plans and final decisions. A concise summary can accidentally turn the loudest suggestion into an agreed action. Tell the assistant how to classify each and require a reference to the notes or transcript.
Use a transcript only when recording and sharing it is authorised. A short, approved note may be enough; do not include personal material simply because it was captured.
Use these meeting notes to separate decisions, proposals, open questions and actions. Reference the relevant passage for each decision. If agreement is unclear, mark it for confirmation rather than presenting it as settled. Preserve important objections.
Give each action a usable shape
‘Improve onboarding’ is not a complete action. The owner needs an observable output, scope and timing. Do not let the assistant invent a person or deadline to make the table look finished.
Illustrative scenario: the team agrees that a handover checklist is missing but never assigns ownership. The correct action register shows the gap. A follow-up message can ask for the owner; it should not silently allocate the task to someone mentioned nearby.
Build an action register with output, named owner, agreed deadline, dependency and source reference. Use ‘not assigned’ or ‘not agreed’ for missing details. Highlight actions that cannot begin until another decision is made. Do not infer ownership from who raised the issue.
Make the follow-up easy to correct
Send a draft that distinguishes confirmed items from questions. Let recipients see where a correction is needed. Avoid saying everyone approved the summary unless that approval actually happened. External sending is a separate action requiring the relevant authority.
Draft a follow-up email from the verified register. Lead with confirmed decisions, then actions, then items needing confirmation. Keep disputed points visible. Do not claim consensus where the notes show uncertainty. Return a draft for my review, not a sent message.
Use the next meeting to resolve the blockage
The next agenda should not merely repeat the previous topics. Identify the decision each item needs, the preparation required and the person who can supply it. If an item is only a status update, ask whether a written update would be enough.
Create the next agenda from these unresolved items. For each, specify the decision needed, preparation, responsible contributor and proposed time box. Label proposed timing as a suggestion. Remove items that require no discussion unless there is a stated reason to include them.
Common questions
Should AI assign missing action owners?
No. It can flag the gap and draft a clarification request. Ownership and deadlines should reflect actual agreement.
What is more useful than a meeting summary?
A traceable decision record and action register may be more useful when the goal is execution. Keep discussion context where it explains a decision or unresolved risk.
Keep exploring
About this workflow
This is an original AI-assisted editorial workflow. Illustrative scenarios are not customer case studies, and the prompts have not been systematically evaluated on live models. Check consequential outputs against your sources and use qualified review where needed.