Use this when a meeting produced useful discussion but unclear ownership.
| Best for | project managers, assistants and team leads |
|---|---|
| Final output | a clean action table with owner, deadline, decision, risk and follow-up summary |
Why this workflow works
This playbook turns one broad AI request into a reviewable sequence. It asks the user to prepare source material first, then uses AI to organize the work, expose missing details and produce a draft that can be checked by a human editor.
For project managers, assistants and team leads, the value is not only speed. The value is a repeatable process: the same inputs, the same review points and the same standard for deciding whether the AI output is ready to use.
What to prepare before running it
- The real business or content goal behind the task.
- Source facts, notes, examples or policies the AI is allowed to use.
- Audience context and channel where the output will appear.
- Boundaries: claims to avoid, facts to verify and details that are unknown.
- The format you want at the end, such as a clean action table with owner, deadline, decision, risk and follow-up summary.
Workflow steps
- Paste raw notes and identify the meeting goal.
- Ask AI to separate decisions from discussion.
- Extract action items with owners and missing owners.
- List risks, blockers and unanswered questions.
- Draft a follow-up message for participants.
Copy-ready prompt
Act as a project coordinator. Turn these meeting notes into a clean summary: [notes]. Return decisions, action items, owner, deadline, risks, unresolved questions and a short follow-up email. Mark missing owners or dates instead of inventing them.
Replace the bracketed fields with your actual source material before using the prompt. If a field is unknown, leave it as unknown and ask the AI to return missing-information questions instead of inventing details.
Example input fields
| Context | Describe the real task, source material and business situation. |
|---|---|
| Audience | Name the reader, buyer, customer, stakeholder or internal team. |
| Constraints | Include claims that must be avoided, facts that must be checked and format limits. |
| Review | Ask for assumptions, missing questions and a checklist before using the output. |
Evaluation rubric
| Clarity | The answer should make the next action obvious without requiring a second explanation. |
|---|---|
| Specificity | The answer should use the provided context and avoid advice that could fit any business. |
| Evidence | Claims, examples and recommendations should be traceable to source material or marked for review. |
| Usability | The final structure should be easy to copy into a document, page, email, ticket or planning tool. |
Common mistakes
- Inventing owners or deadlines.
- Mixing discussion points with decisions.
- Forgetting blockers and open questions.
- Sending the follow-up without confirming sensitive details.
Human review checklist
- Check whether every claim is supported by source material.
- Remove details that the AI guessed.
- Confirm the output matches the intended audience and channel.
- Keep a copy of the source input with the final prompt.
- Revise the prompt when the same issue appears twice.