Every consultant has left a client meeting feeling energised — only to arrive at the next session to find nothing from the last one has moved. Not because anyone was negligent. Because the meeting notes lived in someone’s inbox, the action items were buried in a wall of text, and nobody was certain who owned what.
Structured meeting documentation fixes this. The Meeting Notes tool in The Consultant’s Playbook gives you a consistent format for capturing what happened, what was decided, and — critically — who does what next.
What Gets Captured
A professional meeting record is more than a transcript. The tool captures four distinct layers:
Meeting context — the name, date, location, and participants with their roles. This sounds administrative, but it matters. Six months into an engagement, when you need to establish when a decision was made and who was in the room, this metadata is the evidence.
General insights — the observations, tensions, and contextual information that emerged during the meeting but do not fit neatly into a decision or task. This is where you record the subtext: the CFO’s concern about timeline that was not formally raised, the cultural resistance a particular workstream is facing, the competitive context a stakeholder mentioned in passing. These insights inform your analysis even when they never appear in a formal deliverable.
Key outcomes — the decisions, agreements, and conclusions reached. These are the things the meeting actually produced. Keeping them distinct from general insights forces you to be clear about what was actually resolved versus what was merely discussed.
Action items — and here is where the tool does something most meeting note formats do not.
Splitting Action Items Between Two Columns
The Meeting Notes tool divides action items into two explicit lists: Our To-Dos and Client To-Dos.
This split is not cosmetic. It reflects how consulting engagements actually work.
When action items live in a single undifferentiated list, accountability blurs. The client assumes you are handling something. You assumed they were. The item falls through. The project slips.
By capturing your team’s commitments separately from the client’s, you create two things simultaneously: a task list for your own team and a polite but unambiguous record of what the client agreed to do. When you share the meeting notes after a session — and you should always share them — that two-column structure makes it immediately clear what each party is accountable for.
Each action item supports a due date and an optional note for additional context. The note field is particularly useful for items where the “what” is clear but the “how” needs clarification — a constraint to work within, a dependency to wait on, a person to consult first.
Completing Items Without Losing the Record
Checking off an action item does not delete it. The task gets a strikethrough and fades visually, but it stays in the record. This is intentional.
Completed items are evidence. In a follow-up meeting, you want to be able to show the client that four of the five items from last session are done. That visibility builds trust and keeps the engagement moving. It also protects you if there is ever a question about what was delivered and when.
Using Meeting Notes to Inform the Project
Meeting notes are most powerful when they feed back into the rest of your project work.
The general insights field is where you capture the raw material for your analysis. A comment a stakeholder made about a failing process, an off-hand remark about a competitor, a concern raised about implementation risk — record it here, even if you are not sure yet what to do with it. When you return to your SWOT or your risk register later, these observations are already waiting for you.
Key outcomes inform your project definition. If a steering committee meeting shifts the agreed scope, or a sponsor confirms a new constraint, that decision belongs in both the meeting notes and your Project Definition. The meeting is where decisions happen; the Project Definition is where they live permanently. Keeping both updated ensures the AI tools in The Consultant’s Playbook continue to work from an accurate picture of the engagement.
A Discipline, Not Just a Format
The biggest benefit of structured meeting notes is not the format itself — it is the discipline it imposes.
Filling in the key outcomes field forces you to distinguish decisions from discussions. Filling in the action item columns forces you to leave every meeting with explicit ownership. Filling in the general insights field forces you to process what you heard rather than letting it fade.
Do it during the meeting if you can. The tool is designed for real-time capture — you are filling in a structured form, not writing prose from scratch. If that is not practical, do it within an hour of the meeting ending, while the detail is still fresh.
The notes you write in the first ten minutes after a meeting are worth more than the notes you reconstruct from memory two days later. Use the tool to make that discipline easy.