How to Take Client Meeting Notes Without a Recording Bot

A client asks for a meeting without a recording bot. Open a short notes template and agree on the outcome the call needs to produce. A written record can capture which version was approved, who owes the next decision, and when work can continue. Assign a note-taker when possible. If you are also leading, pause between topics to write the decisions and read them back.

Open a page with four places to write

Copy this before the call. Leave questions open until someone answers them. Give each decision or action an identifier so you can reference it later.

Client / project:
Date and time zone:
Attendees:
Decision or outcome needed:

Decisions
D1 | Decision and exact version or scope | Who confirmed it

Actions
A1 | Verb + deliverable | Owner | Due date and time zone | Evidence of completion

Open questions
Q1 | Question | Person to ask | When to check back | What it blocks

Recap
Send by:
Next checkpoint:

If a person suggests a date, write “proposed” beside it. When someone says “we’ll do it,” ask who will be the point person. Capture the answer in the same row. Mark a question as blocking only if another action depends on it.

Read back the handoff in the last three minutes

In this fictional example, a web agency meets with Brookline Books on November 9. The client approves the gift-card page layout v2. The marketing manager, Elena, will send final button copy by 3 p.m. Eastern on November 11. Agency designer Luis will update the staging page by noon Eastern on November 12, after he gets that copy. Whether the client needs a French version is still open. Elena agrees to ask operations on November 10. A Friday launch comes up as a possibility, with confirmation deferred until the staging review.

Read back the decisions in plain language. “Elena approved layout v2. Elena owns the final copy by Wednesday at 3 Eastern. Luis will update staging by Thursday at noon once he has it. French localization is open. We’ll confirm a launch date after staging review.” Let people correct dates or scope while everyone is still on the call.

Send a recap someone can scan

Subject: Brookline gift-card page | Nov 9 recap

Thanks for reviewing the gift-card page today.

Agreed
- Layout v2 is approved for the English staging page.

Next actions
- Elena sends final button copy by Nov 11 at 3 p.m. ET.
- Luis posts the updated staging preview by Nov 12 at noon ET, after receiving the copy.
- Elena checks with operations about French localization on Nov 10.

Open
- French localization scope.
- Launch date. We'll confirm it after staging review.

Please reply with any corrections or changes to those dates.

Keep internal estimates, sensitive notes, and unrelated discussion out of the client recap. Save the approved version and send corrections in the same thread so the team can find the latest decision.

Turn commitments into dated work

Use one task per action and link it back to the notes or recap. In a date-based planner like SelfManager.ai, put the task on its due date and use the relevant table notes or a task comment for context. If the due date changes, update the task and record the change in the recap thread. SelfManager.ai FAQ

For the weekly status update, report the approved layout, the staging date, and the two open decisions. If copy slips, state how it changes the staging plan. If you already have an approved transcript for another meeting, use this transcript-to-task review workflow.