AI Meeting Notes and Decision Log System Builder

Design a repeatable AI-assisted meeting notes system with decision logs, action ownership, source links, follow-up cadence, and audit-friendly summaries.

Prompt Template

You are a productivity systems designer helping a team turn messy meeting notes into reliable decisions and follow-through. Build the system for:

Team or household context: [startup team, agency, nonprofit board, product squad, operations team, client services, personal projects]
Meeting types: [weekly sync, leadership meeting, client meeting, project review, board committee, vendor call, family planning]
Current capture method: [Zoom transcript, Google Meet notes, Notion, Docs, Slack huddle, handwritten notes, CRM notes]
AI tools allowed: [ChatGPT, Claude, Gemini, Notion AI, Otter, Fireflies, Copilot, none for sensitive meetings]
Privacy constraints: [confidential clients, HR topics, legal, health, minors, no transcript storage, consent required]
Decision pain points: [unclear owner, repeated debates, action items lost, no source of truth, too many meetings]
Output destinations: [Notion, Google Docs, Linear, Asana, Jira, Slack, email, CRM, spreadsheet]
Fields needed: [decision, date, owner, rationale, options rejected, follow-up date, source link, status]
Review cadence: [daily, weekly, before next meeting, monthly retrospective]
Stakeholders: [facilitator, note taker, decision owner, project manager, client, executive]
Automation tolerance: [manual, template-assisted, AI draft with human review, API automation]

Create:
1. Meeting intake template that captures purpose, decisions needed, attendees, and source material.
2. AI note-cleanup prompt that separates facts, decisions, action items, risks, and open questions.
3. Decision log schema with required fields, optional fields, and status definitions.
4. Action item tracker schema with owner, deadline, dependency, next check-in, and escalation path.
5. Human review workflow for correcting AI summaries before they become the record.
6. Privacy and consent rules for recording, transcript use, storage, redaction, and sensitive meetings.
7. Follow-up message templates for meeting recap, decision confirmation, overdue actions, and changed decisions.
8. Weekly review routine that closes loops and archives stale items.
9. Dashboard layout for decisions awaiting confirmation, overdue actions, recurring unresolved topics, and meeting load.
10. Rollout plan for piloting with one meeting type before expanding.

Do not treat AI-generated notes as final records without human review. Flag sensitive topics that should use manual notes or restricted storage.

Example Output

Decision Log Fields

| Field | Required | Example |

|---|---|---|

| Decision | Yes | Move launch from Aug 5 to Aug 12 |

| Rationale | Yes | QA found two payment edge cases and support coverage is thin |

| Owner | Yes | Priya |

| Source | Yes | Leadership sync transcript, 2026-07-21 |

| Revisit date | Optional | 2026-08-02 |

AI Cleanup Prompt

Clean these raw notes into five sections: confirmed decisions, action items, risks, open questions, and useful context. Quote uncertain statements as uncertain. Do not invent owners or dates.

Weekly Review

Every Friday, filter decisions with no owner, actions due in the next seven days, and topics mentioned in three or more meetings without a decision.

Tips for Best Results

  • 💡Define the decision log fields before choosing a tool; otherwise the system becomes another notes archive.
  • 💡Use AI for first-pass cleanup, then require a named human to confirm the record.
  • 💡Include privacy constraints so sensitive meetings do not get routed through the wrong transcription workflow.