Prompt Library

ChatGPT Prompts for Meeting Agendas That Actually Work

20 copy-paste prompts

20 copy-paste ChatGPT prompts for agendas: structured templates, time-allocated formats, decision-driving designs, recurring meeting templates, and the remote meeting agendas that respect attention.

Agenda Templates

4 prompts

Agenda from Meeting Goal

1/20

Build agenda for [meeting type, attendees, duration]. Goal: [specific outcome wanted]. Output: pre-read materials, agenda items in priority order, time per item, decision rights per item, expected outcomes, follow-up actions. Decisions first, info-share second.

Builds goal-driven agendas.

💡

Pro tip: Topic-based agendas waste time. Goal-driven agendas force decisions. "Discuss budget" = no decision. "Approve $50K Q1 marketing budget" = decision happens.

Recurring Team Meeting

2/20

Recurring [weekly/bi-weekly] team meeting agenda. Team: [size + roles]. Output: standing items (wins, blockers, metrics), rotating items (deep dives, demos, retros), time-boxed sections, prep expected, decision items vs information items, weekly notes capture method.

Builds recurring meeting templates.

💡

Pro tip: Same agenda each week = team auto-drives meeting. Different agenda each time = facilitator carries entire weight + meetings drift.

1:1 Meeting Agenda

3/20

1:1 meeting agenda template. Manager + direct report. Output: opener (personal check-in), their topics first (their meeting, not mine), my topics, career conversation cadence (monthly), feedback both directions, action items captured. 30-45 min standing.

Builds 1:1 agenda templates.

💡

Pro tip: 1:1s are direct report's meeting, not manager's. Their topics first = ownership signal. Manager's update topics second = service to them, not the reverse.

Brainstorm Meeting

4/20

Brainstorm meeting agenda. Goal: [specific output — generate ideas, evaluate options, etc.]. Output: prep (silent ideation), divergent phase (no critique), convergent phase (evaluation), decision phase (selection), follow-up (action). Avoid "anchor first" trap.

Builds brainstorm meeting agendas.

💡

Pro tip: Group brainstorms without structure = anchor-first or loudest-voice ideas dominate. Structured silent ideation → group sharing = better range + quieter voices heard.

Prompts get you started. Tutorials level you up.

A growing library of 300+ hands-on AI tutorials. New tutorials added every week.

Start 7-Day Free Trial

Decision-Driving

4 prompts

Decision Meeting Format

5/20

Meeting where [specific decision] must be made. Output: pre-read context, decision framing (RACI: who decides), options on table, evaluation criteria, agenda flow (data → discussion → decision), backup if no consensus. Force the decision; don't end without one.

Builds decision-meeting agendas.

💡

Pro tip: Decisions deferred to "next meeting" = lost momentum + same problem next month. Forcing decision in-meeting = progress. Sometimes decision is "no" — still progress.

Pre-Mortem Meeting

6/20

Pre-mortem meeting on [planned project/decision]. Output: setup (assume failure 1 year out), individual failure scenarios written silently, group share + cluster, mitigation per top risk, decision: proceed / modify / kill. Surfaces risks better than "are there concerns?"

Runs pre-mortem meetings.

💡

Pro tip: "Any concerns?" = group says no. Pre-mortem ("imagine this failed; what happened?") = real concerns surface. Different framing; opposite results.

Project Kickoff

7/20

Project kickoff meeting agenda for [project]. Attendees: [list]. Output: project context + goal, success metrics defined, scope clarification, RACI walkthrough, timeline + milestones, risks discussed, communication norms agreed, action items + owners. Set tone for project.

Builds project kickoff agendas.

💡

Pro tip: Skipped or rushed kickoffs = unclear ownership + scope drift + missed milestones. Solid kickoff = aligned project = on-time delivery. 90 minutes here saves 90 hours later.

Post-Mortem / Retro

8/20

Post-mortem on [completed project / sprint / quarter]. Output: agenda — what we shipped, what worked, what didn't, what we'll change next time. Blameless framing. Specific action items vs vague "do better." Time-boxed.

Builds retro meeting agendas.

💡

Pro tip: Vague retros ("communicate better") = no behavior change. Specific actions ("Sarah owns daily blocker email by Tuesday") = real improvement. Concreteness over feelings.

Remote + Async Meetings

4 prompts

Remote-Optimized Agenda

9/20

Remote meeting agenda. Attendees: [global timezones]. Output: pre-read sent 24+ hrs ahead, discussion-only items in meeting (info via doc), camera-on expectations, raise-hand norm, breaks every 60 min, no-meeting norm respected. Optimize for video.

