The four-pass system for turning any meeting into a client-ready recap with Claude
What got decided, and what has to happen because of it. Most people lose track of the second one somewhere between hanging up and finally sitting down to write it up, usually an hour later, tired, guessing at half of it.
It's not really a note taking problem. It's a timing problem. By the time you get around to writing the recap, you've already forgotten the thing that mattered most.
Almost everyone who tries this makes the same mistake. They paste in their notes, ask for a clean summary, and get something that reads well and is occasionally, confidently, wrong. A "maybe Friday" becomes a hard deadline. A passing comment becomes a commitment. It reads clean, so you stop checking it, and that's exactly when it costs you.
The fix isn't a better single prompt. It's not trying to do extraction, fact checking and formatting in one pass, the same way you wouldn't write, edit and proofread a client email in one breath.
I run this as four short passes instead of one. I call it the Four-Pass Method, and the prompts for each pass are right after you unlock this guide below.
All four prompts, the meeting-type modules, the troubleshooting section and the full worked example. Free, drop your email below.
No spam.
Four short prompts, run one after another in the same chat. Each one has a single job, which is the whole reason it works better than asking for everything at once.
Each pass takes the previous one's output as its input. You're not retyping anything, you're just saying "next" and pasting the prompt.
Before anything gets summarized, pull the raw material out exactly as it appears. This is the pass everyone skips, and skipping it is where the invented deadlines come from.
You'll get something messier than a summary and that's the point, nothing has been quietly smoothed over yet.
This is the pass that actually earns the guide its name. Feed the raw pull back in and make Claude grade its own confidence before anything gets formatted.
Three tags, that's all you need:
Confirmed Inferred Unclear
They carry through into the final recap in Pass 3, which is what makes it trustworthy enough to send without a second read.
Only now, with everything checked, do you ask for the actual recap.
A recap that says "Friday (Inferred, said as 'maybe end of week')" is more useful than one that confidently says "Friday" and is wrong.
The recap from Pass 3 is the source of truth. Where it actually needs to live changes by situation, so reshape it with one more short prompt instead of writing it out by hand each time.
Add one of these as an extra line before Pass 3, depending on what kind of meeting it was.
Be strictest about anything involving price, scope or deadlines when you grade confidence. Clients remember exact numbers even when they were said casually.
Weight blockers over decisions. If someone mentions being stuck or waiting on something, treat it as an action item even without a stated deadline.
Add a fifth section called Next Step in the Pipeline, and list any objections raised as their own line under Open Questions.
Treat every number as Inferred unless it was repeated back and confirmed by both sides in the conversation itself.
Keep the Summary section factual and neutral. This recap may get read by someone in HR later, not just the two of you.
The Four-Pass Method catches most of this on its own. Worth knowing what it's catching.
"ok so jen said pricing by fri maybe, need to loop sam in, deck still not done, ask about the logo again, follow up thurs?"
Action items
Jen: send pricing Inferred
You: loop in Sam Confirmed
You: finish deck Confirmed
Open question
Logo status Unclear
The recap doesn't just look tidier. It surfaces the thing the raw notes buried, that "Friday" was never actually confirmed by anyone.
Retyping four prompts every time you start a chat is how people quietly stop doing this after a week. Don't.
Create one Claude Project called something like Meeting Recaps, and paste the four prompts in as project instructions or reference files. From then on, every new call only needs one thing pasted into a fresh chat inside that project, the raw notes. Claude already knows the Four-Pass Method because it lives in the project, not in your clipboard.
Ten minutes of setup, once. After that, every recap is a paste and a wait.
Not a party trick prompt, the actual four passes I run after every call that matters. If it saved you time, the best test is your very next one.
I write about things like this most weeks, mostly Claude, GPT and a handful of other tools used for actual work, not hype. If that's useful, come find me on LinkedIn.
Made with a little help from Vanpoint.
13 pages · first 3 free to read