Use this AI prompt to prepare for a meeting in 5 minutes
Why this prompt matters
Important meetings are often lost before they begin because people arrive with fragmented context, weak questions, and no clear plan for objections. A reusable prep prompt reduces that risk and helps teams make better decisions under time pressure.
What we use it for
Use this when you have a high-stakes meeting in the next few hours and need a fast, structured briefing from messy notes, email threads, CRM context, or internal documents.
Prompt
Role: Act as a strategic meeting advisor and executive briefing writer. Context: I have an upcoming [MEETING TYPE] on [DATE/TIME] with [ATTENDEES]. My role is [YOUR ROLE]. The main objective of the meeting is [PRIMARY GOAL]. Relevant background: [PASTE EMAIL THREADS, NOTES, CRM CONTEXT, DOC EXCERPTS, PRIOR CONVERSATIONS, OR INTERNAL NOTES HERE] Known constraints or sensitivities: [DEADLINES, POLITICAL ISSUES, CUSTOMER RISKS, BUDGET LIMITS, INTERNAL DISAGREEMENTS, ETC.] What I already know or suspect: [YOUR CURRENT READ OF THE PEOPLE, PROBLEM, AND STAKES] Task: Create a concise but high-value meeting briefing pack that helps me walk into this meeting fully prepared. Constraints: - Do not give generic meeting advice. - Base your analysis on the provided context and clearly label any assumption. - Prioritize the 20 percent of facts or risks most likely to influence the meeting outcome. - If important information is missing, list the missing items separately instead of inventing them. - Keep the tone professional, sharp, and realistic. - Optimize for someone who has less than 5 minutes to review before the meeting. Output Format: 1. Meeting objective in one sentence 2. Who is in the room and what each person likely cares about 3. Key context I must remember 4. Top 3 risks or objections likely to surface 5. Recommended talking points in priority order 6. 5 smart questions I should ask 7. Likely follow-up actions after the meeting 8. Missing information or assumptions to verify before the meeting 9. A 60-second verbal prep summary I can read right before joining
Result
Meeting objective in one sentence: Rebuild confidence with Northstar Retail, align on the delayed rollout plan, and leave the call with agreement on revised milestones and owners.
Who is in the room and what each person likely cares about: - Maya Chen, VP of Operations at Northstar Retail: Wants proof that the rollout delay will not disrupt store readiness for the July campaign. Likely sensitive to credibility and execution risk. - Daniel Ruiz, Northstar IT Director: Cares about system stability, integration timelines, and whether internal resources will be pulled into unexpected work. - Priya Malhotra, Account Executive on our side: Focused on protecting the renewal and reducing escalation. - Leo Grant, Implementation Lead on our side: Closest to the operational details and most likely to be asked for dates and technical commitments.
Key context I must remember: Northstar signed the expansion in March with an expectation of 120 stores live by June 20. Integration testing surfaced data-mapping issues in mid-April. We fixed the first issue, but a second issue slowed QA and pushed training into next week. The customer is frustrated because they were promised a cleaner rollout after last year’s smaller deployment. Internally, our strongest option is a phased go-live starting with 40 stores, then 80, then the full estate.
Top 3 risks or objections likely to surface: 1. Northstar may say our team overpromised and is now asking them to absorb the cost of our delivery miss. 2. They may push for a single hard launch date that our team cannot responsibly guarantee today. 3. They may interpret a phased rollout as a downgrade rather than a risk-control plan.
Recommended talking points in priority order: - Acknowledge the delay directly without defensive language. - Explain the root cause in operational terms, not engineering jargon. - Reframe the phased rollout as the safest path to July readiness rather than a retreat. - Offer concrete milestones, owners, and customer-visible checkpoints. - Confirm what support Northstar will receive during the first wave so they do not feel abandoned after the meeting.
5 smart questions I should ask: - Which July campaign milestones are truly fixed versus preferred? - Would a phased launch still work if the first 40 stores are the highest-priority locations? - What internal communications does Maya need before she can defend a revised plan? - Which integration dependencies on Northstar’s side remain unresolved today? - What would Northstar define as a successful recovery from this delay 30 days from now?
Likely follow-up actions after the meeting: - Send a revised timeline within 2 hours. - Confirm store-wave sequencing by Friday. - Schedule a technical checkpoint between Leo and Daniel. - Prepare customer-facing rollout communications for Maya’s approval.
Missing information or assumptions to verify before the meeting: - Assumption: Northstar can accept a phased rollout if July campaign stores are prioritized. - Missing: Updated QA completion date from the engineering team. - Missing: Whether customer success can provide extra onboarding support for wave one.
60-second verbal prep summary I can read right before joining: Go in calm and direct. Lead with ownership of the delay, then move quickly to the recovery plan. Maya needs confidence, Daniel needs operational clarity, and both need to feel we are controlling the risk instead of reacting to it. Do not promise a single-date rollout unless Leo confirms it. Push the phased plan as the fastest credible route to campaign readiness, and leave the meeting with named owners, milestone dates, and one clear definition of success for the next 30 days.
Most people do not struggle with meetings because they lack a calendar. They struggle because context is scattered across old emails, CRM notes, slide decks, Slack threads, and half-remembered conversations. By the time the meeting starts, everyone is reacting instead of walking in with a point of view.
This prompt is designed to fix that. Instead of asking an AI model for generic prep, it forces the model to work like a sharp chief of staff: gather the facts, identify missing context, surface likely tensions, and turn the chaos into a short, decision-ready briefing. The goal is not to produce a pretty summary. The goal is to help someone walk into an important meeting knowing what matters, what could go wrong, and what to say next.
What this prompt is for
This prompt works best when you have a high-stakes meeting but limited prep time. That could be a sales call with a new enterprise prospect, a one-on-one with your manager, a cross-functional launch review, an investor update, a renewal call with a frustrated customer, or a partnership meeting where you need to sound informed fast.
The pattern is simple: give the model the meeting context you already have, tell it what kind of meeting this is, and make it return a practical briefing instead of vague advice. That means the output should include the meeting objective, who matters in the room, what each person likely cares about, where tension may show up, which questions to ask, and what success looks like by the end of the call.
Why the structure matters
The prompt uses Role, Context, Task, Constraints, and Output Format on purpose. That structure helps the model avoid the biggest failure mode in meeting prep prompts: sounding polished while saying very little.
Role
The model is told to act like a strategic meeting advisor, not a generic assistant. That changes the tone of the output. You want judgment, prioritization, and realism, not a cheerful recap of the notes you already pasted in.
Context
The prompt asks for attendee names, goals, history, constraints, and source material. This matters because meeting prep is never one-size-fits-all. A product review, a difficult client conversation, and a hiring interview all need different framing. The more specific the context, the more specific the prep becomes.
Task
The task section pushes the model to do real work: produce a briefing doc, talking points, questions, risks, and recommended next steps. This is where the prompt moves from passive summary to active preparation.
Constraints
The constraints tell the model to avoid fluff, flag assumptions, and prioritize what is actionable. That matters because AI models love filling space. A good briefing should make you faster, not give you three pages of diplomatic filler five minutes before the meeting starts.
Output Format
The output format forces the model into a reusable template. That makes the result easier to scan under time pressure and easier to compare across repeated meetings. If you use this every week, consistency becomes part of the value.
Where this prompt is especially useful
This prompt is strongest in roles where meetings directly affect revenue, execution, or trust. Sales leaders can use it before late-stage calls. Founders can use it before investor or board meetings. Product managers can use it before roadmap debates. Agency teams can use it before client status calls that are drifting off track. Individual contributors can use it before one-on-ones where they need to raise a difficult issue clearly and calmly.
It is also useful when you are stepping into a meeting with partial context. Maybe a teammate hands you an account at the last minute. Maybe you were added to a call late. Maybe you have only ten minutes between back-to-back meetings. In those situations, the difference between generic prep and structured prep is not cosmetic. It changes whether you sound prepared or exposed.
How to get better results from it
Do not just paste the agenda and hope for the best. The better approach is to feed the model the raw materials you already have: the latest email thread, past meeting notes, a rough goal, known objections, internal concerns, and whatever success would mean from your side. If something is missing, say so. A strong model will often point out the gaps and tell you what to ask before the meeting starts.
You should also customize the tone of the output. For example, if the meeting is politically sensitive, ask for diplomatic phrasing and likely pushback. If the meeting is tactical, ask for a sharper action plan. If the meeting is exploratory, ask for strong discovery questions and signals to watch for.
The bigger lesson
The value of a good workplace prompt is not that it saves typing. It changes the quality of thinking you bring to recurring situations. Meeting prep is one of those cases where a reusable prompt can create compounding returns because the workflow happens constantly, the stakes are often high, and most people still handle it ad hoc.
That is why this prompt is worth saving. It turns messy context into a repeatable preparation system. Used well, it can help you ask better questions, avoid predictable mistakes, and show up sounding like the person who already did the hard thinking before the call began.