Organize information

Create a time-boxed meeting agenda

Turn a meeting goal into sequenced decisions, preparation, time boxes, and named facilitation roles

5 min setupTested with:ChatGPTReviewed: 2026-08-28

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Meeting goal and required outputParticipants and rolesDuration and constraints

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Create a time-boxed meeting agenda.

Goal and required end-of-meeting output:
[goal]

Participants, authority, expertise, facilitator, and note-taker:
[participants]

Duration, context, pre-work, accessibility needs, and non-goals:
[constraints]

Verify that the requested outcome is feasible in the available time. Build the agenda backward from the final decision or artifact. For every segment provide start/end minute, purpose, owner, method, input, and tangible output. Reserve time for opening context, dissent or risk review, decision confirmation, owners and dates, and close. Put information sharing into pre-work where possible. Do not invent attendees, authority, or pre-work completion. Include preparation instructions, decision rule, parking-lot handling, a shorter contingency agenda, and cancellation or conversion criteria if prerequisites are missing.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Meeting goal and required output: Choose one of three onboarding-flow concepts for a two-week usability prototype and leave with documented selection criteria, known risks, and owners for the next steps.
Participants and roles: 45-minute video call. Product lead Maya has final decision authority; designer Leo presents concepts; researcher Priya supplies evidence; engineer Chen advises feasibility. Maya facilitates. Note-taker is not assigned.
Duration and constraints: Concept boards and five interview findings can be sent one day before. No live design edits and no roadmap discussion. One attendee uses captions. If research evidence is not circulated, selection should not proceed.

Example output

Feasibility: achievable in 45 minutes if the concept boards and research findings are read in advance. Pre-work: Leo sends three labeled boards; Priya sends five findings with evidence; attendees record one question and rank the stated criteria. Maya confirms materials were received. Assign a note-taker before the call and enable captions.

Agenda: 0–3 Maya—goal, decision authority, non-goals; output: shared decision rule. 3–8 Priya—evidence questions only, not a presentation; output: agreed user needs. 8–17 Leo—three concepts, three minutes each; output: clarified differences. 17–25 Chen and group—feasibility, dependencies, risks; output: risk list. 25–34 group—score against criteria and surface dissent; output: comparison record. 34–39 Maya—select or explicitly defer; output: decision and rationale. 39–43 assign prototype, test, and risk owners with dates. 43–45 read back decision, open issues, and parking lot.

Decision rule: Maya decides after hearing evidence and recorded dissent. Contingency: cut presentations to one minute each, not dissent or action confirmation. If research was not circulated, convert the meeting to clarification and reschedule the selection.

Why this works

1
Backward planning gives each time block a necessary contribution to the final output.
2
Contingency and prerequisite rules prevent a full meeting from being spent on missing inputs.