Template

A Meeting Notes Template for Consultants

Consulting notes need to track more than actions: who said what position, which hypotheses held, and what the recommendation depends on. This template does that.

Why consultants need a different template

A general meeting template records decisions and actions. Consulting adds three needs: understanding stakeholder positions (who wants what and why), tracking hypotheses as evidence arrives, and recording the assumptions a recommendation depends on. Without those, the final report cannot show why you recommended what you did.

The template

ENGAGEMENT MEETING LOG

Client / engagement: [name]        Meeting: [title]
Date: [date]                       Attendees: [names, roles]
Purpose: [one sentence]

WHAT WE LEARNED
- [Fact, with source: person or document]

STAKEHOLDER POSITIONS
| Person | Role | Position | Concern or motivation |
| [name] | [role] | [for / against / neutral on X] | [why] |

HYPOTHESES
| Hypothesis | Evidence for | Evidence against | Status (open / supported / rejected) |

DECISIONS (agreed)
- [Decision] (by: [name])

COMMITMENTS
- Ours: [action] by [date]
- Theirs: [action, e.g. data access] by [date]

ASSUMPTIONS WE ARE RELYING ON
- [Assumption] - to be confirmed by [name] before [date]

RISKS AND DEPENDENCIES
- [Risk]

DELIVERABLE IMPACT
[Which part of the final deliverable this changes]

NEXT MEETING / NEXT STEP
[Date and purpose]

How to use it well

  • Source everything you learn. "Operations says data access is probable" is different from "the data is available".
  • Record stakeholder positions neutrally. These notes may be seen by others. Write what was said, not what you think of the person.
  • Revisit hypotheses after each meeting. Updating status is the point of the table.
  • Track client commitments as carefully as your own. Data access and approvals often drive the schedule.
  • Flag assumptions loudly. If an assumption turns out wrong, you need to know which recommendations it touches.

Keeping the log findable

An engagement log is valuable at the end, when you need to remember why you reached a conclusion. Keep one entry per meeting, named consistently, and make them searchable. MeetMemo stores notes and transcripts on your device, keeps them searchable, and answers questions across meetings with source references, which helps when you ask "What did finance say about constraints?" See searchable meeting history. For general client calls use the client meeting notes template.

A note on confidentiality

Consulting notes are often sensitive. MeetMemo stores meeting content encrypted on your device, but running an AI action sends the relevant content to an AI service. Check your engagement terms first. See the Privacy Policy.

A filled-in entry

ENGAGEMENT MEETING LOG
Client / engagement: Harbor Logistics, process review
Meeting: Operations interview    Date: 14 Oct 2026
Attendees: Sam Okoye (Head of Operations), me
Purpose: Understand how orders move from warehouse to carrier.

WHAT WE LEARNED
- Manual re-keying between the warehouse system and the carrier portal (Sam Okoye)

STAKEHOLDER POSITIONS
| Sam Okoye | Head of Ops | Supports automation | Wants fewer late shipments |

HYPOTHESES
| Re-keying causes most late shipments | Sam says so | No data yet | Open |

COMMITMENTS
- Ours: draft process map by 21 Oct
- Theirs: share last quarter's shipping data by 18 Oct

ASSUMPTIONS WE ARE RELYING ON
- Data access is granted by 18 Oct (Sam: "probably") - confirm with Sam

NEXT STEP
Review data on 22 Oct

Variants for other session types

  • Stakeholder interviews. Focus on the stakeholder positions and quotes. Record exact words where they matter and mark them as opinion, not fact.
  • Workshops. Add a section for options generated and options selected, with the reasons.
  • Steering committee updates. Add decisions requested of the committee and decisions made, with who made them.
  • Hand-over sessions. Add what you are handing over, what remains open, and who owns it next.

Turning the log into a deliverable

When it is time to write the report, the log gives you the chain of evidence: what you learned, from whom, which hypotheses held, and which assumptions your recommendation rests on. If a client asks "why did you recommend this?", you can answer with the log instead of memory.

Frequently asked questions

Should I share these notes with the client?

Usually not as they are. They include stakeholder positions and hypotheses that are for your working use. Share decisions and next steps instead.

How long should an entry be?

One page. If it is longer, you are probably transcribing.

Can I use this with a recording?

Yes, with consent. The log is what you write after listening to what mattered. See the recording consent guide.

Related on MeetMemo

More to read

Be first to try MeetMemo

Join the early-access list and we will email you when the Android app is ready. No spam.