Monday, 9:30am. The client calls back asking what was decided during last week's kick-off. Nobody on the team can find the file. The project manager digs through emails, then Notion, then a shared Google Doc with a dead link. Twenty minutes gone. This drives me crazy, because it's a structural problem that most agencies have never actually fixed.
Why most meeting notes are completely useless
Meeting minutes are among the most produced and least read deliverables in the service industry. The reason is simple: they're written to prove work happened, not to be useful. The result is 800-word prose blocks with no decided actions, no named owner, no date. A month later, everyone vaguely remembers 'talking about that', but nobody knows what was actually decided.
We lost a 40k annual client because a dispute over a delivered feature traced back to a scoping meeting that nobody had documented. Since then, every meeting has minutes sent within two hours. -- Production Director, e-commerce agency, Lyon.
The format that actually works: DACI + indexed decisions
Forget narrative minutes. What works is a hybrid format combining the DACI framework (Driver, Approver, Contributor, Informed) with a numbered decision log. Every meeting produces two distinct artefacts: a short context summary (5 lines max) and a numbered list of decisions and actions with an owner and deadline.
Numbering matters more than you think. When you can write in an email 'as decided in MOM-2024-047, point 3', the conversation shifts from a battle of memories to a factual reference. Agencies that do this consistently see measurable drops in client back-and-forth. One agency I worked with went from 4.2 average revision rounds per deliverable to 2.7 in three months, purely from this discipline.
The 5 blocks of effective meeting minutes
- Context (2-3 lines): topic, attendees, date, actual duration
- Decisions made: numbered, stated as positive affirmations ('Budget is set at X', not 'We discussed the budget')
- Actions (TODOs): 1 owner per action, precise deadline, no 'ASAP'
- Open points: what was NOT resolved, with a next review date
- Next meeting: date, draft agenda, required attendees
The two-hour rule (and why nobody follows it)
Minutes must go out within two hours of the meeting. Not the next day. Within two hours. After that, participants' memories have already started reconstructing events through their own biases. You're no longer sending minutes, you're sending an interpretation.
The real solution isn't writing after, it's writing during. Not exhaustive note-taking, but a shared live doc (Notion, Google Doc, whatever) where the facilitator checks off decisions in real time. The minutes are 80% done when the meeting ends. The rest is ten minutes of formatting.
Automate without losing the human touch
Transcription tools like Otter.ai, Fireflies or Krisp are useful but often misused. People hit record, hope the AI will summarise, and end up with a wall of verbatim text including every 'uh', every side comment and every end-of-call joke. That's not minutes, that's a transcript. Smart use: let the tool transcribe, use the auto-summary as a starting point, then apply human editorial judgment. You save 15 minutes on drafting and keep the quality. Clynt lets you attach these actions directly to your projects so nothing floats loose in email threads.
Client minutes vs internal minutes: two different logics
A classic mistake is sending clients the same minutes as the internal version. Client-facing minutes serve an implicit contractual function. They document what was validated, what was requested, what was refused. They need a 'tacit approval' clause: 'Unless you raise an objection within 48 hours, these decisions are considered approved.' Internal minutes can be raw and direct. Mixing the two either exposes internal tensions to the client or produces something too soft to be legally useful.
FAQ
What is the ideal length for meeting minutes?
One page, rarely two. If you go over two pages, you've written a report, not minutes. The goal is for an absent team member to be fully up to speed in two minutes of reading.
Should you ask the client to validate the minutes before sending?
No, and this is a common trap. Send them, give the client 48 hours to contest. Waiting for their approval before sending removes the time-stamped traceability advantage and implicitly gives them the right to rewrite history.
How do you handle informal meetings without overcomplicating things?
For exchanges under 15 minutes, a structured three-line Slack message or email (decision, action, deadline) is enough. No need for a full template. The important thing is that the decision is written down somewhere and referenceable.
Do meeting minutes have legal value in a client dispute?
Yes, under certain conditions. They must have been sent by email (with a timestamp), not contested within a reasonable timeframe, and worded with sufficient precision. They don't replace a formal contract amendment for major scope changes, but they form a solid body of evidence.