Meeting Agenda Builder
OPEN SAMPLE Builds a timed agenda for a team meeting based on the topics, owners, and time available you provide. Use it before any standing or ad hoc meeting where scattered discussion is wasting time.
YOUR NAME ·YOUR ROLE ·ORGANIZATION NAME ·MEETING NAME ·MEETING LENGTH ·MEETING DATE ·ATTENDEE LIST OR ROLES ·MEETING PURPOSE ·TOPIC LIST WITH OWNERS AND ROUGH TIME ESTIMATES ·STANDING ITEMS ·PRE-READ MATERIALS
## Context
You are helping [YOUR NAME], a [YOUR ROLE] at [ORGANIZATION NAME], build a meeting agenda for [MEETING NAME]. The meeting is [MEETING LENGTH] minutes long and will be held on [MEETING DATE]. Attendees: [ATTENDEE LIST OR ROLES]. The stated purpose of this meeting: [MEETING PURPOSE]. Topics to cover, in the order I want to address them: [TOPIC LIST WITH OWNERS AND ROUGH TIME ESTIMATES]. Any standing items that open or close every meeting: [STANDING ITEMS]. Materials or pre-reads attendees should bring: [PRE-READ MATERIALS].
## Task
Build a timed meeting agenda with these sections in order:
1. Header: meeting name, date, time, location or link, and expected attendees.
2. Meeting purpose: one sentence stating what we need to accomplish by the end.
3. Timed agenda items: each item on its own line with time block, topic, owner, and expected output (decision, information shared, action assigned, or discussion).
4. Standing items: opening and closing items if I provided them.
5. Pre-read list: materials attendees should review before arriving.
6. Parking lot: a blank section at the bottom for items raised but not scheduled.
## Standards
- Total time blocks must add up to exactly [MEETING LENGTH] minutes. Show the running total.
- Use only the topics, owners, and time estimates I provided. Do not invent agenda items.
- Label each item with its expected output type. A meeting where no one knows why an item is on the agenda wastes everyone's time.
- Keep language short and direct. Each item title should be five words or fewer.
- Do not promise decisions or outcomes in the agenda. State what will be attempted.
- If a bracketed input is missing or ambiguous, ask before drafting.
BEFORE YOU RUN IT
- Confirmed meeting length and date, not a guess at when it might be scheduled
- Topic list with an owner name or role for each item, not just a list of subjects
- Rough time estimates for each topic, even if approximate, so the total can be checked
- The stated meeting purpose in one sentence, not a list of everything the meeting might cover
- Confirm all dates, times, and attendee roles come from the actual meeting invite or project records, not the AI
- Keep attendee names and any personnel or client details general if this tool is not approved under your organization's data policy
VERIFY BEFORE IT LEAVES YOUR HANDS
- Add up all time blocks yourself and confirm they equal the booked meeting length exactly
- Check that every agenda item has an owner that matches someone on the attendee list you provided
- Confirm no topics were added by the AI that you did not supply in your input
- Verify each item is labeled with an output type (decision, information, action, or discussion) and that the label is accurate
- Check that the pre-read list matches what you actually want attendees to prepare, not a generic suggestion
- Confirm the parking lot section is blank and will not be confused with scheduled items
Sample output
Sample output. Generated by AI from sample inputs:
**Weekly Ops Sync**
Northwind Distribution | Operations Team
Date: Wednesday, June 18, 2026 | 9:00 to 9:50 AM
Location: Conference Room B / Teams link in invite
Attendees: Ops Manager, Warehouse Lead, Transport Coordinator, Inventory Analyst
**Purpose:** Confirm Atlas warehouse migration status, resolve the inbound dock scheduling conflict, and assign Week 26 closeout actions.
**Agenda**
0:00 to 0:05 (5 min) - Opening and attendance | Owner: Ops Manager | Output: Information
0:05 to 0:15 (10 min) - Atlas migration status update | Owner: Warehouse Lead | Output: Information + decisions on open items
0:15 to 0:25 (10 min) - Inbound dock scheduling conflict | Owner: Transport Coordinator | Output: Decision
0:25 to 0:35 (10 min) - Week 26 inventory closeout | Owner: Inventory Analyst | Output: Action assignments
0:35 to 0:45 (10 min) - Open items from last week | Owner: Ops Manager | Output: Decision or defer
0:45 to 0:50 (5 min) - Action item recap and close | Owner: Ops Manager | Output: Action
Running total: 5 + 10 + 10 + 10 + 10 + 5 = 50 minutes.
**Pre-reads**
- Atlas migration tracker (shared drive, last updated June 16)
- Inbound dock schedule for weeks 25 and 26
**Parking Lot**
(Items raised during the meeting that need a future slot go here.)
CUSTOMIZATION For project kickoff meetings with larger groups, add a round-robin introductions slot at the top and expand the purpose section to cover scope and ground rules. For daily standups under 15 minutes, strip the pre-read list and parking lot and keep only purpose, timed items, and a one-minute action recap. Veterans who have run battle rhythm meetings will recognize this format: the same discipline applies in any operations environment.
Status Meeting Prep
OPEN SAMPLE Builds a structured agenda and talking points for a recurring status meeting. Use it before any weekly or biweekly team sync where you need to surface progress, blockers, and next steps without letting the meeting run long.
YOUR NAME AND ROLE ·MEETING CADENCE ·PROJECT OR TEAM NAME ·ATTENDEES OR ROLES ·MEETING DATE ·CURRENT PHASE ·CARRYOVER ITEMS ·WORKSTREAM UPDATES ·BLOCKERS ·DECISIONS NEEDED ·PRIOR ACTION ITEMS STATUS
## Context
You are helping [YOUR NAME AND ROLE] prepare for a recurring [MEETING CADENCE: e.g., weekly, biweekly] status meeting for [PROJECT OR TEAM NAME]. The meeting includes [ATTENDEES OR ROLES]. Date of this meeting: [MEETING DATE]. Current project phase or milestone: [CURRENT PHASE]. Items to cover from the last meeting: [CARRYOVER ITEMS]. Updates from each workstream this period: [WORKSTREAM UPDATES]. Open blockers or issues needing the group's attention: [BLOCKERS]. Decisions the group needs to make today: [DECISIONS NEEDED]. Action items from the last meeting and their current status: [PRIOR ACTION ITEMS STATUS].
## Task
Produce a clean meeting agenda with three parts: a one-paragraph opening framing the current state of the project, an ordered list of agenda items with a time allocation and owner for each, and a pre-written closing that captures the standing action-item format you want the note-taker to use. Include a parking lot section at the end for items that come up but are out of scope for today.
## Standards
- Plain language. No management jargon.
- Agenda items must come from the workstream updates and blockers I supply. Do not invent progress, milestones, or risk items.
- Time allocations must add up to the total meeting length I specify. If I do not specify a length, ask before assigning times.
- Blockers should be stated as specific questions the group needs to answer, not as vague problem statements.
- Do not invent action item owners, due dates, or resolution statuses for prior action items.
- If [WORKSTREAM UPDATES] or [BLOCKERS] are missing or vague, ask me to clarify before drafting.
- This prompt is a planning aid. Confirm all statuses, dates, and metrics with your own project records before the meeting.
BEFORE YOU RUN IT
- Workstream updates from each area since the last meeting, pulled from your actual tracking tool or status reports, not from memory
- Open blockers stated as specific questions the group can answer or assign
- Prior action items and their current status, confirmed before the meeting, not assumed
- Decisions needed today, with enough background that attendees can decide without lengthy explanation
- Confirm all dates, statuses, and progress figures come from your project records, not from the AI
- Confidentiality: keep vendor contract terms, personnel performance details, and sensitive cost data out of this prompt
VERIFY BEFORE IT LEAVES YOUR HANDS
- All workstream statuses reflect information you supplied, not AI-assumed progress
- Time allocations add up to the total meeting length you specified
- Blockers are stated as answerable questions, not vague concerns
- Prior action item statuses match what you confirmed, not what the AI guessed
- No invented milestones, percentages, or risk levels appear
- Decisions needed are clearly framed so attendees know what they are being asked to decide
- No confidential vendor, personnel, or contract details appear in the agenda
Sample output
Sample output. Generated by AI from sample inputs:
Atlas Warehouse Migration | Weekly Status Meeting
Northwind Distribution | Tuesday, June 17, 2026 | 9:00-9:45 a.m.
Facilitator: Dana Kowalski, Project Manager
Project State
We are in Phase 2 (rack installation and network cabling) with a target completion of July 11. Phase 1 closeout is complete. Three action items from last week are closed; one is open and on today's agenda.
Agenda
1. (2 min) Quick wins from last week | Dana
2. (8 min) Workstream updates
- Rack installation: 60 of 120 sections complete. On track. | Marcus
- Network cabling: Vendor started Monday. Pull schedule due Friday. | Priya
- IT provisioning: Server migration window confirmed for July 5-6. | Chen
3. (10 min) Open blocker: The fire suppression inspection is scheduled for June 30, but the vendor needs a 10-day clear before we can stage inventory. Does that change our Phase 3 start date, or do we adjust the inspection slot? Decision needed today. | Dana
4. (10 min) Prior action items review
- Order dock levelers (due June 13): CLOSED. Delivery confirmed July 2.
- Confirm backup power specs with facilities (due June 13): CLOSED.
- Security badge access list to HR (due June 13): OPEN. Priya to update today.
5. (10 min) Decisions and direction
- Go/no-go on moving Phase 3 start from July 14 to July 21 based on inspection constraint
6. (5 min) Close + action items
Action Item Format (for note-taker)
Item | Owner | Due Date | Status
Parking Lot
Topics raised today that are out of scope for this meeting go here. Owner assigned to bring back next week.
CUSTOMIZATION For larger programs with multiple project managers, add a roll-up section at the top showing overall schedule and budget health by traffic light color, but only if you supply the actual status for each. For daily standups, cut the agenda to three items: what happened since yesterday, what is happening today, and what is blocked. For executive briefings, reorder the agenda to lead with decisions needed rather than workstream updates.