ChatGPT Meeting Agenda Prompts: 25 Templates for Better Meetings

Create a practical meeting agenda for the following situation. Meeting goal: [goal]. Attendees and roles: [attendees/roles]. Duration: [duration]. Topics that may need discussion: [topics]. Decisions that need to be made: [decisions needed]. Relevant context: [context]. Constraints: [constraints]. Pre-read or preparation: [pre-read]. First, identify the meeting outcome in one sentence. If critical context is missing, ask me up to three clarifying questions before creating the agenda. Then build a time-boxed agenda showing: time, agenda item, owner or responsible role, whether the item is Inform, Discuss, or Decide, and the expected output. Move low-value updates that can be handled asynchronously into a separate list. Put nonessential topics into a parking lot. Do not invent missing facts, priorities, owners, deadlines, or decisions; mark unknown information clearly.

Evaluate whether this situation requires a live meeting. Goal: [goal]. Participants: [participants]. Information to share: [information]. Decisions needed: [decisions]. Collaboration required: [collaboration]. Deadline or urgency: [deadline]. First, separate what can be handled asynchronously from what genuinely requires synchronous discussion, debate, coordination, or a decision. Recommend one of three options: no meeting, a shorter meeting, or the meeting as planned. Explain the reason briefly. If a meeting is still needed, create the shortest realistic agenda with only the items that require people to be present together. Do not create agenda time for updates that could be read in advance.

Create a structured meeting agenda based on this goal: [goal]. Attendees: [attendees]. Duration: [duration]. Topics: [topics]. Decisions needed: [decisions]. Constraints: [constraints]. Organize the meeting around the desired outcome rather than around a generic topic list. Return a table with Time, Agenda Item, Owner, Type (Inform, Discuss, Decide), and Expected Outcome. Reserve time at the end to confirm decisions, owners, and next steps. If the number of agenda items is unrealistic for the available time, prioritize the most important items and move the rest into a parking lot.

Build a decision-first meeting agenda for this decision: [decision question]. Participants: [participants]. Decision-maker: [decision-maker]. Duration: [duration]. Known options: [options]. Evidence or facts available: [facts]. Constraints: [constraints]. Structure the agenda so the team first aligns on the decision question, then reviews only the facts required to decide, compares options and trade-offs, surfaces unresolved risks, and makes or escalates the decision. Clearly separate facts from assumptions. Do not choose the answer yourself. End with the final decision, rationale, owner, and any follow-up actions that must be recorded by the human meeting owner.

Create a focused 15-minute meeting agenda for [team or project]. The purpose is [purpose]. Attendees: [attendees]. Current blockers or questions: [blockers/questions]. Limit the live agenda to a maximum of three substantive items. Remove general status updates that could be shared asynchronously. Prioritize blockers, coordination needs, and decisions. Use realistic timeboxes and leave the final two minutes to confirm owners and next actions. If the requested scope cannot reasonably fit into 15 minutes, identify what should be postponed or handled asynchronously instead of compressing everything into unrealistic time slots.

Create a [duration]-minute weekly team meeting agenda for [team]. Team priorities this week: [priorities]. Current blockers: [blockers]. Decisions needed: [decisions]. Important changes: [changes]. Build the agenda around exceptions, blockers, cross-team dependencies, decisions, and priorities for the next period. Do not create a round-robin section where every person simply reports what they did. Identify which updates should be read asynchronously before the meeting. Include a short opening to confirm priorities and a closing section to record decisions, owners, deadlines, and unresolved issues.

Create a [duration]-minute one-on-one agenda between [manager role] and [employee role]. Current priorities: [priorities]. Topics the employee wants to raise: [employee topics]. Blockers or support needed: [blockers]. Development topics: [development]. Recent feedback or commitments: [context]. Put the employee's topics and concerns early in the agenda. Include progress, blockers, feedback, career or skill development where relevant, and concrete commitments. Do not invent performance problems, motivations, or personal concerns that were not provided. Keep sensitive judgments out of the agenda unless I explicitly include them.

Create a project kickoff meeting agenda for [project]. Duration: [duration]. Participants and roles: [participants]. Project goal: [goal]. Known scope: [scope]. Known constraints: [constraints]. Key milestones: [milestones]. Build the agenda around shared understanding and execution readiness. Cover the project outcome, scope and out-of-scope items, success metrics, roles and decision authority, major milestones, dependencies, risks, working cadence, communication channels, and immediate next steps. Flag any missing information that could create ambiguity later. End with a clear list of owners and actions rather than a generic summary.

Create a project status review agenda for [project]. Duration: [duration]. Current status: [status]. Progress since the last review: [progress]. Blockers: [blockers]. Risks: [risks]. Decisions needed: [decisions]. Timeline or scope changes: [changes]. Separate information that can be read asynchronously from topics that require live attention. Focus the meeting on exceptions, blockers, decisions, dependencies, and risks to scope, budget, or timeline. Do not spend live meeting time repeating routine progress updates unless they materially change a decision.

