60-Second Meeting Brief
Turn meeting context into a focused brief with priorities, questions, and one overlooked insight.
Customise & copy
Add the context you have. The prompt updates as you work.
Choose the format that best describes the meeting.
List each attendee with their role or organization when relevant.
State the concrete outcome you want from the meeting.
Include the latest status, constraints, decisions, or risks.
Live prompt
4 fieldsPrepare a concise meeting brief for the next 60 seconds using the details below. Meeting type: Client meeting Attendees: {{attendee_list}} Meeting goal: {{meeting_goal}} Current project context: {{current_project_context}} Return only these sections: 1. Top 3 things to accomplish — make each specific to the goal, attendees, and context. 2. 2 key questions — make them useful for moving the meeting forward. 3. One surprise element to discuss — a non-obvious risk, opportunity, trade-off, or insight grounded in the context. Keep the entire response under 150 words. Do not ask follow-up questions, add greetings or filler, or invent facts. Make reasonable assumptions when needed.
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"meeting_goal": "Approve the launch date for our new inventory planning platform and align on the minimum viable feature set.",
"meeting_type": "Decision meeting",
"attendee_list": "Priya Shah — Chief Product Officer; Daniel Kim — Engineering Lead; Morgan Lee — Head of Sales",
"current_project_context": "The platform is ready for a pilot, but demand forecasting accuracy is below target and Sales wants a customer-facing demo next month."
}A small ritual that works
How to use it
- 01Choose the meeting type.
- 02List attendees and their roles or organizations.
- 03State the concrete meeting goal.
- 04Add the latest project status, constraints, decisions, or risks.
Why it works
The prompt turns four practical inputs into a tightly bounded meeting brief. It connects the three accomplishment points to the stated goal, attendees, and project context, then adds forward-moving questions and one context-grounded surprise element. The fixed section structure, no-filler instruction, and 150-word limit keep attention on decisions and discussion points rather than general meeting advice.
Where it fails
The brief becomes less reliable when the meeting goal or project context is vague, incomplete, or internally unclear. The instruction to make reasonable assumptions preserves momentum, but it also creates room for recommendations that reflect inferred priorities rather than confirmed facts. The format is also too narrow for meetings that require detailed agendas, background explanation, action registers, or formal documentation.
Customisation tips
Replace the 60-second framing or 150-word limit if the brief will support a longer preparation process. Add a section for decisions, owners, or next steps when accountability matters. Make the surprise element specifically about risks, opportunities, trade-offs, or stakeholder concerns if one category is more useful. Adjust the attendee input helper to request decision authority, priorities, or areas of concern.
Watch-outs
- Provide concrete context, including constraints, recent decisions, unresolved risks, and the desired outcome.
- List attendee roles or organizations so the brief can be tailored to the people involved.
- Treat assumed details as prompts for discussion rather than confirmed facts.
- The three-section format prioritizes immediate meeting focus over comprehensive preparation.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Related prompts
Want to make AI useful across your team? Explore Atul's training.