The Direct Answer: Ten minutes before any important meeting, run three AI passes: (1) summarize the email thread or document trail into a one-paragraph "state of play," (2) generate the three questions you are most likely to be asked, and (3) draft your opening update in two sentences. Paste sanitized text only — never client names or financials.
Who this is for: Analysts, consultants, and managers who attend 4+ meetings a day and routinely walk into at least one of them having skimmed nothing.
Skip this if: Your meetings are mostly informal team syncs with no stakes, or your company prohibits pasting any work text into external AI tools.
Note: AI pricing, plan names, and product features can change quickly. Re-check official pages before you pay for a tool or choose a plan.
The 4 PM Client Call You Forgot About
It is 3:45 PM. Your calendar reminder fires for a 4 PM call with a client stakeholder. The relevant context is buried across a 23-email thread, two attached decks, and a Teams channel you muted last week. You have 15 minutes, and reading everything would take 45.
This is the exact gap AI closes well: compressing a messy information trail into the three things you actually need — what happened, what they will ask, and what you will say. The workflow below takes 10 minutes once you have done it twice.
The 3-Pass Prep Workflow
Pass 1: The State of Play (4 minutes)
Copy the email thread or meeting-relevant document text. Strip out names, client identifiers, and numbers that matter (replace with [Client], [Project X], [the Q2 figure]). Then run this:
I have a meeting in 15 minutes. Below is the email thread / document trail leading up to it (names and figures sanitized). Summarize it as: 1. STATE OF PLAY — one paragraph: where things stand right now 2. OPEN ITEMS — bullet list of unresolved decisions or pending actions, with who owes what 3. LANDMINES — anything in this thread that suggests tension, a missed commitment, or an expectation gap I should be aware of Be blunt in section 3. Do not soften it. The thread: [PASTE SANITIZED TEXT HERE]
The "LANDMINES" section is the one that earns its keep. AI is surprisingly good at noticing that the client asked the same question twice without getting an answer — the kind of detail you miss when skimming at 3:50 PM.
Pass 2: The Questions You Will Be Asked (3 minutes)
Senior stakeholders rarely surprise you with topics. They surprise you with angles. This pass forces you to rehearse the uncomfortable ones before someone else asks them live:
Based on the situation I just shared, act as a sharp, slightly impatient senior stakeholder in this meeting. List the 3 questions you are most likely to ask me, ordered from most to least probable. For each one: - The question, phrased the way a senior person would actually ask it - What a weak answer sounds like - A one-line strong answer structure I can adapt Focus on questions about delays, ownership, and "what's the plan" — not technical detail.
Pass 3: Your Opening Two Sentences (3 minutes)
The first 30 seconds of your update sets how the room reads you. Most people improvise it and ramble. Ask for exactly two sentences:
Draft my opening update for this meeting in exactly two sentences. Sentence 1: current status, stated plainly (no "good progress" filler — say what is done and what is not). Sentence 2: the one decision or input I need from this group today. If I have not given you enough to identify a needed decision, tell me that instead of inventing one.
That last line matters. The most common AI failure in meeting prep is confident invention — it will happily fabricate a "decision you need" if you let it. Telling it to push back is the fix.
Three Rules That Keep This Safe
Rule 1: Sanitize before you paste
Same discipline as drafting performance reviews with AI: placeholders for names, clients, and sensitive figures. The AI does not need to know it is "Infosys" to tell you the thread has an unanswered escalation in it.
Rule 2: Long documents go through the PDF route
If the prep material is a 40-page deck or requirements document rather than an email thread, use the PDF Cruncher workflow first, then feed its summary into Pass 1 here. Do not paste 40 pages into a chat window and hope.
Rule 3: Internal meetings get the lightweight version
For a routine sync with your reporting manager, Pass 3 alone is enough — two sentences of status, one ask. Save the full three-pass treatment for client calls, steering committees, and any meeting where someone two levels above you is on the invite.
The Real World Story
The first time I used this workflow was for a client escalation call I had 20 minutes to prepare for — and the "landmines" pass caught the thing that saved the meeting.
The thread was 30+ emails deep and I had been cc'd on maybe half of it. Pass 1 surfaced that the client had asked for a revised timeline twice — and both times the reply had addressed everything except the timeline. Walking in, I opened with the timeline before they could raise it. The call that was scheduled as an escalation ended as a planning session.
I have run the three passes before every significant meeting since. The honest accounting: it does not make you smarter in the meeting, it just makes sure the smartest version of your preparation actually happens — even when the calendar gives you 15 minutes instead of an afternoon.