Create a cross-functional alignment meeting agenda for [initiative]. Teams involved: [teams]. Duration: [duration]. Each team's goal or concern: [goals/concerns]. Dependencies: [dependencies]. Known conflicts or unclear ownership: [issues]. Decisions needed: [decisions]. Structure the agenda to surface competing goals, dependencies, ownership gaps, and decisions that require multiple teams. Avoid generic departmental updates. For each agenda item, state which teams need to contribute and what agreement or output is required before moving on.

Create an executive meeting agenda for [business area or objective]. Duration: [duration]. Participants: [leaders]. Strategic priorities: [priorities]. Material risks: [risks]. Decisions needed: [decisions]. Resource questions: [resource questions]. Remove operational updates that do not require executive attention. Prioritize business impact, strategic trade-offs, major risks, dependencies, resource allocation, and decisions. For each item, define why leadership attention is required and what outcome should be reached. Do not infer strategy, financial facts, or decision authority beyond the information provided.

Create a client check-in agenda for [client/project]. Duration: [duration]. Current project state: [status]. Recent progress: [progress]. Client questions or concerns: [concerns]. Decisions required from the client: [client decisions]. Actions required from our team: [team actions]. Open issues: [issues]. Structure the meeting so progress is covered briefly, then focus on questions, decisions, risks, and next steps. Clearly distinguish client decisions, our team's actions, and unresolved issues. Avoid implying commitments, dates, or approvals that have not already been confirmed.

Create a sales pipeline meeting agenda for [team]. Duration: [duration]. Priority opportunities: [opportunities]. Deals at risk: [risks]. Blockers: [blockers]. Decisions or leadership support needed: [decisions/support]. Build the agenda around deals that need intervention, decisions, coaching, cross-functional help, or next-step clarity. Do not create time for reviewing every opportunity if the information is already visible in the CRM. Include a short section for patterns across the pipeline and end with owners and concrete next actions for priority deals.

Create a marketing planning meeting agenda for [campaign or period]. Duration: [duration]. Goal: [goal]. Target audience: [audience]. Proposed messaging: [messaging]. Channels under consideration: [channels]. Budget or resource constraint: [budget]. Dependencies: [dependencies]. Measurement approach: [measurement]. Decisions needed: [decisions]. Structure the meeting around choices and dependencies rather than brainstorming everything from scratch. Include target audience, message, channel mix, budget, execution dependencies, measurement, and owners. Clearly identify which items require a decision during the meeting.

Create a product roadmap meeting agenda for [product or period]. Duration: [duration]. Candidate priorities: [priorities]. Customer evidence: [evidence]. Business goals: [goals]. Engineering or resource constraints: [constraints]. Dependencies: [dependencies]. Decisions needed: [decisions]. Structure the agenda around evidence, business impact, effort or capacity, trade-offs, dependencies, and decision criteria. Do not choose roadmap priorities for the team. Instead, create a process that helps participants compare options and document the human decision and rationale.

Create a sprint planning agenda for [team]. Sprint length: [sprint length]. Meeting duration: [duration]. Proposed sprint goal: [goal]. Available capacity: [capacity]. Highest-priority work: [work]. Dependencies: [dependencies]. Known acceptance-criteria gaps or uncertainties: [gaps]. Risks: [risks]. Organize the meeting around confirming the sprint goal, reviewing capacity, selecting realistic work, identifying dependencies and missing information, and confirming ownership. Do not assume capacity or commit work that the team has not validated.

Create a psychologically safe sprint retrospective agenda for [team]. Duration: [duration]. Sprint context: [context]. Known successes: [successes]. Known problems: [problems]. Structure the conversation around what worked, what did not work, recurring patterns, contributing conditions, and improvements the team can test. Avoid language that assigns blame to individuals. Include time to select no more than three concrete improvement experiments with owners and a way to review whether they helped in the next cycle.

Create a concise daily standup structure for [team]. Maximum duration: [duration]. Current sprint or project goal: [goal]. Known blockers: [blockers]. Coordination needs: [coordination]. Keep the meeting focused on progress relevant to the shared goal, blockers, dependencies, and coordination that requires immediate attention. Avoid detailed status reporting and problem-solving discussions that involve only a subset of participants. Add a clear rule for moving deeper discussions offline after the standup.

Create a brainstorming meeting agenda for [problem or opportunity]. Duration: [duration]. Participants: [participants]. Desired output: [output]. Constraints: [constraints]. Structure the session in stages: problem framing, silent individual idea generation, sharing, clustering similar ideas, evaluation using agreed criteria, and selecting next steps or experiments. Do not generate or rank the ideas on behalf of the participants unless I explicitly ask for AI-generated options as an input. Protect time for independent thinking before group discussion to reduce anchoring on the first idea raised.

