Create a meeting agenda that gets the required decisions or working outputs completed in the allotted time. Do not turn it into a general discussion list or invent decisions, attendees, dependencies, or project status. Meeting purpose: [MEETING PURPOSE] Required decisions or outputs: [REQUIRED OUTCOMES] Attendees and roles: [ATTENDEES AND ROLES] Context and pre-read: [CONTEXT AND PRE-READ] Time available: [MEETING LENGTH] Known constraints or tensions: [CONSTRAINTS]
Return a ready-to-send agenda with:
1. Meeting title and one-sentence purpose.
2. A desired-outcomes section using observable results, such as “select option A or B,” “approve owner and deadline,” or “identify blockers requiring escalation.”
3. A timed table with sequence, topic, owner, method, intended output, and minutes. Reserve 10-15% of the meeting for decisions and action confirmation.
4. A pre-work section that states who must read, prepare, or submit something before the meeting. Remove items that can be handled asynchronously by written update.
5. A facilitation note naming the decision-maker, how dissent will be captured, and what happens if the group cannot decide.
6. A closing template for decisions, owners, due dates, and open risks.
Design each discussion item around one question that can be answered during the meeting. Put the highest-consequence decision first, after only essential context. If a topic needs more time than available, label it “defer” and recommend the next format.
Before answering, check that agenda minutes total [MEETING LENGTH] and that every required outcome has an owner and a planned decision method. Ask up to 3 clarifying questions only if a required input is missing.Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [MEETING PURPOSE] | State the business reason for meeting and the decision or work that cannot stay asynchronous. | Choose the launch scope for the October customer onboarding update. |
| [REQUIRED OUTCOMES] | List the specific decisions, approvals, plans, or blockers the group must resolve. | Select minimum launch features, name the launch owner, and decide whether analytics work can move to the next release. |
| [ATTENDEES AND ROLES] | List each attendee with their role, contribution, and decision authority. | Priya, product lead and decision-maker; Marcos, engineering lead; Elise, support lead; Jordan, data analyst. |
| [CONTEXT AND PRE-READ] | Paste the essential background, links, data, and documents attendees should review beforehand. | Customer interview summary, engineering estimate, support ticket themes, and a draft feature comparison. |
| [MEETING LENGTH] | State the total available time in minutes. | 45 minutes. |
| [CONSTRAINTS] | List deadlines, dependencies, disagreements, or non-negotiables that affect the meeting. | Engineering capacity is one squad; legal review requires five business days; launch must occur before October 28. |
How to use
- List decisions as verbs with a clear end state, then identify the person who can make each final call.
- Attach only the context needed to make the decision; move routine progress reporting to a written update.
- Check that each topic produces a choice, commitment, or artifact, then cut topics that cannot reach one.
- Follow up with: “Write a 120-word calendar invite using this agenda and clearly state the pre-work deadline.”
Variations
Executive decision meeting
Use this when leaders need to choose among options.
Create a [MEETING LENGTH]-minute executive decision agenda for [DECISION]. Use [OPTIONS AND EVIDENCE], [ATTENDEES], and [DECISION AUTHORITY]. Start with the recommendation and trade-offs, not a project history. Include the decision question, evidence required, timeboxed challenge period, final decision owner, and a contingency if no decision is reached. Return a timed agenda and a one-page pre-read outline. Ask up to 3 questions only if information is missing.
Team retrospective
Use this after a project, incident, or delivery cycle.
Design a [MEETING LENGTH]-minute retrospective for [PROJECT OR EVENT] with [PARTICIPANTS] using [KNOWN FACTS]. Produce a blameless agenda that separates facts, contributing conditions, and improvement actions. Include a timeline review, prompts for what to keep/change, selection of no more than three actions, owners, and target dates. Do not assign personal fault or speculate about motives. Ask up to 3 questions if needed.
Client kickoff
Use this to align a client and delivery team.
Write a client-kickoff agenda for [PROJECT] using [SCOPE], [STAKEHOLDERS], [TIMELINE], and [OPEN QUESTIONS]. Include success measures, roles and decision rights, working cadence, dependency review, approval process, risks, and immediate next steps. State what will be confirmed during the meeting versus documented afterward. Return a timed agenda and an email-ready pre-work list. Ask up to 3 questions only if required inputs are missing.
Tips
- An agenda item such as “discuss timeline” is too vague; use “choose a launch date from these two options” and name the decision owner.
- Send pre-reads early enough for people to inspect them, and put the one required question at the top of each document.
- If a status item has no requested decision or help needed, collect it asynchronously before the meeting.
- End by reading back each commitment with one owner and one date; a task assigned to “the team” usually has no owner.
FAQ
How long should a work meeting agenda be?
It should match the time available and leave room to decide and assign actions. A 30-minute meeting commonly supports one major decision or two small ones.
Should every attendee have an agenda item?
No. Invite people for a defined contribution, decision right, or needed context. An agenda should name who owns a topic, not distribute speaking time evenly.
Can AI create an agenda from meeting notes?
Yes, but give it the desired outcomes and decision-maker as well as the notes. Otherwise it may preserve a long topic list without creating a useful decision flow.