Client recaps for consultants, without the evening write-up

The wrist matters more than it sounds. In a long session your phone ends up in a bag or face-down at the other end of the table. Your watch goes where you go, which includes the part of the site visit where the useful thing gets said. For multi-person sessions, Pastok separates speakers, so a workshop comes back as a conversation you can follow rather than one undifferentiated block of text.

Permission comes first, and not as a formality. Plenty of clients say no, and some engagements, government work especially, rule it out entirely. One line at the top of the session usually does it: "I'd like to capture this so the recap is accurate rather than from memory — nothing gets shared outside this engagement. Is that alright?" If the answer is no, take notes by hand. This workflow is for the conversations you're allowed to keep.

Synthesis in consulting is moving from "what I found" to "what it means for this client." A finding says what you learned, a recommendation says what they should do and under what conditions. That step was never the slow part. The slow part was rebuilding the evidence underneath it: which stakeholder said the throughput number, whether the sponsor called the date firm or aspirational, what the ops lead actually meant by "the current process works fine."

With the conversations captured, that evidence is there to be queried instead of remembered. The write-up turns into reviewing and correcting a draft rather than producing one from nothing, which is where most of the hours go. The same dated examples also make a communication self-evaluation evidence-based instead of a retrospective guess.

So the queries that earn their keep run across sessions, not within one:

Compare what the operations group and the finance group said about the go-live date across these three sessions. Where do they disagree, and quote each of them.

List every constraint raised so far that we haven't resolved, with who raised it and when.

What did the sponsor say about the November date, in their own words?

Keep the stakeholder groups separate when you ask. Speaker separation is what makes that possible in a workshop transcript, and it's also why "who said this" is worth checking before it becomes an owner in your action list.

For the format you produce every week, define it once as a Skill:

After a client session, produce a recap with the objective, confirmed decisions and their conditions, action items with owner and date, open questions, and anything that sounded like a scope change. Flag uncertainty instead of filling it in.

A Skill can run when you invoke it, on a schedule, or when Pastok detects a situation such as the end of a meeting. Output is Markdown or PDF. Two narrow Skills, discovery and status, beat one prompt trying to cover everything.

Check names, numbers, dates and units first. Then the things that read fine and still cause trouble: was that a decision or a suggestion, did the named owner actually agree, was the deadline firm or contingent on an approval, and did speaker separation put a statement with the wrong person. Diarization gives you structure, not certainty — interruptions, distance and room noise all affect attribution. The full transcript is on the web app at app.pastok.com, which is where you go to confirm anything you're about to act on.

• Open the Pastok web app

Watch for scope language in particular. Experienced consultants already treat a stated requirement or a requested change as something to confirm in writing the same day. Having the actual wording makes that email take two minutes instead of being a judgment call about what you think you heard.

Keep two documents while you're at it. The client recap holds agreed facts, decisions, owners and open questions. Your working note holds hypotheses, the tensions you've spotted and the things you're not ready to say out loud yet. They come out of the same tool in the same prose, which is exactly how the wrong one gets sent.

• Prepare for the next client meeting in 90 seconds