A client meeting can be productive while still leaving the project in a muddle afterwards. Participants may remember different conclusions, actions can disappear inside pages of notes, and an important qualification can be lost once the conversation moves back to email. For a small professional-services firm, the most useful meeting summary is not a transcript. It is a controlled working record of what changed because the meeting happened.
Start with the outcomes rather than the chronology
A minute-by-minute account forces readers to reconstruct the important points themselves. Lead instead with the decisions, instructions, actions and unresolved questions that affect the engagement. Supporting discussion can be noted where it explains an outcome, but it should not bury the outcome.
Distinguish a decision from a point discussed
Meetings often explore several possible approaches before settling on one, or before deciding that more information is required. The summary should not make every suggestion look agreed. Use clear wording to separate decisions, proposals, questions and matters deliberately left open.
Make actions complete enough to execute
An action should normally show what needs to happen and who is expected to coordinate it. Add timing or a dependency where that genuinely matters. Vague notes such as client to review or team to consider create another interpretation exercise instead of a useful next step.
Capture changes to the working position
If the meeting changes scope, priorities, assumptions, deliverables or earlier instructions, say so explicitly. Link the change to the firm's relevant working records rather than leaving colleagues to discover later that an old brief or action list is no longer current.
Keep unresolved questions visible
A question that cannot be answered in the meeting should not disappear from the summary. Record what remains uncertain, who will obtain the missing information and whether other work can continue in the meantime. This makes uncertainty manageable instead of allowing it to become an accidental assumption.
Use proportionate detail for sensitive matters
Record enough information for the engagement to progress, while following the firm's normal controls for confidential or sensitive material. A meeting summary does not need to duplicate every document or piece of background information discussed if those records are already held appropriately elsewhere.
Circulate while correction is still practical
A summary is most useful when participants can identify a misunderstanding before the team has acted on it. Where confirmation is appropriate, make clear which points require it rather than treating silence as universal approval. Internally, the team should also update its action, instruction and decision records so the summary becomes part of the working process rather than an isolated email.