Draft a summary and proposed action list, then confirm the commitments before creating tasks or sending follow-up.
Trigger and approved inputs
Begin with approved notes or a recording that participants understand and are permitted to use for this purpose. Include the meeting date, participant names where appropriate, and any agreed vocabulary. Keep incidental sensitive material out of the initial pilot.
The steps
Keep each stage visible and preserve the evidence needed for the next one.
- Prepare a transcript or organized notes and mark uncertain passages.
- Extract proposed decisions, actions, owners, and dates with supporting passages.
- Separate suggestions from explicit commitments and leave missing owners or dates unresolved.
- Have participants or the meeting owner correct and confirm the list.
- Create tasks or send follow-up only through the approved process after confirmation.
The human checkpoint
The meeting owner checks the evidence and confirms that an action was actually agreed. A generated owner or deadline must not quietly become a person’s commitment. Keep a way for participants to correct the record.
Test before making it routine
Use samples with no decision, conflicting dates, a hypothetical suggestion, and a name the transcript mishears. Check whether the draft distinguishes uncertainty. Measure correction effort as well as drafting time.
When the process should stop
Pause if permission to use the input is unclear, the transcript is too unreliable, or the person who can confirm the commitments is unavailable. Do not send or create final tasks while these conditions remain unresolved.
Would an agent help?
A fixed workflow is usually a sensible starting point. An agent could help locate a referenced document, but it needs a defined source boundary; it should not infer missing commitments from unrelated information.
Sources and verification
Building effective agents · Anthropic