A useful meeting agenda should make it clear what must be decided, who owns each item, and what happens if the group cannot decide. ChatGPT can help when you provide the purpose, decision owner, pre-read, tradeoffs, and time limit.
What to prepare
- The decision or concrete result the meeting must produce.
- Attendees, their roles, and who owns the final decision.
- Pre-read, data, or options people should review before the meeting.
- Known tradeoffs, constraints, and unresolved questions.
- Updates that could be shared without using meeting time.
Best use cases
- Preparing a client call.
- Turning a vague meeting invite into a real agenda.
- Planning a project kickoff.
- Separating discussion topics from decisions.
- Creating follow-up questions before the meeting starts.
Copy this prompt
Create a decision-focused meeting agenda.
Meeting purpose:
[why we are meeting]
Required outcome or decision:
[what must be decided or completed]
Attendees and roles:
[who is joining and why]
Decision owner:
[person or role with final authority]
Time available:
[30 minutes, 45 minutes, 60 minutes]
Context, options, and tradeoffs:
[brief background]
Pre-read or evidence:
[what attendees should review]
Updates that could be shared asynchronously:
[optional]
Return:
1. A one-sentence meeting objective
2. A pre-meeting checklist and pre-read list
3. A timed agenda table with item, type (decide/discuss/inform), owner, key question, intended outcome, and minutes
4. Decisions to confirm before the meeting ends
5. Unresolved items with an owner and next step
6. A short follow-up email template
Rules:
- Move informational updates that do not need group discussion to the asynchronous list.
- Put decision items before general discussion.
- Keep the total agenda within the available time.
- Reserve the final five minutes to confirm decisions, owners, and next steps.
- If required context or authority is missing, mark it as "needs input" instead of inventing an answer.
Test input
Meeting purpose: decide launch scope for the customer portal
Attendees: product manager, engineering lead, support lead, client sponsor
Decision owner: client sponsor
Time available: 45 minutes
Background: payment flow is delayed, mobile layout has two known issues, support wants more time for help center updates
Decisions needed: launch with or without guest checkout, launch date, who owns customer communication
Pre-read: payment-flow delay summary, mobile issue screenshots, support readiness checklist
Updates that could be shared asynchronously: completed design work and routine test progress
What good output should include
- A meeting objective that names the decision, not just the topic.
- Time limits for each agenda item.
- Questions that expose tradeoffs.
- Decision points and owners.
- A follow-up email that confirms what changed after the meeting.
Fix a weak agenda
Review the meeting agenda you just created.
Check:
1. Does every item say whether the group must decide, discuss, or only receive information?
2. Does every decision item name the decision owner and the exact question to answer?
3. Can any item be moved to a pre-read or asynchronous update?
4. Does the total time fit the meeting, including five minutes for decisions and next steps?
5. If the group cannot decide, is there an owner and next step for resolving it?
Rewrite only the weak agenda items. Do not invent missing facts, authority, or deadlines.
Common mistake
Do not create an agenda that is just a topic list. A useful agenda explains what each item must produce, who owns it, and what happens when the group cannot reach a decision.