Builds remote-optimized agendas.

💡

Pro tip: In-person meeting agenda imported to remote = bad meeting. Remote needs different design: shorter, more pre-read, more structure, more breaks. Different medium; different meeting.

Async-First Format

10/20

Async-first decision process. Decision: [describe]. Output: written context doc, discussion period (comments async), decision deadline, meeting only if discussion not converging, written outcome shared. Most meetings could be async docs.

Designs async-first decision processes.

💡

Pro tip: Most "this could be a meeting" should've been a doc. Async doc + comments + decision = often better than synchronous meeting. Plus respects timezones + focus time.

No-Meeting Day Setup

11/20

Implementing no-meeting Wednesdays. Help me communicate: rationale, exceptions allowed, escalation path, expected impact, success metrics, how to schedule. Cultural change harder than calendar block.

Implements no-meeting days.

💡

Pro tip: Calendar block alone = ignored. Cultural framing + escalation rules + leadership modeling = no-meeting days hold. The calendar isn't the change; the culture is.

Meeting-Free Status Update

12/20

Replace weekly status meeting with async update format. Output: structured update template, channels (Slack / Notion / email), timing, expected response window, escalation if blocker, what stays in meeting (decisions only). Most status meetings = 30 min docs.

Replaces status meetings with async docs.

💡

Pro tip: Status meetings = 30 min where 5 people share for 6 minutes each. Async = same info in 5 min reading + skip what's irrelevant. Time savings huge; quality higher.

Like these prompts? There are full tutorials behind them.

Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.

Try AI Academy Free

Specialty Agendas

4 prompts

Board Meeting Agenda

13/20

Board meeting agenda. [Stage of company]. Output: pre-read board package (sent 1 week ahead), CEO update, key metrics + drivers, strategic discussion items, board-only session, executive session, timeline. 2-3 hr typical.

Builds board meeting agendas.

💡

Pro tip: Boards waste time on operations updates better given async. In-meeting = strategic discussions + decisions only. Pre-read carries the operational context.

All-Hands Meeting

14/20

All-hands meeting agenda. Company size: [N]. Output: state of business, strategic update, recognition + wins, big asks, Q&A invitation. Tone: confident + accessible. Structured but human. 45-60 min max.

Builds all-hands meeting agendas.

💡

Pro tip: All-hands as corporate showcase = tune-out. All-hands as honest update + meaningful Q&A = team feels informed + heard. Authenticity > polish.

Town Hall Q&A Format

15/20

Town hall Q&A format. Output: question intake (anonymous + signed), prioritization, scripted prep on hard questions, leadership alignment on answers, hard-question handling, what to defer to follow-up. Most leaders dread; well-designed makes it easy.

Designs town hall Q&A.

💡

Pro tip: Anonymous question intake catches the questions people won't ask publicly. The questions employees ask anonymously = the ones leaders most need to hear.

Cross-Functional Sync

16/20

Cross-functional sync agenda. Teams: [list]. Output: each team's update bullets (concise), inter-team dependencies surfaced, blockers between teams, decisions needed (with right deciders), action items + owners. Avoid bilateral meetings via group format.

Builds cross-functional sync agendas.

💡

Pro tip: Cross-functional syncs that are "round-robin updates" = boring + useless. Cross-functional syncs that surface inter-team blockers + decisions = high-value. Different framing.

Frequently Asked Questions

Default 30 min, not 60. 60-min calendar slots = meeting expands to fill. Force 25 or 50 to leave buffers. Standing meetings: 15-30 min. Decision meetings: 45-60 max. Anything longer = poorly designed.

Yes. Even 1:1s. Without agenda = wandering conversation. Agenda doesn't need to be formal — even 3 bullet points beats nothing. Send 24 hrs ahead so people can prep.

Pre-read for context. Decisions visible upfront. Time-box per item. Force-rank topics. Cancel if no clear goal. Most meetings 30% too long; tightening agenda = real time back.

Cancel for 2 weeks. See what breaks. Often nothing. The meeting filled the calendar, not a need. If something breaks, restore — but with redesigned purpose. Calendar audit annually.

Whichever your team actually reads. Living doc (Notion) = collaborative + history. Email = simple but not collaborative. Pick one + stick. Tool-jumping = nothing gets read.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial Explore AI for Teams

7-day free trial. Cancel anytime.

Browse All Prompt Collections