Build a Tight Meeting Agenda with Timeboxes, Owners and a Clear Decision Goal

You get a meeting agenda with a one-sentence decision goal, timed items with owners, pre-reads, and a list of topics cut to email instead.

Prompt

Prompt
Act as an operations lead who runs short, decision-focused meetings.

Your job: build a tight agenda for a meeting I'm planning. Before writing anything, ask me these questions in one numbered message and wait for my answers:
1. What decision or outcome must this meeting produce?
2. How long is the meeting, and who is attending (names or roles)?
3. What topics do people want to cover?
4. Is there any data or document people should read first?

Rules:
- Write the goal as one sentence starting with "By the end of this meeting we will decide..."
- Every agenda item gets a timebox in minutes and one named owner. Item minutes must total the meeting length minus 5 minutes, which are reserved for the recap.
- Move any status update, FYI or item needing no discussion to a "Send as email instead" list, with a one-line reason each.
- Each item states its expected output: a decision, an owner assigned, or options narrowed.
- Put the main decision in the first half of the meeting.

Output format:
1. Meeting goal (one sentence)
2. Agenda table: # | Item | Owner | Minutes | Expected output
3. Pre-reads (who sends what, and by when)
4. Send as email instead (bullets)
5. Final 5 minutes: decisions recap and action items

End with one line naming any assumption you made or anything missing that could derail the meeting.

Example output

At a glanceMinutes per agenda item (40 of 45 minutes)Timeboxed agenda to choose between HelpLoop and DeskTrail
  • Confirm goal and finalists (Leo): 3 min
  • Feature fit (Priya): 10 min
  • 3-year cost (Dana): 8 min
  • Migration risk (Marcus): 8 min
  • Decision and vote (Leo): 6 min
  • Rollout owner, next steps (Leo): 5 min

Example for: a 45-minute meeting at Northwind Outfitters to choose a new customer support ticketing tool, with four attendees.

1. Meeting goal

By the end of this meeting we will decide which ticketing tool (HelpLoop or DeskTrail) we sign with for the July 1 rollout.

2. Agenda

#ItemOwnerMinutesExpected output
1Confirm the goal and the two finalistsLeo (Ops lead)3Agreement on scope: two options only
2Feature fit against our top 5 support needsPriya (Head of Support)10Options narrowed: any dealbreakers named
3Total 3-year cost, including migration feesDana (Finance)8Cost gap stated in one number
4Migration risk and IT effortMarcus (IT)8Risk rated low/medium/high per tool
5Decision and voteLeo6Vendor chosen
6Rollout owner and next 2 stepsLeo5Owner assigned with dates
Total40

3. Pre-reads

  • Priya sends the feature comparison sheet (one page) by Tuesday 5 pm.
  • Dana sends the 3-year cost table for both vendors by Tuesday 5 pm.
  • Marcus sends a half-page note on data migration from the current tool by Wednesday 10 am.

4. Send as email instead

  • Q2 CSAT results (Priya): numbers to share, nothing to decide.
  • Support hiring update (Priya): status only; questions can go by reply.
  • Holiday coverage schedule (Leo): already agreed; needs a calendar invite, not discussion.

5. Final 5 minutes

  • Leo reads back the chosen vendor and the reason in one sentence.
  • Confirm action items: contract review (Dana), migration plan draft (Marcus), team announcement (Priya), each with a due date.
  • Leo sends a written summary within 2 hours.

Assumption: both vendors can still meet a July 1 start; if either cannot confirm this before the meeting, item 5 may not produce a decision.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Asking for the decision first forces every item to serve one outcome instead of filling the hour.
  • Requiring minutes and a single owner per item makes the agenda checkable and stops topics from drifting.
  • The email-instead list cuts status updates, which is often the fastest way to shorten a meeting.

Use this in ChatGPT, Claude or Gemini a day or two before a meeting. Have the decision you need, the attendee list, meeting length and the topics people have asked to raise.

Common edits

  • Change the 5-minute recap buffer to 10 minutes for meetings over an hour.
  • Ask for a short version formatted as a calendar invite description.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Business