Create a problem-solving meeting agenda for this issue: [problem]. Duration: [duration]. Participants: [participants]. Known facts: [facts]. Current assumptions: [assumptions]. Possible causes: [causes]. Constraints: [constraints]. Decision needed: [decision]. Structure the meeting to define the problem, separate evidence from assumptions, examine likely causes, identify possible responses, compare trade-offs, make or escalate the decision, and assign an owner. Do not present an unverified cause as fact. Clearly mark where additional evidence is required.

Create a workshop agenda for [workshop topic]. Workshop objective: [objective]. Participants: [number and roles]. Total duration: [duration]. Desired outputs: [outputs]. Exercises or activities available: [activities]. Constraints: [constraints]. Build a realistic agenda with opening context, individual or group activities, breakout work where useful, sharing, synthesis, decision or prioritization time, breaks if needed, and a clear close. Include facilitator notes and the expected output of each activity. Do not overfill the schedule; leave enough time for transitions and discussion.

Create a structured hiring debrief agenda for the role [role]. Duration: [duration]. Interview competencies: [competencies]. Interviewers: [interviewers]. Evidence collected: [evidence]. Conflicting observations: [conflicts]. Missing evidence: [missing evidence]. Organize the discussion around job-relevant evidence by competency, areas of agreement, conflicting observations, missing evidence, and the hiring team's decision process. Do not make the hiring decision yourself. Do not infer protected or irrelevant personal characteristics. Flag statements that appear to be unsupported impressions so the panel can return to specific interview evidence.

Create a quarterly business review agenda for [business/team/client]. Duration: [duration]. Targets: [targets]. Actual results: [results]. Material deviations: [deviations]. Known causes: [causes]. Risks: [risks]. Next-quarter priorities: [priorities]. Decisions needed: [decisions]. Focus the live meeting on performance gaps, causes, lessons, future priorities, material risks, and decisions. Move routine metrics that need no discussion into a pre-read. Do not simply turn the dashboard into an agenda. End with agreed priorities, owners, and unresolved decisions.

Create a board meeting agenda based only on the information I provide. Organization: [organization]. Duration: [duration]. Strategic updates: [updates]. Business or financial performance topics: [performance]. Material risks: [risks]. Approvals or decisions requested: [approvals]. Governance topics: [governance topics]. Structure the agenda around strategic oversight, material performance issues, risks, approvals, decisions, and board questions. Do not invent legal or governance requirements. If an item appears to depend on jurisdiction-specific obligations or corporate documents, flag it for legal or governance review instead of stating that the board is required to consider it.

Create a neutral, fact-focused agenda for a difficult meeting about [issue]. Duration: [duration]. Participants: [participants]. Confirmed facts: [facts]. Disputed points: [disputed points]. Business impact: [impact]. Desired outcome: [outcome]. Structure the conversation around shared facts, areas of disagreement, impact, constraints, options, and next steps. Use neutral language and avoid assigning blame. Do not determine fault, disciplinary action, legal conclusions, or intent. If the issue involves HR, legal, safety, or compliance implications, flag those areas for appropriate human review.

Create the next meeting agenda using these previous meeting notes: [notes]. New priorities since the last meeting: [new priorities]. Meeting duration: [duration]. Participants: [participants]. First, extract previous decisions, unresolved questions, incomplete actions, overdue items, and anything that is now closed. Remove completed items unless they affect a new decision. Identify what requires discussion now and what can be handled asynchronously. Then create a time-boxed agenda focused on unresolved work, changed priorities, current blockers, and decisions needed. Do not assume that an old action is still relevant if the notes do not establish that.

Review this agenda and identify any items that are vague topics rather than decisions, questions, or concrete outputs. Rewrite those items so participants know exactly what must be accomplished before the meeting can move on. Do not change the underlying business goal or invent new decisions.

Reduce this agenda from 60 minutes to 30 minutes without simply shrinking every timebox. Identify which items require live discussion, which can be handled asynchronously, which can be combined, and which should be postponed. Preserve the most important decision or outcome of the meeting.

Review this agenda and split the content into two groups: information participants should read or update asynchronously before the meeting, and topics that genuinely require synchronous discussion. Then rebuild the live agenda using only the second group.

Improve this agenda by adding a realistic timebox, owner or responsible role, and expected output to each item. Do not assign named people unless they are explicitly provided. If an item is too broad for the available time, narrow it or flag it for a separate discussion.

Stress-test this meeting agenda. Identify where the timeboxes are unrealistic, where too many decisions are expected, where required preparation is missing, where decision authority is unclear, or where an agenda item depends on information that has not been provided. Recommend specific corrections without inventing missing business facts.