Meeting notes for consultants: a template and best practices
Last updated: July 2026
For a consultant, meeting notes are not admin overhead — they are the record that a decision was made, the proof of what was promised, and the thing a client re-reads before they pay an invoice. This is a practical template for client meeting notes plus the habits that make them worth keeping, and a note on how to produce them without transcribing an hour of audio by hand.
What good client notes actually capture
Vague notes are worse than none, because they invite disagreement later. The notes that hold up capture four things clearly: the decisions that were made (and by whom), the action items with an owner and a date against each one, the context a decision was made in so it still makes sense in three weeks, and the open questions that were not resolved. Everything else — the discussion, the tangents — is supporting detail. The test of a good note is simple: could someone who missed the meeting act on it without asking you what you meant?
A reusable template
A structure you can reuse for almost any client meeting:
- Meeting. Client, project, date, attendees.
- Context / purpose. One or two lines on why this meeting happened.
- Discussion. The key points raised, kept brief — bullets, not a transcript.
- Decisions. What was agreed, stated plainly, each on its own line.
- Action items. Task — owner — due date, one per line, for both sides.
- Risks / open questions. What is unresolved or could go wrong.
- Next steps. The next meeting or milestone and who owns it.
Separating decisions from discussion is the single most useful habit — it is the difference between a note you can point to and a wall of text you have to re-read.
Best practices that hold up
- Capture during, not after. Memory decays fast; notes written from a recording or live beat notes reconstructed the next morning.
- Assign every action an owner and a date. An action item without a name is a wish.
- Send the follow-up within a day. A short, clean recap while it is fresh sets the shared record — and quietly confirms scope.
- Keep client notes confidential. They are commercially sensitive; treat where they are stored as part of the job.
- Be consistent. The same template every time makes notes faster to write and far easier to search later.
From conversation to notes without retyping
The reason notes get skipped is the effort. That has changed: if the meeting is recorded and transcribed, a structured summary — decisions, action items and next steps in your template — can be generated from the transcript in seconds, leaving you to edit rather than author. The workflow is record → transcribe → summarise into a template → send the follow-up, and it turns note-taking from a chore into a quick review. It also means you were in the meeting instead of typing through it.
Keeping client notes confidential
Consultants sit on other people’s secrets, often under an NDA, so where the notes live matters as much as what they say. A transcript of a client strategy call sitting on a third-party server — retained until you delete it, occasionally usable to train a vendor’s model — is a real exposure. Keeping recording, transcription and notes on your own machine keeps a client’s confidential discussion out of someone else’s cloud. Sharing meeting summaries securely covers the other half — getting the recap to the client without over-sharing.
Doing it in folo
folo is built around exactly this loop for people on a Mac. It records and transcribes the call on-device, pulls out action items grouped by owner, and writes the summary into a template — it ships with General, 1:1, Standup and Sales/Customer formats, and you can build your own sections for the way you run client meetings. A one-click follow-up turns the decisions and tasks into an email or a message for the client, and by default none of it leaves your Mac. To set up your own template, see the summaries and templates manual.
Questions, answered
What should consultant meeting notes include?
Decisions (and who made them), action items with an owner and due date, the context behind each decision, and any open questions. Keep the discussion brief and separate it from the decisions.
What is a good meeting notes template?
Meeting details, context, a brief discussion summary, decisions, action items (task–owner–date), risks or open questions, and next steps. Reusing the same structure makes notes faster to write and easier to search.
How soon should I send meeting notes to a client?
Within a day, while it is fresh. A prompt, clean follow-up sets the shared record and quietly confirms scope and next steps.
How can I take meeting notes without writing everything down?
Record and transcribe the meeting, then generate a structured summary from the transcript into your template. You edit a draft rather than writing from scratch — and stay present in the meeting.